This topic applies only on the i5/OS operating system.

Installing additional features on an existing Network Deployment product

You can install additional features on an existing IBM WebSphere Application Server Network Deployment for i5/OS installation.

Before you begin

This topic assumes that you have an existing Network Deployment for i5/OS installation and that you want to install a feature using the installation wizard from a Windows workstation graphical user interface (GUI).

One feature is available, which installs sample applications.

About this task

When you run the GUI installation tool, you specify installation options interactively during the installation process.

Use the following procedure to add a feature to an existing Network Deployment for i5/OS installation.

Procedure

  1. If TCP/IP is not started or if you don't know if TCP/IP is started, enter the Start TCP/IP (STRTCP) command on the Control Language (CL) command line.
  2. Verify that the host server jobs are started on your iSeries server. The host server jobs allow the installation code to run on iSeries.
    Enter this command on a CL command line:
    STRHOSTSVR SERVER(*ALL)
  3. Verify that your user profile has the *ALLOBJ and *SECADM special authorities.
  4. Stop each running application server with the stopServer command.
    Stop all server processes in all profiles on the machine. For example, issue the following command from the profile_root/bin directory to stop the server1 process in the application server profile:
    ./stopServer.sh server1
    If a server is running and security is enabled, use the following command:
    ./stopServer.sh server1 -user user_ID -password password
    If you have multiple servers, you can use the serverStatus command to find running application servers. Issue the following command from the profile_root/bin directory to determine which servers, if any, are running:
    ./serverStatus.sh -all
  5. Stop the node agent process with the stopNode command.
    Stop the node agent process that might be running on the machine. For example, issue the following command from the profile_root/bin directory of a federated node on a Linux® machine to stop the node agent process:
    ./stopNode.sh 
    
    If servers are running and security is enabled, use the following command:
    ./stopNode.sh -user user_ID -password password
    
  6. Stop the deployment manager dmgr process with the stopManager command.
    Stop all dmgr processes that are running on the machine. For example, issue this command on a Linux machine from the profile_root/bin directory of the deployment manager profile:
    ./stopManager.sh -user user_ID -password password
  7. Uninstall all maintenance packages.

    You are using the product installation image to install additional features. The features have not had any maintenance applied to them. If you remove all maintenance packages, your entire product will be at the same release level. You can then reapply the maintenance packages as described in a later step.

    Start the Update Installer program with the updi_root/update command to search for and uninstall all maintenance packages.

  8. Place the WebSphere Application Server Network Deployment for i5/OS disc that provides the feature in the disc drive of your Windows workstation. The autorun feature brings up the launchpad.
    Feature Product disc
    Sample Applications WebSphere Application Server Network Deployment

    Do not use the product Windows disc or any other operating system disc from the product package.

  9. On the Welcome panel, click Next.
  10. On the next panel, if you accept the terms of the license agreement, select I accept the terms in the license agreement, then click Next. If you do not accept the terms of the license agreement, you cannot continue with the installation.
  11. After confirming that your operating system is supported and that you have installed all necessary patches, click Next to continue.

    The installation wizard checks for a previous installation at the same product level. This task describes the scenario where a previous installation exists and you are adding features with an incremental installation.

    When the wizard detects a previous installation, it displays the Existing installation panel. The panel lets you add features to the existing installation, or perform a new installation to another directory.

  12. Choose to install additional features. Click Next to continue to the Features selection panel.

    Do not change the installation directory unless another existing installation is in the directory that you specify. An incremental installation adds features to the shared binaries identified in the field.

    You can add features to the core product files at any time by running the Installation wizard again. Installing additional features does not affect profiles that you might have already created.

    When adding features during an incremental installation, the wizard displays the Features selection panel next.

  13. Select features to install and click Next.

    In Version 6.1, one feature is available, which installs sample applications.

    Table 1. Features for the WebSphere Application Server Network Deployment product
    Feature Description
    Application Server Samples Installs the Samples Gallery and Plants By WebSphere applications.

    For better performance in either a development or production environment, do not install the Samples. By omitting the Samples, you can improve application server startup time by 60 percent and save 15 percent of disk space. You can save up to 30 percent of process footprint (based on a maximum heap size of 256 MB).

    The installation wizard displays a confirmation panel.

  14. On the next panel, verify that the summary information is correct. If not, click Back to change your specifications. If the summary information is correct, click Next to install the feature.

    The InstallShield program displays messages that indicate the status of the installation and a status bar to show the progress of the installation.

    After the installation runs, the Configuration Manager progress panel is displayed. The configuration manager performs post-installation tasks and creates the default profile.

    After the installation process is complete, the summary panel displays the results of the installation process and links to additional information about the product.

  15. Select the check box to open the First Steps console, then click Finish to close the InstallShield program.
  16. For security purposes, if the host servers were not running prior to installation, it is recommended that you run the End Host Server (ENDHOSTSVR) command after the installation is complete

Results

The installation wizard installs the new feature in the existing installation root directory. The installation wizard configures the Network Deployment product for the new feature.

What to do next

Create any deployment manager profile or application server profile that your configuration requires.

Adding the samples feature does not automatically deploy the samples to existing profiles that did not have samples deployed to them initially. You must create a new profile to deploy the samples. For example, create an application server profile and select to deploy the sample applications.

Use the Profile Management tool to create profiles in the default profile_root directory or in a directory that you select.

After creating an application server profile, you can deploy an application. See Fast paths for WebSphere Application Server to get started deploying applications.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Feb 19, 2011 5:25:36 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v610web&product=was-nd-mp&topic=tins_is_featuresn
File name: tins_is_featuresn.html