Configuring Merant SequeLink for use with IBM WebSphere Application Server Advanced Edition

IBM WebSphere Application Server Version 3.5.3 introduced the ability to use a Merant SequeLink Server and JDBC driver with some of its supported administrative databases, as well as a database that is the data source for WebSphere Application Server. See the Prerequisites Web page for the list of supported databases and Merant products.

The instructions in this topic describe how to configure Merant SequeLink for use with IBM WebSphere Application Server and a database product. Merant SequeLink is enabled in the same manner regardless of whether the database is to be used as the data source for WebSphere Application Server or as the administrative database for WebSphere Application Server.

Because the Merant SequeLink driver is not offered as a choice on the WebSphere Application Server product installation screen, you temporarily need to specify one of the databases available on the installation page, and then use the database conversion assistant tool to convert to the Merant SequeLink driver. The database conversion assistant tool can be downloaded from the IBM WebSphere Application Server web site.

These instructions assume that you have already:

When these steps are completed, you are ready to use the database conversion assistant tool to modify the WebSphere Application Server administrative database settings in order to use the Merant driver.

  1. Update your PATH environment variable to include the product location. For example, on Windows, add product_installation_root\jdk\bin to your PATH environment variable.
  2. Download the database conversion assistant from the Tools FTP site accessible from the product Web site.
  3. Extract the database conversion assistant tool ZIP file contents and follow the instructions in the README file for the tool. Instructions on using the tool are given in the article about using the database conversion assistant to switch administrative databases. This site provides instructions for both Windows and UNIX systems.
  4. Follow the instructions in the database conversion assistant tool's graphical user interface.

    Make sure that the hostname, port number, user ID, and password values identify the database to which you want to switch. For example, if switching from DB2 to Microsoft SQL Server, use these settings to establish the Microsoft SQL Server database as the target database.

    Path to administrative configuration file
    product_installation_root\bin\admin.config

    Database type
    Merant

    Enter Merant whether your database is Oracle, Microsoft SQL Server, or another brand.

    Database driver name
    com.merant.sequelink.jdbc.SequeLinkDriver

    Path to JDBC driver file
    These JDBC and JTA drivers are now part of IBM WebSphere Application Server installation. They reside in product_installation_root\lib\sljc.jar and product_installation_root\lib\sljcx.jar

    For corrections or updates to this information, see the database driver location table in the InfoCenter article about database drivers.

    Database prefix (part of database URL)
    jdbc:sequelink://hostname:port

    hostname and port (meaning the database port number) depend upon your environment. Use the short host name instead of the fully qualified host name. For example:

         jdbc:sequelink://stlab23:19998
         

    Database name (part of database URL)
    was or the database name of your choice

    User ID
    EJSADMIN

    Password (and confirm)
    EJSADMIN or the password of your choice


  5. If you have not already done so, obtain the latest FixPak for IBM WebSphere Application Server from the product Web site and apply it.
  6. Start the WebSphere administrative server.

See the InfoCenter article about JDBC drivers for tips about using the Merant JDBC driver.

Troubleshooting

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

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

See also the product Release Notes.