SolarisLinuxWindowsAIX

Removing the fix pack from an instance interactively

Complete the following steps to remove the fix pack from your WebSphere Commerce instance.

Before you begin

  • Identify the WebSphere Commerce instance that contains the fix pack that you want to remove. If you created the instance after you applied the fix pack, you cannot uninstall the fix pack from that instance. Because the instance was created after the fix pack was applied, there was no update on instance. UPDI does not know that the fix pack is applied on the instance and there is no metadata to indicate that either. In such a case, instead of removing the fix pack from the instance, you must delete the instance so that you can complete the steps to uninstall the fix pack.
SolarisLinuxAIXNote: Fix packs that were installed by the root user must be uninstalled by the root user.

Procedure

  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 your 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. 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 removal of maintenance from the WebSphere Commerce instance, the Update Installer stops the WebSphere Commerce application automatically.
  4. Using the command line, navigate to the UPDI_installdir directory and type the following command:
    • SolarisLinuxAIX./update.sh
    • Windowsupdate.bat
  5. 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. On the Product Selection panel, ensure that the directory name is correct. This directory is the WebSphere Commerce installation directory.
    3. Click Next to accept the WebSphere Commerce product found on your computer.
    4. When prompted, specify the WebSphere Commerce instance that you want to remove the fix pack from.
    5. If you are uninstalling from a WebSphere Commerce Payments instance, a panel is displayed asking if you have WebSphere Application Server security enabled. Complete the required fields and click OK.
    6. Select Uninstall Maintenance package. Click Next.
    7. Select the appropriate fix pack file and click Next.
    8. You are prompted to export the WebSphere Commerce Enterprise application you selected. Click OK to start the exporting. This action takes several minutes.
    9. On the Summary page, review the information and click Next to begin the uninstall process.
  6. When the uninstall completes, ensure that the installer displays the message: Success:The following maintenance package was uninstalled. Review the information and click Relaunch to start the Update Installer wizard again or Finish to close the Update Installer. If you do not see a success message, the installer indicates which log files to check.
  7. Check the log files for errors. The log files are in: WC_installdir/logs/update/actions/uninstall.
  8. Restore the database backup to the point where it was before you applied the fix pack on instance
  9. 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

What to do next

If you applied the fix pack to multiple WebSphere Commerce or WebSphere Commerce Payments instances, repeat this process for each instance.