Characters allowed in object names

You must adhere to rules when you provide names or identifiers for the components and resources in your integration server environment.

When you name objects such as integration nodes, integration servers and message identifiers, you can use the following subset of the ASCII Character Set ( ascii-codes) :

Alphabetic and numeric characters:
- Uppercase alphabetic characters A-Z
- Lowercase alphabetic characters a-z
- Numeric characters 0-9
The following special characters:
- Windows operating systems:
  
  $ % ' (apostrophe) " (quotation mark)
  
  - (dash) _ (underscore) @ ~ (tilde)
  
  ! ( ) (space)
  
  = [ ] &
  
  # + , (comma) . (dot)
- Linux® and UNIX operating systems:
  
  . (dot) % - (dash) _ (underscore)
  
  @ ~ (tilde) ! =
  
  [ ] & #
  
  + , (comma) (space)
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.

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.

Note: The name of a policy cannot start with a digit.

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.

On z/OS® systems, you must enclose mixed-case names in quotation marks.

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