One CIP installation alternative is to install WebSphere® Application
Server for IBM® i from
a Windows® workstation
graphical user interface (GUI).
Before you begin
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 WebSphere Installation Factory.
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 for IBM i from
a CIP with the GUI installation program:
Procedure
- 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 IBM i disc
in the disc drive of your Windows workstation. The autorun feature
brings up the launchpad.
Do not use the IBM WebSphere Application Server Windows disc or any other operating system platform
disc from the product package.
- Click Launch the installation wizard for WebSphere Application Server.
- Enter the name of the iSeries server where you 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, 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.
- 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 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.
If you choose not to install a feature at this time, then
you can run the installer later and add features to this installation.
Select the features you want to install and click Next.
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
- 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 for IBM i 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 for IBM i 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
- 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 your WebSphere environment. You can select one
of the following management profile types on the following panel:
|
Application server |
Create a standalone application server profile. |
None |
Do not create a profile during installation.
However, if you do not create a profile during installation, then
you must create a profile after installation to have an operational
product. |
- 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.
- 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
Results
This procedure results in installing the product from a Windows workstation
GUI, which can take up to 120 minutes to complete.