WebSphere Application Server for IBM i - Version 8.0 Fix packs

1. The WebSphere Group PTF has also provided a local repository for the latest IBM Installation Manager (IM) fix pack, and it is recommended that the IM be updated before you install the WebSphere fix packs provided by the WebSphere Group PTF. The Readme.txt and Readme.html files for the IM fix pack can be found here:
   /QIBM/WAS/IMFIXPACKS/Readme.txt /QIBM/WAS/IMFIXPACKS/Readme.html
   
2. Please review and follow the instructions listed in the document below to install the WAS 8.0 fix pack.
   How To Install an IBM WebSphere Application Server (WAS) Fix Pack Using the IBM Web Administration for i Console
   
   Note: Prior to updating your IBM WebSphere Application Server installation, it is HIGHLY recommended to export/backup your IBM Installation Manager installation data. Please refer to the IBM Software Technical Document: "How and When To Export/Backup Your IBM Installation Manager Installation Data on the IBM i?" for more information.

Throughout these instructions, you must replace the following:

• <was_fixpack_product>: ( WAS | NDDMZ | PLG | CLIENT ) The cumulative WebSphere fix pack repositories are provided for each stand-alone product offering. The following names are used to create IFS directories in the path where the expanded WebSphere repositories are restored:
  
  Note: For product 5733W80 options 1,2 and 3 (Express, Base, ND) a common fix pack repository is used that is referred to as WAS. See list below.
  

  WAS:	5733W80 Option 1	- WebSphere Application Server V8 Express
  	5733W80 Option 2	- WebSphere Application Server V8 Base
  	5733W80 Option 3	- WebSphere Application Server V8 Network Deployment
  NDDMZ:	5733W80 Option 4	- WebSphere Application Server V8 ND DMZ Secure Proxy
  CLIENT:	5733W80 Option 6	- WebSphere Application Server V8 Client
  PLG:	5733W80 Option 7	- WebSphere Application Server V8 Plugins

• <was_fixpack_version>: Example '8001'. The cumulative WebSphere fix pack version number is used to create an IFS directory in the directory path where the expanded local repository is restored. For example, fix pack '8.0.0.1' will result in an IFS directory by the name '8001'.
• <was_fixpack_location>: The expanded cumulative WebSphere local repository will be restored into the following IFS directory: /QIBM/WAS/WASFIXPACKS/<was_fixpack_product>/<was_fixpack_version>/FIXPACK
• <product_location>: The location of the V8.0 product you are updating. Default locations are:
  
  

  Express:	/QIBM/ProdData/WebSphere/AppServer/V8/Express
  Base:	/QIBM/ProdData/WebSphere/AppServer/V8/Base
  ND:	/QIBM/ProdData/WebSphere/AppServer/V8/ND
  NDDMZ:	/QIBM/ProdData/WebSphere/AppServer/V8/NDDMZ
  AppClient:	/QIBM/ProdData/WebSphere/AppClient/V8/client
  WebServer Plugins:	/QIBM/ProdData/WebSphere/Plugins/V8/webserver

• <offering_ID>: A list of all supported Websphere Application Server Version 8 product offerings is provided by the topic "WebSphere Application Server Version 8 product offerings for supported operating systems" in the IBM WebSphere Application Server Information Center.
• <Installation_Manager_
  location>: /QIBM/ProdData/InstallationManager
  The root directory of the IBM Installation Manager (IM) product.

• A list of <offering_ID> on the system can be derived from the list of WebSphere packages that are currently installed. The following IBM Installation Manager (IM) imcl command option can be used to acquire this list:
  <Installation_Manager_location>
/eclipse/tools/imcl listInstalledPackages -long
  For all WebSphere installs in the resulting list, the output is in the following format: lt;product_location> : <package> : <product_description> : <product_version> where <package> is <offering_ID>_<offering_version>.
• A list of <product_location> on the system is collected when PTFs are applied. The information is output to a file named WEBSPHEREINSTALLS.TXT and is provided in the following format:

  InstallRoot	: <product_location>
  Offering	: <offering_ID>
  Offering version	: <offering_version : '8.0.0.20110503_0200' denotes the GA offering version>
  Provider	: IBM WebSphere
  Provider version	: <installed_version: 8.0.0.0 | 8.0.0.1 | etc., '8.0.0.0' denotes the GA product version>
  Product ID	: <EXPRESS | BASE | ND | NDDMZ | PLG | APPCLIENT>

  
  This file represents a snapshot of the WebSphere installations that were registered with IM at the time the PTF was installed, and may not contain current information if used at a later date. This file is found in the following location:
  /QIBM/WAS/WASFIXPACKS/<was_fixpack_product>/<was_fixpack_version>/WEBSPHEREINSTALLS.TXT
• Log files are generated when PTFs are applied that lists failure messages if the IFS files cannot be restored. These log files are located in the following IFS directories and the log names will end with a .log extension:
  /QIBM/WAS/WASFIXPACKS/<was_fixpack_product>/<was_fixpack_version>/

1. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
2. Display the current value of QALWOBJRST and then change it to *ALL if needed.
   • Execute the following CL command to display the current value of QALWOBJRST:
     DSPSYSVAL SYSVAL(QALWOBJRST)
   • If the current value is NOT *ALL, record the current value (so you remember what to change it back to) and then change the value to *ALL using the following CL command:
     CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL)
3. The WebSphere Group PTF has also provided a local repository for the latest IBM Installation Manager (IM) fix pack, and it is recommended that the IM be updated before you install the WebSphere fix packs provided by the WebSphere Group PTF. The Readme.txt and Readme.html files for the IM fix pack can be found here:
   /QIBM/WAS/IMFIXPACKS/Readme.txt /QIBM/WAS/IMFIXPACKS/Readme.html
4. Stop all servers and applications on the WebSphere Application Server installation that is being updated. These processes may include application server processes, nodeagent processes, deployment manager processes, job manager processes and WebSphere Application Server client applications.
   
   This is most easily done by ending all of the application server JVM jobs and the subsystem for the WAS installation version and edition you are updating.
   
   For example, if I am updating my WAS v8.0 Express installation; I would end all of the WAS v8.0 Express jobs in the QWAS8 subsystem first using the stopServer Qshell command for each profile job currently active in the subsystem:
   STRQSH cd <product_location>/bin ./stopServer <server> -profileName <profile>
   Note: The <server> and <profile> values are case sensitive and must match the names exactly. Then end the QWAS8 subsystem using the CL command:
   ENDSBS QWAS8 *IMMED
5. Install the fix pack.
   
   From a system command line, invoke the following SBMJOB command to submit the installation process to batch via the UDPATEWAS job; where
   <Installation_Manager
   _location>, <offering_ID>, <product_location> and <was_fixpack_location> are defined above:
   SBMJOB CMD(STRQSH CMD('umask 022;<Installation_Manager
   _location>/eclipse/tools/imcl install <offering_ID> -acceptLicense -installationDirectory <product_location> -repositories <was_fixpack_location>')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)
   
   Note: IBM recommends the use of the SBMJOB command to submit the installation to batch instead of running the command interactively. Running the installation process in batch will prevent issues from occurring if your interactive session loses connectivity or ends unexpectedly.
   
   Optionally, the IM imcl command can be executed interactively using the following steps:
   
   • On a CL command line, run the STRQSH command to start the Qshell command shell.
   • Make sure that the umask is set to 022.
     • To verify the umask setting, issue the following command:
       umask
     • To set the umask setting to 022, issue the following command:
       umask 022
   • Change to the <Installation_Manager_
     location>/eclipse/tools directory by executing the following command:
     cd <Installation_Manager_location>
/eclipse/tools
   • Execute the fix pack install process
     ./imcl install <offering_ID> -acceptLicense -installationDirectory <product_location> -repositories <was_fixpack_location> -showVerboseProgress
   
   Note: Installation of the fix pack may take over an hour depending on your IBM i system. If memory available to the IBM Installation Manager is limited, the update can take much longer, potentially several hours. You will know the installation process has completed when the UPDATEWAS job ends or the "./imcl install" command returns to a dollar sign in Qshell.
6. To verifiy that the fix pack correctly updated the WebSphere installation, execute the following Qshell command:
   <product_location>/bin/versioninfo
   The 'Version' that this command lists should be the same as the fix pack version just installed.
7. End and restart the HTTP Admin instance if it was active during the update. To end and restart the HTTP Admin invoke the following commands from a system command line:
   ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
   Note: In addition, you will want to restart any HTTP server instances associated with your WAS v8.0 application servers. This can be done using the following commands.
   ENDTCPSVR SERVER(*HTTP) HTTPSVR(<HTTPserver>) STRTCPSVR SERVER(*HTTP) HTTPSVR(<HTTPserver>)
8. Once the IBM WAS Fix Pack installation has been verified as successful, you are free to start your IBM WebSphere Application Server profiles back up using the following Qshell command.
   <product_location>/bin/startServer <server> -profileName <profile>
   In addition, you also may want to change your QALWOBJRST IBM i system value back to its original value using the following CL command:
   CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(<previousValue>)
9. The fix pack installation process is now complete. If you experience issues or have questions along the way, please contact the IBM i Global Support Center at 1-800-IBM-SERV and open a new service request

Note: The <was_fixpack_location> directories can be large and are not managed or deleted by WebSphere. After all WebSphere installations have been updated and they are no longer needed, the system administrator can delete them and all their contents.

Tip: IBM recommends saving the previous fix pack installation repository in case you need to rollback the fix pack to the previous version.

Additional information about installing a fix pack may be found in the information center article, "Installing fix packs on IBM i operating systems using the Installation Manager command line", for Express, Base, and Network Deployment.

Note: Prior to updating your IBM WebSphere Application Server installation, it is HIGHLY recommended to export/backup your IBM Installation Manager installation data. Please refer to the IBM Software Technical Document: "How and When To Export/Backup Your IBM Installation Manager Installation Data on the IBM i?" for more information.
Uninstalling a fix pack can be accomplished by rolling back the product to an earlier version using the instructions outlined in the document below.
"How To Rollback/UnInstall a Fix Pack at IBM WebSphere Application Server (WAS) v8.0 and later"
Optional: If you have a Passport Advantage account, you can also rollback the product to an earlier version using an IBM WebSphere Application Server live repository.

To roll back the IBM WAS product to an an earlier version using a live repository, perform the following steps:

1. Sign on to the IBM i system with a user profile that has *ALLOBJ and *SECADM special authorities.
2. Display the current value of QALWOBJRST and then change it to *ALL if needed.
   • Execute the following CL command to display the current value of QALWOBJRST:
     DSPSYSVAL SYSVAL(QALWOBJRST)
   • If the current value is NOT *ALL, record the current value (so you remember what to change it back to) and then change the value to *ALL using the following CL command:
     CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(*ALL)
3. The WebSphere Group PTF has also provided a local repository for the latest IBM Installation Manager (IM) fix pack, and it is recommended that the IM be updated before you rollback the WebSphere fix packs provided by the WebSphere Group PTF. The Readme.txt and Readme.html files for the IM fix pack can be found here:
   • /QIBM/WAS/IMFIXPACKS/Readme.txt
   • /QIBM/WAS/IMFIXPACKS/Readme.html
4. Stop all servers and applications on the WebSphere Application Server installation that is being updated. These processes may include application server processes, nodeagent processes, deployment manager processes, job manager processes and WebSphere Application Server client applications.
   
   This is most easily done by ending all of the application server JVM jobs and the subsystem for the WAS installation version and edition you are updating.
   
   For example, if I am updating my WAS v8.0 Express installation; I would end all of the WAS v8.0 Express jobs in the QWAS8 subsystem first using the stopServer Qshell command for each profile job currently active in the subsystem:
   STRQSH cd <product_location>/bin ./stopServer <server> -profileName <profile>
   
   Note: The <server> and <profile> values are case sensitive and must match the names exactly.
   and then end the QWAS8 subsystem using the CL command:
   ENDSBS QWAS8 *IMMED
5. On a CL command line, run the STRQSH command to start the Qshell command shell.
6. Make sure that the umask is set to 022.
   • To verify the umask setting, issue the following command: umask
   • To set the umask setting to 022, issue the following command: umask 022
7. Change to the <Installation_Manager
   _location>/eclipse/tools directory by executing the following command:
   cd <Installation_Manager_location>
/eclipse/tools
8. Construct the repository URL for your IBM WAS version and edition based on the <offering_ID> argument discussed earlier.
   ${REPOSITORY} would equal: http://www.ibm.com/software/repositorymanager/<offering_ID>/repository.config
   Example: the repository URL for the IBM WebSphere Application Server v8.0 ND product:
   http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80/repository.config
9. Encrypt your IBM Passport Advantage userID and password into a secure storage file.
   • Create your secure storage file and master password files. touch -C 819 /tmp/secureStorageFile.txt touch -C 819 /tmp/masterPasswordFile.txt
   • Populate the /tmp/masterPasswordFile.txt file with a passphrase that will be used to encrypt your IBM Passport Advantage credentials.
     echo '<IBM Master Password Passphrase>' > /tmp/masterPasswordFile.txt
   • Execute the imutilsc saveCredential utility to encrypt your credentials into the /tmp/secureStorageFile.txt file.
     ./imutilsc saveCredential -url http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80/repository.config -userName joe@us.ibm.com -userPassword just4me -secureStorageFile /tmp/secureStorageFile.txt -masterPasswordFile /tmp/masterPasswordFile.txt
     In the example above, just4me is the fictitious password of Joe's Passport Advantage account (joe@us.ibm.com) and /tmp/masterPasswordFile.txt is the master password file containing the secure passphrase.
10. Identify your IBM WebSphere Application Server installation path.
    
    The following steps will refer to your IBM WebSphere Application Server (WAS) installation directory as ${INSTALL_DIR}. Your specific WAS installation directory can be found by executing the following command.
    /QIBM/WAS/bin/queryWASinstalls
    

    Example output:
    WebSphere Edition:	ND
    Version:	8.0.0.5
    Installation Location:	/QIBM/ProdData/WebSphere/AppServer/V8/ND
    Installation Library:	QWAS8A
    Default Profile Location:	/QIBM/UserData/WebSphere/Appserver/V8/ND

    
    For the above example, the ${INSTALL_DIR} variable would equal the value of the "Installation Location" parameter, which equals:
    /QIBM/ProdData/WebSphere/AppServer/V8/ND
11. Display the installation event history for your installation and determine the "Package" value for the fix pack version you wish to roll back to.
    ${INSTALL_DIR}/bin/historyInfo
    After the previous installation events are displayed, you will need to identify the package name of the previous update you wish to rollback to. This is the value displayed next to the "Package" item for the installation event.
    
    For example, I have a WAS v8.0.0.5 ND installation that I would like to roll back to v8.0.0.0. I would execute the historyInfo command as displayed below. Then, I would locate the v8.0.0.0 installation event and make note the value for the "Package" item since it will be required for the "imcl rollback" command discussed later in this document.
    
    

    Installation Event
    Install Manager Offering ID	com.ibm.websphere.ND.v80
    Action	install
    Version	8.0.0.0
    ********
    Package	com.ibm.websphere.ND.v80_ 8.0.0.20110503_0200
    ********
    Log File Name	/QIBM/UserData/InstallationManager/logs/20130311_1700.xml
    Timestamp	2013-03-11 17:00:47-0500
    Result	success
    Installed Features	EJBDeploy tool for pre-EJB 3.0 modules Embeddable EJB container Stand-alone thin clients and resource adapters

    In my example, ${PACKAGE} would be equal to com.ibm.websphere.ND.v80_
    8.0.0.20110503_0200 since I want to roll back the installation to v8.0.0.0.
12. Execute the rollback of the IBM WebSphere Application Server installation to the previous fix pack version using a live repository.
    
    From a system command line, invoke the following SBMJOB command to submit the rollback process to batch via the UDPATEWAS job; where <Installation_Manager
    _location>, ${PACKAGE}, ${INSTALL_DIR} and ${REPOSITORY} are defined above:
    SBMJOB CMD(STRQSH CMD('umask 022;<Installation_Manager_
location>/eclipse/tools/imcl rollback ${PACKAGE} -installationDirectory ${INSTALL_DIR} -repositories ${REPOSITORY} -secureStorageFile /tmp/secureStorageFile.txt -masterPasswordFile /tmp/masterPasswordFile.txt')) JOB(UPDATEWAS) ALWMLTTHD(*YES) JOBQ(QSYS/QSYSNOMAX)
    
    Note: IBM recommends the use of the SBMJOB command to submit the rollback to batch instead of running the command interactively. Running the rollback process in batch will prevent issues from occurring if your interactive session loses connectivity or ends unexpectedly.
    
    Optionally, the IM imcl command can be executed interactively using the following steps:
    umask 022 $ cd <Installation_Manager_
location>/eclipse/tools $ ./imcl rollback ${PACKAGE} -repositories ${REPOSITORY} -installationDirectory ${INSTALL_DIR} -secureStorageFile /tmp/secureStorageFile.txt -masterPasswordFile /tmp/masterPasswordFile.txt -showVerboseProgress
    Once the fix pack rollback completes, you should receive the following message:
    Rolled back to ${PACKAGE} in the ${INSTALL_DIR} directory.
    
    Here is an example command to rollback the IBM WAS ND v8.0 product to 8.0.0.0 from 8.0.0.5.
    ./imcl rollback com.ibm.websphere.ND.v80_
8.0.0.20110503_0200 -repositories http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80/repository.config -installationDirectory /QIBM/ProdData/WebSphere/AppServer/V8/ND -secureStorageFile /tmp/secureStorageFile.txt -masterPasswordFile /tmp/masterPasswordFile.txt -showVerboseProgress
    In my example, here is the message that was returned indicating a successful rollback operation.
    Rolled back to com.ibm.websphere.ND.v80_
8.0.0.20110503_0200 in the /QIBM/ProdData/WebSphere/AppServer/V8/ND directory.
Note: Rollback of the fix pack may take over an hour depending on your IBM i system. If memory available to the IBM Installation Manager is limited, the update can take much longer, potentially several hours. You will know the rollback process has completed when the UPDATEWAS job ends or the "./imcl install" command returns to a dollar sign in Qshell.
13. Verify the IBM WebSphere Application Server installation is at the new version.
    
    Execute the following Qshell command:
    ${INSTALL_DIR}/bin/versionInfo
    i.e. /QIBM/ProdData/WebSphere/AppServer/V8/ND/bin/versionInfo
    
    

    Installed Product
    Name	IBM WebSphere Application Server - ND
    Version	8.0.0.0
    ID	ND
    Build Level	n1118.03
    Build Date	5/3/11
    Package	com.ibm.websphere.ND.v80_ 8.0.0.20110503_0200
    Architecture	System i
    Installed Features	WebSphere Application Server Full Profile EJBDeploy tool for pre-EJB 3.0 modules Embeddable EJB container Stand-alone thin clients and resource adapters

    
    As you can see in my example above, the IBM WebSphere Application Server ND installation was successfully rolled back from 8.0.0.5 to 8.0.0.0.
14. Once the IBM WAS Fix Pack rollback has been verified as successful, you are free to start your IBM WebSphere Application Server profiles back up using the following Qshell command.
    <product_location>/bin/startServer <server> -profileName <profile>
    
    In addition, you also may want to change your QALWOBJRST IBM i system value back to its original value using the following CL command:
    CHGSYSVAL SYSVAL(QALWOBJRST) VALUE(<previousValue>)
15. The fix pack rollback process is now complete. If you experience issues or have questions along the way, please contact the IBM i Global Support Center at 1-800-IBM-SERV and open a new service request.
    
    Additional information about rolling back a WebSphere Application Server installation to a previously installed version may be found in the information center article, "Uninstalling fix packs from IBM i operating systems using the command line", for Express, Base, and Network Deployment