Event source management commands

You can configure monitor model event sources to receive events from business activities using the event source management (BusinessMonitorEventSourceManagement) commands. Use the commands to view, register, unregister, and update event sources in both CEI (deprecated) and Dynamic Event Framework environments.

Event sources indicate where the events that monitor models consume can originate from. Event sources can be registered to a model during install time. During the Fast Path installation of a monitor model, local event sources are automatically registered. During the detailed method of monitor model installation, you can manually select which event sources are registered to the model.

To run the commands, use the AdminTask object of the wsadmin scripting client. Command-line help is available.

To see a list of the event source management commands in Jython, use the following command:

AdminTask.help('BusinessMonitorEventSourceManagement')

For help on a given command, enter the following command:

AdminTask.help('command_name')

Attention: On Microsoft Windows, there are certain character combinations to avoid using because they indicate special conditions in Jython scripting. For more information, see section "Jython usage with Microsoft Windows directories" of the Using wsadmin scripting with Jython topic in the WebSphere Application Server documentation.

Example formats

The following example shows the format for a command with no parameters:

AdminTask.name_of_command()

The following example shows the format for a command with parameters:

AdminTask.name_of_command('[-parm1 value1]')

Tip: If a parameter value needs to be enclosed in double quotes, you have to use the backslash (\) to escape the quotes. Example:

AdminTask.wbmGetDefEventSource('[-sourceID \"event_source_id\"]')

If you start wsadmin without the -c option and execute the command from the wsadmin prompt, you do not need the backslash.

Interactive mode

You can use the administrative command interactive mode to guide you through the steps for each command when using wsadmin scripting. For more information about the interactive mode, see Invoking an administrative command in interactive mode using wsadmin scripting in the Websphere Application Server documentation.

Usage note

The term local refers to the system on which the command is being executed and is always a Business Monitor cell or server that processes the events. The term remote refers to another cell or server that is not part of the local Business Monitor cell or server.