I thought I might take the liberty of posting my instructions/experiences i=
n upgrading Portal Server from v5.0.1 to v5.0.2.2.  Only because i've had s=
o much trouble finding good step by step instructions myself, especially th=
ose that include the tricks and traps you might hit.

When you get to step 5, the upgrades to WPS, make sure you read the supplie=
d URL's very carefully, you should follow every step where possible.  And t=
ake special care that your wpconfig.properties is *exactly* right, in terms=
of wps administrator names, cell names, etc...as any errors in here will c=
ost you a lot of time when the "WPSConfig.sh WP-PTF-502x...." command is ru=
n, especially if you're on a slow Unix box!

The instructions are specific to Solaris, but would probably apply generall=
y to any platform.

Here goes, best of luck to you all:

WebSphere 5.0.2.6 and WPS 5.0.2.2 Upgrade Instructions (incl Lotus Collabor=
ative Components v 6.5.1.1, and upgrade to DB/2 client)



Ensure that the following settings are correct in your wpconfig.properties:
=09CellName=3D& #123;NAME_OF_ND_CELL_THAT_THIS_SERVER_BE
LONGS_TO}

NOTE:  Also ensure that the following parameters in wpconfig.properties are=
not blank.  Although they are used only for iSeries, the WPSconfig command=
will fail if they are left blank.  Set them as shown:
WpsDbSchema=3DQWPSDB
=09WmmDbSchema=3DQWMMDB

NOTE: In order to support WPS 5.0.2.2, the DB/2 client on the Portal Server=
s must be at least V8.1.  See the last page of this document for instructio=
ns on moving from V7.1 to V8.1

1. Install WAS 5.0.2 (ND & ND-PME) onto DM Server using the updateWizard sc=
ript after shutting down all the WAS & httpd servers.  The whole installati=
on takes ~40 mins on a relatively quick box (2 x 1000mhz processors).  This=
may take much longer on a slower box (e.g. 2 hours+ on sau31tm20ap)

=09- Solaris:
Fixpack2 Filenames:
ND =96 was50_nd_fp2_solaris.zip
ND-PME - was50_pme_fp2_solaris.tar
Method: If the server being upgraded is a member of a ND Cell, ensure the D=
M server is running
Untar into the /opt/WebSphere/AppServer/update directory
Run ./updateWizard.sh, follow instructions to install fixpack

Note2: There seems to be a fairly large wait (ie 15-20 mins on a quick box,=
2 hours+ on slower machines) when installing a security module update.  It=
will eventually proceed and continue the installation.


2. Install WAS 5.0.2 (Base & PME Extensions) onto the Portal Servers using =
the updateWizard script
=09- Solaris:
Fixpack2 (PME) Filename:=20
BASE: was50_fp2_solaris.tar
PME: was50_pme_fp2_solaris.tar
Method: Run /opt/WebSphere/AppServer/bin/setupCmdLine.sh from the terminal =
doing the install
Untar into the /opt/WebSphere/AppServer/update directory
Run ./updateWizard.sh, follow instructions to install fixpack

3.  Install WAS 5.0.2.6 Cumulative Fix on all servers, including Base, ND &=
PME.
=09- Solaris:
Cumulative FixPack 2 Filenames:
PME/ND-PME: was502_pme_cf6_solaris.zip
ND: was502_nd_cf6_solaris.zip
Base: was502_cf6_solaris.zip
Method: Run /opt/WebSphere/AppServer/bin/setupCmdLine.sh from the terminal =
doing the install
Unzip into the /opt/WebSphere/AppServer/update directory
Export your display to an X-Windows client (export DISPLAY=3Dnnn.nnn.nnn.nn=
n:0.0)
Run ./updateWizard.sh, follow instructions to install

4.  Update WAS 5.0.2.6 on the Portal Servers with required efixes for WPS 5=
0.2.2
http://publib.boulder.ibm.com/pvc/w.../was_fixes.html

Once the WAS upgrades are complete, close and re-open all Terminal sessions=
=20
Remember to run =93. ./opt/WebSphere/AppServer/bin/setupCmdline.sh=94 befor=
e continuing.

Ensure you have the latest version of =93PortalUpdateInstaller.zip=94, it c=
ontains Java classes that do not exist in the 5.0.2 version.

Ensure that automatic synchronisation for the nodes is turned OFF prior to =
installing the WPS fixpack, and that all nodeagents have been re-started fo=
r the change to take effect.

Ensure Soap Timeout is set to =930=94 in soap.client.props

5. Install WPS 5.0.2 fixpack by following instructions found here (this ste=
p takes ~2 hrs):
http://publib.boulder.ibm.com/pvc/w...ll_cluster.html

6. Install WPS 5.0.2.2 fixpack by following instructions found here (this s=
tep takes ~2 hrs):
http://publib.boulder.ibm.com/pvc/w...ll_cluster.htm=
l

7. Ensure that the version number is correct by checking that the /wps_home=
/wps.properties file contains the following lines:

# Product information for IBM WebSphere Portal Server
product=3DIBM WebSphere Portal Server
version=3D5.0.2.2
fixlevel=3D0
mode=3Dstandard
buildnumber=3D5021_034
WPFamilyName=3DMultiPlatform

8. Complete!
Installation of WPS Collaboration Center=20

Follow these instructions to install and configure the WPS Collaboration Ce=
nter Components:
(NOTE: Required files can be found on sau31tm20ap:/export/home/nconj2s/wps-=
cc-502)

http://publib.boulder.ibm.com/pvc/w...nter/index.html

1. Go to =93Collaboration Center=94  =93Installing=94
2. Go to =93Collaboration Center=94  =93Configuration Overview=94 &=
#61664; =93Configuring Collaboration Center portlets=94
3. Refer to the following URL for additional configuration for the Lotus Co=
llaborative Components (setting up Sametime, Quickplace, etc):
http://publib.boulder.ibm.com/pvc/w...llab/ksa_adv_c=
se.html
You will need to edit the /wps_root/shared/app/config/CSEnvironment.propert=
ies file.

Installation of WPS IBM Lotus Collaboration Center 6.5.1.1

Follow these instructions to install and configure the WPS IBM Lotus Collab=
oration Center Components for Domino 6.5.1:
(NOTE: Required files can be found on sau31tm20ap:/export/home/nconj2s/lcc-=
v6511 - Open the readme.html file from this directory for more information)
=20
To install the portlets and sample pages:
1. On the machine where WebSphere Portal is installed, create the directory=
<wp_root>/EPPUpdate, and copy the Notes/Domino and Extended Product Portle=
ts files into that directory.

UNIX: Set the execute flag "on" for Deploy.sh by typing the following comma=
nd:


$ chmod -f 766 Deploy.sh
2. Verify that the WAS_HOME and WPS_HOME environment variables are set. If =
not, you can specify them in the Deploy command line with the following par=
ameters:


-washome <wasHomeDirectory>
-wpshome <wpsHomeDirectory>

3. Make sure that the WebSphere Portal server is running.

4. To deploy the portlets/sample pages, run the following command:.
(NOTE: For a federated ND node, the <nodename> should be the name of the cl=
uster, not the node itself (e.g. DevNetwork not sau31tm20ap)

/deploy  [-f] [-v] <serverdns:port> <wpsadmin> <wpspassword> [<n
odename>] =
[<lang>] ([-portlets] | [-samplepages] | [-adminpage])

eg:
/deploy =96f =96v sau31tm20ap:9081 wpsadmin frogpoo DevNetwork=20

Notes:

 You can also enter simply "Deploy" and press enter, and you will b=
e prompted for each parameter.=20
 You can also specify the server, administrative user, and administ=
rator's password using the following parameters:=20
-s <server dns name>=20
-u <admin user>=20
-p <admin password>=20
 You can enter the parameter -h to display command line help.=20

5. Log in to WebSphere Portal and select My Workplace to confirm that the s=
ample portal pages and portlets have deployed.

6. To be able to use the portlets, see the topic "Configuring the Notes/Dom=
ino and Extended Products Portlets" in the Lotus Domino and Extended Produc=
ts 6.5.1 Guide on either the Lotus or IBM Web site.

Upgrade DB/2 Admin Client to v8.1

Save details of the existing nodes and databases
1. Run =93db2 list node directory=94, save output to a file
2. Run =93db2 list db directory=94, save output to a file

Remove existing v7.1 installation
1. On the server you=92re upgrading, change to /opt/IBMdb2/V7.1/instance
2. Run =93db2idrop db2inst1=94 to drop the existing db2inst1 instance
3. Mount the DB/2 v7.2 CD (DB/2 UDB EE =96 for Solaris), share it to the se=
rver you=92re upgrading
4. CD to the root of the CD ROM.
5. Run =93db2_deinstall =96n=94
6. Run =93userdel db2inst1=94 to remove the db2inst1 user

Install v8.1 Administration Client
1. Install the DB/2 setup files onto the server=20
 Copy ese.tar.Z from WPS 5.0 disk 5-5 to /var/tmp/db2v81
 Run =93zcat ese.tar.Z | tar =96xf =96=94 to untar the file
2. Export your display to an X-Windows terminal or Sun Blade
3. Run ./db2setup
4. Install the Administration Client, specifying db2inst1 as a new user to =
create the new instance

Setup the user and DB/2 instance=20
1. Run =93useradd -m -g db2grp1 -s /bin/bash -d /export/home/nconj2s =96u 9=
091907 db2inst1=94
2. Change to /opt/IBM/db2/V8.1/instance
3. Run =93db2icrt db2inst1=94

Re-create the catalogs for the nodes and databases (using the saved node/db=
info from above)
1. For each node, run:
 =93db2 catalog tcpip node nodename remote servername server 50000=
=94=20
2. For each database, run:
 =93db2 catalog database dbname as alias at node nodename=94=20

Finalise the installation
1. Close all shells and sign back in, re-run =93. ./setupCmdline.sh=94
2. Update the JDBC Resources and any other existence of =93db2java.zip=94 t=
o point to the new path (/opt/IBM/db2/java/db2java.zip).  NOTE: This includ=
es the wpconfig.properties file!!!
3. Save the changes on the DM, synch to the nodes, then stop and re-start t=
he DM and all nodes.

[ Post a follow-up to this message ]