[Version 5.0.2 and later]Installing additional features on the deployment manager

This topic describes how to install additional features onto an existing Network Deployment product to update the deployment manager node.

Before you begin

You can add features to a deployment manager node at any time, by running the Installation wizard again. 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.

You can add features to Integration Server on a deployment manager node at any time, by running the Installation wizard again and choosing to add features.

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

[5.0 only][Version 5.0.2]

Product Link to installation procedure Label on product CD
(Base) WebSphere Application Server Base product installation Application Server, IBM HTTP Server
Network Deployment Network Deployment installation (which links to this procedure!) Deployment Manager
Enterprise Enterprise installation Enterprise Application Server


Why and when to perform this task

Use the following procedure to avoid component regression problems when installing additional features.

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.
    You can restore it with the restoreConfig command although the configuration that you restore does not include any features that you add after backing up the configuration.

    For example, issue the following command from the install_root/bin directory of the deployment manager node on a Linux system:

    #./backupConfig.sh /tmp/my_backup_2004-06-03.zip -user user_ID -password password

    See backupConfig command for more information.

  3. Stop the deployment manager with the stopManager command.
    Issue the stopManager command from the install_root/bin directory of the Network Deployment product. For example, use the following command on a Linux system:
    #./stopManager.sh -user user_ID -password password
    See stopManager command for more information.
  4. 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.
  5. Uninstall any cumulative fixes you installed, starting with the last one and finishing with the first one.
  6. Uninstall any fix packs you installed, starting with the last one and finishing with the first one.
  7. Log off and back on or reboot a Windows system.
  8. Insert the product CD labeled, Deployment Manager.
    Windows systems and most Linux systems are configured to automatically mount CD-ROM drives.
  9. Open a shell window and mount the CD-ROM drive if necessary.
  10. 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.

    The rest of this procedure assumes that you are using the Installation wizard. Corresponding entries in the response file exist for every prompt that is described as part of the wizard. Comments in the response file describe how to customize the options.

  11. 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.

  12. 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.
  13. 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.

    Previously installed features are checked and grayed out with the term (Installed) at the end of the feature name.

  14. Skip the coexistence panel that lets you select new ports, if it appears.
  15. Select features to install and click Next to continue.
    A description of each feature appears at the bottom of the panel when you roll the cursor over the feature.

    Choose from these features:

    Deployment manager
    Installs the product run time. It provides high performance and scalability across your deployment environment. It includes multiserver administration, server clustering, load balancing and workload management for hosting highly available e-business applications.
    Web services
    The UDDI registry and the IBM Web Services Gateway are enterprise applications that you can deploy to:
    • A base WebSphere Application Server product node federated within a Network Deployment cell
    • A stand-alone base WebSphere Application Server node
    The Network Deployment product is not a stand-alone product for running enterprise applications. To deploy UDDI or the gateway, install the base WebSphere Application Server product. Although it is not installed by default, a copy of the base WebSphere Application Server product is packaged with the Network Deployment product.

    [5.0 only][Version 5.0.2]See Developing Web services for more information.

    UDDI Registry
    Installs a Version 2 compliant universal description, discovery, and identification (UDDI) registry, accessible from the UDDI registry user console application, or from SOAP or EJB interfaces.

    [5.0 only][Version 5.0.2]See IBM WebSphere UDDI Registry for more information.

    Web Services Gateway
    Includes a gateway between Internet and intranet environments so that clients can invoke Web services safely from outside a firewall. The gateway uses automatic protocol conversion for externalizing Web services.

    [5.0 only][Version 5.0.2]See Enabling Web services through the IBM Web Services Gateway for more information.

    Embedded messaging client
    Includes the client necessary for the administration of WebSphere MQ Queues and the mapping of JMS resources into the deployment manager JNDI namespace. It is the same client that you can install as part of the base product embedded messaging feature.

    You can run the uninstaller program to remove all installed features.

  16. Review the features summary information and click Next to install the product code or Back to change your specifications.
    The Summary panel displays the directory for the embedded messaging feature incorrectly on all Linux and UNIX-based platforms, as /opt/IBM/WebSphere MQ. Actual installation locations are /usr/mqm on AIX systems, and /opt/mqm on Linux and all UNIX-based platforms except AIX.
    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 errors occur with its installation.
  17. Review the install_root/logs/mq_install.log installation log if it displays. Click Next to continue.
  18. Click Next to register the product, or clear the check box and click Next to register at a later time.
    The Registration panel is in English when the machine locale uses a double byte character set (DBCS) language.

    You can register the product now by using the link on this panel or later, by using the Web address in the install_root/prt/readme_prt.txt file. The Web address in the file is encoded for your locale. A known problem for some locales corrupts the Web address so that it is similar to the following example. (The Web address is all one line in the file. The following example shows the address on two lines for clarity.)

    http%3A%2F%2Fwww.ibm.com%2Fsoftware%2Fwebprt%2Fregister%2Fprodreg.nsf%
       2Fcontact%3FOpenForm%26lang%3DENU%26pid%3D45P8842%26q2%3DWindows+2000

    Use one of the following Web addresses if your install_root/prt/readme_prt.txt file is corrupt:

    The Installation wizard starts the First Steps tool. See firststeps command for more information.

  19. Verify the success of the installer program by examining the Exit summary panel and the install_root/logs/log.txt for installation status.
    ISMP records a success message in the install_root/logs/log.txt file: "INSTFIN: The installation is complete." The log is the only source of status information for a silent installation.

    [Version 5.0.2]Verify the success of the installer by querying the response code:

    echo $? 
    The return code from the installer is "1" to indicate success; any other response code indicates failure.

    Look for severe errors that the installer records in the install_root/logs/log.txt file in the installation root directory to verify that no file system or other unusual errors occurred during installation.

    If the install_root/logs/log.txt file does not contain a record of any problems but problems exist, verify or troubleshoot the installation, as described in Troubleshooting the installation and in Installation component troubleshooting tips.

    If problems exist, correct them, uninstall the product, as described in Uninstalling the product, log off as root and back on, and reinstall.

  20. Click Finish to close the Installation wizard.
  21. Install the most current fix pack for the WebSphere Application Server Network Deployment product.
    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.
  22. Install the most current cumulative fix for the WebSphere Application Server Network Deployment product.
  23. Install any interim fixes to bring the node back to its previous fix level.
  24. Linux and UNIX only: Issue write permissions for the new files to your non-root user group (wasgroup, for example), if you run the deployment manager or a nodeagent from a non-root user.

    See the following topics for more information:

  25. Start the deployment manager with the startManager command.
    For example, start the deployment manager from the install_root/bin directory of the Network Deployment product on a Linux system with the following command:
    # ./startManager.sh 

    See startManager command for more information.

  26. Use the administrative console on the deployment manager node to synchronize all node agents.
    This action synchronizes the master cell configuration with all of the Application Server nodes.

Results

You have now successfully installed additional features for the WebSphere Application Server Network Deployment product.


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:   featuresn
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_featuresn.html

Library | Support | Terms of Use | Feedback