Install a CIP using a Windows workstation graphical interface

Install a CIP using a Windows workstation graphical interface

One CIP installation alternative is to install WebSphere Application Server for IBM i from a Windows workstation GUI.
This page assumes that we have a CIP image created using the Installation Factory and to install WAS from the CIP. See .
When you run the GUI installation tool, you specify installation options interactively during the installation process.
Use this procedure to install WebSphere Application Server for IBM i from a CIP with the GUI installation program:

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.
Verify that the host server jobs are started on the 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)

Verify that the user profile has the *ALLOBJ and *SECADM special authorities.
Place the CIP for IBM i disc in the disc drive of the Windows workstation. The autorun feature brings up the launchpad.
Do not use the IBM WAS Windows disc or any other operating system platform disc from WAS package.
Click Launch the installation wizard for WAS.
Enter the name of the iSeries server where we are installing WebSphere Application Server for IBM i and your corresponding IBM i login information, then click OK.
You also must enter a valid user ID and password for the server. Your profile must have *ALLOBJ and *SECADM special authorities for this step.
The installation wizard initializes and then displays the Welcome panel.
Click Next to continue.
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, we cannot continue with the installation.
The system prerequisites check verifies that the server meets the minimum requirements to install WAS ND. If the prerequisites are met, click Next. If the prerequisites are not met, we can continue the installation. However, IBM recommends that you exit the installation wizard and make the required changes.
If more than one Java™ SE Development Kit 6 (JDK 6) option is installed on the machine, then select one of the following.

IBM Technology for JDK 6 - 32 bit (5722-JV1 or 5761JV1 option 11)
IBM Technology for JDK 6 - 64 bit (5722-JV1 or 5761JV1 option 12)
IBM Development Kit for Java 1.6 (5722-JV1 or 5761JV1 option 10)

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 admin 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 appserver runtime environment
Installs all the non-English language files that support the appserver runtime environment such as the wsadmin tool and logging. If you do not select this option then only the English language pack is installed.

If you choose not to install a feature at this time, then we can run the installer later and add features to this installation. Select the features you want to install and click Next.
Avoid trouble: We 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 we 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.
The next panel displays WAS installation root directory, the default profile location, and WAS library name. Accept or change these values, then click Next.
The product installation root directory for WAS for IBM i contains the core product files. It is referred to in many information center examples as the .
The default profile location for WAS for IBM i contains the configurable files for the profile. This directory is referred to in many information center examples as the . The default profile location is the directory under which the profile registry and profiles directory are created. The default profile is created under /profiles/default. The profile registry is created under /profileRegistry.
WAS ND v7.0 library is often spelled out in information center examples, but it might also be referred to as the
Select an initial server environment on the WebSphere Application Server environments panel. The following values are valid:
Table 1. Profile types

Profile Type Description

Management
Create a management profile that provides the servers and services necessary to manage the WebSphere environment. We can select one of the following management profile types on the following panel:

Administrative agent

Application server
Create a standalone appserver profile.

None
Do not create a profile during installation. However, if you do not create a profile during installation, then create a profile after installation to have an operational product.

On the next panel, choose whether to enable admin security. If enabled, specify a user name and password to access the administrative tools. Click Next to continue.
The user ID and password do not need to be a system user ID and password or an LDAP user ID and password. The ID-and-password pair specified are stored in the user registry and used for admin security for the default profile.
Click Finish to close the InstallShield program.
For security purposes, if the host servers were not running prior to installation, IBM recommends that you run the End Host Server (ENDHOSTSVR) command after the installation is complete

Results

This procedure results in installing WAS from a Windows workstation GUI, which can take up to 120 minutes to complete.

Next steps

Go to to continue the installation.

Related tasks

Last updated Nov 11, 2010 1:01:09 PM CST

Profile Type	Description
Management	Create a management profile that provides the servers and services necessary to manage the WebSphere environment. We can select one of the following management profile types on the following panel: Administrative agent
Application server	Create a standalone appserver profile.
None	Do not create a profile during installation. However, if you do not create a profile during installation, then create a profile after installation to have an operational product.