Naming conventions for integration nodes and associated resources
Establish a naming convention for all the IBM® App Connect Enterprise resources in your integration node environment to ensure that names are unique, and that users that create new resources can be confident of not introducing duplication or confusion.
Consider the names that you use for your integration nodes and resources:
- Integration nodes
When you create an integration node, give it a name that is unique within your integration node environment. You must use the same name for that integration node when you create it on the system in which it is installed, by using the command mqsicreatebroker. Integration node names are case-sensitive, except on Windows platforms.
- Databases
-
Ensure that the databases that you use for application data, which are accessed through your deployed message flows, are uniquely named throughout your network, so that confusion and errors are avoided by all your users.
- Integration servers
Each integration server name must be unique within an integration node.
- Message flows and message processing nodes
Each message processing node must be unique within the message flow it is assigned to. Nodes within the same message flow must not share the same name, even if they are of different types. 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 integration node. All references to that name are always to the same message flow. If you assign the same message flow to more than one integration node, you must ensure that you maintain unique message flow names across those integration nodes.
- 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 integration node. All references to that name are always to the same message set. If you assign the same message set to more than one integration node, you must ensure that you maintain unique message set names across those integration nodes.
- IBM MQ objects
-
If you are using IBM MQ services and objects with your IBM App Connect Enterprise resources, you must consider what conventions to adopt for IBM MQ object names. If you already have an IBM MQ naming convention, use a compatible extension of this convention for IBM App Connect Enterprise resources.
Ensure that every queue manager name is unique within your network of interconnected queue managers, even if some queue managers are not in your IBM App Connect Enterprise network. Unique naming ensures that each queue manager can unambiguously identify the target queue manager that a message must be sent to, and that IBM App Connect Enterprise applications can also interact with IBM MQ applications.
IBM MQ supports a number of objects that are defined to queue managers. These objects (queues, channels, and processes) also have naming conventions and restrictions. For more information about IBM MQ naming conventions, see the topic Naming IBM MQ objects in the IBM MQ product documentation.