[AIX Solaris HP-UX Linux Windows]

Uninstalling fix packs from distributed operating systems by using response files

You can roll back this product to an earlier version by using Installation Manager response files.

Before you begin

During the rollback process, Installation Manager must access files from the earlier version of the package. By default, these files are stored on your computer when you install a package. If you change the default setting or delete the saved files, Installation Manager requires access to the repository that was used to install the earlier version.

About this task

Restriction: You cannot use the Installation Manager to roll back an installation and add or remove the full WebSphere® Application Server profile feature or the Liberty profile feature.

Procedure

  1. Optional: If the repository requires a username and password, create a keyring file to access this repository.
    Tip: When creating a keyring file, append /repository.config at the end of the repository URL location if the imutilsc command is unable to find the URL that is specified.
    Supported configurations:

    Starting in Installation Manager Version 1.6.2, the -keyring and -password options that were used to access credentials in a key ring file are deprecated. For Installation Manager Version 1.6.2 and later, use the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file.

    In Version 1.7, the format of the secure storage file is revised, and is no longer compatible with versions of Installation Manager before version 1.7. Update Installation Manager to version 1.7 or higher and then re-create and replace any secure storage files that you created with earlier versions.

    There is no migration path from key ring files to storage files because of the differences in the file structures. You must create a storage file to replace a key ring file. For more information about using the -secureStorageFile and -masterPasswordFile options to store credentials in a credential storage file, see the IBM Installation Manager documentation.

  2. Log on to your system.
  3. Stop all servers and applications on the WebSphere Application Server installation that is being rolled back.
  4. Use a response file to roll back the product.

    Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and roll back the product.

    For example:
    • [Windows] Administrator or non-administrator:
      imcl.exe
        input C:\temp\rollback_response_file.xml 
        -log C:\temp\rollback_log.xml 
        -keyring C:\IM\im.keyring
    • [Linux][AIX][HP-UX][Solaris]Administrator:
      ./imcl
        input /var/temp/rollback_response_file.xml 
        -log /var/temp/rollback_log.xml 
        -keyring /var/IM/im.keyring
    • [Linux][AIX][HP-UX][Solaris]Non-administrator:
      ./imcl
        input user_home/var/temp/rollback_response_file.xml 
        -log user_home/var/temp/rollback_log.xml 
        -keyring user_home/var/IM/im.keyring
    Note: The program might write important post-installation instructions to standard output.
  5. Optional: List all installed packages to verify the roll back.
    [Linux][AIX][HP-UX][Solaris]
    ./imcl listInstalledPackages -long
    [Windows]
    imcl.exe listInstalledPackages -long
[Windows]

Example

The following is an example of a response file for rolling back the product to an earlier version. For the Express product, replace BASE in the file with EXPRESS.
<?xml version="1.0" encoding="UTF-8"?>
<agent-input>
<server>
  <repository location='https://www.ibm.com/software/repositorymanager/com.ibm.websphere.BASE.v85'/>
</server>
<profile id='IBM WebSphere Application Server V8.5' installLocation='C:\Program Files\IBM\WebSphere\AppServer'>
  <data key='eclipseLocation' value='C:\Program Files\IBM\WebSphere\AppServer'/>
</profile>
<rollback>
  <offering profile='IBM WebSphere Application Server V8.5' id='com.ibm.websphere.BASE.v85' version='8.5.0.20101025_2108'/>
</rollback>
</agent-input>
Tips:
  • The profile ID (<profile . . . id='profile_ID' . . . .> and <offering . . . profile='profile_ID' . . . .>) can be found when you run the imcl listInstallationDirectories -verbose command from the eclipse/tools subdirectory in the directory where you installed Installation Manager. It is the same as the package group’s name.
  • The offering ID (<offering . . . id='offering_ID' . . . .>) can be found in the Install Manager Offering ID section of the report that is generated when you run the historyInfo or genHistoryReport command from the app_server_root/bin directory.
  • The version is a specific version of the offering to which to roll back (8.5.0.20101025_2108 for example).
    This specification is optional if you are using Installation Manager Version 1.5 or later.
    • If version is not specified, the installation rolls back to the previously installed version of the offering and all interim fixes for that version are installed.
    • If version is specified, the installation rolls back to the specified earlier version of the offering and all interim fixes for that version are installed.

    The offering version can be found attached to the end of the offering ID with an underscore in the Package section of the report that is generated when you run the historyInfo or genHistoryReport command from the app_server_root/bin directory.

  • If you previously installed Liberty Repository features and addons but do not have access to a Liberty repository when you rollback your installation, specify the following properties in the response file:
    <data key='user.feature' value=''/> 
    <data key='user.addon' value=''/>
    Specifying these properties enables the product to rollback and uninstalls all features and addons.