Skip to main content

 
IBM Power Systems software  >  IBM i  > Software  > 

WebSphere Application Server for System i

  
Overview Support Resources


Fix Pack Installation Instructions: WebSphere Application Server V6.1

Throughout these instructions, you must replace the following:

  • UPDI_LOCATION: The location where the V6.1 or V7.0 Update Installer 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

  • EJB3_PACKAGE: The name of the file containing the EJB3 feature pack fix pack. This will be one of the following:
    • Express, Base, ND : 6.1.0-WS-WASEJB3-i5osPPC-FP00000x.pak
    • AppClient :6.1.0-WS-AppClientEJB3-i5osPPC-FP00000x.pak

  • WEBSV_PACKAGE: The name of the file containing the Web Services feature pack fix pack. This will be one of the following:
    • Express, Base, ND : 6.1.0-WS-WASWebSvc-i5osPPC-FP00000x.pak
    • AppClient: 6.1.0-WS-AppClientWebSvc-i5osPPC-FP00000x.pak

Installing the fix pack

  1. 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.
  2. Start the host servers if they are not currently active:
    STRHOSTSVR *ALL
  3. System requirements/recommendations:
    1. The userid used to run the update must have *ALLOBJ authority.
    2. Your HTTP server(s) will have to be ended and restarted at the end of this procedure.
    3. 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.
    4. 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 job will run.
    5. 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.
    6. 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 option 2 below.
  4. Install the fix pack using one of the options below.

    Option 1: installFixpack 610x script
    Use this option when you have obtained the fix pack by applying the WebSphere Group PTF.

    When the WebSphere Group PTF is applied, the Update Installer is installed or updated, maintenance packages are restored to the Update Installer’s maintenance directory, and install/uninstallFixPack610x scripts are created in the bin directory of each WebSphere V6.1 product on the system. If a feature pack is installed, the feature pack fix pack will also be restored to the Update Installer’s maintenance directory.
    The installFixPack610x script can handle installing feature pack fix packs beginning in 6.1.0.21.
    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,
      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. You can use the –jobq, -jobqlib, and -job parameters to specify a different job queue, job queue library, and job name. 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 –job MYJOBNAME

    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('/update -W product.location=PRODUCT_LOCATION -W maintenance.package=UPDI_LOCATION/maintenance/MAINTENANCE_PACKAGE')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)
    • If the Web Services Feature Pack is installed, you must download the Web Services Feature Pack Fix Pack 6.1.0.x to UPDI_LOCATION/maintenance/. This must be done before invoking the installFixPack script. Then you must add the Web Services Feature Pack Fix Pack to the maintenance.package parameter.

      Example:
      -W maintenance.package="/maintenance/MAINTENANCE_PACKAGE; UPDI_LOCATION/maintenance/WSFP_PACKAGE"
    • If the EJB 3.0 Feature Pack is installed, you must also download the EJB 3.0 Feature Pack Fix Pack 6.1.0.x to UPDI_LOCATION/maintenance/. Then you must add the EJB 3.0 Feature Pack Fix Pack to the maintenance,package parameter.

      Example:
      –W maintenance.package="UPDI_LOCATION/maintenance/MAINTENANCE_PACKAGE; UPDI_LOCATION/maintenance/EJB3_PACKAGE"
    • If both Web Services Feature Pack and EJB3.0 Feature Pack are installed, you must download both Feature Pack Fix Packs and add both to the maintenance.package parameter.
    • To obtain the Web Services Feature Pack Fix Pack and the EJB 3.0 Feature Pack Fix Pack, see Feature Packs by version.

    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 your IBM 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 –W maintenance.package=UPDI_LOCATION/maintenance/MAINTEANCE_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. If a feature pack fix pack is installed along with the main fix pack, updatelog.txt will be located at: PRODUCT_LOCATION/logs/update/install The last line of the file indicates if the install was successful (INSTCONFSUCCESS), partially successful (INSTCONFPARTIALSUCCESS) or failed (INSTCONFFAIL).
    • 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
  1. 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.
  2. Start the host servers if they are not active:
    STRHOSTSVR *ALL
  3. System requirements/recommendations:
    1. The userid used to run the update must have *ALLOBJ authority.
    2. Your HTTP server(s) will have to be ended and restarted at the end of this procedure.
    3. 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.
    4. 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.
    5. 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.
  4. 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 the WebSphere Group PTF is applied, a uninstallFixPack610x script is created in the bin directory of each WebSphere V6.1 product on the system. If the uninstallFixPack610x script does 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, -jobq, -job parameters to specify a different job queue, job queue library, and job name.

      Example: uninstallFixPack610x -jobqlib MYLIB -jobq MYJOBQ –job MYJOBNAME

    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= -W backup.package=MAINTENANCE_PACKAGE')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)
    • If you have a EJB3 or Web Services Feature Pack FixPack installed, it will need to be uninstalled prior to the main Web Sphere fixpack.

      Examples:
      SBMJOB CMD(STRQSH CMD('UPDI_LOCATION/update -W update.type=uninstall -W product.location=PRODUCT_LOCATION -W backup.package=EJB3_PACKAGE')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)

      SBMJOB CMD(STRQSH CMD('UPDI_LOCATION/update -W update.type=uninstall -W product.location=PRODUCT_LOCATION -W backup.package=WEBSV_PACKAGE')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)

    Notes:
    • Uninstall of the fix pack may take over an hour depending on your IBM i 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.
  5. 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 logs for an EJB3 fix pack uninstall are located here:
    PRODUCT_LOCATION/logs/update/6.1.0-WS-WASEJB3-i5osPPC-FP000000x.uninstall where x is the fix pack number, for example, 5.

    The logs for a Web Service fix pack uninstall are located here.
    PRODUCT_LOCATION/logs/update/6.1.0-WS-WASWEBSV-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).

  6. End and restart the HTTP Admin instance if it was active during the uninstall. Use the following:
    ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
    STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
    Also stop and restart any HTTP server instances associated with V6.1 application servers.