Glossary for WebSphere Automation

View definitions and examples of frequently used product terms.

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

A

Action: The action triggered by the user or product.
Example: For fix management, when installing a fix, the value is Install.

B

Bulletin: The ID of the security bulletin that contains the CVE.
Bulletin URL: The URL to the security bulletin that contains the CVE.

C

Completion time: The date and time of completion of the action triggered by the user or product. If the listed value is Pending, the action is not complete.
Example: For a health investigation, the date and time refers to the completion of the health investigation.
Creation time: The date and time of creation of the asset, CVE or action in the data store.
Example: For fix history, the date and time refers to the creation of the CVE in the data store.
CVE: The CVE ID for the CVE, as listed in the associated security bulletin. Multiple CVEs can be listed if there are more than one associated CVE with the asset or action. No CVE can be listed if there is no associated CVE with the asset or action.
CVSS: The Common Vulnerability Scoring System (CVSS) is a numerical rating of the severity of a vulnerability, on a scale of 0 (lowest severity) to 10 (highest severity).

D

Days exposed: The total number of days of CVE exposure for the registered server with the oldest detection date. This number only accounts for days that the server was exposed beginning with the date that the server was registered. If an applicable fix was installed and then uninstalled, the days during which the fix was installed are not included in the total.

E

F

Fix: The interim fix APAR number or fix pack installed on the server.
Fix number: The arbitrary sequencing number assigned to the action of downloading and applying a fix.
Fix package name: The name of the download file for the fix package.
Fixed time: The date and time that the fix was installed.
Fixes Applied: A space-separated list of interim fixes or fix packs installed on the server.

G

H

Hostname: A unique label assigned to the server.

I

Initial detection time: The date and time of initial detection of the asset, CVE, or action by the product.
Example: For CVEs affecting registered servers, the date and time refers to the initial detection of the CVE on a registered server.
Initiation / detection time: The date and time of the automated detection of an issue, or of the initiation of an action by the user.
Example: For a health investigation, the date and time refers to the initiation of the health investigation by the user if the listed value for the Investigation method attribute is Manual.
Initiation time: The date and time of initiation of the action triggered by the user or product.
Example: For fix management, the date and time refers to the initiation of installing a fix if the listed value for the Action attribute is Install.
Installation directory: The directory where the server is installed.
Investigation ID: The unique ID that identifies the health investigation upon its initiation.
Investigation method: The initiated method for the health investigation.
Example: For a health investigation, if the investigation was initiated by the user, the value is Manual.
Investigation number: The arbitrary sequencing number assigned to the action of initiating a health investigation.
Investigation type: The type of issue for the health investigation.
Example: For a health investigation, for a memory leak investigation, the value is Memory leak.

J

Java SDK version: The version of Java™ that is installed on the server.

K

L

Last updated time: The date and time of the last update of the asset, CVE or action by the user or product.
Example: For server management, the date and time refers to the most recent date that a fix was applied to the server.

M

N

Notification time: The date and time of notification of a change in status to the product.
Example: For fix history, the date and time refers to the notification of CVE exposure.

O

O/S: The operating system that is installed on the server.

P

Q

R

Risk level: The severity of the security exposure with the greatest risk for each server, with values of Low, Medium, High, and Critical. This is based on the CVSS values of the associated CVEs.
Runtime type: The runtime type.
Example: Examples of possible values are jdk for Java runtime, traditional for WebSphere Application Server, or liberty for WebSphere Application Server Liberty.

S

Server

The name of the server.

Server type

The type of server.

Example: A possible value is Application Server.

Servers fixed

The total number of registered servers for which the CVE is fixed.

Servers vulnerable

The total number of registered servers that are vulnerable to the CVE.

Status

The state of the asset, CVE, or action.

Examples:

For fix management, examples of possible values are Ready to install and Succeeded.
For server vulnerabilities, examples of possible values are Resolved and Unresolved.
For health investigations, examples of possible values are Investigating and Investigation failed.

Summary

A short description of the asset, CVE, or action.

Example: For server security, the summary is a short description of the associated CVE affecting the server, extracted from the security bulletin.

T

Topology: The server topology.
Example: Examples of possible values are the cell and node configuration for a WebSphere Application Server, and the user directory for a WebSphere Application Liberty Server.

U

User directory: The user directory of the server.

V

W

WebSphere version: The version of WebSphere Application Server or WebSphere Application Server Liberty that is used by the server.