4.12 Adding program-specific attributes

If the number of events that might occur increases due to addition of monitored applications and hosts, the system administrator must set similar event conditions for each function, which constitutes an added burden on the management tasks.

Addition of program-specific attributes is a function for adding program-specific attributes to JP1 events. This function enables the system administrator to define actions and filtering for a set of events with a common attribute (grouping). When the number of events increases after program-specific attributes have been defined, the system administrator only needs to modify the attribute addition function definition. There is no need to change the definitions of automated actions or various filters. In addition, the definition of each function becomes simple.

This function enables the system administrator to display events with the added information, such as system names, business names, and system status. This saves time in checking multiple attribute values and system configuration information, which makes the handling of events easier.

The following figure provides an overview of the procedure for adding attributes to JP1 events and defining them in individual functions.

Figure 4‒88: Overview of adding program-specific attributes

Addition of attributes to JP1 events is specified when the corresponding events are registered into or forwarded and received in the event database.

Normally, you can centrally set and manage attribute addition conditions for JP1 events that are transferred from monitored hosts by setting the attribute addition conditions on the manager host.

Note that event registration performance is adversely affected in proportion to the product of the number of attribute addition conditions and the number of registered events. If you run JP1/IM - Manager in a system hierarchy, we strongly recommend that you use a base manager or a relay manager to set attribute addition conditions.

Added attributes are maintained even when the corresponding JP1 events are forwarded to other hosts. Therefore, the attribute information added by a base manager or a relay manager can be used as is, even if the attribute addition conditions are not set in the top JP1/IM - Manager.

Conditions for specifying JP1 events to which attributes are to be added and the attribute names to be added are defined in the additional extended attribute settings block (from add to end-add [exit]) in the additional extended attribute settings file. There must be no more than 2,500 block definitions.

For details about the additional extended attribute settings file, see the JP1/Base User's Guide.

Individual conditions are checked sequentially from the top of the additional extended attribute settings block for each JP1 event that is registered or is forwarded and received. If a condition is satisfied, the specified attribute name and value are added. If exit is specified in an additional extended attribute settings block, the additional extended attribute settings block processing is skipped for the corresponding JP1 event and the next JP1 event is processed.

To minimize the effects of attribute addition on the registration and forwarding of JP1 events, we recommend that you define the additional extended attribute settings file as follows:

• Do not specify exit in additional extended attribute settings blocks except when multiple conditions are used for a single JP1 event to add different attributes. This saves time in processing subsequent additional extended attribute settings blocks.

• In the first additional extended attribute settings block, specify the condition for JP1 events to which no attributes are to be added. This saves time in processing subsequent additional extended attribute settings blocks.

• Define the conditions for JP1 events that occur frequently early in the additional extended attribute settings file.

See the following figure for details.

Figure 4‒89: How to specify the additional extended attribute settings file

For details about adding program-specific attributes, see 5.10 Adding program-specific attributes in the JP1/Integrated Management 2 - Manager Configuration Guide.

To Page Top