The Create RemoveSXP for Non-op Items transformation generates an SXP message that,
if deployed, will delete certain items.
The transformation is used as part of the process of resetting
configuration to a baseline. It is designed for power users
(alternatively, you can use XoomResetHelper.cmd to
create the same SXP file). The Create RemoveSXP for Non-op Items must be executed
from the command line using Xoom Processor. It is best explained by example.
In the following example we have two XoomXML files called current.xml
and baseline.xml. current.xml represents the
configuration on the local server localhost.
We want to remove from this configuration all items that are not
in the baseline configuration, as represented by baseline.xml.
- At a command prompt type: xp current.xml -
baseline.xml # CreateRemoveSXPForNonOpItems.xsl sxp.xml
This command first calculates the
relative complement of
baseline.xml in
current.xml. The result of this operation
contains all
items that are either different between the two
configurations or only exist in
current.xml.
Items
that are different will be decorated with an attribute
op="modified".
Items that only exist
in
current.xml remain undecorated, and hence are the "non-op items" of
the transformation's title.
Next, the result of the relative complement
operation is transformed by CreateRemoveSXPForNonOpItems.xsl into
an SXP that will, if deployed, remove the non-op items. The SXP is
finally saved as sxp.xml
- When you are sure you ready to deploy the changes, type the following command:
xp sxp.xml localhost::SendSxp
SxpResponse.xml
This command takes the SXP message saved in
sxp.xml, and sends it to
the server
localhost. All
items that are
in
current.xml but not in
baseline.xml will be deleted from
configuration on
localhost.
Note: The
exception to this is
Scheme changes which cannot be performed using
SXP messages.
The SXP response from the server is saved in the file
SxpResponse.xml.
