IBM® WebSphere® Diameter
Enabler Component can write system messages to several general
purpose logs. Logging provides information about important lifecycle
events, warnings, and errors that should be addressed by an administrator.
By default,
IBM WebSphere Diameter
Enabler Component logs its messages
to the
WebSphere Application Server JVM
log (
SystemOut.log) and its trace messages to
the
WebSphere Application Server trace
log (
trace.log). Both
log files are located in the
logs directory:
was_profile_root/logs/server_name
was_profile_root/logs/server_name
was_profile_root/logs/server_name
Note: was_profile_root is
the directory for a
WebSphere Application Server
Network Deployment profile
called
profile_name. By default, this directory
is:
/usr/IBM/WebSphere/AppServer/profiles/profile_name
/opt/IBM/WebSphere/AppServer/profiles/profile_name
/opt/IBM/WebSphere/AppServer/profiles/profile_name
In a standalone environment, profile_name is
the name of the application server profile (for
example, AppSrv01). In a clustered environment, profile_name is
the name of a federated node profile (for example,
Custom01).
Each error, warning, or informational log message should include
a message code which is used to identify the message. Additionally,
each message can be identified by the date, timestamp, thread number,
and severity.
IBM WebSphere Diameter
Enabler Component messages are also identified with a class
name. For example:
- [4/8/09 10:45:14:773 EDT] 00000031 DiameterState
I DHAC0100I: Connection has transitioned to the Open state. Peer Host:
hostname.myco.com ApplicationId[0] = VendorId = 10415; Auth Application
Id = 16777217; Supported vendor ids = 10415
Comprehensive information about working with message logs may be
found in the WebSphere Application Server
Network Deployment information
center.