WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Running a customized installation package interactively to add maintenance to an existing WebSphere ESB installation: basic steps

There are several options for installing a customized installation package (CIP) that includes WebSphere® ESB and one or more maintenance packages. You can use the CIP Installation wizard to install features that are included in the CIP. The Installation wizard also installs maintenance packages that are included in the CIP. The steps that are common to each of the possible use-case scenarios are presented.

Before you begin

You must log onto the system with appropriate permissions to install the custom install package. There must be at least one installation of WebSphere ESB on the target system.

About this task

When you have created your CIP it will be stored as a compressed file in the directory (CIP_directory) that you indicated on the Build Information panel of the Build Definition wizard. The CIP_directory has two subdirectories: WBI and custom.wbi.

Before you can install your WebSphere ESB CIP, you must create a WebSphere Application Server Network Deployment CIP. The WAS_ND_CIP_directory contains the following directories:
  • WAS
  • custom
  • JDK

The following steps are common to each of the subsequent tasks, and must be undertaken before moving on to the specific installation scenario you have in mind.

Procedure
  1. Copy the WBI and custom.wbi to the WebSphere Application Server Network Deployment CIP directory WAS_ND_CIP_directory. When you have completed this step, WAS_ND_CIP_directory contains the following subdirectories:
    • custom.wbi
    • WBI
    • WAS
    • custom
    • JDK

    If you have the WebSphere ESB product media, and the version of the WebSphere Application Server Network Deployment CIP reported in the message about required maintenance level is lower than the version on the product media you can simply copy the WBI and custom.wbi directories to the WebSphere Application Server Network Deployment CIP directory of the install image. This overwrites the existing WBI directory.

  2. Commence the installation of your WebSphere ESB custom install package.
    Start the installation directly with the install command.
    1. Change to the WAS_ND_CIP_directory/WBI directory
    2. Issue the install command:
      • For AIX operating systemFor HP-UX operating systemFor Linux operating systemFor Solaris operating system ./install
      • For Windows operating system install.exe
    After launching the CIP installation wizard from the command line, the wizard initializes and displays the Welcome panel.

    Click Next to move on to the License agreement panel.

  3. On the License agreement panel, read the license agreement and accept its terms.

    Click I accept both the IBM and the non-IBM terms to agree to the license agreement and click Next to continue.

    After you accept the licensing terms, the installation wizard checks for a supported operating system and prerequisite patches. If you encounter a problem such as not having the right prerequisite updates on your system, cancel the installation, make the required changes, and restart the installation.

    Although the installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the supported hardware and software Web site if you have not already done so.

    The Web site lists all supported operating systems and the operating system fixes and patches that you must install to have a compliant operating system.

    Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.

  4. Complete the prerequisite check and move on to the Detect existing copy panel. Click Next when the system prerequisite check is complete.
  5. Check for previous versions of the product.

    The installation wizard checks for a previous installation at the same major product level.

    If the wizard detects a previous installation, it displays the Existing installation panel. For this task it is assumed that a previous installation exists and that you are adding features with an incremental installation.

    The CIP wizard detects all WebSphere ESB installations. You can use a CIP to do cross product installation. However, you cannot use a CIP to add features to a different product installation. For example, a WebSphere Process Server CIP cannot be used to add features to an installation of WebSphere Enterprise Service Bus.

  6. Choose to apply maintenance and add features to an existing copy of WebSphere ESB.

    Click Apply maintenance and add features to an existing copy of WebSphere ESB, then select the existing installation from the list.

    System prerequisite checking is performed on the selected installation.

What to do next

Completing the steps described in this task is insufficient to install the CIP. To complete your installation, choose the subtopic that matches your installation plans, and follow the steps described in that topic.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_if_gui_augment.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).