Valid Channel Names

If your channel 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, but the channel 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 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.

Note:
When you create a channel of type Persistent, Mixed or Reliable, this will cause the channel's messages to be persisted to a store in the file system. In the case of a multi-file disk store, the data will be persisted in ".mem" files located in the directory data/<ChannelName><UniqueID> under the realm server directory, where <ChannelName> is the channel name you provide in the dialog and <UniqueID> is an automatically generated unique hexadecimal string of typically 14 characters. In the case of a single-file disk store, the data will be persisted in a file named data/<ChannelName><UniqueID>.mem. All elements in the path (the .mem file and each of the parent directories) are restricted to 255 characters in length, and the entire path cannot exceed 4096 characters. guide. guide.