Installing WebSphere Portal Offering 4.1.4 And WEA 4.21 On AIX

Full Install

For WPO install there is a special build which has a normal NIM build which includes the additional installation of WPO. To install this build on a machine, use the "nimesis" web page, provide the name of the machine with ID and PW, then select "5.1wpo" option, then click the "NIM It" link. In the browser pop-up, click "Lets Roll", and wait a minth.

You might have to reboot the machine after installing this image of the operating system. If this is the case, when you attempt to logon, and it is unsuccessful, follow the instructions in the section AIX Logon Problem to get to an AIX window, then type "reboot" at the command line. Once the machine is rebooted you must manually start wasinst DB2 (i.e. "su - wasinst", then type "db2start"), as well as manually start the WebSphere Admin Server (WAS) (i.e. "/usr/WebSphere/AppServer/bin/startupServer.sh &"). After a few minutes, start the WAS Administration Console (i.e. "/usr/WebSphere/AppServer/bin/adminclient.sh &"), then start the Portal Server application server.

This method presumes you are connected to a network drive which has a WebSphere Everyplace Access (WEA) build available. This process describes the use of Setup Manager, which installs WPO. It includes the installation of components "WebSphere Portal", "Productivity Portlets", "Portal Server", "WebSphere Personalization", "Personalization Server", "WebSphere Application Server, Advanced Edition", "WebSphere Application Server Fixpack 4", "WebSphere Application Server", "SecureWay Directory", "SecureWay Directory Server", "SecureWay Directory Client", "IBM HTTP Server", "DB2 Universal Database, "DB2 Universal Database Server", "DB2 Universal Database Fixpack 7", "DB2 Universal Database Client". Note that this was a snapshot for a particular build. There might be changes in defaults in subsequent builds/installs.

When using Setup Manager without the use of the keyboard (for accessibility), choosing a radio button involves using the "Tab" key to go to the appropriate field, and pressing the space bar to select that field.  For selecting check boxes, use the tab and arrow keys to move to the appropriate  position, then press the space bar to "check" the box. Also, in the following sections, when instructed to "select" or "click", use the tab key to go to the appropriate field, then press the "Enter" key.

Before you begin installation of the full complement of services, you must increase your file sizes. This can be done automatically using a utility provided in the "tools" directory.

1)  Logon to your AIX machine (i.e. "(yourmachinename).raleigh.ibm.com") as "root", but before you attempt to install WEA, you must increase your file sizes. (i.e. change directories to "/WEA/tools/shayden", and execute the script "qp.ksh"). See Increasing File Sizes for details of this script. You will then be instructed to reboot the machine to apply settings (this reboot process is probably not necessary). However, if you wish to do so, it can be done by typing "reboot" .

2)  (After reboot), logon to your AIX machine (i.e. "(yourmachinename).raleigh.ibm.com") as "root", and then mount a network drive to your machine that has the appropriate build on it (i.e. execute the command "/WEA/tools/shayden/mwpo", shell scripts which mount the network disk with builds on it). See Example Mount Script for details of this script.

3)  Change directories to the newly mounted drive (i.e. "cd  /wpo/cd1"), and at the AIX command prompt type "./install.sh". In a few seconds a new window should appear for performing the installation.
 

During installation, progress will be displayed on the window you started the install on.

Once installation is complete the WEA Information Center is located at "HTTPServer/htdocs/en_US/WEAInfo/en/InfoCenter/index.html"

(common Administrator password for Windows/AIX machines is (generic password))
 
 
 

WebSphere Portal Offering Install

1)  After invoking the install script, the first screen you will see is the "View Information" window in the "View Prerequisites" panel. If you wish, view the prerequisites (this will be done via a web browser), then click "Next"

2)  In the "Reading Software License" panel, select "Accept" in the "Program License Agreement" section and click "Next".

3)  In the "Validate the Installation Key" panel, enter the key values for the Enable version of WPO, (see Helen Loder, Jim Brancato, or Hua Guo for the key) then click "Next".

4)  In the "Install Selection" panel, select "Standard Install" and click "Next".

5)  You then have the option to enter a response file of a previously recorded install if desired, do not enter a value (and if one is there by default, delete it from this input field), and click "Next".

6)  In the "Select Components" panel, select only the components "WebSphere Portal", "Productivity Portlets", "Portal Server", "WebSphere Personalization", "Personalization Server", "WebSphere Application Server, Advanced Edition", "WebSphere Application Server Fixpack 4", "WebSphere Application Server", "SecureWay Directory", "SecureWay Directory Server", "SecureWay Directory Client", "IBM HTTP Server", "DB2 Universal Database, "DB2 Universal Database Server", "DB2 Universal Database Fixpack 7", "DB2 Universal Database Client", and click "Next".

7)  In the "Checking Previous Installation" panel, you will (probably) be told you have a "Previous installation of the License Use Management Runtime has been detected on this server. The following components' installation options cannot be modified. License Use Management Runtime - Upgrade the installation", click "Next".
 
 
 

IBM HTTP Server

1)  In the "Collecting Admin Username for IBM HTTP Server" panel, enter "ihsadmin" for the User Name, Password, and Confirm password fields. For the Group enter "ihsgrp", then click "Next".
 
 

SecureWay Directory Installation

1)  In the "SecureWay Directory Server" "Collect LDAP Suffix Information" panel, in the Suffix field enter "dc=rushmore".  In the Administrative User enter "cn=wpsadmin",  for the Password and Confirm Password fields enter "wpsadmin", then click "Next".  (LDAP port is "389").
 
 

WebSphere Application Server

1)  In the "WebSphere Application Server directory" panel, click "Next" to accept the defaults (WebSphere Application Server Directory is "/usr/WebSphere/AppServer").

2)  In the "Choose DB Location" panel "Is this a remote database" field, select "No", and then click "Next".

3)  In the "Choose Database Type" panel, choose "DB2", and click "Next".

4)  In the "Collect DB User Info" panel, accept the default for Database Username = "wasinst" and Local Database Group "wasgrp", and enter "wasinst" for the Database Password and Confirm Database Password fields, then click "Next". (Database Username was "wasinst" and Local Database Group was "wasgrp")

5)  In the "Collect Database Settings" panel, click "Next" to accept the defaults (Local Database Name = "wasdbl", Local Database Alias  name = "wasdb", Node Name = "LOOPBACK", and Database Server Port = "55555").
 
 

Peronalization Server

1) In the "Choose Application Server" panel, accept the default "WebSphere Portal", and click "Next".
 
 

Portal Server
 

1)  In the "Install Type Selection" panel, select "Typical" and click "Next".

2)  In the "Authentication Mode" panel, select "Database and LDAP Directory Mode", and click "Next".

3)  In the "Security Configuration" panel, select "Now" and click "Next".

4)  In the "LTPA Password" panel, enter "wpsbind" for the LTPA Password and Confirm password, and click "Next".

2)  In the "Server Configuration" panel, click "Next" to accept the defaults. (the Install Directory is "/usr/WebSphere/PortalServer", the Hostname is "(yourmachinename).raleigh.ibm.com", the Base URI i.e. "/wps", and the Home page is. "/portal", and the Customized page is "/myportal". Proxy Host and Proxy port were blank. The Base URI and the Home page will be the URL to access the Portal portlet, i.e.. "http://(yourmachinename).raleigh.ibm.com/wps/portal".).

3)  In the "Selection of LDAP Server" panel, for the "User Password" and "Confirm Password" fields, enter "wpsadmin", then click "Next" to accept the defaults ("SecureWay Directory" was selected). (LDAP Server was "(yourmachinename).raleigh.ibm.com", User DN was "cn=wpsadmin", Suffix was "dc=rushmore", and LDAP Port Number was "389").

4)  In the "LDAP Configuration" panel, accept the defaults and click "Next". (User Object Class was "inetOrgPerson", User DN Prefix was "uid", User DN Suffix was "cn=users,dc=rushmore", Group Object Class was "groupOfUniqueNames", Group Member was "uniqueMember", Group DN Prefix was "cn", Group DN Suffix was ""cn=groups,dc=rushmore", Administrator DN was "uid=wpsadmin,cn=users,dc=rushmore", and Administrative group DN was "cn=wpsadmins,cn=groups,dc=rushmore").

5)  In the "Portal Server Database Selection" panel, for the Database Backend select "DB2 Universal Database Server", for the Portal Server database configuration options "Create and initialize a new database (DB2 Only)", and for the "Do you want to share the database with Member Services", select "Share this database" and click "Next".

6)  In the "Additional Database Configuration" panel , enter "wpsdb", and for the Database User, User Password, and Confirm password fields enter "wasinst, and click "Next". (JDBC Database Driver was "COM.ibm.db2.jdbc.DB2ConnectionPoolDataSource", JDBC URL Prefix was "jdbc:db2", and JDBC Driver Library was "/home/db2inst1/sqllib/java12/db2java.zip").

7)  In the "Database option for Member Services" "Database option for Member Services" panel, select "Create and initialize a new database (DB2 Only)", and click "Next".

8)  In the "License User Managment" panel, select "Local License Server" and accept the default Remote LUM Server Hostname "(yourmachinename).raleigh.ibm.com", and click "Next".

Summary

1)  In the "Display Summary", click "Next" to accept the defaults. (note that there is no way to save your *.script configuration file). Go have a latte'.
 
 
 

Installation Details

After several minths a popup "Configuring for Admin Role " will appear.  While you are in the process of performing these steps you should also change the WebSphere Portal Ping Initial Timeout value to 1800.  From the WebSphere Administrative Console, scope down to "WebSphere Administrative Domain", "Nodes", (yournodename), "Application Servers", and select "WebSphere Portal".  In the "Advanced" tab for the Portal Server, change "Ping initial timeout" to "1800", click "Apply".

Follow the Configuring for Admin Role instructions before you continue with the installation of the software. When you are through with the configuring for admin role, be sure to click OK in the Configuring for Admin Role popup. The installation will then continue.
 

Wait a month, and eventually an "Installation Complete" popup should be displayed stating the response file has been saved, click "OK".  In the Display Summary window, click "Finish".

Logs resulting from the installation include the "setup*" file, which is the overall install log. Within that file will be references to additional logs "RunCommand* that will be in the directory "/usr/IBMWPO/RunCommand". (note that in the "setup*", and the "RunCommand*", the "*" refers to a "randomly generated" numeric value created during the install process.)
 

Additional LDAP Steps for WEA Installation

If you install WEA on top of WPO, you must make some changes to the LDAP to get WEA to work properly.

1) From a web browser connect to your ldap using the URL "(yourmachinename).raleigh.ibm.com/ldap".

2) When/If queried for login ID and Password, use "cn=wpsadmin" for the ID, and "wpsadmin" for the Password (or whatever you used in your SecureWay Directory Installation Administrative User and password)

3) Select "Settings", "Suffixes", and in the "Suffix DN" field, enter "dc=ins,dc=ibm,dc=com", then click "Update".

4) Click the link to "restart the server". A message will be displayed reflecting the status, it should eventually state "The directory server is currently running. To stop the server, click the Stop button."
 
 
 
 

Testing The Installation of WPO

At this point WPO and associated software should be installed, and WAS and your applications should have been started. Start the Admin Console, and when queried for authentication, use the value "wpsadmin" for the ID and password. (Note: if you had left the Admin Console running after performing the steps in "Configuring for Admin Role", you still have a snapshot of the configuration of WES/WAS at that point. Refreshing the Admin Console will not show you the remaining applications that were installed after the configuration was performed. To see these applications you must exit the Admin Console and restart it. Logon using ID/Password of "wpsadmin").

Steve:  Apparently during the installation process the Security Center password will be changed from any value input (i.e. "wpsadmin") to "wpsbind". Dont know why!

To verify the installation and operation of WebSphere Application Server, scope down to "WebSphere Administrative Domain", "Nodes", (yournodename), "Application Servers", select "Default Server", right mouse click and select "Start". Once the Default Server has started you should be able to run the "snoop" servlet by using your favorite browser and browsing the url "http://localhost/servlet/snoop". The userid and password for accessing servlets is "wpsadmin".

To verify the installation of WEA, use the url "http://localhost/wps/portal" (or alternatively your machinename, i.e.. "http://rushtest55.raleigh.ibm.com/wps/portal") to run the "World Clock" portlet. If you are queried for an ID/Password, use "wpsadmin" for both.

To login to the WebSphere Everyplace Access using the "portal" portlet, click on the key icon on the upper right corner of the web page. For the User ID and Password, enter the value "wpsadmin", and click the "Log In".

If the snoop servlet and portal portlet both work your installation was (probably) successful.
 
 

(Re)starting WebSphere Everyplace Access

1) From a command prompt, change directories to "/usr/WebSphere/AppServer/bin", and execute the command STEVE FIX THIS
 
 
 

Installing WEA on WPO

Perform the steps in STEVE FIX THIS

5)  In the "Select Components" panel, select only the components "WebSphere Everyplace Access", "WebSphere Everyplace Access Basic Services", "Intelligent Notification Services", "Intelligent Notification Services Server", "Intelligent Notification Services Database", "Everyplace Synchronization","Everyplace Synchronization Server Databases","Everyplace Synchronization Server", "Device Manager",  "Device Manager Database", "Device Manager","SecureWay Directory Server", and "DB2 Universal Database Server", and click "Next". (Some of these will not allow their selection without automatically selecting others)

2)  A panel will be displayed reflecting lots of stuff that is already installed and no action wil be taken, click "Next".

3)  In the panel querying whether WAS security is enabled select "Yes" and click "Next".

4)  In the WAS Security "Collect Administrator ID" panel, for the"Administrator ID", "Password", and "Confirm Password" fields, enter "wpsadmin", and click "Next".
 
 

Portlets

1)  In the "WebSphere EveryPlace Access Portlets" panel, all portlets should be selected, which includes "Portlets for Lotus Domino", "Portlets for Microsoft Exchange", and "Portlets for Productivity Enhancements". Already filled in were "Portal Administrator Username" as "wpsadmin", and "Group" was "wpsgrp". In the "Portal Administrator Password" field enter "wpsadmin",. The "Portal Server Hostname" should be your machine name (i.e. "wea2aix8.raleigh.ibm.com"). In the "Enter Offline Browsing Configurations" section, "Create and initialize a new database (DB2 Only)" should be selected, and in the "Database Administration Username" and "Database Administrator Password" fields enter "wasinst", then click "Next".
 
 

Everyplace Synchronization Server

1)  In the "Choose Everyplace Synchronization Adapters" panel select "Adapter for Microsoft Exchange", and "Adapter for relational databases using DB2 Everyplace (JDBC
compliant)", then click "Next".

2)  In the "Configure Adapter for Microsoft Exchange" panel, for the Hostname enter "abe.raleigh.ibm.com", and your Username and Password (i.e. "shayden").

3)  In the "DB2 Everyplace" panel enter "wasinst" as the Username, Password, and Password Confirm in the associated fields, then click "Next". (Already filled in are the WebSphere Application Path "/usr/WebSphere/AppServer", the DB2 Everyplace Path "/usr/WebSphere/IBMSyncServer/DB2Everyplace81")

4)  In the "Port" field enter "55555","Configure Database Server" panel, for the "Instance", "Password" and "Password Confirm" fields enter "wasinst". In the "Database Username", "Database Password" and "Password Confirm" fields enter "wasinst", then click "Next". (Already filled in were Node Name "LOOPESS", Port "55555" (must be changed to "55555"), Install Directory "/usr/WebSphere/IBMSyncServer", Instance was "db2inst1" (which must be changed!),  JDBC Driver "COM.ibm.db2.jdbc.app.DB2Driver", JDBC URL Prefix "jdbc:db2:" the JDBC Library "/home/db2inst1/sqllib/java12/db2java.zip", and Server Administrator "essadmin" (changed to "wasinst"))

5)  In the "Configure Portal Server" panel, accept the defaults and click "Next". (Already filled in were Portal Base URI "/wps", and the Portal Server Hostname
"(yourhostname).raleigh.ibm.com".)

(Note: to install only Basic and DB2e, select ESS install and only select the "Adapter for relational databases using DB2 Everyplace (JDBC compliant)".)
 
 

Intelligent Notification Services Server
`
1)  In the "General Installation Information" panel, click "Next" to accept the defaults. (Already filled in were Install Path "/usr/WebSphere/INS", and Hostname
"(yourservername).raleigh.ibm.com")

2)  In the "Selected SubComponents configuration" panel, select "Messaging Services" and "Subscription Services", and click "Next".

3)  In the "Subcomponent Configuration" panel, click "Next" to accept the default path (Already filled in was Path "/temp/undDelayQueue").

4)  In the "Select Portal LDAP Type" panel, select "SecureWay Directory", and click "Next".

5)  In the "Configure LDAP Server", click "Next" to accept the defaults. (Already filled in were LDAP server hostname "(yourhostname).raleigh.ibm.com", LDAP Server Port "389",
Root Username "cn=wpsadmin", Root Password (8 "*"'s), and LDAP Suffix "dc=rushmore".)

6)  In the "Configure Database", use the default database name ("insdb"), and enter "wasinst" for the Database User, Database Password, and Confirm Password fields, and click
"Next".

7)  In the "Administration portlets install", accept the defaults and click "Next". (Already filled in were WebSphere Portal Hostname "(yourhostname).raleigh.ibm.com", and Portal
Base URI "/wps").
 
 

Device Manager Database

1)  In the "Choose or use an existing database", click "Next" to accept the defaults.(Create and initialize a local database (reommended)).

2)  In the "Database creation mode", for the "Database Username", "Database Password", "Confirm Password" and "Instance Name" fields enter "wasinst", then click "Next". (Already filled in was the "Instance Name", with a value of "db2inst1" which must be changed to "wasinst").
 
 
 

Device Manager

1)  In the "Configure Device Manager", click "Next" to accept the defaults.  (Already filled in were Device Manager Directory "/usr/WebSphere/DMS", Web Service Directory
"/usr/HTTPServer", JDBC Driver "/home/db2inst2/sqllib/java12/db2java.zip", Database Username, Database Password and Confirm password was "wasinst")
 
 
 
 

Post Installation Required Steps

After the installation has completed, manual steps are required which corects a shared memory problem between the Application Server and DB2 on AIX machines and allow users to be added to WEA portal, as well as initializing appropriate environment variables for INS.

1) Logoff and then log back on the AIX session.

2) Stop WAS and all application servers,

3) Change the DB2 instance you installed the Portal Server as (i.e. "wasinst") to support adding users and groups, by performing the following:

          su - wasinst
          export EXTSHM=ON
          db2set DB2ENVLIST=EXTSHM
          db2stop force
          db2start

4) Add the command "export EXTSHM=ON" to the associated DB ".profile" file.

5)  Restart WAS, all application servers, and any associated INS and ESS servers.
 
 
 
 
 

Example Mount Script

The following are the contents of a schell script which can be used as is or modified for mounting the build you wish.

#!/usr/bin/ksh
mkdir /wpo
mount -o ro linwps1:/ghost  /wpo
 
 
 
 

Increasing File Sizes

This script contains the commands to increase your file sizes to accomodate the larger build. Note that it only adds to the current size of your file system without knowing or caring what they currently are!

#!/bin/ksh

print "Fixing the /etc/profile -- to resolve stty issue"
cat /etc/profile | sed -e "s/stty erase/#stty erase/g" >/tools/mo.log
mv /tools/mo.log /etc/profile

chfs -a size='+200000' /
chfs -a size='+2400000' /home
chfs -a size='+800000' /tmp
chfs -a size='+1200000' /usr
#usr/sbin/chfs -a size=6553600 /home
usr/sbin/chfs -a size=224000 /home

echo
echo "Filesystem /, /tmp, /usr and /home modified."
echo "Updating /etc/security/limits file"
echo
cp /tools/insv2/shilen/limits /etc/security/limits

echo
echo "Remember to reboot to apply settings"
 
 
 
 
 
 

AIX Logon Problem

When you attempt to login to AIX and get the Action Required dialog box, it states:

The DT messaging system could not be started.

To correct the problem:

1.  Choose [OK] to return to the logon screen.
2.  Select Failsafe Session from the logon screen's optoin menu and log in.
3.  Check to see that the hostname is correct in "/etc/hosts".
     Other hostname problems can be corrected by usingthe command "smit mktcpip"
4.  Check to see that if a search list is specified in "/etc/resolv.conf" it includes the domain your machine is configured on.

For additional information, see the DT Users's Guide.

[OK]