WebSphere brand IBM WebSphere XML Document Management Server, Version 7.0

Configuring IBM XDMS to work with Oracle Database

You must configure IBM® XDMS so that it will work with an Oracle thick client.

About this task

As an alternative to installing the thick client, you can configure a thin client for Oracle Database. To configure the thin client, you will need to install XDMS 7.0 interim fix 1. Contact your IBM representative for more information.

Follow these steps to configure IBM XDMS to work with an Oracle thick client.

  1. Make two directories for the Oracle XML files, for example /usr/Oracle_XML_files and /usr/Oracle_jdbc_files.
  2. Copy the following files to the Oracle_jdbc_files directory:
    • ojdbc6.jar (for WebSphere® Application Server version 7.0.0.1)
    • ojdbc5.jar (for WebSphere Application Server version 6.1.0.x)

    Copy the following files to the Oracle_XML_files directory:

    • xdb.jar
    • xmlparserv2.jar
    Note: The ojdbc* JAR file must be in a different directory than the xdb and xmlparserv2 JAR files. If the xdb and xmlparserv2 JAR files are in the directory that is pointed to by the data source, the deployment manager could fail to start. If you will be installing XDMS 7.0 interim fix 1 and moving to the thin client, enter the Oracle_jdbc_files directory into the Data Source Creation screen of the installer, or else enter the Oracle client installation directory.
  3. Add the absolute path to these JAR files in each XDMS Application server JVM:
    1. Open the Integrated Solutions Console.
    2. Click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    3. Click server_name > Process Definition > Java Virtual Machine and select the Configuration tab.
    4. Add the absolute path to the JAR files in the Class Path text box. Example: /usr/Oracle_jdbc_files/ojdbc6.jar, /usr/Oracle_XML_files/xdb.jar, or /usr/Oracle_XML_files/xmlparserv2.jar.
  4. Add the following generic JVM arguments:
    -Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl 
    -Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl 
    -Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl 
  5. Restart the deployment manager and all managed node servers.
What to do next

Repeat these steps on each managed node. Then perform a test connection to make sure that the configuration is successful.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.