Generating the base transaction pathway

Generating a transaction pathway creates a snapshot of the configuration and creates objects used internally for monitoring. For example, generation associates configured event and history templates. The base transaction pathway must pass validation at the time you generate. Generation of the base transaction pathway creates a generated transaction pathway model instance. In the BTM Model list, this instance is designated by an i in the modified column. The instance also has a version which is appended to the name of the model.

You can generate any number of generated transaction pathway model instances but you only deploy one and that is usually the last generated instance. Generally you might keep older generated model instances for access to historical data. Afterwards they should be removed to reduce overhead.

Some information in the generated instance can be altered. Only items that allow the model to remain valid and do not require a deployment can be changed. These changes take effect at the time the workspace is committed. You cannot copy, promote to another profile or export, using the mqsexport command line tool, a generated instance. You can promote changes to a generated instance back to the base transaction pathway if needed. 

Once you have generated one or more transaction pathways, you can deploy the configurations to begin monitoring. See Deploying BTM configurations.

A view for the generated transaction pathway instance is created in the logical tree. See Working with transaction pathway views for additional details.