Generating an audit report of fix management records for all servers
You can generate an audit report that shows the fix management records for the runtimes
in your inventory in comma-separated value (CSV) format.
Before you begin
You must have a user profile with the View security data permission
or the Manage security data permission. For more information, see Configuring roles and
permissions.
About this task
Note: Beginning in WebSphere Automation 1.6.4, audit reports contain
information about registered servers and servers that are no longer registered with WebSphere Automation.
If necessary, open the Security page, then click the Fix
management tab, as shown in the following image.
Figure 1. Example Servers page that lists fix management records
If you do not see a listing of fix management records, either no servers are registered, or
you have insufficient permissions. For instructions on registering servers, see Registering a server. For more
information about permissions, see Roles and
permissions.
Click Download audit report.
In the system dialog that opens, you can open or save the audit report to your local
computer.
Open the audit report by using a program capable of viewing CSV files, such as a spreadsheet
editor.
The data looks similar to the following image:Figure 2. Viewing example audit report of security status of servers in CSV format
Note the column headings:
Fix number
Fix management IDs are arbitrary values that are assigned to the job of downloading and applying
a fix to one or more managed servers.
Fix package name
The 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.
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.
Hostname
The hostname of the server.
Installation directory
The directory where the server software is installed.
WebSphere version
The version of WebSphere Application Server or WebSphere Application Server Liberty that is used by the server.
Java SDK version
The version of Java™ that is installed on the server.
Initiation time (UTC)
The date and time that the action indicated for the fix management record was started, in ISO
standard yyyy-MM-dd HH:mm (UTC time) format. The editor that you import the data
into might convert the date to a different format. If the completion date shows
Pending for a fix management record, the fix is fetched but is not automatically
installed.
Completion time (UTC)
The date and time of the completion of the action indicated for the fix management record, in
ISO standard yyyy-MM-dd HH:mm (UTC time) format. The editor that you import the
data into might convert the date to a different format. If the completion date shows
Pending for a fix management record, the fix is fetched but is not automatically
installed.