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

Update the instance silently

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

Before you begin

Ensure the following task is completed:

• Update the installation directory silently

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

2. 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.

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

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

Procedure

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 is 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 user has *SECOFR authority.

4. Ensure the database server is started.

5. 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.

6. Navigate to the UPDI_installdir/responsefiles directory and open the install.txt file in a text editor. 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 with the location of the WebSphere Commerce install directory.

   3. Complete one of the following steps:

      • If you are updating a WCS instance, add the following lines to the end of the install.txt file:

        -W update.instancename="instance"
        -W update.db="true"
        

        If you set -W update.db="false" you must update the database manually. See Install final steps.

      • If you have a WebSphere Commerce Payments instance without WebSphere Application Server security enabled, add the following line to the end of the install.txt file:

        -W update.instancename="payments_instance"
        

      • 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"
        -W update.wassecurityenable="true"
        -W update.wasuserid="WAS_user"
        -W update.wasuserpassword="WAS_password"

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

      The database update could take some time. Check updatedb-instance.log

7. cd UPDI_installdir
   ./update.sh -silent -options UPDI_installdir/responsefiles/install.txt

   When the prompt returns wait for the Java process associated with the Update Installer to finish.

8. Check the log files for errors.
   WC_INSTALL/logs/update
   WC_INSTALL/logs/update/actions/install

9. Check...
   WC_PROFILE/logs/server1/SystemOut.log

   ...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:

   EAR	WC_PROFILE/installedApps/cell_name/WC_instance.ear/properties/version/COMMERCE.product
   Database	SITE table

   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:

         • ./IBMPayServer payments_instance payment_password

         • IBMPayServer payments_instance payment_password

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

Refer to Install final steps to complete the fix pack installation.

+

Search Tips   |   Advanced Search