One CIP installation alternative is to install WebSphere Application
Server for
i5/OS from a Windows workstation graphical user interface (GUI).
Before you begin
Restriction: You cannot
install a feature pack remotely. Thus, you cannot install a feature pack CIP
from a Windows workstation. You must install a feature pack on an iSeries
server using a local command-line installation.
This topic assumes
that you have a CIP image created using the Installation Factory and that
you want to install the product from the CIP. See IBM Installation Factory for WebSphere Application Server.
About this task
When you run the GUI installation tool, you specify installation
options interactively during the installation process.
Use this procedure
to install WebSphere Application Server Network Deployment for i5/OS 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 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)
- Verify that your user profile has the *ALLOBJ and *SECADM special
authorities.
- Place the CIP for i5/OS disc in the disc drive
of your Windows workstation. The autorun feature brings up the launchpad.
Do not use the IBM WebSphere Application Server Network Deployment Windows
disc or any other operating system platform disc from the product package.
- Enter the name of the iSeries server where you are installing WebSphere
Application Server Network
Deployment for i5/OS and your corresponding i5/OS 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.
- On the Welcome panel, click Next.
- 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.
- The system prerequisites check verifies that your server meets
the minimum requirements to install the product. If the prerequisites are
met, click Next. If the prerequisites are not met,
you can continue the installation. However, it is recommended that you exit
the installation wizard and make the required changes.
- On the next panel, select features to install and click Next.
In Version 6.1, just one feature is available, which installs the
Samples Gallery.
A CIP might not have the Samples feature. You can install
only what was included in the CIP.
- The next panel displays the product installation root directory,
the default profile location, and the product library name. Accept or change
these values, then click Next.
The product
installation root directory for WebSphere Application Server Network Deployment for
i5/OS contains the core product files. It is referred to in many information
center examples as the app_server_root.
The
default profile location for WebSphere Application Server Network Deployment for
i5/OS contains the configurable files for the profile. This directory is referred
to in many information center examples as the user_data_root.
The default profile location is the directory under which the profile registry
and profiles directory are created. The default profile is created under user_data_root/profiles/default.
The profile registry is created under user_data_root/profileRegistry.
The product library is often spelled out in information center examples,
but it might also be referred to as the product_library
- On the next panel, select the
type of WebSphere Application Server Network Deployment for i5/OS profile
to create after the installation of the core product files, then click Next.
Choose one of the following profile types:
- Cell
The cell includes a deployment manager and a federated application
server on one machine or partition.
- Deployment manager
The deployment manager provides a single administrative
interface to a logical group of application servers on one or more machines.
- Application server
An application server profile has a default server
(which is server1), the default application that includes the snoop servlet
and the hitcount servlet, and application Samples. You can federate the application
server or use it as a stand-alone application server.
- Custom
A custom profile is an empty node that you must customize to
include application servers, clusters, or other Java processes such as a messaging
server.
See Creating, deleting, and augmenting profiles.
- On the next panel, choose whether to enable administrative 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 administrative security for the default profile.
- 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 WebSphere Application Server Network Deployment for i5/OS.
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.
- Click Finish to close the InstallShield
program.
- 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