[Event_Service]

This topic was edited by a BMC Contributor and has not been approved.  More information.

The [Event_Service] stanza is used to configure the MVMMEvent Service.

Parameter

Description

action_processor_threads

Default: 1 (only value allowed)

Number of threads processing actions. Before editing this setting, contact BMC Support.

amount_of_event_journal_to_keep

Defines the amount of Event Service Journal (ESJ) that is stored in the database. This parameter is specified either in days (d) or in hours (h). The default is 0d for backward compatibility (0 means no purge is done) for upgrade installations, and 40d for new installations. ESJ entries will get purged from the database when the purge kicks off and it obtains the "current date & time" from the system - ESJ entries that have a beginning time older than "current time" less the "amount of ESJ to keep" become candidates for deletion.

Minimum valid value is 2 days in the form of 2d or 48h.

backlog

Default: 50. Defines the number of packets that are queued if the service cannot remove them faster than they are arriving. This is a TCP/IP setting.

bem_executableDefault: msend.exe on windows and msend on linux. May be used to specify the executable to execute. May be a batch file when bem_add_shell_cmdline is true. A restart of the Event Service is not required for this keyword but may take up to five minutes for the change to be recognized. Before editing this setting, contact BMC Support.
bem_prefixDefault: MVMM. This should match <BEMPrefix> from the BAROC file. See the section for integrating with BMC Event and Impact Management for more details.
bem_redirect_max_log_filesDefault: 20. Allowed range is 10-100. See bem_redirect_to_log_file for more information. A restart of the Event Service is not required for this keyword but may take up to five minutes for the change to be recognized.
bem_redirect_to_log_fileDefault: true. The valid options are true and false. When true, stdout and stderr is redirected to a file (qpes_bem_n.log). As event actions are executed, they rotate through a set of log files. Examine these logs as well as qpes.log for errors when your action is not working. You may alter bem_redirect_max_log_files if it appears the programs are taking long enough that multiple are writing to the same file. You may disable the output by using bem_redirect_to_log_file=false. A restart of the Event Service is not required for this keyword but may take up to five minutes for the change to be recognized. Before editing this setting, contact BMC Support.

class_path

Default: ".\qpesActions.jar". Defines the location of the jar file that the MVMMEvent Service uses. You must enclose the class_path definition in double quotes.

db_mode

Default: client. Defines the mode in which the [Service_Connections] is opened. There are two valid options: client or one_subscriber_client. The one_subscriber_client option improves performance for installations that have thousands of objects associated with event rules or templates. If you have only a several hundred or a few thousand (less than 5000) event rules or templates, you do not see any performance improvement by using the one_subscriber_client option. This option need only be set in the services.cfg file on the MVMMEvent Service computer. It does not need to be set on the client computers.

db_seconds_between_retries

Defines the number of seconds between connection attempts to the database if no connection is established. If this field is not defined in the services.cfg file, then db_seconds_between_retries defaults to 30 seconds. If a connection to the database exists, then no further attempt is made.

exec_redirect_max_log_filesDefault: 20. Allowed range is 10-100. See exec_redirect_to_log_file for more information. A restart of the Event Service is not required for this keyword but may take up to five minutes for the change to be recognized.
exec_redirect_to_log_fileDefault: false. The valid options are true and false. When true, stdout and stderr is redirected to a file (qpes_exec_program_n.log). As event actions are executed, they rotate through a set of log files. Examine these logs as well as qpes.log for errors when your action is not working. You may alter exec_redirect_max_log_files if it appears the programs are taking long enough that multiple are writing to the same file. You may disable the output by using exec_redirect_to_log_file=false. A restart of the Event Service is not required for this keyword but may take up to five minutes for the change to be recognized. Before editing this setting, contact BMC Support.

demarshaller_stack_size

Defines the stack size. The default setting is usually acceptable. Before editing this setting, contact BMC Support.

threads

Default: 5. Defines the maximum number of concurrent threads that the MVMMEvent Service uses to listen on the TCP port. This is a tuning parameter and generally should not be modified.

evaluate_rules_with_unmonitored_objects_interval

Min: 30000 (30 seconds)

Default: 300000 (5 minutes)

Specifies the interval to check whether rules are only associated with unmonitored objects and force the clear pipeline to be executed or console alert to be cleared.

event_action_processor_stack_size

Defines the event action processor stack size. The default setting is usually acceptable. Before editing this setting, contact BMC Support.

event_init_stack_size

Defines the event initiation stack size. The default setting is usually acceptable. Before editing this setting, contact BMC Support.

event_journal

Default: explicit_actions. Defines whether event messages are written to the event journal tables of the database and if so what appears in the Monitor Console.

Off: No event journal information is recorded to the database. Nothing is recorded even if an action has a journal node in it.

Explicit_actions: All journal instance information (including timings, input values and journal action records) for every triggered event is recorded and stored in the database. In the Event Journal, input data is available for all event instances (including re-triggered actions), however, the Action Flow tab only contains details of actions that have a journal node. This is the default setting.

All_actions: All journal instance information (including timings, input values and all action flow records) for every triggered event is recorded and stored in the database. In the Event Journal, input data is available for all event instances (including re-triggered actions) and the Action Flow tab contains details of all executed actions. This option should be used sparingly for debugging purposes as it could have a significant impact on your database!

event_journal_purge_buffer_sizeDefines the ESJ purge buffer size. This parameter drives the size of database transactions, meaning that when the purge feeds candidate keys (a.k.a. instance ids) into its DELETE statements, the purge commits the database transaction when the buffer size is reached. The default value is 1000.
event_journal_purge_candidate_keys_in_memoryDefines the size of an in-memory container from which the purge fetches the candidate keys. The default value is 10000.

event_trigger_processor_stack_size

Defines the event trigger processor stack size. The default setting is usually acceptable. Before editing this setting, contact BMC Support.

execute_clear_action_on_rule_changeDefault: true. When true the clear action is executed for any concrete event rule or template association rule when the rule or template or its trigger is changed and the state of the rule is active (ie. has been triggered). Prior to version 9.0 the clear action was not executed. Specify false to retain that behavior.

hostname

Default: localhost. Defines the host name or IP address of the computer on which the MVMMEvent Service runs.

jvm_cmdline

Default: -Xrs. This field tells the JVM to ignore logoff events and stop services from being shut down when a user logs off.

jvm_path

Defines where the Java Virtual Machine (JVM—jvm.dll) file is located and accessible to MainView Middleware Monitor. This information is captured during the installation process. Do not edit.

library_path

Defines where Java files that TrueSight Middleware and Transaction Monitor needs are located. Specifically, the service looks for the JNI objects, loads them, and uses them with the WebSphere MQ Java binding. For internal program use only.

This setting is only used when an event action writes to a queue. If the library path does not point to the location of your Java library, change it to reflect your configuration.

listen_port

Default: 15003. Defines the port on which the MVMM Event Service listens.

load_errors_fatal

Default: false. Defines whether the MVMM Event Service should fail to start if a corrupt action or trigger is encountered. The following error message is printed to the qpes.log file:

Level=LM_WARNING Errors occurred loading rules, TMTM Event Service shuts down.

The valid options are true and false. If set to true, then the MVMM Event Service fails to start. If set to false, the MVMM Event Service starts and operates normally.

message_block_pool_size

Default: 16384 (64MB). Defines how much memory is pre-allocated for the MVMM Event Service to use for message processing. The message_block_pool_size is allocated in blocks of 4KB.

password

Default: encrypted. On startup, the MVMM Event Service reads the one-time password in the user's file. The MVMMEvent Service then selects a new password, informs the MVMMApplication Service, and writes the new password here.

seconds_to_delay_event_rule_removal

Default: 10 minutes. Specifies to keep a rule in memory for ten minutes after it has been altered or removed. The rule is not functional, it is used to manage memory and this value should only be altered after the recommendation of BMC Support.

service_state_monitor_stack_size

Defines the size of the service state monitor. The default setting is usually acceptable. Before editing this setting, contact BMC Support.

demarshaller_threads

Default: 5. Thread pool handling messages received. Generally the same value as threads=. This is a tuning parameter and generally should not be modified.

username

Default: EventService. Defines the user account that the MVMMEvent Service uses. When starting the MVMM Event Service, it reads the user's file and uses the user name for the MVMMEvent Service.

trigger_tracer_mode

Default: off. This enables diagnostic information. Additional configuration is required and therefore only BMC Support should set this.

trigger_processor_threads

Default: 1 (only value allowed)

Number of threads processing trigger evaluations. Before editing this setting, contact BMC Support.

populate_last_load_timestamps

Default: on. Values: on or off

Controls whether the event rule in the DB is time stamped when the rule attempts to gets loaded or reloaded by the Event Service. Two timestamps indicate the last time the rule loaded successfully and when it failed to load. Only BMC Support should set this.

mcell_name

Default: Not set. Defines a default BEM Cell name; used when running BEM actions.

mcell_home

Default: Not set. Defines a default BEM Cell home location; used when running BEM actions.

Was this page helpful? Yes No Submitting... Thank you

Comments