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:
  • The name of the broker
  • The name of each message set that is assigned to the broker
  • The name of each execution group within the broker
  • For each execution group within the broker, the name of each message flow that is assigned to the execution group
  • For each message flow assigned to an execution group, the following properties:
    • Additional instances
    • Commit count
    • Commit interval
    • Coordinated transaction
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>paton</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="APATON" 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>
You can find the assignments configuration data in an export file as follows:
  • For each broker in the broker domain, there is a section that starts with a <Broker> tag and ends with a </Broker> tag. This section is nested within the <XMI.content> and </XMI.content> tags. The name of the broker is the value of the xmi.label attribute on the <Broker> tag.

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

  • For each message set assigned to a broker, there is a section that starts with an <AssignedMsgProject> tag and ends with a </AssignedMsgProject> tag. This section is nested within the <Broker> and </Broker> tags for the broker. The name of the message set is the value of the xmi.label attribute on the <AssignedMsgProject> tag.

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

  • For each execution group within a broker, there is an <ExecutionGroupRef> tag. This tag is nested within the <Broker> and </Broker> tags for the broker. The name of the execution group is the value of the title attribute on the <ExecutionGroupRef> tag.

    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 a section that starts with an <ExecutionGroup> tag and ends with a </ExecutionGroup> tag. This section is nested within the <XMI.content> and </XMI.content> tags.

    You can determine the broker to which an execution group belongs by examining the value of the xmi.uuid attribute on the <ExecutionGroup> tag. This value forms part of the value of the href attribute on the corresponding <ExecutionGroupRef> tag for the broker.

    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> tag is 23bd6f02-f500-0000-0080-8818935dcec8, and this forms part of the value of the href attribute on the <ExecutionGroupRef> tag for the broker fred_tp.

  • For each message flow assigned to an execution group, there is a section that starts with the <AssignedMessageFlow> tag and ends with the </AssignedMessageFlow> tag. This section is nested within the <ExecutionGroup> and </ExecutionGroup> tags for the execution group. The name of the message flow is the value of the xmi.label attribute on the <AssignedMessageFlow> tag.

    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.

  • For each property of an assigned message flow, there is a corresponding tag. This tag is nested within the<AssignedMessageFlow> and </AssignedMessageFlow> tags for the assigned message flow. 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 value attribute on the corresponding tag.
    For example, the following table displays the properties of the message flow mqsistrmrmswiftflow assigned to the default execution group within broker fred_tp:
    Property Value
    Additional instances 3
    Commit count 5
    Commit interval 1
    Coordinated transaction no

Related tasks
Migrating from WebSphere MQ Integrator Broker Version 2.1 to WebSphere Business Integration Message Broker Version 5.0