Messages logged by IBM Security Access Manager for Mobile
adhere to the Tivoli® Message
Standard. Each message consists of a message identifier (ID) and accompanying
message text.
Message ID format
A message ID consists
of 10 alphanumeric characters that uniquely identify the message.
A
message ID in Security Access Manager for Mobile is composed of:
- three-character product identifier
- two-character or three-character component or subsystem identifier
- three-digit or four-digit serial or message number
- one-character type code indicating the severity of the message
The figure that follows shows a graphical representation
of a possible message ID and identifies its different parts. (Some
messages might use 2 characters for the component ID and 4 digits
for the serial number.)
Figure 1. Message ID format
Component identifiers
The component identifier
indicates which component or subsystem produced the message.
- ADM
- Administration commands
- AUD
- Audit
- CC
- Common Auditing and Reporting Service disk cache
- CDS
- InfoCard messages
- CE
- Common Auditing and Reporting Service emitter
- CFG
- Configuration properties
- CLI
- Command-line interface
- CO
- Common Audit Service Configuration Console
- CON
- Security Access Manager console
- CTG
- Authorization service
- DPW
- Secure reverse proxy
- FMS
- Management service
- FBT
- Protocol service
- IDS
- Identity service
- IN
- Common Auditing and Reporting Service installation
- ISJ
- Alias service JDBC component
- ISL
- Alias service LDAP component
- IVT
- Installation verification test
- KES
- Key service keystore management
- KJK
- Key service keystore management
- LIB
- Liberty single sign-on protocol
- LOG
- Logging
- MB
- Common Audit Service Configuration MBean
- MGT
- Management
- MET
- Metadata handling
- MOD
- Module
- OID
- OpenID messages
- PWD
- Password handling
- RPT
- Report messages
- RTE
- Runtime environment component configuration
- SML
- SAML single sign-on protocol
- SOC
- SOAP client
- SPS
- Single sign-on protocol service
- STM
- Secure token service
- STS
- Secure token service modules
- STZ
- RACF® PassTicket tokens
- SU
- Common Audit Staging Utility
- TAC
- Tivoli Access Manager
configuration as point-of-contact server
- TRC
- Trust client
- USC
- User self care
- WS
- Common Auditing and Reporting Service Mobile service
- WSF
- WS-Federation single sign-on protocol
- WSP
- Provisioning service
- WSS
- Mobile services security management
- XS
- Common Audit Service XML data store
- XU
- Common Audit Service XML store utilities
Severity
Associated with each message is
a severity level that indicates whether corrective action must be
taken.
Table 1. Severity level| Severity |
Description |
| I (Informational) |
Provides information or feedback about normal
events that occur. In general, no action needs to be performed in
response to an informational message. FBTRTE033I The domain default was successfully created.
FBTSTM066I The Trust Service has been disabled.
|
| W (Warning) |
Indicates that a potentially undesirable
condition has occurred, but processing can continue. Intervention
or corrective action might be necessary in response to a warning message. FBTLOG002W An integer was expected.
FBTTRC004W The returned RequestSecurityTokenResponse
did not have a wsu:Id
|
| E (Error) |
Indicates that a problem has occurred that
requires intervention or correction before processing can continue.
An error message might be accompanied by one or more warning or informational
messages that provide additional details about the problem. FBTCON013E The federation with ID insert could not be
retrieved from the single sign-on protocol service.
Explanation:
This error can occur if the console is unable to
communicate with the single sign-on protocol service.
FBTSML260E The binding value value for attribute attr
is not valid for profile profile.
|
Message text
The text of the message, in
the system locale, also is recorded in the log file. If the message
text is not available in the desired language, the English language
text is used.