Assignments configuration data in an export file

This topic describes how to find the assignments configuration data in the XML file that is generated when you export everything in a Version 2.1 Control Center workspace by clicking File > Export All in Workspace. Specifically, the topic tells you how to find the following configuration data for each broker in the broker domain:
Here is an example of an export file. Only the beginning of the file is shown.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE XMI SYSTEM "mqsi.dtd">
<XMI xmi.version="1.0">
  <XMI.header>
    <XMI.documentation>
      <XMI.owner>name</XMI.owner>
Broker/a3916f02-f500-0000-0080-8818935dcec8
ExecutionGroup/23bd6f02-f500-0000-0080-8818935dcec8
MessageProcessingNodeType/24c55cb6-ea00-0000-0080-c5b38dd899ad
MessageProcessingNodeType/7e8b6bb6-ea00-0000-0080-c5b38dd899ad
MessageProcessingNodeType/c0656ab6-ea00-0000-0080-c5b38dd899ad
MessageProcessingNodeType/575960b6-ea00-0000-0080-c5b38dd899ad
TopicRoot/TopicRoot
PubSubTopology/PubSubTopology
MessageProcessingNodeType/2f11692e-e900-0000-0080-c5b38dd899ad
MessageProcessingNodeType/8322692e-e900-0000-0080-c5b38dd899ad
MessageProcessingNodeType/4e2f692e-e900-0000-0080-c5b38dd899ad
MessageProcessingNodeType/ff3c692e-e900-0000-0080-c5b38dd899ad
MessageProcessingNodeType/fba95b0e-ef00-0000-0080-aed9bbfe32dc
MessageProcessingNodeType/fc149e14-ef00-0000-0080-aed9bbfe32dc
MessageProcessingNodeType/857e100f-ef00-0000-0080-aed9bbfe32dc
    </XMI.documentation>
  </XMI.header>
  <XMI.content>
    <Broker icon="images/Broker.gif" creator="" version="" collectionPath=""
          versionTimestamp="" longDescription="" status="" versionCreator=""
          creationTimestamp="" shortDescription=""
          xmi.uuid="a3916f02-f500-0000-0080-8818935dcec8"
          xmi.id="a3916f02-f500-0000-0080-8818935dcec8" xmi.label="fred_tp">
      <Broker_queueManager value="ANAME" encoded="false"
            xmi.label="queueManager" type="String" valueMandatory="true"/>
      <AssignedMsgProject icon="images/MRProject.gif" collectionPath="MRM"
            status="" xmi.label="MQSISTR_MRM2">
        <MRProjectRef icon="images/MRProject.gif" xml:link="simple"
              xmi.label="MRProject" type="MRProject" refType="MRProject"
              title="MQSISTR_MRM2"
              href="MRM/MRProject/71bb0097-e700-0000-0080-abda7687be69"/>
      </AssignedMsgProject>
      <ExecutionGroupRef icon="images/ExecutionGroup.gif" xml:link="simple"
            xmi.label="ExecutionGroup" type="ExecutionGroup"
            refType="ExecutionGroup"
            href="ExecutionGroup/23bd6f02-f500-0000-0080-8818935dcec8"
            title="default"/>
    </Broker>
    <ExecutionGroup icon="images/ExecutionGroup.gif" creator="" version=""
          collectionPath="" versionTimestamp="" longDescription="" status=""
          versionCreator="" creationTimestamp="" shortDescription=""
          xmi.uuid="23bd6f02-f500-0000-0080-8818935dcec8"
          xmi.id="23bd6f02-f500-0000-0080-8818935dcec8" xmi.label="default">
      <AssignedMessageFlow icon="images/MessageProcessingNodeType.gif" status=""
            xmi.label="mqsistrmrmswiftflow">
        <AssignedMessageFlow_additionalInstances value="3" encoded="false"
              xmi.label="additionalInstances" type="Integer"
              valueMandatory="false"/>
        <AssignedMessageFlow_commitCount value="5" encoded="false"
              xmi.label="commitCount" type="Integer" valueMandatory="false"/>
        <AssignedMessageFlow_commitInterval value="1" encoded="false"
              xmi.label="commitInterval" type="Integer" valueMandatory="false"/>
        <AssignedMessageFlow_coordinatedTransaction value="no" encoded="false"
              xmi.label="coordinatedTransaction" type="yes_no"
              valueMandatory="false"/>
        <MessageProcessingNodeTypeRef icon="images/MessageProcessingNodeType.gif"
              xml:link="simple" xmi.label="MessageProcessingNodeType"
              type="MessageProcessingNodeType" refType="MessageProcessingNodeType"
              href="MessageProcessingNodeType/24c55cb6-ea00-0000-0080-c5b38dd899ad"
              title="mqsistrmrmswiftflow"/>
      </AssignedMessageFlow>
    </ExecutionGroup>
    ...
  </XMI.content>
</XMI>

The following sections describe how to find the assignments configuration data in an export file.

The name of the broker

For each broker in the broker domain, there is a Broker element within the XMI.content element. The name of the broker is the value of the Broker element's xmi.label attribute.

In the example, there is only one broker. The name of the broker is fred_tp.

The name of each message set that is assigned to the broker

For each message set that is assigned to a broker, there is an AssignedMsgProject element within the Broker element. The name of the message set is the value of the AssignedMsgProject element's xmi.label attribute.

In the example, only one message set is assigned to the broker fred_tp. The name of the message set is MQSISTR_MRM2.

The name of each execution group within the broker

For each execution group within a broker, there is an ExecutionGroupRef element within the Broker element. The name of the execution group is the value of the ExecutionGroupRef element's title.

In the example, the broker fred_tp has only one execution group, which is the default execution group.

For each execution group in the broker domain, there is an ExecutionGroup element within the XMI.content element. You can determine the broker to which an execution group belongs by examining the value of the ExecutionGroup element's xmi.uuid attribute. This value forms part of the value of the href attribute on the Broker element's corresponding ExecutionGroupRef element.

In the example, there is only one execution group in the broker domain, the default execution group for the broker fred_tp. The value of the xmi.uuid attribute on the ExecutionGroup element is 23bd6f02-f500-0000-0080-8818935dcec8, and this forms part of the value of the ExecutionGroupRef element's href attribute for the broker fred_tp.

The name of each message flow that is assigned to each execution group

For each message flow that is assigned to an execution group, there is an AssignedMessageFlow element within the ExecutionGroup element. The name of the message flow is the value of the AssignedMessageFlow element's xmi.label attribute. In the example, only one message flow is assigned to the default execution group for the broker fred_tp. The name of the message flow is mqsistrmrmswiftflow.

The properties of each message flow

For each property of an assigned message flow, there is a corresponding element within the AssignedMessageFlow element. The following table lists each property and its corresponding tag:
Property of an assigned message flow Corresponding tag
Additional instances <AssignedMessageFlow_additionalInstances>
Commit count <AssignedMessageFlow_commitCount>
Commit interval <AssignedMessageFlow_commitInterval>
Coordinated transaction <AssignedMessageFlow_coordinatedTransaction>
The value of a property is the value of the corresponding element's value attribute.
For example, the following table displays the properties of the message flow mqsistrmrmswiftflow that is assigned to the default execution group within broker fred_tp:
Property Value
Additional instances 3
Commit count 5
Commit interval 1
Coordinated transaction no