InfoCenter Home >
2: Installing WebSphere Application Server

2: Installing WebSphere Application Server

If the WebSphere Application Server Advanced Edition is installed and migrated into the same directory as a previous Advanced Single Server Edition installation, the Advanced Single Server Edition installation is no longer a valid installation. Do not run the uninstallation program because it uninstalls the new Advanced Edition installation.

Further, if the WebSphere Application Server Advanced Edition is installed and migrated into the same directory as a previous Advanced Single Server Edition installation, the Advanced Single Server Edition property files are lost. If you plan on manually migrating any of your property files, back up the Advanced Single Server Edition property files before installing the Advanced Edition.

Perform the following steps to install WebSphere Application Server:

  1. See the WebSphere Application Server Supported Hardware, Software, and APIs Web site at www.ibm.com/software/webservers/appserv/doc/latest/prereq.htm to learn which products and fix levels are supported for use with WebSphere Application Server on your operating system.

    The following supported software is provided in addition to WebSphere Application Server in the product package:

    • Java 2TM Software Developer's Kit (SDK) 1.3.0
    • IBM HTTP Server 1.3.19
    • IBM DB2 Universal Database (UDB) 7.2

  2. Follow the installation instructions appropriate for your choice of supported operating system, Web server, and database. Installation instructions in HTML and PDF formats can be accessed by clicking one of the following links:

    Note for all operating systems: If you plan to use iPlanet (a.k.a. Sun ONE) Web Server 6.0.1 with WebSphere Application Server 4.0.1, you must modify the installation process according to these steps, or the installation will be incomplete:

    1. Install WebSphere Application Server 4.0.1, selecting IBM HTTP Server as the Web server.
    2. Install Fix Pack 5 and select the option to update the iPlanet Web server configuration. Click Yes and select iPlanet 6.
    3. Start the administrative server, default server, and iPlanet 6.
    4. If you encounter an error when serving http:///servlet/snoop, open the iPlanet administrative interface (http://hostname:8888). Select your HTTP server and check Manage. On the Java tab, clear both boxes (Enable Java globally and Enable default class).
    5. Click Apply and restart the Web server.
    6. Regenerate the plug-in and restart the Web server.

    If you are installing a Web server on a remote machine, use the WebSphere Application Server installer to install the plug-in. This lets you apply any subsequent fix packs using the WebSphere Application Server fix pack installer. Choose a custom installation and deselect all features but the plug-in. If you are installing IBM HTTP Server, deselect all features but the IBM HTTP Server and the plug-in for IBM HTTP Server.

    Note: There are limitations when using the Secure Sockets Layer plug-in with the Apache Web server and Solaris Operating System, Linux and HP-UX. See the respective installation instructions for specific problems in each of these environments.

Perform any post-installation processing necessary to enable the database repository

In some cases, you must performs some post installation processing to create the database tables and default configuration. See the "Creating the database tables and default configuration section in "Administering WebSphere administrative servers (overview): WebSphere Application Server." There are special cases for Oracle and Sybase Version 12.5.

Installing WebSphere Application Server on multiple machines

If you want to install identical configurations of WebSphere Application Server on multiple machines, see "Performing identical installations on multiple machines." It outlines the use of the XML export/import facilities and silent installation functionality that will enable you to perform identical installations of WebSphere Application Server on multiple machines.

Migrating data from a previous version of WebSphere Application Server

If you are using a version of WebSphere Application Server previous to Version 4.0 and have data that you want to use with Version 4.0, see "Migration overview" for instructions.

Uninstalling WebSphere Application Server

If you want to uninstall WebSphere Application Server from a Windows machine, see "Uninstalling WebSphere Application Server" for instructions.

If you want to uninstall WebSphere Application Server from a UNIX machine, see "Uninstalling WebSphere Application Server (UNIX)" for instructions.

Configuring the Merant ConnectJDBC data source for MS SQL Server for the WebSphere Application Server Advanced Single Server Edition

This information describes how to configure the Merant ConnectJDBC data source for Microsoft SQL Server on the Advanced Single Server Edition.

Before you install WebSphere Application Server, ensure that you have done the following:

  1. Installed Microsoft SQL Server and the Merant ConnectJDBC (type 4) driver.
  2. Using the SQL Server, created a user, created a database, and associated the user with that database. Write down the server name and port number MS SQL Server is using; the default port number is 1433.
  3. Started the Microsoft SQL Server service.

Add the Merant ConnectJDBC driver. See topic 6.6.0.2.2.4.7: Creating and installing drivers and data sources, for instructions.

To configure the Merant ConnectJDBC data source for MS SQL Server:

  1. In the tree view on the left of the adminstrative console, expand JDBC Drivers, expand the category for the driver you just created, and select Data Sources. A list of data sources created with the driver (initially empty) displays on the right.
  2. Click New to create a new data source.
  3. Under Properties, do the following:
    1. Type a name for your data source. The name will be used to identify your data source on the data sources list.
    2. Type a JNDI name for applications to look up your data source (for example, jdbc/myDataSource).
    3. Optionally, type a description and specify a category.
    4. Type the name of an existing MS SQL Server database to use for your data source.
    5. Type a valid user ID to use as the default ID for connecting to MS SQL Server.
    6. Type the default password for the chosen user ID.
    7. In the remaining fields, specify the connection pooling properties as you would for any other data source.
  4. Under Driver Specific Settings, click Properties and set values for the resource properties according to your configuration. Click on the serverName link and do the following:
    1. Leave the values for Name and Type as is. Only change these values when adding in new properties.
    2. For Value, type the name of the server where you are running SQL Server (for example, localhost).
    3. Optionally, type a description or change the existing description to any value.
    4. Click OK. The serverName property updates.

    If necessary, update the portNumber, disable2Phase, and selectMethod properties. Then, click OK on the Resource Properties panel.

  5. Click OK on the Data Sources panel to add your data source to the list.
  6. Click Save in the top frame to save your data source configuration.
  7. Expand the ConnectJDBC driver entry you created under Resources and JDBC Drivers, select DataSources, and verify that your data source is in the list on the Data Sources panel.

Go to previous article: Finding product prerequisite information Go to next article: Migration overview

 

 
Go to previous article: Finding product prerequisite information Go to next article: Migration overview