The element <XoomQueries> forms the second part of the configuration
file. It contains the named queries that will be sent to specific Xoom servers,
determines how the configuration will be transformed, and specifies
where the results should be stored.
Each
<XoomQuery> contains the following elements:
- <Source>: specifies the source from which
configuration will be retrieved. This uses the same grammar as when specifying a source in Xoom Processor. The
source can be a live Xoom server or a previously saved file. If you specify <Source> you do not need to specify <HostName> and <GetQuery>.
- <HostName>: the host name of the Xoom server to which the
query will be addressed.
- <GetQuery>: the named query that determines the
subsets of configuration to be retrieved. Choose an appropriate
named query from those supplied with Xoom.
- <Transform>: the name of the XSLT file that will
transform the result of the query once it has been retrieved. The
default file RemoveTransactionalInformation.xsl removes
transactional information, that is, dynamic data (as opposed to
static data. Generally speaking, transactional information is not helpful when
comparing the state of configuration through time, but if you do wish to include
it, simply remove the <transform> element.
Alternatively, replace it with the name of another Xoom report as required.
- <Path>: the full path (including file name) where the
final file will be stored. This path should typically be in the correct part of the
repository/ working copy such that it can be versioned. You can specify that
configuration be saved as a
Xoom folder, with a file-per-item
structure.
<XoomQuery>
<Source>[xoom-server?localhost]:[query-name?DEFAULT] | repo-relative\file\path.xml</Source>
<HostName>xoom-server</HostName>
<GetQuery>query-name</GetQuery>
<Transform>xp.exe-relative\transformation\path.xsl</Transform>
<Transform>another\transformation.xsl</Transform>
<Transform>Reports\RemoveTransactionalInformation.xsl</Transform>
<Path>configuration\path\file.xml | configuration\path\per-item\</Path>
</XoomQuery>
<XoomQueries> can contain any number of
<XoomQuery> elements. Use more than one when you want to:
- Version configuration for a number of environments from a single
Xoom client machine.
- Send different kinds of queries to the same Xoom server. You could, for
example, retrieve both configuration and information on the Service Optimization
files you have installed.
- Version a number of reports. Rather than retrieving configuration
afresh with every <XoomQuery> element, which places
unnecessary load on your server, we recommend you retrieve
configuration the once, and save it, in the first <XoomQuery> element, and then transform and save that file in
further <XoomQuery> elements, one per report. See the
following example.
- Version, say, just a single item. In the first <XoomQuery> element, retrieve configuration and save it as
a Xoom folder, outside the repo. In the second <XoomQuery> element, use the <Source> element
to specify the item you want to version, and the path to the repo in the <Path> element.