About the installation program

 

Contents

  1. Overview
  2. Install with the graphical installation program
  3. Install with the console interface
  4. Install with a response file
  5. Next steps

 

Overview

The installation program for WebSphere Portal provides a layered approach to building your WebSphere Portal environment, enabling you to start with WebSphere Portal as the base and then add other components in an incremental fashion as you need them. The installation process is made up of two general steps:

  1. Install the product files to the file system and set appropriate operating system information

  2. Perform a series of configuration tasks using a scripting interface

Accessibility note: The console interface is the only installation method that is accessible to assistive technology.

 

Install with the graphical installation program

WebSphere Portal includes a graphical installation program that gathers essential information for the installation, such as where WebSphere Portal should be installed, and then performs the installation accordingly. The installation program also sets certain properties in wpconfig.properties.

To run the graphical installation program...

    ./install.sh|bat

Before starting the install, disable any screen saver software that is running on the machine. This software can affect the ability of the machine to connect to the network and sometimes interfere with the operation of the WebSphere Portal installation program.

The installation program requires a Java Run-time Environment (JRE) to run. The installation program checks for the correct level of the JRE and automatically installs it if it does not exist on the machine.

The installation program verifies the following information prior to installation:

  • Operating system and its prerequisites
  • Disk space available
  • Software prerequisites, if required

When a dialog is displayed and enter text, use either your pointing device, or press the TAB key at least twice, to move between the entry fields.

 

Install with the console interface

The WebSphere Portal installation program also provides a console interface, which enables you to perform an interactive installation from a command prompt.

To launch the installation program from the console interface, do the following steps:

  • For Windows, enter...

    install.bat -console

    ...from the root directory of the setup CD.

  • UNIX:

    Do the following steps:

    1. If you are installing from physical CD-ROM discs, attempting to use the console interface to install directly from the CD-ROM discs can cause the CD drive to become unmountable. To avoid this problem, copy the contents of the setup CD to a location on your hard drive, such as a directory called cdSetup.

    2. From the hard drive, enter...

      cdSetup/install.sh -console

The console interface presents the same content as the graphical installation program, only in a textual form. Indicate your selections by entering a number corresponding to your choice and proceed through the installation by pressing Enter.

For example, to select the language that you want to use for the installation, you would see output similar to the following example: 

D:\>install -console
IBM WebSphere Portal for Multiplatforms 5.1

------------------------------------------------------------------------
Select a language to be used for this wizard.

[ ] 1  - Czech
[X] 2  - English
[ ] 3  - French
[ ] 4  - German
[ ] 5  - Greek
[ ] 6  - Hungarian
[ ] 7  - Italian
[ ] 8  - Japanese
[ ] 9  - Korean
[ ] 10 - Polish
[ ] 11 - Portuguese
[ ] 12 - Portuguese (Brazil)
[ ] 13 - Russian
[ ] 14 - Simplified Chinese
[ ] 15 - Spanish
[ ] 16 - Traditional Chinese
[ ] 17 - Turkish

To select an item enter its number, or 0 when you are finished: [0]

 

Install with a response file

WebSphere Portal can also be installed from a command line through the use of a response file. When installing with a response file, the installation program can retrieve information from the response file that would otherwise be entered by the user during the installation, such as the directory where WebSphere Portal is to be installed or the location of WebSphere Application Server (WAS). Installing from a command line with a response file is well suited to situations where the use of a graphical installation program is impractical or undesirable or where you want to install WebSphere Portal on multiple machines with a similar setup.

To run the installation program, enter the following command from the root directory of the setup CD:

./install.sh -options /path/to/responsefile.txt

A sample response file (installresponse.txt) file is located in the root directory of the setup CD.

When you run the WebSphere Portal installation program, a response file containing the information that you entered during installation is automatically created and saved in...

<wp_root>/log/responselog.txt

This response file can be useful if you want to install a similar WebSphere Portal configuration on multiple machines. By modifying a few parameters in the response file, such as the host.name of the machine where you want to install, you can perform multiple installations without having to enter information in the installation program each time.

 

Install response file parameters

The following parameters can be specified in the response file or directly on the command line when issuing the installation command.

Parameter default Description
-silent

SILENT INSTALLATION CHOICE

Specify this parameter if you want to install WebSphere Portal silently. When installing silently, the installation program will not display any graphical interface panels or solicit input from the user. Note that if a required parameter is not specified in this response file, an error message will be logged.

If you want to use this response file but do not want to install silently, comment the parameter out.

-W setupTypePanel.selectedSetupTypeId="full"

INSTALL WEBSPHERE PORTAL

Indicate the type of WebSphere Portal installation you want to perform.

Values:

full Install WebSphere Portal and all the components that it requires, including WAS.
custom Select an existing WAS on which to install WebSphere Portal.
toolkit Install the WebSphere Portal Test Environment into Application Developer and products that extend Application Developer.

-W was.location="C:\WebSphere\AppServer"

WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION

If you are installing WAS (specified a value of "install" for the installWas.choice parameter), specify the directory where you want to install WAS. If the directory does not exist, it will be created.

If you are using an existing instance of WAS (specified a value of "use" for the installWas.choice parameter), specify the directory where WAS is installed.

Be sure to follow the convention for specifying path information on your platform.

-W node.name="DefaultNode"

WEBSPHERE APPLICATION SERVER NODE NAME

Specify the node within the WAS cell to which the WebSphere Portal appserver will belong. This value must be unique among other node names in the same cell. Typically, this value is the same as the host.name for the computer.

replace the "DefaultNode" value with the node name that you want to use for your default node.

-W node.hostName="hostname.setgetweb.com"

WEBSPHERE APPLICATION SERVER HOST NAME

Specify the fully qualified host.name or IP address of the computer that is running WAS. For example, "hostname.setgetweb.com".

-W wasService.was="true"

INSTALL THE WEBSPHERE APPLICATION SERVER SERVICE (Windows only)

If you are installing WAS on a machine that is running Windows, specify whether you want to install it as a service. Using Services, you can start and stop services, and configure startup and recovery actions.

If you are not installing WAS or are installing it on a system that is not running Windows, you can ignore this parameter or comment it out.

Values:

  • true - Install WAS as service

  • false - Do not install WAS as service
-W wasService.wps="true"

INSTALL THE WEBSPHERE PORTAL SERVICE (Windows only)

If you are installing WebSphere Portal on a machine that is running Windows, specify whether you want to install it as a service. Using Services, you can start and stop services, and configure startup and recovery actions.

If you are installing WebSphere Portal on a system that is not running Windows, you can ignore this parameter or comment it out.

Values:

  • true - Install WebSphere Portal as service

  • false - Do not install WebSphere Portal as service

-W wasService.user="YOUR_USER_NAME"

-W wasService.password="YOUR_PASSWORD"

USER NAME AND PASSWORD FOR SERVICE INSTALLATION (Windows only)

If you chose to install WAS or WebSphere Portal as a service (specified a value of "true" for the wasService.was or wasService.wps parameters), also specify the user name and password that will be used to install the services.

In order to install the service and have it run properly, the user that you specify must have administrator authority and "Log on as a service" authority.

If you are not installing WAS or are installing it on a system that is not running Windows, you can ignore these parameters or comment them out.

Replace the placeholder values "YOUR_USER_NAME" and "YOUR_PASSWORD" with appropriate values for your system.

-W portal.location="C:\WebSphere\PortalServer"

WEBSPHERE PORTAL INSTALLATION LOCATION

Specify the directory where you want to install WebSphere Portal. If the directory does not exist, it will be created.

Be sure to follow the convention for specifying path information on your platform.

-W portalAdmin.user=""

-W portalAdmin.password=""

WEBSPHERE PORTAL ADMINISTRATOR USER ID AND PASSWORD

Specify the user ID and password of the WebSphere Portal administrator.

-W cdSetup.cdPath="/cdimg/cdSetup"

SETUP CD LOCATION

Specify the directory path to the Setup CD installation image. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

This directory should contain the executable program that is used to launch the WebSphere Portal installation program. For example: install.exe.

Replace the placeholder value with the appropriate value for your system.

-W archiveMediaPanelMQ.cdPath="/cdimg/cd1-1"

Use when performing a full installation on a machine that does not have WAS installed.

WEBSPHERE BUSINESS INTEGRATION SERVER FOUNDATION CD LOCATION

Specify the directory path to the WebSphere Business Integration Server Foundation CD installation image. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

This directory should contain the executable program that is used to launch the WebSphere Business Integration Server Foundation installation program. For example: install.exe.

Replace the placeholder value with the appropriate value for your system.

The default CD layout according to platform:

cd1-1: Windows
cd1-3: Linux for Intel
cd1-5: AIX
cd1-7: Solaris
cd1-9: HP-UX
cd1-11: Linux for zSeries
cd1-13: Linux for PowerPC

-W archiveMediaPanel1.cdPath="/cdimg/cd4-1"

Use when performing a full installation on a machine that does not have WAS installed.

WEBSPHERE APPLICATION SERVER ARCHIVE CD LOCATION

Specify the directory path to the WAS CD installation image. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

Replace the placeholder value with the appropriate value for your system.

The default CD layout according to platform:

cd4-1: Windows
cd4-2: Linux for Intel
cd4-3: AIX
cd4-4: Solaris
cd4-5: HP-UX
cd4-6: Linux for zSeries
cd4-7: Linux for PowerPC

-W archiveMediaPanel2.cdPath="/cdimg/cd5-1"

Use when performing a full installation on a machine that does not have WAS installed.

WEBSPHERE PORTAL ARCHIVE DISC 1 CD LOCATION

Specify the directory path to the first WebSphere Portal archive CD installation image. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

Replace the placeholder value with the appropriate value for your system.

The default CD layout according to platform:

cd5-1: Windows

cd5-2: All other platforms

-W archiveMediaPanel4.cdPath="/cdimg/cd5-3"

Use when performing a full installation on a machine that does not have WAS installed.

WEBSPHERE PORTAL ARCHIVE DISC 2 CD LOCATION

Specify the directory path to the second WebSphere Portal archive CD installation image. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

Replace the placeholder value with the appropriate value for your system.

The default CD layout according to platform:

cd5-3: All other platforms

-W userInputCDLocWas.cdPath="/cdimg/cd1-1"

Use when performing a custom installation or a coexistence installation on a machine that has WAS installed.

WEBSPHERE BUSINESS INTEGRATION SERVER FOUNDATION CD LOCATION

Specify the directory path to the WebSphere Business Integration Server Foundation CD installation image. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

This directory should contain the executable program that is used to launch the WebSphere Business Integration Server Foundation installation program. For example: install.exe.

Replace the placeholder value with the appropriate value for your system.

The default CD layout according to platform:

cd1-1: Windows
cd1-3: Linux for Intel
cd1-5: AIX
cd1-7: Solaris
cd1-9: HP-UX
cd1-11: Linux for zSeries
cd1-13: Linux for PowerPC

-W userInputCDLocWasCumulativeFix.cdPath="/cdimg/cd1-2"

Use when performing a custom installation or a coexistence installation on a machine that has WAS installed.

WEBSPHERE BUSINESS INTEGRATION SERVER FOUNDATION CD 2 LOCATION

Specify the directory path to the second WebSphere Business Integration Server Foundation installation image. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

This directory should contain the executable program that is used to launch the WebSphere Business Integration Server Foundation fix pack installation program. For example: install.exe.

Replace the placeholder value with the appropriate value for your system.

The default CD layout according to platform:

cd1-2: Windows
cd1-4: Linux for Intel
cd1-6: AIX
cd1-8: Solaris
cd1-10: HP-UX
cd1-12: Linux for zSeries
cd1-14: Linux for PowerPC

-W userInputCDLocWasFixpack.cdPath="/cdimg/cd1-15"

Use when performing a custom installation or a coexistence installation on a machine that has WAS installed.

WEBSPHERE BUSINESS INTEGRATION SERVER FOUNDATION FIX PACK CD LOCATION

Specify the directory path to the WebSphere Business Integration Server Foundation fix pack installation images. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

This directory should contain the executable program that is used to launch the WebSphere Business Integration Server Foundation fix pack installation program. For example: install.exe.

Replace the placeholder value with the appropriate value for your system.

The default CD layout according to platform:

cd1-15: Windows
cd1-16: Linux for Intel
cd1-17: AIX
cd1-18: Solaris
cd1-19: HP-UX
cd1-20: Linux for zSeries
cd1-21: Linux for PowerPC

-W WPSCDLoc.cdPath="/cdimg/cd2"

Use when performing a custom installation or a coexistence installation on a machine that has WAS installed.

WEBSPHERE PORTAL CD LOCATION

Specify the directory path to the WebSphere Portal installation images. Although this can be to a CD-ROM drive, for unattended installation this location is more likely to be a directory where electronic product images are stored, such as on a network drive.

This directory should contain the script files that are used to launch the WebSphere Portal installation program. For example: install.bat/install.sh.

Replace the placeholder value with the appropriate value for your system.

-W managedNode.primaryNode="false" SECONDARY NODE CHOICE (MANAGED NODES ONLY)

If you are installing WebSphere Portal on a WAS node that is already federated into a deployment manager cell and you intend to use this WebSphere Portal installation as a cluster member, specify whether the installation will be the primary node or a secondary node. This parameter only needs to be specified explicitly when you are installing on a secondary node.

Values:

  • true - Applications installed with WebSphere Portal will be copied to the deployment manager's master configuration as part of installation. This value is assumed if the managedNode.primaryNode parameter is not specified or is commented out.

  • false - Applications installed with WebSphere Portal will not be copied to the deployment manager's master configuration as part of installation. Note that after installation, WebSphere Portal will not be operable until it has been added to a cluster.
-W installPortletsSequence.active="false"

INSTALL EMPTY WEBSPHERE PORTAL

Specify whether you want to install WebSphere Portal as an empty portal, where WebSphere Portal is installed normally but no portlets are installed or deployed and no pages are created.

This parameter is only used in special circumstances and is not included in the sample response file (installresponse.txt). Refer to the Advanced installation options topic for more information on installing an empty portal with this parameter.

Values:

  • true - Portlets are installed and deployed and pages are created automatically. This is the default value and is assumed if the installPortletsSequence.active parameter is not specified.

  • false - Portlets are not installed or deployed and no pages are created.
-W skipCoexistFlag.visited="false"

SKIP COEXISTENCE INSTALLATION

Indicate whether you want to skip the coexistence installation scenario when installing WebSphere Portal. Typically, if you are performing a full installation and the installation program detects an existing instance of WAS on the machine, a coexistence installation is triggered. The coexistence installation launches the WAS installation program to enable you to select the proper ports to avoid port conflicts after installation.

If you intend to specify a value of "true" for the skipCoexistFlag.visited parameter, stop all instances of WAS and WebSphere Portal before installing; otherwise, the installation will fail.

Values:

  • true - A full installation of WebSphere Portal and WAS will be installed without regard to whether an instance of WAS is already installed. After installation, change the port numbers used by one installation or the other, or you will be unable to run both instances of WAS at the same time.

  • false - The standard coexistence installation scenario is triggered if you attempt to perform a full installation and the installation program detects an existing instance of WAS on the machine.

 

 

Next steps

You have completed this step. Continue to the next step by choosing one of the following topics:

 

See also

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

 

AIX is a trademark of the IBM Corporation in the United States, other countries, or both.