Operations Management Infrastructure Settings Manager

Configure which audit categories are logged. The default value is Configuration, which only writes configuration changes to the Audit Log. When you set the audit category to All, event and configuration changes are written to the Audit Log.

If enabled, Operations Management actions are written to the Audit Log.

Name of the DDM routing domain. Keep empty if you want to use the default domain.

Enable if you have a highly dynamic environement. CIs for new systems are automatically generated in the RTSM.

Sets of IP address ranges that specify the IP addresses that relate to the dynamic environment.

Format: <ip_start>-<ip_end>,<ip-start>-<ip-end>

Node name patterns using regular expressions that specify the nodes that relate to the dynamic environment.

Format: <pattern1>,<pattern2>

Sets, using XML format, the attributes and CI types that should be used and those that should be ignored during CI resolution.

Some CI attributes do not provide useful information. For example, an attribute value may apply to many CIs but does not help to identify matching CI. These types are specified in the <IgnoreAttributes> and the <IgnoreCiTypes> entries.

Any CI types and attributes included in the ignore lists are always ignore by CI resolution.

Some types of information are essential for successful CI resolution. These types are specified in the
<WhiteListType> entries. Should it not be possible to load all CIs, the CI types specified in the whitelist are used. The order of the CI types in the list represent the order in which these CIs are included. As soon as the CIs belonging to a CI type cannot be accommodated in the cache, these CIs are excluded and no further CI Types are assessed.

Entries in the ignore lists override entries in the whitelist. Entries in the whitelist are handled in their order of appearance.

Specifies the frequency with which the CI cache is refreshed (minutes).

Sets the Cache Type for CI Resolution.

In Memory — It is recommended to select the In Memory cache type when CI resolution performance is more important than minimizing the memory footprint on the Data Processing Server. In smaller managed environments, where the total number of CIs in the monitored environment is smaller than the default value in the CI Limit setting, using the In Memory cache type is preferable. CI Resolution maintains all CIs in RAM. Use this setting for larger environment only when there is sufficient RAM available.

Database — It is recommended to select the Database cache type when your monitored environment is very large (when the number of CIs being monitored is larger than in the CI Limit setting). CI Resolution maintains only the most often-used CIs in RAM. This is typically 20% of the CI Limit setting. All other required CIs are maintained in a cache file. This option results in a lower memory footprint but may have an impact on CI resolution performance.

Sets the maximum number of CIs that are loaded into cache by the CI Resolver.

Sets the event source attribute of the event sent to the Event Browser when the CI Limit is reached.

Semicolon separated list of attribute/pattern pairs:

<CI Type name>.<attribute name>=<regular expression>;<CI Type name>.<attribute name>=<regular expression>;...

Character used to divide the host name from the CiInfo text string, for example: @@

Character used to divide the CiInfo text string into keywords used to find CIs in the RTSM, for example, a colon (:)

Sets the file path to the specified folder for the Persistent cache type, which maintains cache entries in a file in the file system. You can use either an absolute path or a relative path to the BSM home directory.

Number of previous results that are cached for fastest resolution. This cache notes the most frequent resolution results which are then reused for subsequent resolutions.

Maximum number of CIs that are transferred within a chunk from RTSM.

Time in minutes after which the CI Resolver does a retry for previously failed resolution attempts.

Defines the TQL queries to run for resolving a CI.

CI Resolver can use service ID information from Topology Sync to map service IDs directly to CIs.

Specifies the IP Address of Data Processing Server to which certificate requests are forwarded.

Change state of all related events to the specified value, either Closed or Resolved.

When an event is closed, it is no longer possible to execute any further actions on the event upon resolution of the failure. When closing an event automatically, the Change State setting provides the option of either closing an event or setting the lifecycle state of that event to Resolved. You can further process Resolved events before closing them.

When you select the value Resolved for the Change State setting, operations such as those described in the above examples result in setting the corresponding events to state Resolved. As a result, it is possible to do additional steps, manual or automated, before finally setting these events to closed.

Existing events must have same CI and ETI as new event, but a different ETI value. Only if ETI contributes to health. Default value is true.

Key of existing events must match closeKeyPattern of new event. Default value is true.

For each newly received event, the existing events are inspected to find events related to the new event. Any events that are related to the new event are closed or set to resolved. Default value is true.

Sets the maximum number of closed events to be displayed in the Closed Events Browser. Default is 1000.

Enables the development of predefined Content Packs.

List of custom attributes separated by semicolons (;) that you can add to the Event Browser as columns, for example: "Customer;Region;Manager;Company".

Time period in minutes within which past downtime configurations are considered. All downtime periods are ignored which have an end time that is before the beginning of the configured history time period.

Ignore all maintenance windows which starts after current time plus the future downtime range in minutes.

Maximum time in minutes after changes in the maintenance windows configuration are taking effect.

Use ETIs to find original event. Duplicate events must have same CI, ETI, and ETI value, and the ETI must contribute to health. Default value is true.

Use selected attributes (for example Select Application or Select CI) to find the original event. All selected attributes must be identical. Default value is false.

Use key attribute to find original event. Duplicate events must have identical key. Default value is true.

If enabled, duplicate events are dropped and the related original event is updated instead. Default value is true.

Maximum number of seconds difference between received times of original and new event (0 = infinite). Default value is 0.

Duplicate events must have identical application. Default value is true.

Duplicate events must have identical category. Default value is true.

Duplicate events must have identical CI. Default value is true.

Duplicate events must have identical CI hint. Default value is true.

Duplicate events must have identical ETI hint. Default value is true.

Duplicate events must have identical ETI and ETI value. Default value is true.

Duplicate events must have identical HPOM service ID. Default value is true.

Duplicate events must have identical node. Default value is true.

Duplicate events must have identical node hints. Default value is true.

Duplicate events must have identical object. Default value is true.

Duplicate events must have identical policy condition ID. Default value is true.

Duplicate events must have identical severity. Default value is true.

Duplicate events must have identical subcategory. Default value is true.

Duplicate events must have the same SubComponentID value.

Duplicate events must have identical title. Default value is true.

Duplicate events must have identical type. Default value is true.

Update severity of original event based on selected mode. The mode values are:

• Use new (severity value)

• Most critical (severity value)

• No (do not change severity of event)

Default value is No.

Update title of original event with title of last duplicate event. Default value is false.

Time interval in seconds after which the cache is cleaned up. Default: 60 Seconds (Minimum: 10 seconds).

Maximum age of cached events in minutes. Older events are removed from the cache during clean-up.

Maximum number of events held in the cache. If the current cache size is greater than this number, the oldest events are removed from the cache during clean-up.

Configures the maximum time period (in msec) for event processing in the EPI Server. The value zero (0) disables the timeout which means that a problem during processing in the EPI server may block further event processing indefinitely.

Base directory path used by all event archives. If no value is specified, the default base path is used.

Default base path: [OvDataDir]/shared/server/datafiles/archive

To find the value of the default base path for achiving, execute the following command on the Data Processing Server system:

ovpath -ovrg server -datadir archive

Linux default: /var/opt/OV/shared/server/datafiles/archive

Windows default: C:\ProgramData\HP\HP BTO Software\shared\server\datafiles\archive

You can enter an alternative base path. Both absolute and relative paths are accepted, for example:

Absolute: C:\ArchiveFiles

Relative: events/

The specified relative path is appended to the default base path. For example, events/ results in the following base path:

C:\ProgramData\HP\HP BTO Software\shared\server\datafiles\archive\events

Time period (hours) between the completion of the last automatic archiving of events and the start of the next execution.

Access Key ID used for HP Cloud Object Storage.

History of properties of type string or text which are longer than the configured value are ignored. Values with a fixed length like UUID cannot be limited.

The default value is 0 which retains all information regardless of length.

If an attribute modification where the new or old value exceeds the maximum length, the following text appears in place of the value in the event history:

Value exceeds the maximum permitted length of `configured length' characters.

Enables the propagation of user and group assignments to symptom events.

When enabled (True), changing the user or group assignment of a cause event also applies the change to all symptom events.

Enables the propagation of lifecycle state changes to symptom events.

• Disabled but close operation is propagated to symptom events — Lifecycle state changes are not propagated to symptom events except for closing of events.

• Enabled — Lifecycle state changes are propagated to symptom events.

• Disabled but close operation unrelates symptom events — Lifecycle state changes are not propagated to symptom events. Closing the cause event unrelates symptom events.

Maximum number of events or updates send simultaneously for each synchronization request to HPOM and BSM Connector servers.

The default value is 100. Minimum value is 1. Maximum value is 500.

Number of hours an event forward request or event update synchronization request is held in the queue. If the request cannot be delivered to the target server before this expiration time, it is automatically deleted from the queue.

Default value is 12 hours. Minimum value is 1 hour. Maximum value is 720 hours (30 days).

Failure to deliver can occur for retry timeouts, or a catastrophic delivery error. A catastrophic delivery error is a situation where it does not make sense to retry the request, for example, a mis-configuration (authentication fails), or a programming error is encountered in an External Process groovy adapter (NullPointerException). These cases require manual intervention before retrying.

To manually retry failed requests to a particular connected server, from the Event Browser, manually transfer control of an event that has previously failed delivery to a particular server.

If disabled (false), event attributes that are unknown in HPOM for Windows or HPOM for UNIX are not forwarded as Custom Message Attributes. This affects the following Event properties: Priority, Description, State, Subcategory, Cause Event Id, Solution, Related CI, Related CI Hint, Node Hint, Source CI, Source CI Hint, ETI, ETI Hint, Skip Duplicate Suppression, Controlled Transferred.

Specifies whether automatic forwarding of events to connected servers is enabled. If set to true, event forwarding using event forwarding rules is active.

Specifies lifecycle state in Operations Management to which the Acknowledge message state in HPOM is mapped.

Every forwarded event includes a list of servers that have a copy of this event. By default, when the event is modified on one server, it notifies all servers in the list of the change.

When enabled (true), for each event change (for example, close, annotation, or add), the server only informs the server from which the event was received and to which the event was forwarded.

This can be useful in simplifying connections in firewall environments.

Event Forwarding automatically retries delivery of event forward requests once a minute. Whenever a target server is unavailable, an internal event is generated indicating the failure to deliver. This setting defines the minimum number of minutes to elapse before generating another event for the failing request.

Default: 60 minutes. Range: Minimum of 1 minute and a maximum of 1440 minutes (1 day).

Note: This setting does not affect the retry interval of one minute.

Permits ETI Mapping Rules to overwrite indicators specified in custom attributes (CAs).

Default: False

If set to false, and CMA-matched event type indicators are recognized, mapping rules are ignored.

If set to true, the CMAs are still evaluated but mapping rules are used to process events.

For example, migrating from customized, non-Operations Management-ready SPIs to Operations Management-ready SPIs can result in errors in event processing as new content packs no longer work as expected with the existing handling.

Permitting mapping rules to override the CMA-driven event assignment leaves the Operations Management administrator in control.

Specifies how the number of unassigned/unresolved events are calculated for display. The following options are available:

• MOST_CRITICAL - only the count for the highest severity is displayed.

• AGGREGATIVE_WITHOUT_NORMAL - the total count for all not-normal states is displayed.

• AGGREGATIVE - the total count for all severities is displayed.

The default setting is MOST_CRITICAL. The sum of the number of events with the highest severity is recorded by Service Health. For example, 1 critical event, 5 major events, and 2 normal event for the CI: My Web Server are active.

The value displayed for the number of highest severity events for CI: My Web Serveris: 1 and the highest severity Critical.

AGGREGATIVE calculates the sum of all events related to CI: My Web Server. In this case, the value displayed for the number of events for CI: My Web Serveris: 8 and the highest severity Critical.

AGGREGATIVE_WITHOUT_NORMAL calculates the sum of all events related to CI: My Web Server but excludes any events with severity Normal. In this case, the value displayed for the number of events for CI: My Web Serveris: 6 and the highest severity Critical.

The MOST_CRITICAL setting is designed to hide the information about the events which do not have the highest severity. When you close the highest severity events, the events with the next highest severity are displayed. In our example, closing the critical event changes the value of the KPI from 1 to 5, and the severity changes from Critical to Major. Initially, it would not be obvious that there were a number of events with the severity Major related to CI: My Web Server.

To avoid this situation, select one of the other options: AGGREGATIVE or AGGREGATIVE_WITHOUT_NORMAL.

List of event subcategories, separated by semicolons. For each subcategory, additional health indicators are calculated based on the number of unassigned and unresolved events with that subcategory.

Enables (true) forwarding of all events to this HPOM system. Use for testing only. For production systems, set up servers using the Connected Servers manager and create appropriate Event Forwarding Rules.

Name of the system hosting the HPOM management server that is forwarding events. This setting is used for the bi-directional synchronization of events between Operations Management and one HPOM management server.

It is recommended to specify connections to external servers, including HPOM management servers, using the Connected Servers manager. For details, see How to Create a Connection to an HPOM Server.

Password for the user that Operations Management uses to connect to the configured HPOM management server.

Port number to use when establishing a connection to the HPOM management server.

Specify the platform of the HPOM installation.

For HP Operations Manager for Windows, the user must have at least PowerUser rights and must be a member of HP-OVE-Admins group and the local administrators group.

User name that Operations Management uses to connect to the configured HPOM management server.

Set to true to use HTTPS to connect to the HPOM web service.

Saves all data from the topology synchronization to the hard disk. This setting is not recommended for production systems because it can have a significant negative effect on performance. The default setting is False.

Enables Groovy scripts used to manipulate the synchronization data during the synchronization process.

Lists the packages used for the topology synchronizations.

Enable IP resolution for nodes without IP address information in HPOM. Enable IP resolution (true) has a negative effect on the synchronization performance.

Disables the automatic deletion of CIs when performing topology synchronization. The responsibility for CI deletion is transferred to RTSM.

Specifies the fully qualified domain name of the License Reporting Server.

If no server is specified, no reports are generated.

Maximum allowed age (in hours) of an event to be processed. If the creation time of an incoming event is older than that allowed by the Maximum Event Age period, the event is dropped. To disable, set to 0.

Specifies the interval used to poll RTSM for reconciliation changes (in seconds).

Use 0 to disable polling.

Specifies the time after which relative date filters are re-evaluated (in seconds).

Valid range is 30 seconds to 86400 seconds (24 hours).

List indicating event categories recognized by Operations Management separated by semicolons (;), for example: Exchange;WebApp;System.

Event categories are logical groups of events (for example: database, OpenVMS, or hardware) which can be assigned to Operations Management users.

Refresh interval in minutes for reloading user permissions from the database. Operations Management reloads user permissions every 10 minutes by default. However, events already loaded into the browser remain unaffected. Changes to a user account are only fully available after a new logon to Operations Management.

Enables updating of the view selector in the Top View when a CI is selected in the view.

Enables the automatic extension of the correlation time period whenever an additional symptom is correlated to the same cause.

Each time that an event is correlated with a problem, the time period set in the correlation time window is restarted to help enable the correlation of a greater proportion of symptoms associated with the original event.

The correlation time window is only automatically extended when an a new symptom is added to a cause AND the cause is not yet closed.

If the cause is already closed, the time window is not extend anymore so that after the last time window elapses, future repetitions of symptoms are no longer correlated to the closed cause.

This avoids ignoring new similar symptoms. Just because a cause is closed, it is not necessarily true that the problem is solved. If the same symptoms continue to occur, they were most likely not caused by the closed cause event and should become visible in the Event Browser.

Controls whether symptoms are correlated to closed causes or not. Default is true. If set to false, no correlation is done with newly occurring symptom events after a cause is closed. This prevents any auto-closing of new events.

Correlation takes place regardless of the lifecycle state of cause event, as long as events occur within the correlation time window. Correlating a symptom to a closed cause closes the symptom as it is not possible to have open symptoms with a closed cause.

Sets the period of time in seconds that correlation rules wait for all required events to occur before reporting the cause event and emptying the correlation rule cache.

Cause and symptom events must arrive within that time frame in the correlation engine to be considered for correlation. A time window starts when a first cause or symptom event arrives that cannot be correlated with any other event.

Default value is 960 seconds (16 minutes).

Sets the maximum time in seconds that a query result for a cause-symptom relationship between CIs for a given correlation rule is cached. After this time period elapses, the RTSM is queried again.

Valid range is 0 seconds to 86400 seconds (24 hours). Default value is 300 seconds (5 minutes).

For very high numbers of possible cause-symptom relationships, event correlation can take a long time. The result of the correlation query for possible symptom CIs is stored in a cache and this cache is used for further checks. When the configured Max Query Result Cache Time period has elapsed, the query is rerun. This minimizes the number of times that queries are run for multiple open causes/symptoms relationships.

Maximum number of events waiting to be processed by the correlation engine. If this limit is exceeded, the oldest event is removed from the queue and no longer considered for correlation.

Default value: 5000

Valid range of Values: 100-20000

Changes are enabled immediately.

Controls which events contribute to an event count, for example in Event Dashboard widgets. Possible values are:

• Most Critical. Only the most critical events are counted.

• Non-Normal. Only events with a severity other than normal are counted.

• All. Events of all severities are counted. This is the default value.

Maximum number of active events (excluding events with parents) that is shown in a UI. If the actual event count exceeds this number, the system switches to Purge Mode and only displays the latest events.

When in Purge Mode, a confirmation of being in Purge Mode (maximum number of active events than can be displayed in the Event Browser has been reached) is displayed in the information bar. In addition, it states which events are still displayed based on their time received (all events older than the stated time are purged out).

The value is automatically set during deployment and is dependent on the selected deployment option:

Small - 1000

Med. - 5000

Large - 10000

Extra large - 20000

If you change the deployment in ServerDeployer, you will have to change the memory settings again.

If the configured maximum is reached the oldest 10% of the top level events are removed from the cache.

When the number of active, top-level events is less than 80% of the maximum value, the purged events are reloaded.

For example, if the default Event Cache Max Level of 20000 is reached, the 2000 oldest events are removed from the cache. As the number of events in the Event Browser drops to 16000, the purged events are reloaded.

The settings are per deployment. The same setting is applied to all gateway servers within the same deployment.

Enables sound notification for new events. When loading an event browser, this setting is used unless the user has defined alternative behavior in the browser options.

The interval of user interface updates (in milliseconds). The default value is 5000 ms (5 seconds).

Controls the verbosity of responses from the Operations Management Web Service. The option Standard returns to the caller of the web service the appropriate HTTP error code, as listed in the HTTP 1.1 standard, along with a standard error text message describing the error. The option Verbose is recommended for development environments and returns a detailed message describing the reason for the error. The option Brief returns only error codes 400 (Bad Request) or 503 (Service Unavailable), depending on the type of the error, and an error identifier. A detailed error message may be obtained by locating the identifier and detailed error message in the error logs.

Operations Management Web service modify operations are secured by setting the X-Secure-Modify-Token HTTP header on Web service modify requests (PUT, POST and DELETE). For details on how to set this header, see the Operations Manager i Extensibility Guide. This header provides enhanced security protection against malicious exploits of web applications. Secure Modify is enabled by default.