Changing from basic mode to HPEL logging and tracing

The basic mode log and trace framework is enabled by default when you set up a new application server. Use this topic to switch to the High Performance Extensible Logging (HPEL) log and trace framework.

Before you begin

Before beginning this task, read about the differences between HPEL mode and basic mode. Be aware of changes you might need to make to any tools and scripts you have that use the basic mode log and trace files.

About this task

HPEL provides faster log and trace handling capabilities and more flexible ways to use log and trace content than the basic mode. You can switch to HPEL mode using the administrative console, or using wsadmin scripting.

Procedure

  • Use the administrative console to switch to HPEL.
    1. Log on to the administrative console.
    2. If using an admin agent topology select a node that you want to manage and navigate to it.
    3. From the navigation section in the console choose Troubleshooting > Logs and trace .
    4. .View your log and trace data using the LogViewer command-line tool or using the administrative console.
    5. Select the server that you want to switch to HPEL.
    6. Click Switch to HPEL Mode .
    7. Save the changes.
  • Use wsadmin scripting to switch to HPEL.
    Complete these steps to modify the server configuration.
    1. Start wsadmin.
      In this case, you can connect wsadmin to a running server or access the configuration data for a stopped server. Read about starting the wsadmin scripting client for more information.
    2. Get a reference to the HighPerformanceExtensibleLogging configuration object.

      Using Jython:

      HPELService = AdminConfig.getid("/Cell:myCell/Node:myNode/Server:
      myServer/HighPerformanceExtensibleLogging:/")
      Table 1. AdminConfig command description . The table lists AdminConfig command and description.
      Command Description
      myCell The name of the cell
      myNode The host name of the node
      myServer The name of the server
    3. Set the HighPerformanceExtensibleLogging enable attribute to true.

      Using Jython:

      AdminConfig.modify(HPELService, "[[enable true]]")
    4. Get a reference to the RASLoggingService object.

      Using Jython:

      RASLogging = AdminConfig.getid("/Cell:myCell/Node:myNode/Server:myServer/RASLoggingService:/")
      Table 2. AdminConfig command description . The table lists AdminConfig command and description.
      Command Description
      myCell The name of the cell
      myNode The host name of the node
      myServer The name of the server
    5. Set the RASLoggingService enable attribute to false.

      Using Jython:

      AdminConfig.modify(RASLogging, "[[enable false]]")
    6. Save the configuration.

      Using Jython:

      AdminConfig.save()

Results

The server is now configured to use HPEL when you restart.

If this task was done using the deployment manager, you might need to synchronize the node agent on the target node before restarting the server.

What to do next

Configure HPEL to meet your needs. If you have any tools or scripts that were using the basic mode log and trace files, you might need to modify them to continue working with HPEL.