[Version 5.0.2 and later]Installing deactivated Integration Server features on a base node

This topic describes how to install additional features on the WebSphere Business Integration Server Foundation product that is installed on a managed node.

Before you begin

If you encounter a problem such as not having enough temporary space or not having the right packages on your system, cancel the installation, make the required changes, and restart the installation.

The installation of new features uses the InstallShield for Multiplatforms (ISMP) wizard to perform the installation. You can use the Installation wizard or perform the installation from a command line, using the silent installation method.

Installation programs in WebSphere Application Server products

If you are adding features to the base product, see Installing additional features on a base Application Server.

This topic describes adding Integration Server features on a base node.

Why and when to perform this task

You can add features to the WebSphere Business Integration Server Foundation product on a stand-alone base node at any time, by running the Installation wizard for WebSphere Business Integration Server Foundation again.

If you are adding features to WebSphere Business Integration Server Foundation on a managed node, you cannot install certain features. The following Integration Server features are always hidden and deactivated on a federated base node:

Integration Server features that are not grayed out are available for installation on a managed base node. You do not have to unfederate the base node to add available Integration Server features.

If the managed node does not have both the administrative console feature and the administrative scripting features, the following Integration Server features are hidden and deactivated:

To install any of these deactivated features, you must remove the base node from the cell as described in the following procedure.

See Installing available Integration Server features on a base node for a procedure to install available Integration Server features on the stand-alone or managed node.u

Use the following procedure to avoid component regression problems when installing additional features to the WebSphere Business Integration Server Foundation product on a base node.

Steps for this task

  1. Log on as the root user on a Linux or UNIX system or as a user in the administrator group on a Windows system.

    You cannot install features correctly as a non-root user on a Linux or UNIX system, or as a non-administrator on a Windows system.

  2. Use the backupConfig command to save the configuration.

    The backupConfig command works well in an unfederated environment, to save the configuration of the base node. Issue the command from the install_root/bin directory of the base node.

    Use the backupConfig command to save the Network Deployment configuration so that you can restore the configuration if necessary. Although you can use the backupConfig command to save the configuration, the restoreConfig command restores the configuration without any of the deactivated features you add to the base node during this procedure.

    However, you can refer to the saved configuration after adding features and adding the base node back to the cell. Refer to the saved configuration as you use the administrative console of the deployment manager to reconfigure the base node.

    Use the following command to back up the configuration on a Linux system:

    #./backupConfig.sh /tmp/my_backup_2004-09-30.zip -user user_ID -password password

    See backupConfig command for more information.
  3. Copy configuration files if you installed the Integration Server product on a managed node after the base node was federated. If you installed the Integration Server product on a stand-alone base node before the node was federated, you can skip this step.
    Copy the following files on the base node from the install_root/config/cells/cellname/nodes/nodename/servers/server1/ directory to the install_root/config/backup/base/cells/cellname/nodes/nodename/servers/server1/ directory:
    • server-pme.xml
    • server-pme502.xml
    • server-pme51.xml
    • resources-pme.xml
    • resources-pme502.xml

    Copy the following files on the base node from the install_root/config/cells/cellname/nodes/nodename/ directory to the install_root/config/backup/base/cells/cellname/nodes/nodename/ directory:

    • resources-pme.xml
    • resources-pme502.xml

  4. Unfederate the managed node with the removeNode command.
    Removing the base node from the cell also removes the configuration for the base node, which resides at the cell level. Issue the removeNode command from the install_root/bin directory of the base Application Server. For example, on a Linux server, issue the following command:
    #./removeNode.sh -user user_ID -password password
    See removeNode command for more information.
  5. Uninstall any interim fixes, starting with the last one and finishing with the first one.
    See Uninstalling interim fixes, cumulative fixes, and fix packs for more information about how to remove an interim fix, a cumulative fix, or a fix pack.
  6. Uninstall any cumulative fixes you installed, starting with the last one and finishing with the first one.
  7. Uninstall any fix packs you installed, starting with the last one and finishing with the first one.
  8. Log off and back on or reboot a Windows system.
  9. Insert the product CD labeled, Integration Server Disk 1.
    Windows systems and most Linux systems are configured to automatically mount CD-ROM drives.
  10. Open a shell window and mount the CD-ROM drive if necessary.
  11. Start the installation with the ./launchpad.sh command or the launchpad command on a Windows system.
    See the platform-specific installation instructions if you need more information about restarting the installation from the product CD-ROM, such as instructions for mounting the CD drive.

    Corresponding entries in the response files exist for every prompt that is described as part of the wizard. Comments in the response file describe how to customize the options.

    The rest of this procedure assumes that you are using the Installation wizard.

  12. Click Next to continue.
    The license agreement displays.

    The Installation wizard does not support hot keys, such as Alt-N. You can tab to Next and press Enter to select it, for example.

    [5.0 only][Version 5.0.2]The license that the Installation wizard displays can contain characters that display incorrectly in Japanese. For example, the section labeled Part 1 does not show the number 1. These missing characters do not significantly affect the content of the license agreement.

  13. Click the radio button beside the I accept the terms in the license agreement message if you agree to the license agreement and click Next to continue.
    After you accept the licensing terms, the Installation wizard checks for prerequisites and for previous versions, with which it can either migrate or coexist.
  14. Choose to install additional features.
    The Installation wizard panel that appears when the installer program detects a previous installation at the same product level has an option for installing additional features. Select the check box labeled "Add features to the existing copy."
  15. Skip the coexistence panel that lets you select new ports, if it appears.
  16. Configure the sample business process container, if you selected it and click Next to continue.
    Specify values for the following fields:

    User ID to authenticate with the embedded messaging queue manager

    This field is the JMS user ID who authenticates the connection to the JMS provider. This user ID must have administration rights for the messaging service.

    The JMS user ID must be less than or equal to 12 characters.

    You can create the user ID later and add the user to the mqm user group. Or specify the root user as the value for the field:

    root

    Password

    Type the password for the user you specified as the JMS user ID in the first field.

    Confirmation password

    Repeat the password for the user you specified as the JMS user ID in the first field.

    Security role for the business process system administrator

    This field is the security role mapping. Specify the user or group from the domain user registry that is mapped onto the role of Business Process Administrator. The value to use depends on the local settings. For example, you can specify that the Administrator group is to perform the security role on some systems.

    The user registry can be the local operating system, Lightweight Directory Access Protocol (LDAP), or custom registry. The user or group specified must already exist in the user registry being used.

    See Using Process Choreographer for more information.

  17. Review the summary information and click Next to install the product code or Back to change your specifications.
    When the installation is complete, the wizard displays the install_root/logs/mq_install.log installation log if you selected the embedded messaging feature and if errors occur during its installation.
  18. Review the mq_install.log installation log if it displays. Click Next to continue.
    The wizard displays the Registration panel.
  19. Clear the check box and click Next on the registration panel.

    The Installation wizard starts the firststeps command.

  20. Click Finish to close the Installation wizard.
  21. Close the First Steps panel.
  22. Install the most current fix pack on the base product and the Integration Server product that is also installed on the deployment manager node.
    The deployment manager must be at the highest fix level within the cell.

    See Recommended updates for WebSphere Application Server for information about downloading and installing the upgrades. See Installing interim fixes, cumulative fixes, and fix packs for information about using the update installer program.

  23. Install the most current cumulative fix for the base product and the Integration Server product that is also installed on the deployment manager node.
  24. Install any recommended interim fixes.
  25. Linux and UNIX only: Issue write permissions for the new files to your non-root user group (wasgroup, for example), if you run the Application Server from a non-root user.
  26. Rejoin the node to the cell with the addNode command or the deployment manager administrative console.
    This action synchronizes the master cell configuration with changes you make to the Application Server configuration during the installation of the new features.
  27. Reconfigure the base node with the Network Deployment administrative console.

Results

You can successfully install additional features for the Integration Server on a managed node.


Related tasks
Installing the product
Using the Launchpad to start the installation
Installing silently
Automatically restarting WebSphere processes
Related reference
Platform-specific tips for installing and migrating
Tips for installing the embedded messaging feature



Searchable topic ID:   featureswb
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tins_featureswb.html

Library | Support | Terms of Use | Feedback