Setting up Version 5.1.x or Version 6.x and Version 7.0 coexistence

You can install WebSphere® Application Server Version 7.0 to coexist with another installation instance of Version 5.1.x or Version 6.x.

Before you begin

Read Overview of migration, coexistence, and interoperability and Premigration considerations.

Procedure

  1. Be aware of the basic rules of WebSphere Application Server coexistence.

    Each installation of the base product is a standalone application server with its own set of unique configuration files.

    Be aware of the following multiple-instance limitations:
    • If you install more than one instance, the most recent installation is the only one in the operating system registry.
    • To uninstall a registered product instance, always use the operating-system removal program, such as the Add/Remove Program utility on Windows® platforms. To uninstall an unregistered instance, use Uninstall.exe or the uninstall command in the app_server_root/_uninstall directory that matches the instance that you intend to remove.
    Reasons to use multiple installation instances include the following items:
    • You can achieve complete isolation between each WebSphere Application Server instance. You can uninstall one instance independently of the others.
    • You can install the base WebSphere Application Server more than once on the same machine.
    • You can install the base Version 5.1.x or Version 6.x product and the Version 7.0 product on the same machine.
    Reasons to not use multiple installation instances include the following items:
    • The machine might have a hard-disk space constraint.
    • You can use the operating system registry to locate the last installed instance of a WebSphere Application Server product only.

      When you install any product a second time, the last installation is the one that is displayed in the registry.

    • Uninstalling the last instance removes any record of the product in the registry.

      Suppose you have installed three instances of the base WebSphere Application Server product. You use the remove program function of the operating system to uninstall the registered third copy of the base product. A registry record no longer exists that indicates the existence of the other two installation instances. Other applications cannot use a query of the operating system registry to detect the presence of either base WebSphere Application Server product instance.

    The "Creating profiles using the graphical user interface" article in the information center describes installing the WebSphere Application Server product once and creating multiple profiles.

  2. Use the Installation wizard to install another instance.

    Read the "Installing the product and additional software" article in the information center for more information.

    If you intend to share a single Web server among installations, install the appropriate Version 7.0 Web server plug-in using the standalone Web server Plug-in installation wizard that is provided on the WebSphere Application Server product disk.

  3. Share a Web server among multiple installation instances.
    1. Use the Plug-in installation wizard to select a Web server plug-in.
    2. Use the administrative console to generate the plug-in configuration files for every installation instance and merge them into one primary configuration.
    3. Use the administrative console to replace the original plugin-cfg.xml file with the primary file on the Web server.
    You can access samples from only one of the installation instances.
  4. Change the port assignments in the configuration files if you have a node that you cannot start because of port conflicts.

    Read Port number settings in WebSphere Application Server versions for more information.

    Note: If ports are already defined in a configuration being migrated, the migration tools fix the port conflicts in the Version 7.0 configuration and log the changes for your verification .

What to do next

Tip: If you are using a WebSphere Application Server for z/OS Version 5.1 node with a Version 7.0 deployment manager, make sure that you specify "false" for the -ignoreCase parameter on the SAF registry. Otherwise, the Version 5.1 node agent might send a lowercase realm name over in the LTPA token and cause a realm mismatch.



In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 12:47:02 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-express-dist&topic=tmig_6coexist70
File name: tmig_6coexist70.html