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


Installing WebSphere ESB and creating a profile interactively

Use this procedure to install WebSphere® ESB and create a profile using the installation wizard graphical user interface (GUI). You can install WebSphere Application Server Network Deployment with Web Services Feature Pack as part of your installation. You can also install WebSphere ESB over an existing installation of WebSphere Application Server or WebSphere Application Server Network Deployment, version 6.1.x.

About this task

Perform the following procedure to make those choices. This topic assumes that you have started the installation wizard, checked for prerequisites and existing WebSphere installations, and chosen to perform a Typical installation, by following the procedure in Installing WebSphere ESB interactively. The Features selection panel is displayed.

Procedure
  1. From the Features selection panel, select the feature you want to install and click Next.

    See Installable features for a description of the feature you can select from this panel.

    The next step depends on whether or not you are installing over an existing WebSphere Application Server or WebSphere Application Server Network Deployment installation.

    Installation status Next step
    You are installing over an existing installation of WebSphere Application Server or WebSphere Application Server Network Deployment.
    Important: The user who installs WebSphere ESB must be the same user who installed WebSphere Application Server or WebSphere Application Server Network Deployment. You cannot install over an existing installation that contains parenthesis in the installation path.
    The WebSphere ESB environments panel is displayed. Proceed to step 3.
    You are not installing over an existing installation of WebSphere Application Server or WebSphere Application Server Network Deployment. The Installation location panel is displayed. Proceed to step 2.
  2. In the Installation location panel, accept the default installation root directory for the products, or specify a different directory, and click Next.
    Note: The installation path cannot contain parentheses.

    For i5/OS operating system On i5/OS® platforms: The Installation location panel on i5/OS systems also lets you specify the profile installation directory.

    For Linux operating systemFor UNIX operating systemFor Windows operating system On Linux®, UNIX®, and Windows® platforms: The installation wizard presents a system-owned, default installation root directory for root or Administrator users. It presents a different user-owned, default installation root directory for non-root users.

    See Default installation directories for the product, profiles, and tools for information on default installation directories and how they are determined by the installation wizard.

    The installation wizard verifies that the installation location is fully qualified, formed correctly, can be written to by the user ID performing the installation, and has sufficient disk space (including any required temporary space) to complete the installation successfully. If you do not have enough space, stop the installation program, free space by deleting unused files and emptying the recycle bin, and restart the installation.

    Important:
    • You must provide a value for the installation root directory to continue.
    • For i5/OS operating systemFor Linux operating systemFor UNIX operating system On i5/OS, Linux, and UNIX platforms: Do not use symbolic links as the installation root directory; they are not supported. Also, do not use spaces in the directory path.
    • For Windows operating system On Windows platforms: Do not use a semicolon in the directory name on Windows systems (a semicolon is the character used to construct the class path on Windows systems). WebSphere ESB cannot install properly on a Windows platform if the target directory includes a semicolon.
    On completion of this step the WebSphere ESB environments panel is displayed.
  3. In the WebSphere ESB environments panel, choose the type of profile you want to create (or None if you do not want to create a profile at this time), and then click Next. The next step depends on your selection.
    Profile type Next step
    Stand-alone server or Deployment manager The Administrative security panel is displayed. Proceed to step 5.
    Custom The Federation panel is displayed. (A custom profile has an empty node that you must federate to use it.) Proceed to step 4.
    None
    Tip: If you are creating a production environment, select None and create profiles later either with the Profile Management Tool or silently.
    A warning panel alerts you that your installation cannot function without at least one profile. Do one of the following:
    • Click Yes to continue without creating a profile. The Installation summary panel is displayed. Proceed to step 6. After you complete your installation, the final panel of the installation wizard will provide you with a link to open the Profile Management Tool, which provides several options for creating or augmenting new profiles.
    • Click No to return to the WebSphere ESB environments panel.
  4. For custom profiles only: In the Federation panel, choose to federate the node into the deployment manager now as part of the profile creation, or at a later time and apart from profile creation.
    Important: Federate the custom node at this time only if all of the following are true:
    • No other node is being federated at the same time. (Node federation must be serialized.)
    • The deployment manager is running.
    • The deployment manager is a WebSphere ESB deployment manager at the same version level or higher as the custom profile you are creating.
    • The deployment manager has a JMX administrative port enabled. The default protocol is SOAP.
    • You do not plan to use this custom node as a migration target.
    Do not federate the custom node at this time if any one of the following is true:
    • Another profile is being federated. (Node federation must be serialized.)
    • The deployment manager is not running or you are not sure if it is running.
    • The deployment manager has not yet been augmented into a WebSphere ESB deployment manager.
    • The deployment manager does not have a JMX administrative port enabled.
    • The deployment manager is reconfigured to use the non-default remote method invocation (RMI) as the preferred Java™ Management Extensions (JMX) connector. (Select System administration > Deployment manager > Administration services in the administrative console of the deployment manager to verify the preferred connector type.)
    • You plan to use the profile as a migration target profile.
    To federate the node now as part of the profile creation, perform the following steps:
    1. Specify the host name or IP address and SOAP port of the deployment manager, and an authentication user ID and password if administrative security is enabled on the deployment manager. To find the SOAP port number, open the AboutThisProfile.txt file for the deployment manager located in profile_root/logs/, and review the value for "SOAP connector port."
    2. Leave the Federate this managed node later using the addNode command check box cleared.
    3. Click Next. The installation wizard verifies that the deployment manager exists, can be contacted, and that the authentication user ID and password are valid for that deployment manager (if it is secured). The Installation summary panel is displayed.
    4. Proceed to step 6.
    If you attempt to federate a custom node when the deployment manager is not running or is not available for other reasons, a warning panel prevents you from continuing. If this warning panel appears, click OK to exit from it, and then make different selections on the Federation panel.

    To federate the node at a later time and apart from profile creation, perform the following steps:

    1. Select the Federate this managed node later using the addNode command check box.
    2. Click Next. The Installation summary panel is displayed.
    3. Proceed to step 6.

    See Federating custom nodes to a deployment manager for more information on how to federate a node by using the addNode command. Read more about this command in the addNode command topic in the WebSphere Application Server Network Deployment information center.

  5. For WebSphere ESB stand-alone server and deployment manager profiles only: In the Administrative security panel, configure administrative security for your installation. Leave the Enable administrative security check box selected and supply an administrative ID and password to enable security, or clear the check box to disable security. Then click Next.
    For WebSphere Process Server stand-alone profiles only: For stand-alone server profiles, the installer configures Business Space using Derby Embedded.
    Tip: Record the administrative ID and password and store in a secured area. You cannot log onto the administrative console or use WebSphere ESB unless you know these values.

    In environments where you plan to have multiple stand-alone servers, the security policy of each server profile is independent of the others. Changes to the security policies in one server profile are not synchronized with the other profiles.

    The Installation summary panel is displayed.

    Note: An integrated installation package (IIP) containing WebSphere Application Server Network Deployment and Feature Pack for Web Services is installed as part of the WebSphere Process Server installation. If IIP validation fails, an error panel displays and provides information on how to correct the problem.
  6. In the Installation summary panel, review the components that will be installed, the amount of space they will consume, and where they will be located on the system, and click Next to install or Back to change your specifications.

    The installation wizard creates the uninstaller program and shows a progress panel to indicate that components are being installed.

    If you chose to install WebSphere ESB over an existing version of WebSphere Application Server or WebSphere Application Server Network Deployment, the installation wizard examines it and takes one of the following actions:
    • If the installation is at the correct service level, the installation wizard does nothing.
    • If the installation is at an earlier service level, the installation wizard applies the necessary fixes to bring the installation up to the appropriate level and also applies any necessary interim fixes.
    • If you selected the WebSphere ESB Samples feature, and you are installing over an installation of WebSphere Application Server Network Deployment that does not have its Samples gallery feature installed, the installation wizard adds the Samples gallery feature silently to the WebSphere Application Server Network Deployment installation.
      Restriction: The WebSphere ESB Samples feature can be incrementally installed only over a WebSphere Application Server Network Deployment installation, not over a WebSphere Application Server installation. Thus, if you select the WebSphere ESB Samples feature, and you are installing WebSphere ESB over an installation of WebSphere Application Server that does not have its Samples gallery feature installed, the Sample applications gallery feature is not added silently to the WebSphere Application Server installation.
      For i5/OS operating system Restriction: On i5/OS platforms: If the WebSphere Application Server Network Deployment installation is at an earlier service level and the WebSphere ESB installation is being performed remotely from a Windows client, then WebSphere Application Server Network Deployment must be updated using a local silent installation from the i5/OS system before continuing with this installation. If you selected the WebSphere ESB Samples feature and you are installing over an installation of WebSphere Application Server Network Deployment that does not have its Samples gallery feature installed, then the Samples Gallery feature must be added to WebSphere Application Server Network Deployment using a local silent installation from the i5/OS system before continuing with this installation.

    At the end of the installation, the Installation results panel is displayed with a Success indication.

    Attention:

    If errors are detected during installation, other messages might appear in place of Success.

    A message of Partial success indicates that the installation completed but errors were generated. If an installation is partially successful, the Installation results panel identifies the exact log files required to troubleshoot the problems, together with their locations in your installation. The log files include the following:
    • install_error.log
    • log.txt
    Both files are located by default in the following directory:
    • For i5/OS operating systemFor Linux operating systemFor UNIX operating system On i5/OS, Linux, and UNIX platforms: install_root/logs/wbi/install
    • For Windows operating system On Windows platforms: install_root\logs\wbi\install

    See descriptions of these log files in Installation and profile creation log files.

    A message of Failed indicates that the installation failed completely. If an installation fails completely, the Installation results panel identifies the locations of log files useful in troubleshooting problems:
    • Log files related to installation, located by default in the following directory:
      • For i5/OS operating systemFor Linux operating systemFor UNIX operating system On i5/OS, Linux, and UNIX platforms: install_root/logs/wbi/install
      • For Windows operating system On Windows platforms: install_root\logs\wbi\install
    • Temporary log files, located by default in the following directory:
      • For i5/OS operating systemFor Linux operating systemFor UNIX operating system On i5/OS, Linux, and UNIX platforms: user_home/wbilogs
      • For Windows operating system On Windows platforms: user_home\wbilogs

    See descriptions of relevant log files in Installation and profile creation log files.

  7. Complete the installation. The actions you take to complete the installation differ depending on whether you created a profile during installation. On the Installation results panel, take one of the following actions depending on whether you created a profile during installation:
    Profile status Next step
    You created a profile Ensure the check box to launch the First steps console is selected, and click Finish to close the installation wizard and start the First steps console.
    You did not create a profile The next step depends on whether you want to create a new profile now:
    • If you want to create a new profile, leave the check box beside Create a new WebSphere ESB profile using the Profile Management Tool selected and click Finish. The installation wizard closes and the Profile Management Tool starts. See Creating profiles using the Profile Management Tool or Augmenting profiles using the Profile Management Tool for instructions on how to use this tool to create new WebSphere ESB profiles or augment existing profiles into WebSphere ESB profiles.
    • If you do not want to create a new profile, clear the check box beside Create a new WebSphere ESB profile using the Profile Management Tool and click Finish.
      Attention: To have an operational environment, a WebSphere ESB stand-alone server profile or deployment manager profile with managed nodes must exist.

Results

If the Installation results panel indicates Success, the components you selected were installed successfully, and if you created a profile, it was created successfully.

What to do next

Install the most recent WebSphere ESB fix pack on top of the installation (if any fix packs exist at the time of installation). For information about installing fix packs on WebSphere ESB, see the instructions under Recommended Fixes on the support pages at http://www.ibm.com/software/integration/wsesb/support/.

For Linux operating systemFor UNIX operating system On Linux and UNIX, platforms: If you removed the freeware directory from your PATH (instructed in an earlier topic), add the freeware directory back to the PATH variable.

Start the WebSphere ESB stand-alone server or deployment manager profile from its First steps console to verify that your installation is operating properly. See Options on the First steps console for more details.

You can also use the installation verification tools to verify your installation. See Verifying the product installation for more information.


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_gui_install.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).