Uninstalling fix packs from distributed operating systems by using the command line

You can roll back this product to an earlier version by using the Installation Manager command line.

Before you begin

Restriction: In order to use this procedure, you must have Installation Manager Version 1.6 or later installed on your system.

During the rollback process, the Installation Manager must access files from the earlier version of the product package. By default, these files are stored on your computer when you install a product package. If you change from the default and choose not to save backup files for rollback or if you delete the saved files, the Installation Manager requires access to the installation package in the repository at the prior level to roll back to earlier versions of the product package.

If fix packs are installed on the original installation package, you need to specify the repositories of the fix pack version that you want to roll back to. You also need to specify other repositories that the Installation Manager requests. The general availability repository is the most important to specify. Specify this repository as 8.5.5.0 for version 8.5.5.

Important: Installation Manager can install any fix-pack level of the product directly without installing the interim fix packs. In fact, Installation Manager installs the latest level by default. For example, you can skip fix-pack levels and go from Version 8.5.0.1 directly to Version 8.5.0.5. However, keep in mind that later you cannot roll back to any level that was skipped. If you directly install to Version 8.5.0.5, for example, you cannot roll back to Version 8.5.0.4. If you skip from Version 8.5.0.1 to Version 8.5.0.5, you can roll back only to Version 8.5.0.1.

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

Optional: If the repository requires a username and password, create a keyring file to access this repository.
For more information on creating a keyring file for Installation Manager, read the IBM Installation Manager documentation.

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.
Log on to your system.
Stop all servers and applications on the WebSphere Application Server installation that is being rolled back.
Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager.
Use the imcl command to roll back the product.
```
./imcl rollback offering_ID_offering_version
  -repositories source_repository 
  -installationDirectory installation_directory
  -preferences preference_key=value
  -properties property_key=value
  -keyring keyring_file -password password
  -acceptLicense
```
```
imcl.exe rollback offering_ID_offering_version
  -repositories source_repository 
  -installationDirectory installation_directory
  -preferences preference_key=value
  -properties property_key=value
  -keyring keyring_file -password password
  -acceptLicense
```
Tips:
- The offering_ID is the offering ID that is listed in WebSphere Application Server product offerings for supported operating systems.
- The offering_version, which optionally can be attached to the offering ID with an underscore, is a specific version of the offering to which to roll back (8.5.0.20110503_0200 for example).
  - If offering_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 offering_version is specified, the installation rolls back to the specified earlier version of the offering and no 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 on the command line:
```
-properties user.addon="",user.feature=""
```
  Specifying these properties enables the product to rollback and uninstalls all features and addons.
For more information on using Installation Manager, read the IBM Installation Manager documentation.

Optional: List all installed packages to verify the roll back.

./imcl listInstalledPackages -long

imcl.exe listInstalledPackages -long