Universal Messaging 10.5 | Administration Guide | Universal Messaging Enterprise Manager | Channel Administration | Creating Channels | Valid Channel and Queue Names
 
Valid Channel and Queue Names
The channel and queue names can contain any of the following characters:
*All letters and digits
*Slash "/"
*Hyphen "-"
*Underscore "_"
*Hash symbol "#"
Certain character strings are replaced:
*Backslash "\" is replaced by slash "/"
*Two colons "::" are replaced by slash "/"
*Two slashes "//" are replaced by one slash "/"
Valid names have the following length restrictions:
*Channel and queue names have a maximum limit of 235 characters.
*Namespace names have a maximum limit of 255 characters.
*The full path containing the data directory folder path with a channel or queue path appended to it has a maximum limit of 4096 characters.
If your channel or queue name contains slash characters, for example "a/b/c", this is represented in the Enterprise Manager view as a hierarchy, with "a" being the top node, "b" being the child node of "a", and "c" being the child node of "b". This virtual hierarchy is just a visual aid to help you to keep track of your channels and queues, but the store itself is not divided internally into hierarchical parts and can only be referenced by the full name, which in this example is "a/b/c".
Note:
There is a restriction that a channel or queue name cannot be the same as an existing folder name. So if you have named a channel "a/b/c", you cannot name a different channel "a" or "a/b". This would lead to a display conflict in Enterprise Manager, since we would have a folder "a" as the root of the path "a/b/c", as well as a channel "a" at the same position in the display. Similarly, trying to assign the name "a/b" to a new channel would conflict in the display with the folder named "a/b". You can however name a different channel "a/c", since "a" is used here again as a virtual folder. Similarly, you can name another channel "a/b/d", since both "a" and "a/b" are used here as virtual folders.