Home

 

WebSphere Application Server

If you are using WebSphere MQ JMS, with WebSphere Application Server as your transaction manager, you must perform the following configuration tasks:

• Configure WebSphere MQ Java for use in client mode as described in WebSphere MQ Using Java.

• Configure the interface between WebSphere MQ JMS and WebSphere Application Server. WebSphere MQ Using Java describes how to do this for WebSphere MQ JMS applications that connect to a queue manager in bindings mode. For client mode, you configure the interface in exactly the same way.

To complete the configuration for the extended transactional client, then perform the following task. The procedure you follow depends on which version of WebSphere Application Server you are using. In each procedure, we need to enter the fully qualified path name of the Java archive file, com.ibm.mqetclient.jar, which is installed with the extended transactional function. See Table 17 for this information.

Table 17. The location of the com.ibm.mqetclient.jar file

Platform	Location of com.ibm.mqetclient.jar
AIX	/usr/mqm/java/lib/com.ibm.mqetclient.jar
HP-UX Linux Solaris	/opt/mqm/java/lib/com.ibm.mqetclient.jar
Windows systems	C:\\IBM\WebSphere MQ\Java\lib\com.ibm.mqetclient.jar 1
Notes: This is the default location for the file, but you might have installed it in a different location.

For WebSphere Application Server V4:

1. Open the WebSphere Application Server Administrative Console.

2. In the navigation pane on the left side of the window, expand the following items in sequence:

   1. WebSphere Administrative Domain

   2. Nodes

   3. The name of the system that contains the application server in which you want to run your WebSphere MQ JMS applications

   4. Application Servers

   Then click the application server in which you want to run your WebSphere MQ JMS applications (Default Server, for example).

3. In the right side of the window, click the JVM Settings tab.

4. In the System Properties section of the page, click Add. An empty row is created in the System Properties table.

5. In the Name column of the empty row, type

   ws.ext.dirs.

6. In the Value column of the empty row, type the fully qualified path name of the Java archive file, com.ibm.mqetclient.jar.

7. Click Apply.

8. Restart the application server for the changes to take effect.

For WebSphere Application Server V5:

1. Start the WebSphere Application Server Administrative Console in your Web browser and log in.

2. In the navigation frame on the left side of the page, expand Servers.

3. Click the Application Servers link. A list of application servers is displayed on the right side of the page.

4. Click the link for the application server in which you want to run your WebSphere MQ JMS applications (server1, for example). A page containing the properties of the application server is displayed. Ensure the configuration properties are displayed by clicking the Configuration tab, if necessary.

5. In the Additional Properties section of the page, click the Process Definition link. The Process Definition page is displayed.

6. In the Additional Properties section of the page, click the Java Virtual Machine link. The Java Virtual Machine page is displayed.

7. In the Additional Properties section of the page, click the Custom Properties link. The Custom Properties page is displayed.

8. Click New. A page to enter the name and value of a custom property is displayed.

9. In the Name field, type

   ws.ext.dirs.

10. In the Value field, type the fully qualified path name of the Java archive file, com.ibm.mqetclient.jar.

11. Click OK.

12. Click Save to save the changes to the configuration. A page containing a confirmation prompt is displayed.

13. Click Save to confirm the changes.

14. Restart the application server for the changes to take effect.

 

Home