Because we already have an incompatible version of MQ installed, I did not install any of the WAS MQ or JMS support. This may or may not cause problems later (it hasn't yet). It is important that we find out ASAP whether the customer is already running MQ, and if so at which level - we should definitely install these WAS MQ pieces at the customer site to avoid future problems - IBM says that their installation is required.

a) Installed the missing prerequisite licensed programs (DCM and 5722AC3 in this case). I also installed 5799PTL, but this is definitely optional. It is entirely likely that the customer will be missing additional pieces (e.g. PASE). The list of prerequisite software must be checked very carefully. See these Web sites

http://publib.boulder.ibm.com/pvc/wp/502/smbi/en/InfoCenter/wpf/is_inst_req_smb.html

and

http://publib.boulder.ibm.com/pvc/wp/5022/smbi/en/InfoCenter/wpf/is_inst_req_smb.html

b) Installed latest V5R2 cumulative PTF package we had available (in fact 04244) via image catalog. This required an IPL.

c) Installed the latest Java, DB2 and HTTP server group PTFs I had available, via image catalog. This required an IPL.

d) Installed WAS Base (5733WS5 options *BASE, 1, 2, 3).

e) Installed group PTF SF99245 (requires an IPL) via image catalog.

(In fact I ordered and downloaded SF99280 (see below) and SF99245 arrived within this.)

f) Installed WAS Enterprise Enablement (5733WS5 option 10).

N.B. You do not need option 11 unless you have WAS Network Deployment installed.

g) Installed group PTF SF99280 (requires an IPL) via image catalog (same image catalog as for SF99245).

h) Installed Portal itself

i) Ran one-step portal wizard from HTTP Admin function (see below).