Omni-Payer™ Management Central Installation and Configuration Guide > Installing Omni-Payer Management Central and Deploying to IBM WebSphere Application Server > Resolving Library Conflicts

Resolving Library Conflicts

How to:

This section describes how to configure isolated shared libraries and is used to resolve library conflicts between IBM WebSphere Application Server and the Omni-Payer application. For now, the only conflicted library is the Apache HTTP Client.

Procedure: How to Configure Isolated Shared Libraries

To configure isolated shared libraries:

  1. From the Environment section, click Shared libraries.
  2. From the Scope/Server drop-down list, select the node and the server (for example, Node=iwaix3Node01, Server=server1), and then click New.
  3. Enter the required values for the parameters.
    1. In the Name field, enter a library name, for example, apachehttpclient.
    2. In the Classpath field, enter a list of paths separated by semicolons (;), for example, C:\httpclient-4.3.2.jar;C:\httpcore-4.3.1.jar.

      Note: You can find the specified libraries in the opmc.war file (WEB-INF\lib\ directory). You can copy them to your file system and edit the classpath according to the new location.

    3. Select the Use an isolated class loader for this shared library check box, as shown in the following image.
  4. Click Apply, and then click Save.
  5. Prepare the opmc.war file. Some additional preparations are required due to library incompatibilities.
    1. Explore the contents of the opmc.war file using any archiving tool.
    2. Navigate to the WEB-INF\lib\ directory.
    3. Delete the validation-api-1.0.0.GA.jar and xml-apis-1.3.04.jar files.