Trace logs show trace events such as function
entries and exits, component events, and debugging activities. Use
the administration console to enable trace for a process.
About this task
You can configure the IBM® WebSphere® Diameter
Enabler Component to start in a trace-enabled state by setting
the appropriate configuration properties.
You can control how
much detail each logger records by adjusting the log level details.
Because the loggers are grouped hierarchically, setting the trace
level on one logger also sets all subsequent loggers to the same level.
Altering the tracing levels impact the performance of the system.
Enable
and configure trace by completing the following steps:
- Log in to the Integrated Solutions Console:
- Open a browser and navigate to the following
URL: https://host_name:port/ibm/console.
Where:
- host_name is the fully qualified host name
of the server where the application or the network deployment manager
is deployed.
- port is the secured port used to access the
console. The default port is 9043.
Note: The default unsecured port is 9060.
If you use 9060, you must have "http" instead of "https" in the URL.
- Enter an administrator user ID and password. (Omit the password if security is
not enabled.)
- Click Log in.
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click the name of the server you want to manage.
- Click .
- Click Diagnostic Trace Service.
- Configure your trace options:
- Display the Runtime tab.
- To disable tracing, select File and
then select None.
Note: If you are
using WebSphere Application Server version 6.1.0.x,
disable tracing by selecting Enable log and
then substituting disabled in place of enabled.
- Click Change Log Level Details.
- Click Components to view all
loggers for the individual components.
- Click + to show the children of
the logger.
- Click logger_name to
change the log details. To enable tracing on specific
components of IBM WebSphere Diameter
Enabler Component,
click one of these logger groups:
- com.ibm.diameter.*
- com.ibm.diameter.base.*
- com.ibm.diameter.cfsm.*
- com.ibm.diameter.charging.*
- com.ibm.diameter.packet.*
- com.ibm.diameter.rf.*
- com.ibm.diameter.ro.*
- com.ibm.diameter.sh.*
- com.ibm.ws.diameter.*
- Choose the appropriate level of tracing.
Remember: When you change the level for a logger, the change
is propagated to the children of the logger.
For additional
information regarding trace levels, click ? in
the title bar of the panel to open the help page.
- Optional: To control logging
of information about offline accounting and online charging functions,
you can configure trace options for Rf accounting Web service and Ro online charging Web service usage
information.
- Click com.ibm.diameter.rf.usage to
change the log details. The com.ibm.diameter.rf.usage
logger controls the logging of information about the beginning and
ending of offline accounting functions.
- Click com.ibm.diameter.ro.usage to
change the log details. The com.ibm.diameter.ro.usage
logger controls the logging of information about the beginning and
ending of online charging functions.
- Click to log usage information.
The messages will be logged in rfUsage_x.log and roUsage_x.log,
where x is a number from 0 to 9. The maximum size
of the log file is 100 Mb. When the log file reaches the maximum size,
a new log will be created. After the tenth file has been created,
the first file will be overwritten. For example, assume rfUsage_0.log (or roUsage_0.log)
is the first file created. When rfUsage_9.log (or roUsage_9.log)
reaches the maximum size, rfUsage_0.log (or roUsage_0.log)
will be overwritten with the latest information. The rfUsage_x.log and roUsage_x.log files
will be created in the following location:
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).
- Click OK.
- Click Save.
Results
The specified traces are enabled for the current server session.
To make the changes permanent, use the Configuration tab rather than
the Runtime tab when you configure the trace options. Note that when
you use the Configuration tab, you will need to restart the server
for your changes to take effect.