All message file sare located in the following directory of the IBM WebSphere Business Integration Server Express product directory:
DLMs\messages
Three types of message files can be used to generate messages for a map:
Map messages appear in the Messages tab of Map Designer Express and are stored as part of the map definition in the repository. When you compile the map, Map Designer Express extracts the message content and creates (or updates) the message file for run-time use. The name of the message file has the following format:
MapName_locale.txt
Example: For the LegacyAddress_to_CwAddress map, if it is created in an English locale in the United States, Map Designer Express creates the message file called LegacyAddress_to_CwAddress_en_US.txt and places it in the ProjectName\Maps\Messages directory. After the map is deployed to InterChange Server Express, it will be placed in the DLMs\messages directory.
To this file, you can add new message numbers that fall into a "safe" range, as defined by WebSphere Business Integration Server Express (see Table 148). You can also use a message number that is already defined in the WebSphere Business Integration Server Express generic message file (CwMapMessages.txt, described next) and change the existing message text to text of your choice. Since the UserMapMessaages.txt file is searched before the WebSphere Business Integration Server Express message file, your additions override those messages.
If your map does not reference one of the other two message files, it must reference this one. Table 148 lists the message numbers that WebSphere InterChange Server has assigned and that are contained in the generic message file.
These files range from map-specific to general purpose. Messages that can be used by any map are located in a generic file, provided by WebSphere Business Integration Server Express. The other two files provide you with the option to customize messages for your maps, as needed.
When a map references a message number, the message files are searched in the following order:
Table 149 shows code examples that demonstrate situations in which each of the messages in the CwMapMessages.txt file might be used.