Installing Merant SequeLink JDBC provider for use with IBM WebSphere Application Server and Oracle on Solaris

IBM WebSphere Application Server supports the use of the Merant SequeLink JDBC provider with Oracle databases. The Merant product provides the Oracle database with JDBC functionality.

The steps in this topic describe how to install Merant SequeLink for use with a single configuration of WebSphere Application Server that uses:

  • Sun Solaris 7 or 8
  • Java 2 Software Development Kit (SDK) 1.3 (version supplied with WebSphere Application Server)
  • IBM HTTP Server 1.3.19 (or another supported Web Server)
  • A supported Oracle database
  • A supported Merant SequeLink Server for Oracle on Solaris
  • A Merant SequeLink driver (supplied with WebSphere Application Server)
  • A single node

Prerequisite conditions

These instructions assume the following prerequisite conditions:

  • You have checked the WebSphere Application Server Supported Hardware, Software, and APIs Web site at www.ibm.com/software/webservers/appserv/doc/latest/prereq.html to identify which products and fix levels are supported for your level of WebSphere Application Server.
  • You have installed IBM WebSphere Application Server specifying Merant as the administrative database. Although you specify Merant as the administrative database so that WebSphere Application Server uses its JDBC provider, you will configure communications between Merant and Oracle so that Oracle is actually used as the database.
  • You have installed your Web server and Oracle database server. For links to installation instructions for various sets of prerequisites on the Solaris operating system, see the article "IBM WebSphere Application Server for Solaris."

Steps for installation

To enable the Merant SequeLink JDBC provider for use with Oracle as the administrative database for IBM WebSphere Application Server, complete the following steps:

  1. Before the Merant driver is used, ensure that the Merant SequeLink driver files, sljc.jar and sljcx.jar (supplied with WebSphere Application Server in the directory /opt/WebSphere/AppServer/lib by default), are both included in the value for the CLASSPATH environment variable (com.ibm.ejs.sm.adminserver.classpath) in the administrative server configuration file, admin.config. The file admin.config is located in the directory /opt/WebSphere/AppServer/bin by default.
  2. Install the Merant SequeLink Server for Oracle without a registration key on the same machine as the Oracle database product with which you want to use the Merant driver. Refer to the article "Installing the Merant SequeLink Server without a registration key" for instructions.
  3. Perform any configuration necessary to establish communications between the Oracle database and the Merant SequeLink Server. Refer to Merant documentation at www.merant.com/products/datadirect/download/docs/dochome.asp for instructions appropriate for your configuration.
  4. Start the WebSphere administrative server by using the startupServer.sh script as follows:
    # ./startupServer.sh

Troubleshooting

The database configuration and tables must be correct in order for WebSphere Application Server to complete its startup routine. If the administrative server starts, then the configuration is successful.

If the administration server does not start, try to determine the problem as follows:

  • Use the database management system to check that the database tables were created successfully. If they were not, then double-check the database settings.
  • Open the following files in a text editor to confirm that the settings are configured correctly for your system:
    • /opt/WebSphere/AppServer/bin/admin.config
    • /opt/WebSphere/AppServer/properties/initial_setup.config
  • Investigate typical reasons that the administrative server fails to start in the Troubleshooting area of the InfoCenter.
  • Check the product Release Notes for WebSphere Application Server version-specific problems and solutions.