WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Installing the WebSphere Application Server log file adapters

Follow the instructions below to install the WebSphere® Application Server log file adapters on WebSphere Premises Server using the Tivoli Enterprise Console®.

About this task

The WebSphere Application Server log file adapters enable you to view exceptions that occur on WebSphere Premises Server from the Tivoli Enterprise Console. You must first load the adapters into the Tivoli Enterprise Console, and then distribute them to your premises servers. The adapters then run as services on WebSphere Premises Server, allowing you to view the exceptions from the console.

Note: You must have Tivoli Enterprise Console installed on your Tivoli® server and Tivoli endpoints installed on each premises server. For instructions on how to install these products, refer to the product documentation for Tivoli Enterprise Console. Refer to the online help in the Tivoli Enterprise Console for additional information about performing the tasks below.
Procedure
  1. Ensure that the following files exist in the IBM_RFID_HOME\monitoring directory:
    • wasjava.cds
    • wasjava.conf
    • wasjava.fmt
    • wasjava.baroc
  2. Edit the following properties in wasjava.conf:
    1. Set the path to the WebSphere Application Server log file that you want to monitor.
    2. Set the Event Server name.
    3. Modify the value of the BufEvtPath attribute if the file named is already in use by another adapter.
    4. Adjust the PollInterval attribute to a suitable value.
  3. Open the Tivoli Desktop.
  4. Select an existing policy region or create a policy region to contain the profile manager for log file monitoring.
  5. Add ACP to the selected policy region as a managed resource type.
  6. Add Profile Manager to the selected region as a managed resource type.
  7. Open the policy region and create a new Profile Manager.
  8. Open the new Profile Manager and create a new ACP profile
  9. Open the new profile for editing and add a tecad_win entry.
  10. Click the General tab of the new entry and select Identifer. Then enter a descriptive name in the Identifier Name field.
  11. Click the Distribution tab of the entry and double-click the C/tecad_win.fmt entry. You can now edit the entry.
  12. Edit the value to reflect the location of the supplied wasjava.fmt file. Click the check mark button to save the changes.
  13. Enter tecad_win.cds as the property name, and enter the path to the supplied wasjava.cds file as the property.
  14. Click the check mark button to add the property.
  15. Add the tecad_win.conf file using the supplied wasjava.conf file.
  16. Click Save & Close to save the entry.
  17. Set the subscribers for the profile manager to include the WebSphere Premises Server from which you want to monitor the WebSphere Application Server.
  18. Import the supplied wasjava.baroc file.
  19. After importing the new classes, compile the Rule Base and load it into the Event Server.
  20. Distribute the profile to WebSphere Premises Server. After distribution, a new service should be listed in the Windows® Services Manager, with an ID equal to the Identifier Name given to the ACP entry.
What to do next
Now, the log file adapter should be monitoring the log file entered into the wasjava.conf file. Exceptions logged to the WebSphere Application Server log file are changed to an instance of the Was_Java_Exception class and sent to the Tivoli Enterprise Console Event Server.

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.