Error message reference

AS4 Microservice messages relay information about how the system or application is doing and can alert you to exceptional conditions when they occur.

Messages are displayed through the user interface and written to the log files. If error details are contained in a visibility event, those details are displayed in human-readable format in the user interface. The visibility receiver collects and stores the error code and parameters that are related to each error. Then, a translation service determines the locale of the user and displays the error code and translated error message.

If you receive a warning or error message, you can perform one of the following actions:

Follow the instructions that are listed in the detail section of the message to see what action you can take to correct the problem.
Consult the message log for the message ID, message description, time, and date of the message, and other data that you can use to diagnose and correct the problem.

The content of each AS4 Microservice message is defined by a triplet format. The triplet format is as follows:

Message ID and short text: Product-specific unique message identifier and short description of the problem.
Explanation: Describes the cause of the problem and includes information to help you avoid this problem in the future.
User action: Describes what you must do to proceed, recover from the error, or to prevent a pending problem.

Message IDs are formatted as BCXSSNNNNT, in which these prefixes and identifiers are the constituent components.

BCX: Is the three-character prefix that identifies the AS4 Microservice software brand.
SS: Is the two character prefix extension that is used to identify one or more software components.
NNNN: Is a unique four-digit identifier for the message.
T: Indicates whether the message is information (I), warning (W), or an error message (E).

The AS4 Microservice component prefix extensions (the SS part of the message ID) are defined as follows:

AC: Indicates that the component that produced the exception is the AS2 common component.
AI: Indicates that the component that produced the exception is the AS2 inbound engine.
AO: Indicates that the component that produced the exception is the AS2 outbound engine.
AS: Indicates that the component that produced the exception is the AS4 inbound and outbound engine.
CC: Indicates that the component that produced the exception is the communication common component used by all protocols (for example, AS2 and AS4).
CH: Indicates that the component that produced the exception is the cache component (the base component that provides an abstraction layer for WebSphere eXtreme Scale).
CS: Indicates that the component that produced the exception is the Cryptographic Message Syntax component, which provides cryptographic services used by the AS2 protocol.
DI: Indicates that the component that produced the exception is the communications dispatcher.
ID: Indicates that the component that produced the exception is identity.
HI: Indicates that the component that produced the exception is HTTP inbound.
HO: Indicates that the component that produced the exception is HTTP outbound.
JI: Indicates that the component that produced the exception is JMS inbound.
JO: Indicates that the component that produced the exception is JMS outbound.
MF: Indicates that the component that produced the exception is the message fabric.
PL: Indicates that the component that produced the exception is the Process State Logger component, which is used by AS2 and AS4.
PP: Indicates that the component that produced the exception is the Protocol Profile, which is the component that stores protocol profile configurations.
PR: Indicates that the component that produced the exception is provisioning.
SC: Indicates that the component that produced the exception is the scheduler.
SF: Indicates that the component that produced the exception is the Store and Forward service.
SM: Indicates that the component that produced the exception is collective and gateway management.
ST: Indicates that the component that produced the exception is storage.
TM: Indicates that the component that produced the exception is the Thread Management component that is used for all the communication protocols.
UI: Indicates that the component that produced the exception is the user interface.
WP: Indicates that the component that produced the exception is the WebSphere eXtreme Scale Purge component for communications.