Define mapping specifications
Detailed mapping specifications are defined for each mapper.
The following tables show the specifications for the Messaging API mappings.
MsgApi path | ISF path | Database | Comment |
---|---|---|---|
header.msgDesc | Header.MessageName | TRANSACTION_V.OBJ_CLASS | A Service_Request or Service_Response |
header.msgType | Header.BusinessConcept | TRANSACTION_V.SUBTYPE | The business purpose |
header.version | Ignored | ||
header.messageTime | Ignored | ||
header.sourceId | Header.Sender | The sending component | |
header.destinationId | Header.Receiver | The receiving component | |
header.unitOfWork | Header.MasterTransactionId | TRANSACTION_V.CID | The key that identifies the unit of work. |
header.unitOfWork @type | Header.TransactionRef | Unit of work type, such as TRANSMISSION_ID, OUTBOUND_PRESENTMENT_GROUP_ID, and others | |
header.responseRequired | Ignored | ||
payload | Wrapper | The schema allows any XML payload content. |
ISF path | MsgApi path | Comment |
---|---|---|
Header.BusinessConcept | header.msgType | The business purpose |
Header.MasterTransactionId | header.unitOfWork | The key that identifies the unit of work. |
Header.RequestID | Ignored | |
Header.TransactionId | Ignored | |
Header.TransactionRef | header.unitOfWork @type | Unit of work type, such as TRANSMISSION_ID, OUTBOUND_PRESENTMENT_GROUP_ID, and others |
Header.Priority |
Ignored | |
Header.MessageName | header.msgDesc | A Service_Request or Service_Response |
Header.Sender | header.sourceId | The sending component |
Header.Receiver | header.destinationId | The receiving component |
'1.0.0' | header.version | The version of the message |
CURRENT_TIMESTAMP | header.messageTime | The time. It is in the I format. |
'false' | header.responseRequired | Response required flag. It is used in the Service_Request only. |
Wrapper | payload | The schema allows any content. |