IBM Power Systems software > IBM i > Software >

WebSphere Application Server for System i

Updated: January 12, 2006

Overview

Support

Resources

Fix Pack Installation Instructions: WebSphere Application Server V6.0

Throughout these instructions, you must replace with either 'Base' or 'ND', depending on the product edition installed. The Express edition installs in the 'Base' directory path.

Installing the fix pack

If you applied the WebSphere Application Server V6 for OS/400 group PTF, skip step 1 – this step was done for you when the PTF was applied.

If you downloaded the fix pack from the internet, extract the contents of the .zip file to the product install root. For V6, the product install root is:
/QIBM/ProdData/WebSphere/AppServer/V6/ .

For example, if the fix pack zip file is in /home/fp60x, do the following from the OS/400 command line: STRQSH
cd /QIBM/ProdData/WebSphere/AppServer/V6/
jar –xf /home/fp60x/
End any active WebSphere Application Server jobs.
End the QWAS6 subsystem if active.
Start the host servers if they are not active: STRHOSTSVR *ALL
System requirements/recommendations:
1. The command in step 6 submits the job to the QBATCH subsystem which uses storage pool 2 by default. Also by default, the QBATCH subsystem allows only one active job at a time. To run the install process in a different job queue, subsystem and storage pool, you can specify the JOBQ parameter. For example, the QSYSNOMAX job queue is associated with subsystem QSYSWRK and has a default of *NOMAX for number of jobs.
2. Ensure that the storage pool in which the job runs has sufficient dedicated memory. A minimum of 512MB of dedicated memory is required, however, 1GB is recommended.
3. Ensure that no other workloads are competing for this dedicated memory. This can be accomplished by submitting the job to a subsystem associated with a storage pool containing this dedicated memory.
Install the fix pack using one of the options below:

Option 1: Submit the update script to batch using the installFixPack602x script.

Use this option to install the fix pack after applying the WebSphere Application Server V6.0 Group PTF.

When you apply the WebSphere Application Server V6.0 group PTF, two Qshell scripts are placed in the bin directory of each WAS V6.0 edition installed on the system. The installFixPack602x and uninstallFixPack602x scripts (where x is the fix pack number) are customized to install and uninstall the fix pack contained within the group PTF. If the install/uninstallFixPack602x scripts do not exist, you must use Option 2 below.
1. From QShell, invoke: /QIBM/ProdData/WebSphere/AppServer/V6//bin/installFixPack602x where is Base or ND, and x is the fix pack number, for example, 19.
  
  Example:
  /QIBM/ProdData/WebSphere/AppServer/V6/Base/bin/installFixPack60219
3. By default the installFixPack602x script submits the job to install the fix pack to the QSYSNOMAX job queue which is associated with the QSYSWRK subsystem and storage pool 2. You can use the -jobq and -jobqlib parameters to specify a different job queue and job queue library. This allows you to run the job in a different subsystem associated with a different storage pool if necessary. You can also specify a JOB name with the -job parameter. By default, the job is named UPDATEWAS.
  
  Example:
  installFixPack602x -jobqlib MYLIB -jobq MYJOBQ -job MYJOBNAME
Option 2: Submit the update Qshell script located in the updateinstaller directory under the product install root to run as a batch job.

Examples:
(each is a single command, typed as a continuous line of text)
1. Install the Base/Express edition fix pack, running the update script as a batch job in the QBATCH subsystem:
  SBMJOB CMD(STRQSH CMD('/QIBM/ProdData/WebSphere/AppServer/V6/Base/updateinstaller/update')) JOB(UPDATE) ALWMLTTHD(*YES)
2. Install the ND edition fix pack, running the update script as a batch job in the QSYSWRK subsystem:
  SBMJOB CMD(STRQSH CMD('/QIBM/ProdData/WebSphere/AppServer/V6/ND/updateinstaller/update')) JOB(UPDATE) JOBQ(QSYS/QSYSNOMAX)
3. ALWMLTTHD(*YES)
Notes:
- Installation of the fix pack may take over an hour depending on your iSeries system.
- If more than one V6 edition is installed on your system (e.g. Base/Express or ND), you must run the update command for each of the products separately. You must not run multiple update commands at the same time.
If your System i has a large amount of free disk space, 10 terabytes or more, you may get an error similar to the following:
1. There is insufficient free disk space on the system: /QIBM/ProdData/WebSphere/AppServer/V6/Base:
  Required: 600 MB
  Available: - 6669118 MB
  
  /tmp/InstallShield:
  Required: 250 MB
  Available: - 6669118 MB
  
  Please ensure there is enough free disk space on all required filesystems and retry the operation.
If this is the case, run option 2 above with the added command:
-OPT -disableDiskSpaceCheck=true

Example:
SBMJOB CMD(STRQSH CMD('/QIBM/ProdData/WebSphere/AppServer/V6/Base/updateinstaller/update-OPT -disableDiskSpaceCheck=true')) JOB(UPDATE)ALWMLTTHD(*YES)
The installation is complete when the job ends. Check the updatelog.txt file located under this directory:
/QIBM/ProdData/WebSphere/AppServer/V6//logs/update/ for successful completion, where is one of the two following directories and xx is the fix pack number, for example, 17:
– 6.0.2–WS–WAS–OS400PPC64–FPfull00xx.install
– 6.0.2–WS–WAS–OS400PPC64–FPdelta0xx.install
– 6.0.2–WS–WAS–OS400PPC64–FP000000xx.install
After installing the fix pack, stop and restart the *ADMIN HTTP Server instance, if it is running. Also stop and restart any HTTP server instances which are associated with V6 application servers

Uninstalling the fix pack

End any active WebSphere Application Server jobs. End the QWAS6 subsystem if active.
Start the host servers if they are not active:
STRHOSTSVR *ALL
System requirements/recommendations:
1. The command in step 4 submits the job to the QBATCH subsystem which uses storage pool 2 by default. Also by default, the QBATCH subsystem allows only one active job at a time. To run the uninstall process in a different job queue, subsystem and storage pool, you can specify the JOBQ parameter. For example, the QSYSNOMAX job queue is associated with subsystem QSYSWRK and has a default of *NOMAX for number of jobs.
2. Ensure that the storage pool in which the job runs has sufficient dedicated memory. A minimum of 512MB of dedicated memory is required, however, 1GB is recommended.
3. Ensure that no other workloads are competing for this dedicated memory. This can be accomplished by submitting the job to a subsystem associated with a storage pool containing this dedicated memory.
Submit the update script using one of the options below.

Option 1: Submit the update script to batch using the uninstallFixPack602x script.

Use this option to uninstall the fix pack delivered by the WebSphere Application Server V6.0 Group PTF.

When you apply the WebSphere Application Server V6.0 Group PTF, two Qshell scripts are placed in the bin directory of each WAS V6.0 edition installed on the system. The installFixPack602x and uninstallFixPack602x scripts (where x is the fix pack number) are customized to install and uninstall the fix pack contained within the group PTF. If the install/uninstallFixPack602x scripts do not exist, you must use Option 2 below.
1. From QShell, invoke: /bin/uninstallFixPack602x where x is the fix pack number, for example, 19.
  
  Example:
  /QIBM/ProdData/WebSphere/AppServer/V6/Base/bin/uninstallFixPack60219
3. By default, the uninstallFixPack602x script submits the job to uninstall the fix pack to the QSYSNOMAX job queue which is associated with the QSYSWRK subsystem and storage pool 2. You can use the -jobqlib and -jobq parameters to specify a different job queue and job queue library. You can also specify a JOB name with the -job parameter. By default, the job is named UPDATEWAS.
  
  Example: uninstallFixPack602x -jobqlib MYLIB -jobq MYJOBQ -job MYJOBNAME
Option 2: Submit the update Qshell script located in the updateinstaller directory under the product install root to run as a batch job.

Examples: (each is a single command, typed as a continuous line of text)
1. Uninstall the Base/Express edition fix pack, running the update script as a batch job in the QBATCH subsystem: SBMJOB CMD(STRQSH CMD('/QIBM/ProdData/WebSphere/AppServer/V6/Base/updateinstaller/update -W update.type=uninstall')) JOB(UNINSTALL) ALWMLTTHD(*YES)
2. Uninstall the ND edition fix pack, running the update script as a batch job in the QSYSWRK subsystem: SBMJOB CMD(STRQSH CMD('/QIBM/ProdData/WebSphere/AppServer/V6/ND/updateinstaller/update -W update.type=uninstall')) JOB(UNINSTALL) JOBQ(QSYS/QSYSNOMAX) ALWMLTTHD(*YES)
Notes:
- Uninstall of the fix pack may take over an hour depending on your iSeries system.
- If more than one V6 edition is installed on your system (e.g. Base/Express or ND), you must run the update command for each of the products separately. You must not run multiple update commands at the same time.
The uninstall is complete when the job ends. Check the updatelog.txt file located under directory /QIBM/ProdData/WebSphere/AppServer/V6//logs/update/ for successful completion, where is one of the two following directories and xx is the fix pack number, for example, 17:
– 6.0.2–WS–WAS–OS400PPC64–FPfull00xx.uninstall
– 6.0.2–WS–WAS–OS400PPC64–FPdelta0xx.uninstall
– 6.0.2–WS–WAS–OS400PPC64–FP000000xx.uninstall

The last line of the file indicates if the uninstall was successful (INSTCONFSUCCESS), partially successful (INSTCONFPARTIALSUCCESS) or failed (INSTCONFFAIL).
After uninstalling the fix pack, stop and restart the *ADMIN HTTP Server instance, if it is running. Also stop and restart any HTTP server instances which are associated with V6 application servers.