Creating a Load Generator Property File

Testing Applications With the Event Inspector 26-3 Example 26–1 Event Inspector JSON Event { event-type: myEventType, operation: insert, binding: outbound, value:{ firstname: Jane, lastname: Doe, phone: { code: 12345, number: office }, } } For more information, see: ■ http:www.json.org ■ Section 1.1.2, Oracle CEP Event Types ■ Section 26.1.1, Tracing Events ■ Section 26.1.2, Injecting Events

26.1.4 Event Inspector HTTP Publish-Subscribe Channel and Server

The Event Inspector service uses a dynamic HTTP publish-subscribe HTTP pub-sub channel not configured in config.xml that is named: SERVERNAMEAPPLICATIONNAMESTAGENAMEDIRECTION Where: ■ SERVERNAME : the name of the Oracle CEP server on which the Oracle CEP EPN stage is running. ■ APPLICATIONNAME : the name of the Oracle CEP application. ■ STAGENAME : the name of the EPN stage. ■ DIRECTION : one of either: – input: for event injection. Table 26–1 Event Inspector JSON Event Required Attributes Attribute Description event-type The name of the Oracle CEP event as you defined it in the application assembly file’s event-type-repository. operation Specify the type of event: ■ insert: insert event. ■ delete: delete event ■ update: update event ■ heartbeat: heartbeat event binding One of: ■ inbound: injected event. ■ outbound: trace event. value One or more JSON-formatted event properties as defined by the event-type. 26-4 Oracle Complex Event Processing Developers Guide – output: for event tracing. For example: server-1myappMyInputAdapterinput The Event Inspector service uses an HTTP pub-sub server. This can be any of: ■ Local: you configure your config.xml file with an event-inspector-service element and configure its pubsub-server-name child element with the name of local pubsub server running on this machine. For more information, see Section 26.2.1, How to Configure a Local Event Inspector HTTP Pub-Sub Server . ■ Remote: you configure your config.xml file with an event-inspector-service element and configure its pubsub-server-url child element with a URL to an HTTP pub-sub server running on a remote machine. For more information, see Section 26.2.2, How to Configure a Remote Event Inspector HTTP Pub-Sub Server . ■ Default: if there is only one HTTP pub-sub server defined in your config.xml file and you do not specify a local or remote HTTP pub-sub server, then the Event Inspector service uses the local HTTP pub-sub server by default. The Event Inspector service uses the same HTTP pub-sub channel and server for both tracing and injecting events. For more information, see: ■ Section 26.1.1, Tracing Events ■ Section 26.1.2, Injecting Events

26.1.5 Event Inspector Clients

The Event Inspector service supports the following clients: ■ Section 26.1.5.1, Oracle CEP Visualizer

26.1.5.1 Oracle CEP Visualizer

You can access the Event Inspector service using the Oracle CEP Visualizer. For more information, see Testing Applications With the Event Inspector in the Oracle Complex Event Processing Visualizer Users Guide.

26.2 Configuring the Event Inspector HTTP Pub-Sub Server

You can configure the Event Inspector service with a local or remote HTTP pub-sub server: ■ Section 26.2.1, How to Configure a Local Event Inspector HTTP Pub-Sub Server ■ Section 26.2.2, How to Configure a Remote Event Inspector HTTP Pub-Sub Server You configure the Event Inspector HTTP pub-sub server in a component configuration file. For general information about these configuration files, see Section 1.1.5, Component Configuration Files. If there is only one HTTP pub-sub server defined in your config.xml and you do not specify a local or remote HTTP pub-sub server, then the Event Inspector service uses