Fix Readme
Abstract
To use the audit logging feature in DB2 Content Manager V8.3, which requires fix pack 4 or later, the resource manager needs a Java Message Service (JMS) queue set up to log events in an asynchronous way (the default behavior).
This document provides the steps to set up the JMS queue in WebSphere® Application Server V5.1.x.
Content
Log on to the WebSphere administration console (for example, the URL might be http://<hostname>:9090/admin)
1. Expand Resources in the left-hand menu. Select WebSphere JMS Provider.
2. In the right-hand menu, select the Resource Manager server as the scope.
- Click Browser Servers.
- Select the resource manager server name.
- Click Apply.
You should see the resource manager server selected as the scope.
3. Scroll down to the section Additional Properties and select WebSphere Queue Connection Factories.
4. On the next page, click New, and enter the following values:
- Name: rmeventCF
- JNDI Name: jms/rmeventCF
Scroll down and click Apply.
5. Go back to WebSphere JMS Provider, make sure the scope is the resource manager server (repeat step 2), and select WebSphere Queue Destinations.
6. On the next page, click New. Enter the following values:
Name: rmeventQueue
JNDI Name: jms/rmeventQueue
Scroll down and click Apply.
6. On the left-hand menu, click Servers, Application Servers and click the resource manager server name (example: icmrm).
7. On the application server properties, scroll down and click Server Components.
8. Click JMS Servers.
9. For Internal JMS Server, enter the following values:
Queue names: rmeventQueue
Initial State: STARTED
10. Click Save to save the changes in the configuration, as prompted on top of the screen.
11. Confirm the Save to Master Configuration.
12. Restart the resource manager server.
Was this topic helpful?
Document Information
Modified date:
08 October 2019
UID
swg21248649