Previous
3.4.2 Interface Messages Log
An interface message log is maintained in the database. It is written to during batch, (asynchronous and synchronous) single message processing and for some UI related operations. For each operation an interface message entry is created which may have zero, one or more details. The structure of the interface messages log is listed in the following sub-paragraphs.
3.4.2.1 Interface Message
Interface Messages carry the following details:
|
Attribute |
Asynchronous Single Message |
Batch |
Synchronous Single Message |
|---|---|---|---|
|
Subtype |
ASYNC |
BATCH |
SYNC |
|
Task Id |
Identifier of the system task that was created for processing the request |
n/a |
n/a |
|
Job Instance Id |
n/a |
Reference to the job execution id |
n/a |
|
Correlation Id |
WS-Addressing messageId as given by the client that called the web service for invoking the asynchronous process (external identifier) |
WS-Addressing messageId as given by the client that called the web service for invoking the batch process (external identifier) |
n/a |
|
Service Name |
IP name. This is the same name that appears for the service in the WebLogic Console. |
n/a |
IP name. This is the same name that appears for the service in the WebLogic Console. |
|
Operation Name |
IP operation name as it appears in the WSDL. |
Batch job name |
IP operation name as it appears in the WSDL. |
|
Request Received Time |
The time that processing of the request started |
The time that processing of the batch request started |
The time that processing of the request started |
|
Request Processed Time |
The time that processing of the request finished |
The time that processing of the batch request finished |
The time that processing of the request finished |
|
Request Message |
Original request message payload that was received |
Original request notification message (containing link to file that contains the actual request message) that was received. |
Original request message payload that was received |
|
Response Message |
Response message that was sent. |
Response notification message (containing link to file that contains the actual response message) that was sent. |
Response message that was sent. |
|
Result Code |
'F' if message not processed successfully, 'S' if processed successfully. |
'F' if message not processed successfully, 'S' if processed successfully. |
'F' to indicate that message is not processed successfully. Synchronous messages that were processed successfully are not logged. |
3.4.2.2 Interface Message Details
Zero, one or more interface message details may be logged for an interface message. The structure of the interface message details is listed in the following table:
|
Attribute |
Description |
|---|---|
|
Interface Message Id |
Reference to Interface Message |
|
Element Id |
From message elementId attribute (only if result message relates to a main-level element in a batch file - otherwise n/a) |
|
Message Code |
Code of the message |
|
Message Text |
Descriptive text of the message with values substituted for the placeholders |
|
Message Detail |
Additional 'technical' detail (e.g. stack trace). Optional. |
Processing of a message failed if a message code is logged that is classified as Fatal.
Note that in case of synchronous single messages only failures are logged. This is done to make message processing more efficient. The idea of not logging successfully processed messages is that the absence of a failure implies success. If processing the request was successful, the audit columns for the entity reflect the change.