Installing additional features on an existing application server product

You can install additional features on an existing IBM® WebSphere® Application Server Network Deployment for IBM i installation.

Before you begin

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

About this task

When you run the GUI installation tool, you specify installation options interactively during the installation process. You can also choose to silently install the features locally using the response file.

Use the following procedure to add a feature to an existing application server 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 IBM i server. The host server jobs allow the installation code to run on IBM i.
    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.

    Stop all server processes in all profiles associated with the target product instance. For example, issue the following command from the profile_root/bin directory to stop the server1 process in the application server profile:

    ./stopServer server1

    If a server is running and security is enabled, use the following command:

    ./stopServer server1 -user user_ID -password password
    If you have multiple servers, you can use the serverStatus command to find running application servers associated with the target product instance. Issue the following command from the profile_root/bin directory to determine which servers, if any, are running:
    ./serverStatus -all
  5. Stop the node agent process with the stopNode command.
    Stop the node agent processes associated with the target product instance. 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 
    
    If servers are running and security is enabled, use the following command:
    ./stopNode -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. The example assumes you have administrative security enabled.
    ./stopManager -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. Access the root directory of the application server installation image on your hard disk, or insert the WebSphere Application Server Network Deployment for IBM i disk into the disk drive of your Windows workstation. The application server product installer is spanned across multiple CDs. If you are installing the product from CD, you might be prompted during the installation for the next CD depending on which CD contains the feature you are installing.
    Avoid trouble Avoid trouble: The installer might fail if you are installing the product from a CD or DVD. To prevent this possibility, you can either install the features silently on the local machine, or run the install program with an additional option. To run the installer with an additional option, cancel the launchpad application if it was initiated by the Windows autorun feature, and invoke the installer from a command line with the following option:
    install.exe -W failurerecoverysequence.active=false
    gotcha

    Do not use the product Windows disk or any other operating system disk 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 both the IBM and the non-IBM terms, 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 optional features 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. The optional features panel is displayed.
    There are several features available:
    • Install the sample applications

      Installs the samples applications for learning and demonstration environments. The samples are not recommended for installation on production environments.

    • Install non-English language packages for the administrative console

      Installs all the non-English language files for using the administrative console from machines with non-English locales. If you do not select this option then only the English language pack is installed.

    • Install non-English language packages for the application server runtime environment

      Installs all the non-English language files that support the application server runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.

    It is recommended that you add the sample applications if you are also adding other features to the installation. You might experience some error messages if you do not select the samples applications with your other features. However, these messages can be safely ignored and the feature installation will proceed successfully.

    Select the features you want to install and click Next.

    Avoid trouble Avoid trouble: You might want to defer installing features, such as language packs and samples, to save disk space. However, consider installing the features if there is a chance you might use them in the future. If you choose not to install the features and then later install maintenance, you will have to uninstall all maintenance, install the features, and then reapply all maintenance or the features might be corrupted.gotcha
  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 application server 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 or the manageprofiles command to create additional profiles.

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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 2:38:31 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=tins_is_features
File name: tins_is_features.html