In this tip, we give suggestions about how to use Setup Manager to successfully install WebSphere Portal on Linux for zSeries V4.2.
After several failed attempts to install WebSphere Portal Server (WPS) on Linux for zSeries by using Setup Manager (the installation program provided with WPS), we began to record error messages, incorrect procedures, missing information, and hints and tips needed to correctly install the product. Out of that experience we developed the following suggestions, which you can use for successful installation.
What do you need to do to successfully install WPS on Linux for zSeries?
- Read the latest relevant information on portal installation and fixes.
- Verify that all requirements are met.
- Prepare your worksheet and system environment for Setup Manager.
- Validate that all products were successfully installed.
Before installing WPS, visit the Information Center at http://publib.boulder.ibm.com/pvc/wp/42/ena/en/InfoCenter/ and read “Getting started”. Also read the section “Preparing to install” , which documents both software and hardware requirements and Setup Manager, and offers a planning worksheet.
Refer to the TECHNOTES section of portal support for errors or updates that have been resolved:
Refer to the following site for useful problem determination information:
The requirement for memory is 1 GB (or greater). We found that when installing the WebSphere Content Publisher (WPCP), we could use more than 1 GB. If we did not have enough memory and swap, the installation would go into a recursive spin loop doing nothing but swap!
Print off the planning worksheet and complete the form; this information will be used as you install all of the necessary products.
We defined a VM user (ETPLN0) to install Linux for zSeries on, and used CTC connection between the Linux for zSeries and the z/VM machines. We installed all of the WPS products on the Linux for zSeries machine.
Following is the USER definition for ETPLN0:
USER ETPLN0 ETPLIN 2047M 2047M G
MACH esa 4
cpu 00 base
SPOOL 000C 2540 READER *
SPOOL 000D 2540 PUNCH A
SPOOL 000E 1403 A
CONSOLE 009 3215 T
special 150 ctca
special 151 ctca
MDISK 100 3390 0001 3238 VM51134 MR
MDISK 101 3390 2701 0635 VM51135 MR
MDISK 102 3390 0001 3338 VM51136 MR
Linux for zSeries preparation
We used 2.4.7-SuSE-SMP #1 SMP as our Linux for zSeries to install WPS on. We chose a Standard Install. We used three minidisks, defined as follows:
We needed to install pdksh with the following commands and selections:
YaST -> Package Management -> Change or create configuration -> ap -> pdksh
Setup Manager requires libncurses.so.4 to reside in /usr/lib directory, so we created a symbolic link to the directory /usr/lib/ for libncurses.so.4 for Setup Manager
ln –s /lib/libncurses.so.4 /usr/lib/libncurses.so.4
In /opt, we installed the IBM HTTP server, WebSphere Application Server, JAVA and WPS using the WPS Setup Manager.
Preparing the CDs that come with WPS
There are eight CDs that we used for WPS. These CDs should be NFS-mounted and made available to your Linux for zSeries.
Note: The name of the directory matters! If you call the directory cdn (lower case), where n is the CD number, then Setup Manager finds the directory and continues without intervention. However, if you name the directory anything else, Setup Manager takes a while looking for the directories, then prompts you for the directory.This is has both positive and negative aspects:
- If the directories are called cdn, then you cannot intervene with the installation at all. As a consequence, if you want to pause anywhere during the installation (to verify or alter anything between product installs), you cannot.
- Alternatively, if the directories are not called cdn, then you will be prompted for each CD and the Setup Manager cannot continue until you enter the directory name. Thus, if you are not attentive, Setup Manager will wait forever for you.
The CDs you will require for Linux for zSeries are:
- cd1 HTTP Server
- cd2-10 DB2
- cd2-15 DB2 Fix Pack
- cd3-3 WebSphere Application Server
- cd4 WebSphere Content Publisher
- cd5-2 IBM Directory Server
- cd7 WebSphere Portal Server
- setup Setup Manager
Using Setup Manager
Setup Manager requires an X11 window to execute, because it has a GUI interface. For our Linux for zSeries installation, we exported our Linux for zSeries DISPLAY variable to our workstation’s IP address with the export DISPLAY=184.108.40.206:0.0 command, then started KDE with the startkde & command from Linux for zSeries.
On our workstation, we started an X11 window software program called Exceed, made by Hummingbird, with the communications setting set to PASSIVE. After Exceed started with our Linux for zSeries settings, we opened a terminal window within Exceed and started the Setup Manager installer program.
We found that if we installed all products at once using the Setup Manager, we encountered a variety of problems and were not able to reach the /wps/portal portlets, even though it appeared that everything was installed correctly. Instead, we discovered that we needed to first install the IBM Directory Server, and let Setup Manager select the co-requisite products.
Next, we installed Portal Server and let Setup Manager select the co-requisites; then we were successful and reached our /wps/portal home page. We referred to the IBM Redbook IBM WebSphere Portal V4.1 Handbook Volume 1, SG24-6883, which walked us through the procedures successfully. The Redpaper REDP3699 also contains relevant installation information.
We found some inconsistencies in the InfoCenter and what the Setup Manager used as defaults. We found useful information in the TECHNOTES and the Hints and Tips sections of portal support at the following site, and used it to check for errors or updates that had already been resolved:
Saving your responses
If you have another mount point to write your response file to which is not on your Linux for zSeries, you may wish to use it to save your response file (to avoid having to type in all the fields again, if you have to recreate your Linux for zSeries and start over). If you do not have another mount point, copy the response file to a safe place.
As documented in SG24-6883, you can validate the IBM Directory Server by making sure slapd processes have been started, and by going into the Directory Management Tool and browsing the tree to verify that wpsadmin and wpsbind are there.
You can also go into the WebSphere Administrative Console and verify that the WebSphere Portal Server is there. Go to the http://localhost/wps/portal page and verify that you have portlets. You can further validate the portal server by logging on to the WPS Administrator, wpsadmin, clicking the Portal Administration tab, and then clicking Managing Portlets. You should see 70+ portlets if you took the Setup Manager defaults to install them.
Customization for automatic start up
When DB2 and LDAP are installed, there is an entry in /etc/inittab to automatically start them at startup. Depending on the runlevel you are using, this entry will have to be updated. You also need to check the DB2AUTOSTART=YES parameter for DB2, LDAP, and WebSphere DB2 database instances.
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.