Configuring WebSphere Application Server for use with Sybase 11.9.2 or 12

To configure a quick installation of WebSphere Application Server so it can use Sybase 11.9.2 or Sybase 12:

  1. Add \product_installation_root\jdk\bin to your PATH environment variable. For Windows NT, the default product_installation_root is:
    <drive>:\\WebSphere\AppServer
  2. Download the database conversion assistant from the product Web site. Look for the assistant under the Tools, service upgrades, fixes, and more link in the Support downloads section of the Support page.
  3. Extract the assistant ZIP file contents and follow the instructions in the README file for the assistant. The instructions are repeated in "3.5.1: Using the database conversion assistant to switch administrative databases." (Be sure to update your locally installed InfoCenter to include changes made in version 3.5.1 or later.)
  4. Follow the instructions in the assistant interface. For the fields, enter the values shown below:
    Path to administrative configuration file
    <product_drive>:\\WebSphere\AppServer\bin\admin.config

    <product_drive> is the letter of the drive onto which you installed WebSphere Application Server 3.5. If you installed to a directory other than the default, then the path WebSphere\AppServer will vary according to where you installed the product.

    Database type
    Sybase
    Database driver name
    com.sybase.jdbc2.jdbc.SybDriver
    Path to JDBC driver file
    <jConnect5_2_directory>/jConnect5_2/classes/jconn2.jar
    Database prefix (part of database URL)
    jdbc:sybase:Tds:<hostname>:<port>

    <hostname> and <port> depend upon your environment. The default port is 5000. Use the short hostname instead of the fully qualified hostname.

    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. Obtain the latest fixpack for IBM WebSphere Application Server Version 3.5 (3.5.2 or later) from the product Web site and apply it.
  6. Start the WebSphere administrative server.

Troubleshooting

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

If the server does not start, try determining the problem as follows: