|
|
 |
|
|
Throughout these instructions, you must replace the following:
- <updi_location>: The location where the V6.1 UpdateInstaller is installed. The default location is /QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI.
- <product_location>: The location of the V6.1 product you are updating. Default locations are:
- Express: /QIBM/ProdData/WebSphere/AppServer/V61/Express
- Base: /QIBM/ProdData/WebSphere/AppServer/V61/Base
- ND: /QIBM/ProdData/WebSphere/AppServer/V61/ND
- AppClient: /QIBM/ProdData/WebSphere/AppClient/V61/client
- WebServer Plugins: /QIBM/ProdData/WebSphere/Plugins/V61/webserver
Tip: Invoke the querywasinstalls Qshell script located in directory /QIBM/WAS/bin from a Qshell session to list the WebSphere Application Server products installed on your system.
- <maintenance_package>: The name of the file containing the fix pack. This will be one of the following, where x is the fix pack number, for example, 5:
- Express, Base, ND: 6.1.0–WS–WAS–i5osPPC–FP000000x.pak
- AppClient: 6.1.0–WS–AppClient–i5osPPC–FP000000x.pak
- WebServer Plugins: 6.1.0–WS–PLG–i5osPPC–FP000000x.pak
Installing the fix pack
- Stop all Java processes that use the WebSphere Application Server product you are updating. These processes include all application server processes, the nodeagent process, the deployment manager process, and any WebSphere Application Server client applications.
- Start the host servers if they are not currently active:
STRHOSTSVR *ALL
- System requirements/recommendations:
- The userid used to run the update must have *ALLOBJ authority.
- Your HTTP server(s) will have to be ended and restarted at the end of this procedure.
- Ensure that as little activity as possible is occurring on the system. Do not put the system in restricted state or the fix pack install will fail.
- 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. More memory improves the performance of the update installer significantly. See step 4 to determine in which storage pool the the job will run.
- 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. Over time, as multiple versions of fix packs have been installed, there will be multiple .pak source files stored in the source directory, <updi_location>/maintenance. When the update function is performed, the most recently stored .pak file will be used in the update. If you wish to override this behavior, you can indicate a specific fix pack source file. See example 4b below.
- Install the fix pack using one of the options below.
Option 1: Submit the update script to batch using the installFixPack610x script. Use this option to install the fix pack after applying the WebSphere Application Server group PTF.
When you apply the WebSphere Application Server V6.1 group PTF, two Qshell scripts are placed in the bin directory of each V6.1 product installed on the system. The installFixPack610x and uninstallFixPack610x scripts (where x is the fix pack number) are customized to install and uninstall the fix pack contained within the group PTF to or from the product which is installed in the location containing the scripts. If the install/uninstallFixPack610x scripts do not exist, use Option 2 below.
- From QShell, invoke: <product_location>/bin/installFixPack610x where x is the fix pack number, for example, 5.
Example: /QIBM/ProdData/WebSphere/AppServer
/V61/Express/bin/installFixPack6105
- By default the installFixPack610x 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 have the job run in a different subsystem associated with a different storage pool if necessary.
Example: installFixPack610x –jobqlib MYLIB –jobq MYJOBQ
Option 2: Submit the update script to batch manually.
Use this option when you have obtained the fix pack image from the WebSphere Application Server support download site or from some location other than by applying the group PTF.
- This is a single command, typed as a continuous line of text. This will install the fix pack, running the update script as a batch job in the QSYSWRK subsystem. To submit the batch job to a different subsystem, modify the JOBQ parameter to specify the job queue you want to use.
- SBMJOB CMD(STRQSH CMD('<updi_location>/update –W product.location=<product_location> –W maintenance.package=<updi_location>/maintenance/<maintenance_package>')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)
Notes:
- Installation of the fix pack may take over an hour depending on your iSeries system. If memory available to the update process is limited, the update can take much longer, potentially several hours.
- If more than one V6.1 product is installed on your system (i.e. Express, Base or ND), you must use option 1 or option 2 above to install the fix pack for each of the products separately. You must not run multiple installs of the fix pack 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:
- There is insufficient free disk space on the system: /QIBM/ProdData/WebSphere/AppServer/V61/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('<updi_location>/update –W product.location=<product_location> –Wmaintenance.package=<updi_location>/maintenance/<maintenance_package>-OPT -disableDiskSpaceCheck=true')) JOB(UPDATEWAS)ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)
- The installation is complete when the job ends. Check the updatelog.txt file located under this directory:
<product_location>/logs/update/6.1.0–WS–WAS–i5osPPC–FP000000x.install for successful completion, where x is the fix pack number, for example, 5.
The last line of the file indicates if the install was successful (INSTCONFSUCCESS), partially successful (INSTCONFPARTIALSUCCESS) or failed (INSTCONFFAIL).
- 6. End and restart the HTTP Admin instance if it was active during the update. Use the following commands at the command prompt:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
Also stop and restart any HTTP server instances associated with V6.1 application servers.
Uninstalling the fix pack
- Stop all Java processes that use the WebSphere Application Server product you are updating. These processes include all application server processes, the nodeagent process, the deployment manager process, and any WebSphere Application Server client applications.
- Start the host servers if they are not active:
STRHOSTSVR *ALL
- System requirements/recommendations:
- The userid used to run the update must have *ALLOBJ authority.
- Your HTTP server(s) will have to be ended and restarted at the end of this procedure.
- Ensure that as little activity as possible is occurring on the system. Do not put the system in restricted state or the fix pack install will fail.
- 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. More memory improves the performance of the update installer significantly.
- 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.
- Uninstall the fix pack using one of the options below.
Option 1: Submit the update script to batch using the uninstallFixPack610x script. Use this option to uninstall the fix pack after installing the fix pack delivered by the WebSphere Application Server group PTF.
When you apply the WebSphere Application Server V6.1 group PTF, two Qshell scripts are placed in the bin directory of each V6.1 product installed on the system. The installFixPack610x and uninstallFixPack610x scripts (where x is the fix pack number) are customized to install and uninstall the fix pack contained within the group PTF to or from the product which is installed in the location containing the scripts. If the install/uninstallFixPack610x scripts do not exist, use Option 2 below.
- From QShell, invoke: <product_location>/bin/uninstallFixPack610x where x is the fix pack number, for example, 5.
Example: /QIBM/ProdData/WebSphere/AppServer/
V61/Express/bin/uninstallFixPack6105
- By default the uninstallFixPack610x 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 –jobqlib and –jobq parameters to specify a different job queue and job queue library.
Example: uninstallFixPack610x –jobqlib MYLIB –jobq MYJOBQ
Option 2: Submit the update script to batch manually.
Use this option when you have obtained the fix pack image from the WebSphere Application Server support download site or from some location other than by applying the group PTF.
- This is a single command, typed as a continuous line of text. This will uninstall the fix pack, running the update script as a batch job in the QSYSWRK subsystem. To submit the batch job to a different subsystem, modify the JOBQ parameter to specify the job queue you want to use.
- SBMJOB CMD(STRQSH CMD('<updi_location>/update –W update.type=uninstall –W product.location=<product_location> –W maintenance.package=<updi_location>/maintenance/<maintenance_package>')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)
Notes:
- Uninstall of the fix pack may take over an hour depending on your iSeries system.
- If more than one V6.1 product is installed on your system (i.e. Express, Base, or ND), you must use option 1 or 2 above to uninstall the fix pack for each of the products. You must not run multiple uninstalls of the fix pack at the same time.
- The uninstall is complete when the job ends. Check the updatelog.txt file located under this directory:
<product_location>/logs/update/6.1.0–WS–WAS–i5osPPC–FP000000x.uninstall
where x is the fix pack number, for example, 5
.
The last line of the file indicates if the uninstall was successful (INSTCONFSUCCESS), partially successful (INSTCONFPARTIALSUCCESS) or failed (INSTCONFFAIL).
- End and restart the HTTP Admin instance if it was active during the uninstall. Use the following commands at the command prompt:
ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
Also stop and restart any HTTP server instances associated with V6.1 application servers.
|
|
|
