In Xoom Processor, functionality is accessed by writing command lines. Xoom Processor utilises its own expression language. Here, we provide an overview of this language, in prose and using a railroad diagram.
The Xoom Processor command is xp.exe. The command takes a number of global options that modify and control its behaviour.
Each command line requires a source document, which can be: a subset of live configuration, retrieved via a named query; a previously saved XML file; or a Xoom folder. Thereafter a command line consists of a sequence of arguments. As many arguments as are required can be sequenced together.
The XML document at the current state of the sequence is called the buffer. The buffer is originally populated from the source. The buffer is fed into each argument, and its contents replaced with the argument's results. Thus, the results of each argument are fed into the next argument.
If you need to operate upon the same document multiple times in the same command line, such as to deploy a specific configuration patch to more than one Xoom server, you need to use subsequences.
- Saved as a file, or a Xoom folder with a file-per-item structure.
- Output to the console.
- Deployed to a live server.
- Transformed in some way.
- Used as the input for a Xoom custom command.
Command ::= 'xp' Options Source ( Subsequence | Operation | XmlFormat )*
