Standalone: Install with response file on IBM i
First install IBM Installation Manager. Then use a response file to install IBM WebSphere Portal and IBM WAS. Modify the appropriate sample response file, located in...setup_root/responsefiles/iseries
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.
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.
- To install the IBM Installation Manager, run...
installc -acceptLicense
If you have an existing IBM Installation Manager, search for updates to the latest supported version.
- Manually update the appropriate sample response file, located in...
setup_root/responsefiles/iseries
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='-'/>
To encrypt the portal administrator password run imutilsc. Enter the encrypted password in the response file.
imutilsc encryptString stringToEncrypt
If installing on a different computer, copy the updated response file to the response file directory on that computer.
We can record a response file using a different operating system. After recording the response file on the other operating system, modify the file for IBM i. Then copy the response file to the IBM i server.
- 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 was successful; access WebSphere Portal using...
http://myserver:myport/wps/portal
Complete the following steps after a successful installation:
- If you changed the context root on the panel...
Configuration for IBM WebSphere Portal: Profile configuration details: Advanced panel
...complete the steps in Change the portal URI.
- To configure the Portal application server to use a 64-bit SDK:
- Stop the WebSphere_Portal server.
- cd WAS_HOME/bin
- Switch the Portal profile to a 64-bit SDK...
managesdk -enableProfile -profileName profile -sdkname 1.6_64
- cd WP_PROFILE/ConfigEngine
- Adjust the JVM max heap size to support the 64-bit SDK...
ConfigEngine.sh modify-jvm-heap-size -DWasPassword=foo
- Restart the WebSphere_Portal server.
- To configure the Portal application server to use a 32-bit SDK:
- Stop the WebSphere_Portal server.
- cd WAS_HOME/bin
- Switch the Portal profile to a 64-bit SDK...
managesdk -enableProfile -profileName profile -sdkname 1.6_32
- cd WP_PROFILE/ConfigEngine
- Adjust the JVM max heap size to support the 32-bit SDK...
ConfigEngine.sh modify-jvm-heap-size -DWasPassword=foo
- Restart the WebSphere_Portal server.
Parent: Install WebSphere Portal on IBM i
Related:
Install Web Content Manager into an existing Server installation on IBM i