Guidelines for using patterns
Patterns identify the types of objects that can be exported and imported, and you can list multiple patterns within one export or import command. If you want to export many or most of the patterns, create a text file that includes them and specify the text file with the [option_file] parameter, which ensures that you do not skip or duplicate any patterns.
- If you do not specify any patterns, all patterns are exported or imported.
- Some patterns contain objects that cannot be exported on their own. For instance, the physical view pattern contains any reports and charts associated with that view. These are stored and imported with the physical view. For TrueSight Middleware and Transaction Monitor, the profile pattern contains all the models, activities, and message formats associated with that profile.
- When you are importing, you can select to import only some objects by specifying the pattern.
For example, if you exported an entire environment, but only want to import the history information, you can set your pattern to only import history rules and history templates.
- For each pattern you specify, you must also specify a regular expression. If you want to export or import all of a pattern, specify the generic wildcard ".*". If you want a subset of the pattern, use a regular expression.
- For history rules, the first part of the regular expression describes the instance, or location, of the object. The second part of the regular expression describes the object type.
--History-Rule "LONDON!LONDON!TORONTO:ComMQSoftwareWebSphereMQLocalQueue"This example exports all history rules on the LONDON system, the LONDON queue manager, and the TORONTO queue. The objects come from a WebSphere MQ local queue. You can insert a regular expression at any point in the pattern.