Designer 10.15 | Software AG Digital Event Services Help | Working with the Event Console | Configuring the Event Console
 
Configuring the Event Console
Using the Event Console, you monitor specific digital event types that are published to a Universal Messaging channel. You create a launch configuration in Designer to enable the Event Console to listen for incoming events.
*To configure the Event Console to monitor digital event types:
1. In Designer, click Create new Event Console icon.
2. In the Name field, specify a name for the launch configuration.
3. On the Configuration tab, select the Digital Event Services (DES) runtime configuration that the Event Console uses for subscribing to incoming events:
*Use Universal Messaging Service - select this option when all events that the Event Console monitors are published to a single Universal Messaging server.
In the Provider URL field, specify the host and port of the Universal Messaging server to which the Event Console connects. The default value is nsp://localhost:9000.
*Use External Configuration - select this option to publish events to a messaging service in the configuration of another product that uses Digital Event Services.
In the Configuration Location field, specify the configuration folder of Digital Event Services (DES) in the runtime where DES is embedded. The configuration folder you specify must contain a subfolder called DigitalEventServices.
Note:
DES configurations for Software AG OSGi runtimes are located in Software AG_directory \profiles\profile_name\configuration.
4. On the Event Types tab, select the event types that you want to monitor.
5. On the Message Format tab in the Type Name Details section, select the format of the information that the Event Console displays.
Note:
The message format settings that you choose apply to the digital event types that you select on the Event Types tab and to the digital event types that they implicitly require in their event type definition.
*Show no type information - this is the default. The Event Console prints events without the name of the digital event type, for example:
[{"id":"order #1"},{"order":[{"item_id":"item #1"},
{"item_count":23}]}]
*Show local name only - each line that the Event Console prints starts with the name of the digital event type, without package and variant key, for example:
{"EventType":"DemoType","EventFields":[{"id":"order #1"},{"order":
{"EventType":"OrderType","EventFields":[{"item_id":"item #1"},
{"item_count":23}]}}]}
*Show full type information - each line that the Event Console prints starts with the name of the digital event type, which includes the name of the package of the event type, for example:
{"EventType":"des.sample.DemoType","VariantKey":"158502b503f3afbf",
"EventFields":[{"id":"order #1"},{"order":{"EventType":"des.sample.
OrderType","VariantKey":"25c7bb036ce347a6","EventFields":
[{"item_id":"item #1"},{"item_count":23}]}}]}
6. Optional. In the Additional Message Format Settings section, select one or more options:
*Show every hundredth event on the console only - the Event Console prints only one in every hundred events.
*Show formatted event content - the Event Console indents the content of the events it prints, for example:
[ {
"id" : "order #1"
}, {
"order" : [ {
"item_id" : "item #1"
}, {
"item_count" : 23
} ]
} ]
7. Click Run.