Steve Pitcher › Installing WebSphere Portal and IBM Web Content Manager
March 7th, 2013
The installation instructions for WebSphere Portal on IBM i could be a little more clear. I'll be submitting my suggestions to IBM to update them. Here's what I did in order to install Portal and WCM on IBM i. If you're not using IBM i, but want to do a silent installation using response files, you may still get some value out of this.
I downloaded the following images from IBM Passport Advantage. All these images need to be consolidated in a single repository. More on that below.
CI7N3ML IBM WebSphere Portal and Web Content Manager Install V8.0 (1 of 5) Multiplatform Multilingual
CI7N4ML IBM WebSphere Portal and Web Content Manager Install V8.0 (2 of 5) Multiplatform Multilingual
CI7N5ML IBM WebSphere Portal and Web Content Manager Install V8.0 (3 of 5) Multiplatform Multilingual
CI7N6ML IBM WebSphere Portal and Web Content Manager Install V8.0 (4 of 5) Multiplatform Multilingual
CI7N7ML IBM WebSphere Portal and Web Content Manager Install V8.0 (5 of 5) Multiplatform Multilingual
In actuality, once downloaded these zip files are labeled as 1 of 7, 2 of 7 so there's some confusion there. I spent some time wondering where the two I missed were. I didn't. There's only 5.
Then these two:
CI7VIML IBM Web Content Manager Setup V8.0 (1 of 2) Multiplatform Multilingual
CI7VJML IBM Web Content Manager Setup V8.0 (2 of 2) Multiplatform Multilingual
Then these three:
CI7N8ML IBM WebSphere Application Server Network Deployment V8.0.0.3 (1 of 3) Multiplaform Multilingual
CI7N9ML IBM WebSphere Application Server Network Deployment V8.0.0.3 (2 of 3) Multiplaform Multilingual
CI7NAML IBM WebSphere Application Server Network Deployment V8.0.0.3 (3 of 3) Multiplaform Multilingual
Under CI7N3ML and CI7N4ML there are a Setup folders (containing one for Installation Manager, and WASFixes). Also, under CI7VIML there is a Setup folder, that's for the WCM.
I created a Portal8 folder comprised of the different packages. This is probably my biggest issue with the installation. There is no documentation showing what the final installable directory should look like, so you may be left with a bit of trial and error, especially since you may be hesitant to combine directories. Ideally, IBM could package these images in a nice and tidy format to minimize both confusion and customer effort. Here's how I built my directory.
Then, I created a folder on the IFS called InstallPortal, shared it via NetServer and pushed the customized Portal8 folder to it via drag/drop in Windows.
I then installed Installation Manager via the following steps.
Sign onto a 5250 session.
Start Qshell by typing Qsh on a command line and press enter.
Change working directory to the Installation Manager install directory:
cd /InstallPortal/Portal8/Setup/IIM/os400
Run the Installation Manager installer:
installc -acceptLicense
While in Qshell, change your working directory to the newly created Installation Manager directory and encrypt your wpadmin password. Copy the password when the command finishes.
cd /qibm/proddata/InstallationManager/eclipse/tools
imutilsc encryptString insertpasswordhere
Then I changed the response file /InstallPortal/Portal8/Setup/responsefiles/iseries/wcm_standalone_full.xml repository location parameters to point at /InstallPortal/Portal8/Setup/eimage/repository.config and /InstallPortal/Portal8/Setup/WASFixes/8.0.0.3-WS-WAS-i5OSPPC-IFPM59405.zip.
Also in there, I had to update two other parameters. The first is the web address of the server. Before changing this I created a new IP interface on IBM i, assigned a host table entry for www-2.scotsburn.com to it. If you have other web servers on your IBM i partition running HTTP/HTTPS then it's a good idea to give each web service a dedicated IP address so that you won't run into port conflicts.
The documentation also tells you to "ping yourserver.yourcompany.com"
On IBM i, you actually ping rmtsys('yourserver.yourcompany.com') or ping 'yourserver.yourcompany.com' so you need to either qualify the parameter name by using the rmtsys parameter or just use single quotes to signify there's a parameter being sent to the PING program in IBM i.
Either way, once you have a pingable host, change the following parameter with that host address:
data key="user.wp.hostname,com.ibm.websphere.PORTAL.SERVER.v80" value="www-2.scotsburn.com" />
The 2nd parameter is for the encrypted password we created earlier.
Save the file. Now we're ready to install Portal and WCM.
Back in Qshell, your directory should still be /qibm/proddata/InstallationManager/eclipse/tools so you can run the installation procedure from there:
imcl -acceptLicense input /InstallPortal/Portal8/Setup/responsefiles/iseries/wcm_standalone_full.xml -log /portal8install
The install log will be a generated as the stream file /portal8install. Kick back and grab some lunch because it may take a while to install all this stuff.
Good luck!
I downloaded the following images from IBM Passport Advantage. All these images need to be consolidated in a single repository. More on that below.
CI7N3ML IBM WebSphere Portal and Web Content Manager Install V8.0 (1 of 5) Multiplatform Multilingual
CI7N4ML IBM WebSphere Portal and Web Content Manager Install V8.0 (2 of 5) Multiplatform Multilingual
CI7N5ML IBM WebSphere Portal and Web Content Manager Install V8.0 (3 of 5) Multiplatform Multilingual
CI7N6ML IBM WebSphere Portal and Web Content Manager Install V8.0 (4 of 5) Multiplatform Multilingual
CI7N7ML IBM WebSphere Portal and Web Content Manager Install V8.0 (5 of 5) Multiplatform Multilingual
In actuality, once downloaded these zip files are labeled as 1 of 7, 2 of 7 so there's some confusion there. I spent some time wondering where the two I missed were. I didn't. There's only 5.
Then these two:
CI7VIML IBM Web Content Manager Setup V8.0 (1 of 2) Multiplatform Multilingual
CI7VJML IBM Web Content Manager Setup V8.0 (2 of 2) Multiplatform Multilingual
Then these three:
CI7N8ML IBM WebSphere Application Server Network Deployment V8.0.0.3 (1 of 3) Multiplaform Multilingual
CI7N9ML IBM WebSphere Application Server Network Deployment V8.0.0.3 (2 of 3) Multiplaform Multilingual
CI7NAML IBM WebSphere Application Server Network Deployment V8.0.0.3 (3 of 3) Multiplaform Multilingual
Under CI7N3ML and CI7N4ML there are a Setup folders (containing one for Installation Manager, and WASFixes). Also, under CI7VIML there is a Setup folder, that's for the WCM.
I created a Portal8 folder comprised of the different packages. This is probably my biggest issue with the installation. There is no documentation showing what the final installable directory should look like, so you may be left with a bit of trial and error, especially since you may be hesitant to combine directories. Ideally, IBM could package these images in a nice and tidy format to minimize both confusion and customer effort. Here's how I built my directory.
| InstallableDirectory | Source Media | ||||
| Portal8/Portal/disk1 | CI7N5ML | ||||
| Portal8/Portal/disk2 | CI7N6ML | ||||
| Portal8/Portal/disk3 | CI7N7ML | ||||
| Portal8/WAS/disk1 | CI7N8ML | ||||
| Portal8/WAS/disk2 | CI7N9ML | ||||
| Portal8/WAS/disk3 | CI7NAML | ||||
| Portal8/WCM | CI7VJML | ||||
| Portal8/Setup/IIM | CI7N3ML | ||||
| Portal8/Setup/WASFixes | CI7N4ML and CI7VIML | ||||
| Portal8/Setup/Components | CI7VIML | ||||
| Portal8/Setup/eimage | CI7VIML | ||||
| Portal8/Setup/IBMPU | CI7VIML | ||||
| Portal8/Setup/launchpad | CI7VIML | ||||
| Portal8/Setup/quickstart | CI7VIML | ||||
| Portal8/Setup/repository | CI7VIML | ||||
| Portal8/Setup/autorun.inf | CI7VIML | ||||
| Portal8/Setup/setup64.exe | CI7VIML | ||||
| Portal8/Setup/setup64.ini | CI7VIML | ||||
| Portal8/Setup/setup.exe | CI7VIML | ||||
| Portal8/Setup/setup.ini | CI7VIML | ||||
| Portal8/Setup/setup.sh | CI7VIML |
| Portal8/Setup/responsefiles | CI7VIML |
Then, I created a folder on the IFS called InstallPortal, shared it via NetServer and pushed the customized Portal8 folder to it via drag/drop in Windows.
I then installed Installation Manager via the following steps.
Sign onto a 5250 session.
Start Qshell by typing Qsh on a command line and press enter.
Change working directory to the Installation Manager install directory:
cd /InstallPortal/Portal8/Setup/IIM/os400
Run the Installation Manager installer:
installc -acceptLicense
While in Qshell, change your working directory to the newly created Installation Manager directory and encrypt your wpadmin password. Copy the password when the command finishes.
cd /qibm/proddata/InstallationManager/eclipse/tools
imutilsc encryptString insertpasswordhere
Then I changed the response file /InstallPortal/Portal8/Setup/responsefiles/iseries/wcm_standalone_full.xml repository location parameters to point at /InstallPortal/Portal8/Setup/eimage/repository.config and /InstallPortal/Portal8/Setup/WASFixes/8.0.0.3-WS-WAS-i5OSPPC-IFPM59405.zip.
Also in there, I had to update two other parameters. The first is the web address of the server. Before changing this I created a new IP interface on IBM i, assigned a host table entry for www-2.scotsburn.com to it. If you have other web servers on your IBM i partition running HTTP/HTTPS then it's a good idea to give each web service a dedicated IP address so that you won't run into port conflicts.
The documentation also tells you to "ping yourserver.yourcompany.com"
On IBM i, you actually ping rmtsys('yourserver.yourcompany.com') or ping 'yourserver.yourcompany.com' so you need to either qualify the parameter name by using the rmtsys parameter or just use single quotes to signify there's a parameter being sent to the PING program in IBM i.
Either way, once you have a pingable host, change the following parameter with that host address:
data key="user.wp.hostname,com.ibm.websphere.PORTAL.SERVER.v80" value="www-2.scotsburn.com" />
The 2nd parameter is for the encrypted password we created earlier.
Save the file. Now we're ready to install Portal and WCM.
Back in Qshell, your directory should still be /qibm/proddata/InstallationManager/eclipse/tools so you can run the installation procedure from there:
imcl -acceptLicense input /InstallPortal/Portal8/Setup/responsefiles/iseries/wcm_standalone_full.xml -log /portal8install
The install log will be a generated as the stream file /portal8install. Kick back and grab some lunch because it may take a while to install all this stuff.
Good luck!
Read the original at Steve Pitcher.
Categories: Blogs
