WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Naming conventions for brokers and associated resources

Establish a naming convention for all the WebSphere® Message Broker resources in your broker environment to ensure that names are unique, and that users creating new resources can be confident of not introducing duplication or confusion.

Consider the names that you use for your brokers and resources:

Brokers

When you create a broker, give it a name that is unique within your broker environment. You must use the same name for that broker when you create it on the system in which it is installed, using the command mqsicreatebroker. Broker names are case sensitive except on Windows platforms.

Execution groups

Each execution group name must be unique within a broker.

Message flows and message processing nodes

Each message processing node must be unique within the message flow it is assigned to. For example, if you include two MQOutput nodes in a single message flow, provide a unique name for each one.

Message flow names must be unique within the broker. All references to that name are always to the same message flow. If you assign the same message flow to more than one broker, you must ensure that you maintain unique message flow names across those brokers.

Message sets and messages

Each message name must be unique within the message set to which it belongs.

Message set names must be unique within the broker. All references to that name are always to the same message set. If you assign the same message set to more than one broker, you must ensure that you maintain unique message set names across those brokers.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:58


Reference topicReference topic | Version 8.0.0.7 | ae19580_