- A map-specific message file,
mapName_locale.txt where mapName corresponds to the name of the
map and locale corresponds to the locale that the map is
defined in.
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
For 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.
- The UserMapMessages.txt message file
To this file, you can add new message numbers that fall into a
"safe" range, as defined by IBM WebSphere InterChange Server
Express (see Table 112).
For example, if you create a message for an Oracle map, you would
assign the message a number between 6101 and 6200. You can also use
a message number that is already defined in the IBM WebSphere
InterChange 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
IBM WebSphere InterChange Server Express message file, your
additions override those messages.
- The IBM WebSphere InterChange Server Express generic message
file, CWMapMessages.txt (which IBM WebSphere
InterChange Server Express provides).
If your map does not reference one of the other two
message files, it must reference this one. Table 112 lists the message
numbers that IBM WebSphere InterChange Server Express has assigned
and that are contained in the generic message file.
Attention: Do not change the contents of the IBM
WebSphere InterChange Server Express generic message file
CwMapMessages.txt! Make changes to a generic message by
copying it into the UserMapMessage.txt message file and
customizing it.
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 IBM WebSphere InterChange Server Express. The other two files
provide you with the option to customize messages for your maps, as
needed.
Message
number |
Message
text |
Message
usage |
5000 |
Mapping -
Value of the primary key in the source object is null. Map
execution stopped. |
Used if the
primary key of the source object is null. The check for the source
primary key = null should always be performed before any of the
relationship methods are called that are based on the source
object's primary key. If the key is null, the error should display
and the map should stop execution. |
5001 |
Mapping -
RelationshipRuntimeException.
Map execution stopped. |
Used if
RelationshipRuntimeException is caught in one of the
following:
- Function blocks
- General/APIs/Identity Relationship/Maintain Simple Identity
Relationship
- General/APIs/Identity Relationship/Maintain Composite
Relationship
- Mapping APIs
-
maintainSimpleIdentityRelationship()
-
maintainCompositeRelationship()
|
5002 |
Mapping -
CxMissingIDException.
Map execution stopped. |
Used if
CxMissingIDException
is caught in one of the following:
- Function blocks
- General/APIs/Identity Relationship/Maintain Simple Identity
Relationship
- General/APIs/Identity Relationship/Maintain Composite
Realtionship
- Mapping APIs
-
maintainSimpleIdentityRelationship()
-
maintainCompositeRelationship()
|
5003 |
Mapping -
Data in the {1} attribute is missing. |
Used when the
source attribute is null before using the function block Foreign
Key Lookup (
foreignKeyLookup()) or Foreign Key Cross-Reference (foreignKeyXref()). The check
for the source attribute = null should always be performed before
these relationship methods are called. If the key is null, the
error should be displayed and the map might stop execution. |
5007 |
Mapping -
ForeignKeyLookup() of '{1}' with Source Value of '{2}' failed for
the '{3}' relationship and '{4}' participant on Initiator '{5}'.
Map execution stopped. |
Used if the
destination attribute is null after using the function block
Foreign Key Lookup (
foreignKeyLookup()). Map has to stop execution. |
5008 |
Mapping -
ForeignKeyLookup() of '{1}' with Source Value of '{2}' failed for
the '{3}' relationship and '{4}' participant on Initiator '{5}'.
Map execution continued. |
Used if the
destination attribute is null after using the function block
Foreign Key Lookup (foreignKeyLookup()). Map has to
continue execution. |
5009 |
Mapping -
ForeignKeyXref() of '{1}' with Source Value of '{2}' failed for the
'{3}' relationship and '{4}' participant on Initiator '{5}'. Map
execution stopped. |
Used if the
destination attribute is null after using the function block
Foreign Key Cross-Reference (foreignKeyXref()). Map has to
stop execution. |
When a map references a message number, the message files are
searched in the following order: