Uninstalling fix packs from the Web Server Plug-ins on IBM i operating systems using response files

You can roll back the Web Server Plug-ins to an earlier version 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

Perform this procedure to use Installation Manager to roll back the Web Server Plug-ins to an earlier version using Installation Manager response files.

Note: For information on installing and removing fix packs for WebSphere Application Server offerings on IBM i systems using the Installation Manager command line, read the following topics:

Installing fix packs on IBM i operating systems using the command line
Uninstalling fix packs from IBM i operating systems using the command line

Procedure

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.
Sign on to the IBM® i system with a user profile that has *ALLOBJ and *SECADM special authorities.
On a CL command line, run the STRQSH command to start the Qshell command shell.
Use a response file to roll back the Web Server Plug-ins.
Change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and roll back the Web Server Plug-ins. For example:
```
./imcl
  input $HOME/WASFiles/temp/rollback_response_file.xml 
  -log $HOME/WASFiles/temp/rollback_log.xml 
  -keyring $HOME/WASFiles/temp/im.keyring
```

Example

The following is an example of a response file for rolling back the Web Server Plug-ins to an earlier version.

<?xml version="1.0" encoding="UTF-8"?>
<agent-input>
<server>
   <repository 'https://www.ibm.com/software/repositorymanager/com.ibm.websphere.PLG.v85'/>
</server>
<profile id='Web Server Plug-ins for IBM WebSphere Application Server V8.5' installLocation='/QIBM/ProdData/WebSphere/AppServer/V85/PLG'>
  <data key='eclipseLocation' value='/QIBM/ProdData/InstallationManager'/>
</profile>
<rollback>
  <offering profile='Web Server Plug-ins for IBM WebSphere Application Server V8.5' id='com.ibm.websphere.PLG.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 Installation 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 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.