WebSphere® Telecom Web Services
Server 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,
WebSphere Telecom Web Services
Server 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. In a clustered environment, profile_name is
the name of a federated node profile.
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. For example:
- [5/5/09 18:38:03:598 EDT] 0000002d AbstractServi
I com.ibm.twss.parlayx21.termstatus.AbstractServiceBindingImpl getSipURIFromTarget
SOAX3511I: SOAContextImpl_9.42.126.119_1146868683342_2047515057: Presence_IMS:
Unable to retrieve presence information for target http://hostname.myco.com.
Unable to parse target as a SIP URI: retval.getScheme() = http
Comprehensive information about working with message logs may be
found in the WebSphere Application Server
Network Deployment information
center.