Remove the fix pack from an instance silently

Before removing a fix pack, remove the fix pack from any WebSphere Commerce instances that were updated to the fix pack level.

Prerequisite Identify the WebSphere Commerce instance that the fix pack will be removed from. If you have created your instance after applying the fix pack, you cannot uninstall the fix pack from that instance.
Complete the following steps to remove the fix pack from your WebSphere Commerce instance.

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

2. AIX|Linux|Solaris|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.

3. I5/OS|Ensure that you are logged in 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 WAS 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 WAS Deployment Manager (dmgr), start the WAS server1.

   
   

   During the removal of maintenance from the WebSphere Commerce instance, the Update Installer stops the WebSphere Commerce application automatically.

5. Navigate 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 directory name that contains the maintenance package.
      

      If the W backup.package is not specified, the most recently installed fix pack is uninstalled.

   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 WebSphere Commerce instance, add the following lines to the end of the uninstall.txt file

        -W update.instancename="instance"
        
        
        

      • If you have a WebSphere Commerce Payments instance without WAS security enabled, add the following line to the end of the uninstall.txt file

        -W update.instancename="payments_instance"
        
        
        

      • If you have a WebSphere Commerce Payments instance with WAS security enabled, add the following lines to the end of the uninstall.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.

   4. Save the file changes.

6. I5/OS|Open the QShell by typing QSH at the command prompt.

7. Run one of the following commands from the UPDI_installdir directory:

   • AIX|Linux|Solaris|./update.sh -silent -options UPDI_installdir/responsefiles/uninstall.txt

   • I5/OS|update -devkit14 -options UPDI_installdir/responsefiles/uninstall.txt

   • Windows: update.bat -silent -options UPDI_installdir/responsefiles/uninstall.txt

   Windows:

   When the prompt returns wait for the Java process 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/actions/uninstall.

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

     1. Linux|AIX|Solaris|Log in as the non-root user.

     2. Navigate to directory WC_installdir/payments/bin.

     3. Run the following command:

        • AIX|Linux|Solaris|./IBMPayServer payments_instance payment_password

        • Windows: IBMPayServer payments_instance payment_password

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

 

Related Reference

WebSphere Commerce APARs
Troubleshoot: WebSphere Commerce fix pack issues