Additional node: Install with response file on Windows
First install IBM Installation Manager. Then use a response file to install IBM WebSphere Portal and IBM WAS on your additional nodes. Product binary installation parameter. Record response files on the same OS you plan for the installation. For multiple operating systems, record a response file for each operating system.The bit architecture of the installation program uses:
- The bit architecture of the operating system
- The bit architecture of the existing WAS
When you install onto a 64-bit operating system, WebSphere Portal installs as a 64-bit version. We can force a 32-bit application installation onto a 64-bit operating system.
There are sample response files, located in...
$SETUP_ROOT/responsefiles
Manually update these files based on the environment. Also replace the following lines in the sample response files if you installed WAS and WebSphere Portal from the live repository (Passport Advantage):
- Existing lines in the response file
- <offering id='8.0.0.3-WS-WAS-TFPM59935' version='8.0.3.20120309_1201' profile='IBM WAS Network Deployment V8.0' features='-'/>
- <offering id='8.0.0.3-WS-WAS-TFPM60670' version='8.0.3.20120319_1949' profile='IBM WAS Network Deployment V8.0' features='-'/>
- <offering id='8.0.0.3-WS-WASProd-TFPM60134' version='8.0.3.20120312_1656' profile='IBM WAS Network Deployment V8.0' features='-'/>
- <offering id='8.0.0.3-WS-WAS-TFPM61934' version='8.0.3.20120409_1230' profile='IBM WAS Network Deployment V8.0' features='-'/>
- Replace with
- <offering id='8.0.0.3-WS-WAS-IFPM59935' version='8.0.3.20120424_1630' profile='IBM WAS Network Deployment V8.0' features='-'/>
- <offering id='8.0.0.3-WS-WAS-IFPM60670' version='8.0.3.20120428_0856' profile='IBM WAS Network Deployment V8.0' features='-'/>
- <offering id='8.0.0.3-WS-WASProd-IFPM60134' version='8.0.3.20120425_1032' profile='IBM WAS Network Deployment V8.0' features='-'/>
- <offering id='8.0.0.3-WS-WAS-IFPM61934' version='8.0.3.20120417_1256' profile='IBM WAS Network Deployment V8.0' features='-'/>
Use a response file for installation
- Verify the fully qualified host name...
ping myserver.myco.com
- Verify network configuration...
ping localhost
- For servers with a firewall, antivirus, screen saver, and/or desktop search engine enabled, disable them before installing.
- Install IBM Installation Manager:
- Run the install task to install the IBM Installation Manager from the IBM Installation Manager media.
- Run the setup.exe task from the Portal Setup disk if you have a Windows 32-bit operating system and to start the launchpad.
- Run the setup64.exe task from the Portal Setup disk if you have a Windows 64-bit operating system and to start the launchpad. Right-click on setup64.exe, then select "Run as administrator", to launch.
To search for IBM Installation Manager updates, navigate to...
File > Update
- To record a response file:
This step does not install WebSphere Portal. You are only recording the response file used to install portal later.
./IBMIM :
IBMIM.exe -record responsefile.xml -skipInstall /path/to/install/directory
- Navigate through the IBM Installation Manager panels and set values for the environment.
Before adding the repositories, make sure they are located in a directory accessible to all required computers.
On the Select the features to install panel, keep the default selection checked to create a new Portal server profile.
- On the panel...
Select packages to install
...select both the WAS and WebSphere Portal packages.
- Click Next.
- On the panel...
Select the fixes to install
...select the following fixes based on how we are accessing the repository:
- When you install WAS and WebSphere Portal together from the live repository (Passport Advantage)
- 8.0.0.3-WS-WAS-IFPM59935
- 8.0.0.3-WS-WAS-IFPM60670
- 8.0.0.3-WS-WASProd-IFPM60134
- 8.0.0.3-WS-WAS-IFPM61934
- When you install WAS and WebSphere Portal together from the local repository (DVD or downloaded eImage)
- 8.0.0.3-WS-WAS-TFPM59935
- 8.0.0.3-WS-WAS-TFPM60670
- 8.0.0.3-WS-WASProd-TFPM60134
- 8.0.0.3-WS-WAS-TFPM61934
- Accept the license agreement and then click Next.
- Select shared resources directory and then click Next.
- Set Installation Directory:
- Select the WAS Package Group Name and then select the installation directory path.
- Select the WebSphere Portal Package Group Name and then select the installation directory path.
- Click Next.
- Select the translations to install and then click Next.
- On the panel...
Select the features to install
...expand the WAS and WebSphere Portal packages
Expand the WebSphere Portal package and deselect the feature...
Create a new Portal Server Profile
A full WebSphere Portal server is not currently required. We create the custom profile later.
- Confirm the information on the Summary panel and then click Install.
- After the Installation Manager finishes creating the response file, click Finish and then close the Installation Manager to complete the response file recording.
- If installing on a different computer, copy the response file to the response file directory on that computer.
- If the repository URL requires authentication, use imutilsc.sh to create a keyring file store for credentials.
The keyring file stores the credentials required for the repositories. The IBM Installation Manager command-line tool imutilsc is available from the installation tools directory.
imutilsc saveCredential -url repository_URL -userName credential_userName -userPassword password -keyring keyring_file [ -password keyringfile_password ] [ -proxyHost proxy_host -proxyPort proxy_port [ -proxyUsername proxy_username -proxyUserPassword proxyuser_password ] [ -useSocks ] ] [ -verbose ]If installing on a different computer, copy the keyring file to that computer.
- Install WebSphere Portal and IBM WAS run...
imcl -acceptLicense -input /path/to/response.xml -log /path/to/log/files
To use your repository keyring file...
-keyring /path/to/keyring -password keyringfile_password
- Verify the installation successfully created the WebSphere Portal file system.
Because the WebSphere Portal profile was not created, the WebSphere_Portal server does not exist. We create the server when adding the node to the cluster.
Parent: Install WebSphere Portal on Windows for the horizontal cluster nodes