Updating the instance silently

After you install the WebSphere Commerce fix pack, use the silent method to update any existing instances to the same fix pack level.

Before you begin

Ensure that the following task is completed:
Important:
  1. If you have a database performance concern, consider having your database administrator tune the database before the fix pack update. If the database is poorly tuned, the update command might run a long time. Refer to your database manual for specifics of tuning the database.
  2. Each new WebSphere Commerce or WebSphere Commerce Payments instance that is created after you applied the fix pack to your WebSphere Commerce installation directory, is created at that specific fix pack level. You are not required to update the WebSphere Commerce or WebSphere Commerce Payments instance to the fix pack level.
  3. If you have multiple WebSphere Commerce or WebSphere Commerce Payments instances created you must repeat the installation, of the fix pack, for each instance.
  4. If you have both a staging and a production environment, you must perform the steps that are outlined in Step 5 of Installing WebSphere Commerce fix packs to ensure that the following actions are completed:
    1. The environments are synchronized.
    2. You made note of the latest STAGLOG record.
    3. All other activities on the staging server are stopped before the fix pack is installed and the instance is updated.

Procedure

Complete the following steps to install the fix pack to the WebSphere Commerce instance.
  1. WindowsEnsure that you are logged in with a user ID that is a member of the Windows Administration group.
  2. SolarisLinuxAIX Log on.
    • Log on as the root user
      • If you are already signed onto the system, issue the command su - root. Do not use the command su root. This command does not load the necessary root user's profile and environment.
    • Feature Pack 8WebSphere Commerce Version 7.0.0.9Or log on as a non-root user that owns WC_installdir.
    Note:
    • Ensure that the file size limit is set to unlimited. To check the current limit, type the following in a command window: ulimit -a

      If the value returned for the file size is not set to unlimited, change the limit by running the following command: ulimit -f unlimited​

    • Ensure that you increase the default limit of the open files parameter. Change the limit by running the following command: ulimit -n 8192
  3. For IBM i OS operating systemEnsure that your user has *SECOFR authority.
  4. SolarisLinuxWindowsAIXEnsure that your database server is started.
  5. Ensure that the WebSphere Commerceadministrative server is started.
    For example:
    • If WebSphere Commerce is managed by WebSphere Application Server Deployment Manager (dmgr), start the deployment manager and all node agents. Your cluster can also be started.
    • If WebSphere Commerce is not managed by WebSphere Application Server Deployment Manager (dmgr), start the WebSphere Application Server server1.
    Note: During the application of maintenance to the WebSphere Commerce instance, the Update Installer stops the WebSphere Commerce application automatically.
  6. Navigate to the UPDI_installdir/responsefiles directory and open the install.txt file in a text editor.
    Note: By default, lines with which you must provide information, start with a hashtag (#) character, such as: 
    #-W update.instancename="instance_name"
    The hashtag comments out the line. Be sure to remove the hashtags on any lines you change to ensure that they are no longer commented out.

    Edit the following lines:

    1. Update the -W maintenance.package entry with the directory name that contains the maintenance package.
    2. Update the -W product.location entry with the location of the WebSphere Commerce installation directory.
    3. Complete one of the following steps:
      • If you are updating a WebSphere Commerce instance, add the following lines to the end of the install.txt file: 
        -W update.instancename="instance_name"
-W update.db="true"
WebSphere Commerce Version 7.0.0.9 or later-W update.exportearTimeout=interval
        Note:
        • If you set -W update.db="false", you must update the database manually. See Installing final steps.
        • WebSphere Commerce Version 7.0.0.9 or laterupdate.exportearTimeout:

          Optional: The maximum amount of allowable time (in minutes) for the export EAR process, which is exporting the WebSphere Commerce Application, to complete. If the export EAR process takes more than interval minutes, then a timeout error occurs. By default, the interval is set to 240 (minutes) but can be changed to suit your system needs. For example, -W update.exportearTimeout=360 allows for 360 minutes.

      • If you have a WebSphere Commerce Payments instance where WebSphere Application Server security is not enabled, add the following line to the end of the install.txt file: 
        -W update.instancename="payments_instance_name"
      • If you have a WebSphere Commerce Payments instance with WebSphere Application Server security enabled, add the following lines to the end of the install.txt file: 
        -W update.instancename="payments_instance_name"
-W update.wassecurityenable="true" 
-W update.wasuserid="WAS_user" 
-W update.wasuserpassword="WAS_password"

        Where WAS_user is a user that is defined in the user registry and WAS_password is the associated password for the user.

  7. For IBM i OS operating systemStart a Qshell session by typing QSH at the command prompt.
  8. Run one of the following commands from the UPDI_installdir directory:
    • SolarisLinuxAIX./update.sh -options UPDI_installdir/responsefiles/install.txt -silent
    • For IBM i OS operating systemupdate -options UPDI_installdir/responsefiles/install.txt
    • Windowsupdate.bat -options UPDI_installdir/responsefiles/install.txt -silent

    WindowsWhen the prompt returns wait for the Java process that is associated with the Update Installer to finish.

    If you specified -W update.db="true", the database update might take some time to complete. Check the updatedb-instance_name.log file and refer to Troubleshooting: Update Installer warning message during database update.

  9. Check the log files for errors. The log files are in the following directories:
    • WC_installdir/logs/update
    • WC_installdir/logs/update/actions/install
  10. Complete one of the following steps:
    • If you have a WebSphere Commerce instance, restart the WebSphere Commerce application.
    • If you have a WebSphere Commerce Payments instance with no security enabled, restart the WebSphere Commerce Payments application.
    • If you have a WebSphere Commerce Payments instance with security enabled, complete the following steps:
      1. SolarisLinuxAIXLog in as the non-root user.
      2. Navigate to directory WC_installdir/payments/bin.
      3. Run the following command:
        • SolarisLinuxAIX./IBMPayServer payments_instance_name payment_password
        • WindowsFor IBM i OS operating systemIBMPayServer payments_instance_name payment_password
  11. Check the WC_profiledir/logs/server1/SystemOut.log file to ensure that the database version is at the same level as the EAR version.
    For example, search for a message similar to the following message: 
     0000000a SystemOut O WC.SERVER: Enterprise 7.0.0.X / Database: ENT 7.0.0.X
    Where X is the level of fix pack installed.
    This message indicates that the EAR version and database version are the same version. The levels are retrieved from:
    • EAR: WC_profiledir/installedApps/cell_name/WC_instance_name.ear/properties/version/COMMERCE.product
    • Database: SITE Table

    If the versions are not the same, contact IBM Support.

  12. If you have both a staging and a production environment, you must perform the steps that are outlined in Step 5 of Installing WebSphere Commerce fix packs to ensure that the following actions are completed:
    1. All the STAGLOG records inserted during fix pack installation and instance update are deleted from the staging database.
    2. If Access Control Policy is in a staging environment, run the stagingcopy utility.
    DB2If you encounter problems with stagingcopy, complete the following steps:
    1. Update the STMTHEAP database configuration parameter for both staging and production server databases, db, to a higher value. For example:

      db2 update database configuration for db using stmtheap 240000

    2. Similarly, update the APPLHEAPSZ database configuration parameter for both staging and production server databases, db, to a higher value. For example:

      db2 update database configuration for db using applheapsz 3000

    3. Disconnect all users from both staging and production server databases.
    4. Run the stagingcopy utility.

What to do next

To complete the fix pack installation, see Installing final steps.