Adding New Domain to an Existing Enterprise

Procedure

  1. Navigate to the $MQ_HOME/bin/migration directory.
  2. Update addNewRules.xml file with the list of rule domains that need to be inserted. (See $MQ_HOME/config/security/defaultdata.xml for sample entries.)
    • ‘rulemetamodel’ is the same as the name of the domain definition file under $MQ_HOME/config/rules.

      For example, $MQ_HOME/config/rules/NewProductIntroductionEdit.xml.

    • ‘active’ is set to ‘Y.’
    • ‘description’ is description of the rule domain.
    • ‘name’ is same as the ‘RulesetName’ attribute in the domain definition file.
    • ‘type’ is ‘BUSINESSPROCESS’.
  3. Update orglist.txt. Enter the list of organization IDs to which you want to add the domains (the rule domains listed in the rulelist.xml file).
  4. Create a new rule file in $MQ_HOME/config/rules by running the following command:

    ./MigrateRules.sh -addNewRules

    In case of errors or warnings, you can correct them and try again as the script can be re-run without generating duplicates. 

    <?xml version="1.0" encoding="utf-8" ?>
- <mlXML>
- <mq_default table="rulemetamodel">
- <default_row>
  <rulemetamodel>CustomProtocol123</rulemetamodel>
  <active>Y</active>
  <memberid id="memberid" />
  <description>Rulebase to be used for Custom Protocol123.</description>
  <name>Custom Protocol 123</name>
  <type>BUSINESSPROCESS</type>
  <restrictto>3</restrictto>
  <orgid id="orgid" />
  </default_row>
  </mq_default>
- <mq_default table="rulemodel">
- <default_row>
  <rulemetamodel>Custom Protocol123</rulemetamodel>
  <description>Default System Template123.</description>
  <memberid id="memberid" />
  <name>Default</name>
  <orgid id="orgid" />
  </default_row>
  </mq_default>
  </mlXML>