SolarisLinuxWindowsAIX

Updating the instance interactively

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

Before you begin

Important:
  1. If you have a database performance concern, consider having your database administrator tune the database before the fix pack update to the WebSphere Commerce or WebSphere Commerce Payments instance. If the database is poorly tuned, the update command might run a long time. See 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. Windows Log on 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. Ensure that the Configuration Manager server is stopped.
  4. Ensure that your database is started.
  5. Ensure that WebSphere Commerce administrative server is started.
    • If WebSphere Commerce is managed by WebSphere Application Server Deployment Manager (dmgr), start the deployment manager and all node agents. Optionally, 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. Using the command line, navigate to the UPDI_installdir directory and enter the following command:
    • SolarisLinuxAIX./update.sh WebSphere Commerce Version 7.0.0.9[-W update.exportearTimeout=interval]
    • Windowsupdate.bat WebSphere Commerce Version 7.0.0.9[-W update.exportearTimeout=interval]
    Where
    WebSphere Commerce Version 7.0.0.9 or laterupdate.exportearTimeout
    WebSphere Commerce Version 7.0.0.9 or laterOptional: 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.
  7. The WebSphere Commerce Update Installer wizard is launched. Complete the following steps:
    1. On the Welcome panel, review the information and click Next to continue.
    2. Specify the WebSphere Commerce installation directory or click Next to accept the WebSphere Commerce product found on your computer.
    3. When prompted, specify the instance name from the drop-down list that you want to apply the fix pack to. If you are applying the fix pack to a WebSphere Commerce Payments instance, complete the information in the panel. Click OK to continue.
    4. Select Install maintenance package and click Next.
    5. Select the UPDI_installdir/maintenance directory and click Next.
    6. On the Available Maintenance Package to Install page, select the appropriate fix pack and click Next to begin the installation.
      Ensure that you select the fix pack package only.
      Note: You cannot install fix packs and individual interim fixes at the same time.
    7. You are prompted to update the database.
      • To automatically update your database, select Yes for the message:
        Do you want the wizard to apply the database update?
The process could take approximately nn minutes.
        Where nn indicates the number of minutes.

        The database update could take some time. Check the updatedb-instance_name.log file and see Troubleshooting: Update Installer warning message during database update.

      • If you select No, you can still manually update your database later. To manually update the database after installation, see Installing final steps.
    8. You are prompted to start exporting the WebSphere Commerce Enterprise application that you selected. Click OK to export the application. This action takes several minutes.
    9. On the Summary page, review the information and click Next to begin the installation process.
  8. Ensure that the installer displays the message: Success:The following maintenance package was installed. If you do not see this message, the installer indicates which log files to check. Click Finish. to exit the Update Installer wizard.
  9. Check the database log file for errors.
    • WC_installdir/logs/update/updatedb-instancename.log
  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
        • WindowsIBMPayServer 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

    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

See Installing final steps to complete the fix pack installation.