Job Management Partner 1/Base User's Guide
Format
to-upper
event-filter
end-to
or
to event-server-name
event-filter
end-to
File name
Storage destination directory
- In Windows:
folder-specified-in-event-server-index-file\ shared-folder\jp1base\event\ (in a cluster system)- With the default event server index file (index), the file name is: installation-folder\conf\event\servers\default\
- In UNIX:
directory-specified-in-event-server-index-file\ shared-directory/event/ (in a cluster system)- With the default event server index file (index), the file name is: /etc/opt/jp1base/conf/event/servers/default/
Description
A forwarding settings file (forward) is a group of forwarding setting blocks that define which JP1 events will be forwarded to a specific event server.
Application of settings
The settings are applied when the event service starts or restarts, or the forwarding settings file is reloaded by executing the jevreload command. For details on the jevreload command, see jevreload in 13. Commands.
Definition details
The following conventions apply to entries in the forwarding settings file (forward).
- The forwarding settings file (forward) is a text file and each line cannot exceed 1,024 bytes.
- Separate parameter keywords with a space (code 0x20) or a tab (code 0x09).
- Do not insert a space or any other characters in front of the parameter name at the start of a line.
- A hash mark (#) (code 0x23) at the start of a line indicates a comment.
- Letters are case sensitive.
In the to-upper format, the JP1 events are forwarded to a server at a higher level in the hierarchy defined in JP1/IM - Manager.
In the to format, you can choose the destination event server. Specify an event server name defined in the remote-server parameters in the event server settings file (conf).
Whichever format you use, you must write filter conditions for forwarding JP1 events to the remote server. For details on the writing format of an event filter, see Event filter syntax.
Notes
- In a forwarding settings file (forward), you can write comments between the blocks, but not within a block. You can also specify multiple forwarding setting blocks.
- When JP1 events are forwarded through several routes, the destination event server might receive multiple instances of the same JP1 event. In this case, a duplication check is performed for the transferred JP1 event. The check examines the following conditions:
If all of these conditions are met, the JP1 event is considered to be a duplicate, and the second and subsequent events are not registered in the event database.
- Whether the first JP1 event matches the source event server name.
- - Whether the first JP1 event matches the serial number for the source event server.
- - Whether the first JP1 event matches the registered time.
- - Whether the registered reason is 4 (a forwarded event)
- When multiple transfer blocks (to to end-to) are specified and have the same destination assigned, the transfer processing is done in the order of event filters set in these blocks. At the end, the forwarding processing is the same as the case when events are transferred with multiple event filters specified and connected with OR.
Definition examples
The setting examples in the figures below refer to forwarding JP1 events in the following system configuration:
Table 14-9 Example of forwarding settings
Host name Role in configuration jp1-svs1 Integrated manager jp1-svs2 Submanager jp1-sva1 JP1 site host Conditions
JP1 events are forwarded from jp1-sva1 to jp1-svs2 if any one of the following is true:
- SEVERITY is set to Error
- PRODUCT_NAME is set to /HITACHI/JP1/AJS, and SEVERITY is set to Warning or Notice
- PRODUCT_NAME is set to /HITACHI/JP1/AOM
JP1 events are forwarded from jp1-svs2 to jp1-svs1 if any one of the following is true:
- SEVERITY is set to Error
- PRODUCT_NAME is set to /HITACHI/JP1/AJS, and SEVERITY is set to Warning
- PRODUCT_NAME is set to /HITACHI/JP1/AOM, and SEVERITY is set to Warning
The flow of JP1 event transfers is shown below.
Figure 14-4 Definition examples and flow of JP1 event transfers
- Example of defining the forward file in jp1-svs1
#---------------------------------------------------------- # JP1/Base - Event Service Forwarding Setting #---------------------------------------------------------- # Event Server Name: jp1-svs1 # (Nothing)
- Example of defining the forward file in jp1-svs2
#----------------------------------------------------------- # JP1/Base - Event Service Forwarding Setting #----------------------------------------------------------- # Event Server Name : jp1-svs2 to jp1-svs1 E.SEVERITY IN Error OR E.PRODUCT_NAME IN /HITACHI/JP1/AJS E.SEVERITY IN Warning OR E.PRODUCT_NAME IN /HITACHI/JP1/AOM E.SEVERITY IN Warning end-to
- Example of defining the forward file in jp1-sva1
#----------------------------------------------------------- # JP1/Base - Event Service Forwarding Setting #----------------------------------------------------------- # Event Server Name : jp1-sva1 to jp1-svs2 E.SEVERITY IN Error OR E.PRODUCT_NAME IN /HITACHI/JP1/AJS E.SEVERITY IN Warning Notice OR E.PRODUCT_NAME IN /HITACHI/JP1/AOM end-to
All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.