Overview Monitoring Events Monitoring and Managing Events

9-74 Oracle Fusion Middleware Configuration Guide for Oracle Enterprise Repository

9.7 Monitoring and Managing Events

This section discusses the steps to monitor and manage events in Oracle Enterprise Repository. This section contains the following topics: ■ Section 9.7.1, Overview ■ Section 9.7.2, Monitoring Events ■ Section 9.7.3, Cleaning Up Stored Events ■ Section 9.7.4, Configuring Workflow ■ Section 9.7.5, Encrypting Your Passwords

9.7.1 Overview

This section describes how to use the administrative tools that are shipped as part of Oracle Enterprise Repository. The Advanced Registration Flow administrative tools are used to: ■ Monitor events using a command-line interface ■ Clean up the events and unsubscribe the JMS durable subscriber ■ Generate the Workflow Configuration file ■ Refresh the Oracle Business Process Management Engine with the latest Workflow Configuration file ■ Encrypt the passwords stored in the Workflow Configuration and Subscription Manager files The administrative tools are installed under the following directory: ORACLE_HOMErepositoryXXXcoreworkflow-tools

9.7.2 Monitoring Events

The Event Manager has a tool for monitoring the events that are generated by the Event Manager. The tool peeks into the event traffic and prints information, such as the Event Body and Event Properties, as shown in this section.

9.7.2.1 Prerequisites

The following prerequisites apply before starting the monitoring tool: ■ If the default embedded JMS server is used, then Oracle Enterprise Repository needs to be running with the cmee.eventframework.enabled system setting set to true. This is to make sure that the JMS broker that is embedded within Oracle Enterprise Repository is running so that the monitoring tool can connect to it and monitor the events. ■ If an external JMS server is used, then the external JMS Server needs to be running and the JNDI-related eventing.properties that are required to connect to the external JMS server must be configured. For more information, see Section 9.6.2, Configuring Connectivity Properties for External JMS Servers . Configuring Oracle Enterprise Repository Workflow 9-75

9.7.2.2 Usage

From a command prompt, run the Event Monitoring tool as follows: event_monitor.bat Path of WEB-INF\classes For example, if Oracle Enterprise Repository is deployed to a domain named oerdomain under: D:\bea816\user_projects\domains\oerdomain Then the Path of WEB-INF\classes is: Oracle_HOME\user_projects\applications\base_domain\applications\oer_ 11.1.1.4.0\oer-app\WEB-INF\classes where Oracle_HOME represents the OER_HOME install location. This path is needed to get the JMS configuration from the eventing.properties file so that the tool can connect to the JMS server. Figure 9–44 Event Monitor Console

9.7.3 Cleaning Up Stored Events