Removing the fix pack from an instance silently

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. For IBM i OS operating system Log on with a user profile that has *SECOFR authority.
  4. 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.
  5. Go to the UPDI_installdir/responsefiles directory and open the uninstall.txt file in a text editor. Edit the following lines:
    1. Update the -W backup.package entry with the name of the maintenance package you intend to uninstall.
      For example: 7.0.0-WS-WCServer-FP002.pak.
      Note: If the -W backup.package is not specified, the most recently installed maintenance package is uninstalled.
    2. Update the -W product.location 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 uninstall.txt file:
        -W update.instancename="instance_name"
      • 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 uninstall.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 uninstall.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.

    4. Save the file changes.
  6. For IBM i OS operating systemOpen the Qshell by typing QSH at the command prompt.
  7. Run one of the following commands from the UPDI_installdir directory:
    • SolarisLinuxAIX./update.sh -silent -options UPDI_installdir/responsefiles/uninstall.txt
    • For IBM i OS operating systemupdate -options UPDI_installdir/responsefiles/uninstall.txt
    • Windowsupdate.bat -silent -options UPDI_installdir/responsefiles/uninstall.txt

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

  8. Refer to the log files in the following directory to verify that your uninstall was successful: WC_installdir/logs/update/7.0.0-WS-WCServer-FP000X.uninstall/.
  9. Restore the database backup to the point where it was before you applied the fix pack on instance
  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

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.