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


Creating a deployment manager and choosing a deployment environment pattern

Learn how to create a new deployment manager and choose a deployment environment pattern.

About this task

This procedure assumes that you want to create a new deployment manager and choose a deployment environment pattern. As a result of following the procedure in Installing WebSphere ESB with a deployment environment interactively, you are viewing the Administrative security panel. Perform the following steps to complete your installation.
Procedure
  1. In the Administrative security panel, configure administrative security for your installation. You must use administrative security for a Deployment environment installation. Supply an administrative ID and password to log into the administrative tools and click Next. The administrative user is created in a repository within WebSphere ESB. After installation completes, you can add more users, groups, or external repositories.

    The "Deployment manager and deployment environment pattern" panel is displayed.

  2. On the "Deployment manager and deployment environment pattern" panel, choose the deployment environment pattern to use with your installation.
    Perform the following steps:
    1. Select the deployment environment pattern you want for your installation:
      • Remote Messaging and Remote Support: defines one cluster for the application deployment, one remote cluster for the messaging infrastructure, and one remote cluster for the Common Event Infrastructure and other support applications. This pattern configures a setup that performs well for most of your business integration needs. When in doubt, select this pattern.
      • Remote Messaging: defines one cluster for the application deployment and one remote cluster for the messaging infrastructure. The Common Event Infrastructure and other support applications are configured on the application deployment cluster.
      • Single Cluster: defines one cluster for the application deployment. Both messaging infrastructure and Common Event Infrastructure with support applications are also configured on the application deployment target cluster.

      See the following topics for more information:

      • Deployment environment patterns – A deployment environment pattern specifies the constraints and requirements of the components and resources involved in a deployment environment. The patterns are designed to meet the needs of most business requirements and are intended to help you create a deployment environment in the most straightforward way.
      • Deployment environment functions – To design a robust deployment environment, you need to understand the functionality each cluster can provide in a particular IBM-supplied deployment environment pattern or a custom deployment environment. This knowledge can help you make the correct decisions as to which deployment environment pattern best meets your needs.
    2. Click Next. The Deployment manager database configuration pattern panel is displayed.
  3. On the Deployment manager database configuration pattern panel, choose the database to use with your installation.
    Perform the following steps:
    1. Select the database product to use with your installation from the drop-down list.
      Important: When you perform a Deployment environment installation with the installation wizard, you are limited to using only the following subset of the total supported database products for WebSphere ESB:
      • Derby Network Server
      • DB2 Universal Database™
      • Oracle 9i, 10g, or 11g
      You can use other supported database products not in this list (with the exception of Informix® and Microsoft® SQL Server – these are not supported in deployment environment configurations). However, to use other database products, you must create your deployment manager using the Profile Management Tool. See Creating profiles for more information. Also i5/OS® systems cannot use databases created with the DB2 Universal Database product on local i5/OS systems. The DB2 Universal Database product can be used only on remote servers that reside on non-i5/OS systems. This requires a JDBC driver type 4.
    2. In the Database name field, accept the default value of WPRCSDB or enter the name of the Common database to be used with your installation.
    3. Click Next. The Additional database configuration panel is displayed with fields specific to the database product you selected.
    4. Review the topic Additional database configuration panel for information on how to complete this panel. When you've completed entering information on the Additional database configuration panel, click Next. 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.
  4. 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 Network Deployment with Web Services Feature Pack, 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.
      For i5/OS operating system Restriction: On i5/OS platforms: If the WebSphere Application Server Network Deployment installation with Web Services Feature Pack is at an earlier service level and the WebSphere ESB installation is being done remotely from a Windows® client, then the WebSphere Application Server Network Deployment with Web Services Feature Pack 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 Web Services Feature Pack 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 Web Services Feature Pack installation.
      For i5/OS operating system Restriction: On i5/OS platforms: If you selected the WebSphere ESB samples feature and you are installing over an installation of WebSphere Application Server Network Deployment Web Services Feature Pack that does not have the Samples gallery feature installed, then the Samples Gallery feature must be added to WebSphere Application Server Network Deployment Web Services Feature Pack using a local silent installation from the i5/OS system before continuing with this installation.

    If you chose to install WebSphere ESB over an existing version of WebSphere Application Server Network Deployment, the installation wizard first installs the Web Services Feature Pack and then takes one or more actions mentioned above to bring the installation up to the appropriate level.

    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.

  5. Ensure that the check box to start the First steps console is selected, and click Finish to close the installation wizard and start the First steps console.

Results

If the Installation results panel indicates Success, the components you selected were installed successfully, and your deployment environment 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 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 your database if it is not already active. Then start the WebSphere ESB deployment manager from its First steps console to verify that your installation is operating properly. See Options on the First steps console for more details. The First steps console also includes links to perform verification tests and to start the Profile Management Tool, with which you can create WebSphere ESB custom profiles to define additional cluster members in the deployment environment.


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