Entering content frame

Procedure documentation start Locate the document in the library structure

Use

You start an event dispatcher that monitors a database instance.

Prerequisites

     You have added entries to an event dispatcher configuration file using the add command.

     To enable the event dispatcher to log on to the database instance, you need the name and password of a DBM operator who has the DBInfoRead server authorization and at least one of the server authorizations EvtDispAdmin | EvtDispUse.

Procedure

dbmevtdisp start [-remoteaccess] <configuration_file> -l <log_file> <database_authentication>

<database_authentication> :: = -d <database_name> <user_authentication> [-n <database_computer>] [-e SSL]

<user_authentication> :: = -u <user_data> |-U <user_key>

<user_data> :: = <dbm_operator>,<dbm_operator_password>

Option

Description

-remoteaccess

If you do not specify this option, you can only stop the event dispatcher from the database computer and the computer you used to start it.

If you specify this option, you can stop the event dispatcher from any computer.

<configuration_file>

Configuration file for use by event dispatcher.

Recommendation

We recommend that you create the configuration file on the computer you used to start the event dispatcher.

<log_file>

Log file of the event dispatcher

If the file does not exist yet, it is created with the specified name by the event dispatcher.

<database_name>

Name of the database instance to be monitored

<database_computer>

Name of the database computer

SSL

Encryption method

See Database Manager CLI, -e: Activate Encryption

<user_key>

XUSER key

See Utilities, XUSER

<dbm_operator>,<dbm_operator_password>

DBM user data that is used by the event dispatcher to log on to the database instance to be monitored

See Database Manager CLI, user_logon

Result

Event Dispatcher instance <instance_ID> running
using configuration file <configuration_file>

The database system assigns a numerical <instance_ID> to the event dispatcher.  This ID is unique for the database instance monitored by the event dispatcher. You need the ID to stop the event dispatcher.

Example

You start an event dispatcher that uses the configuration file C:\test\testconfig.cfg and the log file C:\test\mylog.log and logs on to the database instance DEMODB with the authentication data of the DBM operator OLEG with password MONDAY on database computer PARMA.

dbmevtdisp start C:\test\testconfig.cfg –l C:\test\mylog.log –d DEMODB -u OLEG,MONDAY –n PARMA

See also:

Overview of Event Dispatcher Commands

 

Leaving content frame