You can uninstall the fix package that WebSphere Automation
has most recently applied from a server installation by using the WebSphere Automation UI.
Before you begin
You must have a user profile with the Manage security data
permission. For more information, see Configuring roles and
permissions.Important: WebSphere Automation cannot install or uninstall fixes on WebSphere® Application Server or WebSphere Application Server
Liberty that are
installed on z/OS or iSeries platforms.
The server
installation with the fix that you want to remove must have a fix management record with a
successfully installed fix package (that is, an Install action with a
Succeeded status).
About this task
Only the most recently applied fix can be uninstalled by using the WebSphere Automation UI. To uninstall a fix package that is not the most
recently applied, remove the more recently applied fixes first, one at a time. Alternately, you can
use the instructions for uninstalling fixes by using the command
line.Note: The command-line method can be used to uninstall any fix package
that is installed on a server installation, unlike Uninstalling fixes by using the UI, which
removes only the most recently applied fix. However, using this command-line method does not create
a fix management record for the uninstallation of the fix package. If you use the command-line
method, the WebSphere Automation UI continues to show that the fix is
installed on the server installation. If you attempt to uninstall an uninstalled fix package using
the UI method, the uninstallation fails. A fix management record in this state prevents the UI
method from being used to uninstall any fix packages that were previously applied to the server
installation.
Procedure
-
Log in to WebSphere Automation; in the menu, click .
- Click Server management.
- Select the server that you want to modify from the list.
The server
installation details page opens.
- Click the Vulnerabilities tab, then click Fix
management within the Vulnerabilities page.
The
Fix management page displays the installation history for all of
the packages of fixes for the selected server. If fixes have been applied to this server, the
Uninstall latest package button is active. If the
Uninstall latest
package button is inactive, one of the following conditions is true:
- No fixes are installed. In this case, the table is empty.
- All of the fixes that were installed are uninstalled.
- The latest fix package is currently being uninstalled. Only one request to uninstall the latest
fix package can be issued for a server installation.
Note the following controls:
- Filtering options:
- Status
- To show fix management records of particular status, select one or more states from the list.
For more information, see the description of the Status column.
- Action
- To show fix management records that involve installing a fix, select
Install. To show fix management records that involve uninstalling a fix,
select Uninstall.
- Download audit report: Click this link to generate an audit report with
fix management records for this server in comma-separated text format. For more information, see
Generating an audit report of fix management records for a server.
- Uninstall latest package: Click this link to uninstall only the most
recently applied fix package. If you want to uninstall a fix package that is not the most recent,
you must first uninstall the more recently applied fix packages in succession.
Note the column headings:
- Fix number
- The unique, arbitrary number of the fix management record.
- Fix package name
- The ID for the interim fix or fix pack associated with the fix management record.
- Action
- Indicates whether the fix package is being installed or uninstalled as part of this fix
management record.
- Status
- The state of the fix. The possible states are:
- Ready to install. WebSphere Automation has the fix and is ready to
install it. To begin the installation of the fix, click the Install fix link
in the same row.
- Fetching fix. WebSphere Automation is still receiving the fix.
- Installing fix. The fix is being installed.
- Successful. Depending on the indicated action, the fix is either successfully installed on, or
successfully uninstalled from, the selected servers.
- Failed. The installation of the fix failed. Check the runbook.log file for
more information about the cause of the failure.
- Uninstalling package. The uninstallation of the fix package is in progress.
- Initiation time
- The date that the fix management record is created.
- Completion time
- The date and time of the completion of the action indicated for the fix management record. If
the completion date shows Pending for a fix management record, the fix is fetched but
is not automatically installed.
- Click Uninstall latest package.
The Uninstall
package window opens.
- Review the details of the fix package to be uninstalled.
Information about the
server installation with the fix package to be uninstalled is also shown.
- Click Uninstall.
The Confirm
uninstall window opens.
- Review the information in the Confirm uninstall
window.
WebSphere Automation stops any running servers to
uninstall the fix package. After the fix package is uninstalled, WebSphere Automation restarts any servers that are running when the command
to uninstall the fix package is given. WebSphere Automation does not
start any servers that are not running when the command to uninstall the fix package is
given.
- In the Confirm uninstall window, select whether to create a backup of the server
metadata.
- Click Proceed.
The Confirm uninstall window closes and
the Fix management page is shown. A notification is displayed that indicates whether the request to
uninstall the fix package is successful or not. This notification includes a new fix management
record ID for the request to uninstall the fix package. The table shows a new fix management record
for the request to uninstall the fix package, with an action of Uninstall and a
status of Pending.
- Monitor the fix management record.
When the fix package is uninstalled, the
status of the fix management record is Succeeded.