Zip files used during imports and exports of the environment

The stage between importing and exporting TrueSight Middleware and Transaction Monitor objects is a zip file or files. These files can be stored as a backup for your TrueSight Middleware and Transaction Monitor environment, or imported into a new services system or systems as part of a migration plan

You can export an entire environment to one zip file. Each command line allows you to specify one zip file. If you are using a batch file, you can specify a zip file for each command in the batch file.

A zip file created by mqsexport contains an XML file that contains all the information for the exported objects.

Each object has a different XML format. If you have one zip file for multiple types of objects, then objects of the same type are grouped together within the zip file.

The following is an example of an event rule described in XML. This particular event rule is automatically generated from an event template. Note the following in relation to the example:

  • The name of the event rule is "AAA_QueueFull10869779143343"
  • The action pipeline is of the e-mail action type.
  • The rule is associated with the template named AAA_QueueFull.
  • The rule is triggered when the queueFull trigger is fulfilled.
  • The rule gets its input from a local queue called PARIS on the LONDON queue manager and the LONDON system.

To determine an object name so that you can use regular expressions to filter it, use the raw output in the command window after you run the mqsexport command.

EXAMPLE: Sample event rule described in XML 

PipelineURL="events/pipelines/e-mail ACTION.xml"
InputName="Local Queue"
NodeName="Local Queue">
<TopicPath InstPath="LONDON!LONDON!PARIS" TypePath="ComMQSoftwareNetworkHost!ComMQSoftwareWebSphereMQ QueueManager!ComMQSoftwareWebSphereMQLocalQueue" />
NodeName="nid167840573350700148" />

Was this page helpful? Yes No Submitting... Thank you