Viewing and managing fix management records
You can view and manage the installation of fixes to the servers in your inventory from the Security page in the WebSphere Automation UI.
Before you begin
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.
Procedure
-
Log in to WebSphere Automation; in the menu, click Operate > Application runtimes.
For more information, see Accessing the WebSphere Automation UI.
-
If necessary, open the Security page, and then click Fix
management.
Figure 1. Viewing example Security page with installation status of fixes 
If you do not see the menu option Operate > Application Runtimes, or if you see a message that you are not authorized, then you do not have permission to access the page. For more information about permissions, see Roles and permissions.
Note the following controls:- Filtering options:
- Hostname
- To show fix management records for a certain hostname, select hostname from the list. For more information, see the description of the Hostname column.
- 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.
- Sorting options (column headings):
- Fix number
- Fix numbers are arbitrary values that are assigned to the job of downloading and applying a fix
to one or more managed servers. A number is assigned when you click Prepare
fix on the information page for a CVE that affects your servers, or when you click
Uninstall latest package to uninstall a fix package. Click anywhere in a fix
management row to open the side panel with more information about the fix and the servers to which
it is applied. The following figure is an example of the Fix management side panel. The figure includes the following information.
- Fix management number
- Action indicated for the fix management record (either installing or uninstalling a fix package)
- Status
- Selected fix package
- Server information, including the type of application server, the hostname, installation directory, WebSphere version, and Java DSK version
- History of the status (that is, a record of actions taken and the results)
Figure 2. Fix management record that shows the server installation information and fix installation history 
- If the fix is in the
Fetchingstate, a toggle control appears in the side page. Set the toggle control to the On position to automatically begin applying the fix when the process is complete. When the toggle is not in the On position, you must initiate the installation of the fix. - If the fix is downloaded but not yet installed, an Install fix button displays in the side panel. Click the button to begin the process of installing the fix to the selected servers.
- When an installation or uninstallation process finishes, regardless of success or failure, a
runbook.log file is available for download. If the process failed, view the log
file with a text editor to find the cause of failure. For more information and user response for
common error messages, see Troubleshooting runtime issues.
Figure 3. Fix management record entry showing the runbook.log file download link 
- Fix package name
- The unique ID for the interim fix or fix pack that is installed or uninstalled as part of this fix management record.
- Action
- Indicates whether the fix management record involves installing or uninstalling the fix package.
- Hostname
- The hostname of the server installation.
- Installation directory
- The directory for the server installation.
- 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.
- Other controls or column headings:
- Download audit report
- Opens a dialog to open or save an audit report with fix management records in comma-separated text format. For more information, see Generating an audit report of fix management records for all servers.
- 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. The timeout value for this state is 7 days, although the download terminates long before this timeout occurs.
- Installing fix. The fix is being installed. The timeout value for this state is 24 hours.
- Succeeded. Depending on the indicated action, the fix is either successfully installed on, or successfully uninstalled from, the selected servers.
- Pending. The fix is fetched but not yet installed. Installation must be manually initiated. The timeout value for this state is 30 minutes.
- 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.
- Install fix
- When the fix is ready to be installed, the Status column for the Installation ID displays Ready to install and an Install fix link appears in the row. To install the fix on the indicated servers, click Install fix.
- Page controls
- You can select the number of servers to display per page, and move from page to page when the list requires more than one page.
- Filtering options:
- Use the data to assess your exposures and plan your mitigation.