Characters allowed in object names

When you name objects such as integration nodes, integration servers, and message identifiers, you can use uppercase alphabetic characters (A-Z), lowercase alphabetic characters (a-z), and numeric characters (0-9). A limited number of special characters might also be supported, depending on your operating system and your version of IBM App Connect Enterprise.

If you expect to trace the operation of an integration server, restrict the name of the integration server to include only the valid alphabetic and numeric characters listed. The trace commands do not support the use of special characters for an integration server name.

If you intend to use IBM MQ File Transfer Edition for managed file transfers, see Preparing the environment for IBM MQ File Transfer Edition nodes for information about naming integration servers.

The acceptable character set for policy names is identical to the character set for directory names on the file system of the target integration node. The name of a policy cannot start with a numeric character.

The names of deployable resources (such as message flows, dictionaries, and JAR files) must consist only of characters that are acceptable in file names on the file systems of both the IBM App Connect Enterprise Toolkit and the target integration node.

On Windows operating systems, integration node names are not case-sensitive. For example, integration node names inode1 and INODE1 refer to the same integration node.

On Linux® and UNIX systems, integration node names are case-sensitive. For example, integration node names inode1 and INODE1 refer to different integration nodes.

Additional rules are enforced for naming message service folders in the MQRFH2 header.