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
- Ensure that the following files exist in the IBM_RFID_HOME\monitoring directory:
- wasjava.cds
- wasjava.conf
- wasjava.fmt
- wasjava.baroc
- Edit the following properties in wasjava.conf:
- Set the path to the WebSphere Application Server log file
that you want to monitor.
- Set the Event Server name.
- Modify the value of the BufEvtPath attribute
if the file named is already in use by another adapter.
- Adjust the PollInterval attribute to
a suitable value.
- Open the Tivoli Desktop.
- Select an existing policy region or create a policy region
to contain the profile manager for log file monitoring.
- Add ACP to the selected policy region
as a managed resource type.
- Add Profile Manager to the selected
region as a managed resource type.
- Open the policy region and create a new Profile Manager.
- Open the new Profile Manager and create a new ACP profile
- Open the new profile for editing and add a tecad_win entry.
- Click the General tab of the new
entry and select Identifer. Then enter a descriptive
name in the Identifier Name field.
- Click the Distribution tab of the
entry and double-click the C/tecad_win.fmt entry. You can now edit the entry.
- Edit the value to reflect the location of the supplied wasjava.fmt file.
Click the check mark button to save the changes.
- Enter tecad_win.cds as the property
name, and enter the path to the supplied wasjava.cds file
as the property.
- Click the check mark button to add the property.
- Add the tecad_win.conf file using
the supplied wasjava.conf file.
- Click Save & Close to save the
entry.
- Set the subscribers for the profile manager to include
the WebSphere Premises Server from
which you want to monitor the WebSphere Application Server.
- Import the supplied wasjava.baroc file.
- After importing the new classes, compile the Rule Base
and load it into the Event Server.
- 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.