Install > Installing maintenance > WebSphere Commerce > Installing WebSphere Commerce fix packs > ...interactively


Update the instance interactively

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


Before you begin

If you have a database performance concern, consider having the database administrator tune the database before the fix pack update to the WebSphere Commerce or WebSphere Commerce Payments instance. The update command might run a long time if the database is poorly tuned. See the database manual for specifics of tuning the database.

Each new WebSphere Commerce or WebSphere Commerce Payments instance that is created after you have applied the fix pack to the 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.

If you have multiple WebSphere Commerce or WebSphere Commerce Payments instances created repeat the install, of the fix pack, for each instance.


Procedure

Complete the following steps to install the fix pack to the WCS instance.

  1. Ensure that you are logged in with a user ID that is a member of the Windows Administration group.

  2. Ensure that you are logged in as the root user. Use one of the following methods:

    • Sign on with 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 root user's profile and environment which are required for fix pack installation.

    The root user's umask must be set to 0027 in order to secure the fix pack installation.

  3. Verify the WebSphere Commerce administrative 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. 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.

    During the application of maintenance to the WCS instance, the Update Installer stops the WebSphere Commerce application automatically.

  4. Verify the database is started.

  5. Use the command line, navigate to the UPDI_installdir directory and enter the following command:

    • ./update.sh

    • update.bat

  6. 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 the computer.

    3. When prompted, specify the instance name from the drop down list that to apply the fix pack to. If you are applying the fix pack to a WebSphere Commerce Payments instance, complete the information about 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 maintenance and click Next to begin the installation.

    7. You are prompted to update the database.

      • To automatically update the database, select Yes for the message: 

        Do you want the wizard to apply the datbase 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.log file and see ../refs/rigfixpacktowebspherecommerce.htm.

      • If you select No , see Install final steps after you have completed the installation.

    8. You are prompted to start exporting the WebSphere Commerce enterprise application that you have selected. Click OK to export the application. This action will take several minutes.

    9. On the Summary page, review the information and click Next to begin the install process.

  7. Verify the installer displays the message: Success:The following maintenance package was installed. If you do not see this message, the installer will indicate which log files to check. Click Finish. to exit the Update Installer wizard.

  8. Check the log files for errors. The log files are located in the following directories:

  9. Check the WC_PROFILE/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: 

     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 the EAR version and Database version are the same version. The levels are retrieved from:

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

  10. Complete one of the following steps:

    • If you have a WCS 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...

      1. Log in as the non-root user.

      2. Navigate to directory WC_INSTALL/payments/bin.

      3. Run the following command:

  11. If you are using a staging server run the stagingcopy utility.

    If you encounter problems with staging copy...

      1. Change STMTHEAP to the maximum value. For example:

        db2 update database configuration for db_schema using stmtheap 240000

      2. Change APPLHEAPZ to 3000. For example:

        db2 update database configuration for db_schema using applheapsz 3000

      3. Disconnect all users from DB2.

      4. Stop and restart DB2.

      5. Run the stagingcopy utility.


    What to do next

    See Install final steps to complete the fix pack installation.


    +

    Search Tips   |   Advanced Search