i5/OS: Install WebSphere Portal with the console interface

i5/OS: Install WebSphere Portal with the console interface

+
Search Tips | Advanced Search

The console interface is available for both local and remote installation, for the Install and configure and Install only options. This is a textual interface, so to make selections as the installation program progresses, type in the number corresponding to the appropriate option displayed on screen and press Enter.
Review Installation scenarios before installing WebSphere Portal for iSeries.
Ensure that you have met the hardware and software prerequisites on the machine where you are installing WebSphere Portal, specifically for the memory and hard disk requirements and the appropriate level of i5/OS.
An edition of WebSphere Application Server (WAS) must be installed prior to beginning a WebSphere Portal install. Then the WebSphere Portal installation program automatically creates a WAS profile based on the WAS edition installed, for use with WebSphere Portal.
If more than one edition is installed, you will be asked to choose one. The installation program assigns a default profile name of wp_profile. If this profile already exists, then the profile name becomes wp_profilex, where x is 1 or the next available number. There is no maximum number of profiles set. Pre-existing profiles will not work; they may not have the right level of additional functionality required to run WebSphere Portal for iSeries.
Upon completion of a local installation, the QHST message queue will contain a completion message. We can display the message details to obtain the fully qualified job name associated with the WebSphere Portal install job. To retain the i5/OS job log from a remote installation, change the Job Description for the remote command server job prior to installing WebSphere Portal by typing the following on an i5/OS command line:
CHGJOBD JOBD(QSYS/QZBSJOBD) LOG(4 00 *SECLVL)

After changing JOBD, also restart the remote command server by typing the following:
ENDHOSTSVR SERVER(*RMTCMD)
STRHOSTSVR SERVER(*RMTCMD)

Upon successful completion of these commands, any subsequent remote installations will retain a job log on the i5/OS server.
We cannot install two profiles of the portal server at the same time, even in different directories. You must install each portal server completely before beginning the installation of the next one.

Install WebSphere Portal locally with the console interface

To install WebSphere Portal locally on the iSeries system...

Insert the WebSphere Portal Setup CD into the optical drive of the iSeries system.

Open an i5/OS command prompt and start the Qshell Interpreter by typing the following:
STRQSH

Change to the system root directory by entering the following:
cd /

Now start the installation. Provide a general command and let the installer program fill in the defaults, or provide a specific command with information for the installer program to use. Enter one of the following commands, all on one line, to start installation:

Specify only the default installation command with no options:
/QOPT/WPEX-0/install.sh

Specify the WAS profile name and starting port on which you will install WebSphere Portal (the system will prompt you for login information):
install.sh -W iSeriesStartingPort.startingPort=starting_port -W iSeriesdetectProfileAction.profileName=profile_root

where starting_port is the starting port for the WAS profile creation and profile_root is the name of the WAS profile where WebSphere Portal is installed.

Specify the installation of an empty portal, where a normal WebSphere Portal is installed without portlets or pages. This command is useful when you want to transfer an entire portal configuration from one portal to another, for example transferring a test portal environment to a production portal environment. Install an empty portal by typing:
install.sh -W emptyPortal.active="True"

Type in the number representing the language desired for the install and press Enter.

Review the license agreement. Type in the number representing I accept the terms of the licensing agreement and press Enter.

Review the information on the installation summary screen and press Enter. Throughout installation, the program displays progress messages related to the various components.

When prompted for the location of CD2, insert WebSphere Portal CD2 into the optical drive and enter the following on the Qshell command line to continue installation:
/QOPT/WPXP-2

Continue with selecting the install option, and follow the steps thereafter, as detailed in the next section.

Install WebSphere Portal remotely with the console (text) interface
To install WebSphere Portal remotely from a Windows workstation connected to the iSeries system...

If you are installing on a machine with a firewall enabled, IBM recommends that you disable the firewall before beginning installation.

Insert the WebSphere Portal Setup CD.

Open a DOS command prompt and change to the root directory of the CD. For example, to change from the C:/ drive to the CD root directory on drive E:/, you would enter the following:
cd /D E:/cd_root

...where cd_root is the root directory of the WebSphere Portal Setup CD. Note that the /D command is only necessary when changing from one drive to another.

Provide a general command and let the installer program fill in the defaults, or provide a specific command with information for the installer program to use. Enter one of the following commands, all on one line, to start installation:

Specify only the system and login information:
install400.bat ISERIES_SYSTEM USER_ID PASSWORD -console

Specify the WAS profile name and starting port on which you will install WebSphere Portal (the system will prompt you for login information):
install400.bat -W iSeriesStartingPort.startingPort=startingPort -W iSeriesdetectProfileAction.profileName=profile_root

where profile_root is the name of the WAS profile where WebSphere Portal is installed.

Specify the installation of an empty portal, where a normal WebSphere Portal is installed without portlets or pages. This command is useful when you want to transfer an entire portal configuration from one portal to another, for example transferring a test portal environment to a production portal environment. Install an empty portal by typing:
install400.bat -W emptyPortal.active="True"

where ISERIES_SYSTEM is the name of the iSeries system on which you are installing WebSphere Portal, and USER_ID and PASSWORD are the user ID and password you use to log on to that system.
The ID you use to log on must be of the user type (user class) *SECOFR. To check the level of authority, type the command DSPUSRPRF userID.

Type in the number representing the language desired for the install and press Enter.

Review the license agreement. Type in the number representing I accept the terms of the licensing agreement and press Enter.

Select an install option by typing in the number representing...
Install and Configure

...or...
Install only

...and press Next.
Select either option will copy WebSphere Portal files into ProdData's portal_server_root. The Install and Configure option will continue to install and perform basic configuration of WebSphere Portal on an existing WAS. The Install only option stops after the copy of files.

The installation program will search for an installed WAS.
In the event that there is more than one application server, you will be given the option to select the application server on which to install WebSphere Portal. If none is detected, cancel out of the installation program and first install an edition of WAS. Select from the list the WAS edition that you installed and on which you wish to install WebSphere Portal ; selecting either...
WAS - Base

...or...
WAS - Network Deployment

If you installed WAS - Express, select -Base, because the file system is shared between these two editions.

For either option...
Install and Configure

...or...
Install only

... the appropriate binary file will be copied from the install CD or filesystem to ProdData's path for portal_server_root directory on the hard drive. If you selected Install only, skip to reviewing the summary screen step.

Install and Configure If you chose this option, the installation program continues, automatically creating a WAS profile, naming it wp_profile. If this profile already exists, then the profile name becomes wp_profilex, where x is 1 or the next available number.

The screen for this step only appears if you chose the Install and Configure option:
A port number is automatically chosen by the installation program when the profile is created. The starting port is based on a range of 50 free ports within ports 10000 to 65000. If for some reason the installation program cannot detect ports for WAS or WebSphere Portal a warning message pops up stating that there was a problem detecting ports. Then a panel will prompt the specification of a starting and ending port, as well as the port block range which needs to include a minimum of 20 ports. Press Enter.

The screen for this step only appears if you chose the Install and Configure:
Enter a user ID and password for the WAS administrator. Do not use blanks in either the user ID or the password, and ensure that the password is at least five characters in length. This user ID is collected by the installation program in order to enable security. This user ID is also used to access WAS with administrator authority after installation. Press Enter.

The screen for this step only appears if you chose the Install and Configure:
Enter a user ID and password for the WebSphere Portal administrator. Do not use blanks in either the user ID or the password, and ensure that the password is at least five characters in length. This user ID is collected by the installation program in order to enable security. This user ID is also used to access WebSphere Portal with administrator authority after installation. Note that this user ID is only used to log into WebSphere Portal and is not related to any user IDs used to access the operating system itself. If you intend to use a LDAP directory to manage the users, ensure that the administrator user ID you specify here conforms to the recommendations specified in Special characters in user IDs and passwords. Press Enter.

The screen for this step appears whether you chose the Install and Configure or Install only option:
Review the information on the installation summary screen and press Enter. Wrapper files from the install image are copied into the ProdData path for portal_server_root.
The Install only option will complete in a matter of minutes. If you chose the Install and Configure option, it will take about an hour for the process to complete, and a progress panel is displayed.
A sequential summary of the automatic copy, install, and configuration steps follows, described within the option in which it occurs:

Install and Configure or Install only:
This is the point at which the appropriate binary file is copied from the install CD or filesystem to the ProdData path for portal_server_root on the hard drive. The i5/OS library is populated with Java Content Repository (JCR) files.

It is at this point that the Install only option completes. The Install and Configure option continues:

The installation program extracts the WebSphere Portal install image files into the created WAS profile in UserData app_server_root.

Files used to update WebSphere Portal are copied into the UserData app_server_root.

The Cloudscape database is created.

Portlets are deployed automatically, unless you specified an empty portal install.

Security is enabled.

After the installation program has completed the configuration tasks just described, the Install and Configure option will prompt you to decide whether or not to run the Configuration Wizard. This provides the ability to transfer the Cloudscape database to IBM DB2 Universal Database for iSeries V5.2, and also to configure security on the LDAP server or an External Security Manager server of the choice. If you installed an empty portal, the portal is ready for importing the new configuration when the installation program is finished. Refer to details on transferring a portal configuration in Working with the XML configuration interface.

When WebSphere Portal finishes installing, the installation program will display a confirmation panel. Press Finish to exit the installation program.

Return to i5/OS Installation scenarios to complete the installation process.
We can install more than one copy of WebSphere Portal on the same machine and have each WebSphere Portal operate independently of the others. Each copy of WebSphere Portal must be installed on a separate WAS profile.
If an installation has already been completed, running the installation program again presents the default option of Config only. This option allows the addition of more than one portal on the same iSeries server where WebSphere Portal was installed. This option has the identical functions as the Install and configure option.

Related information

Installation scenarios
Install remotely with the graphical interface
Install with a response file