Multi-Node Configuration

2. Create an Apama project that emits DES events (e.g., by modifying the StreamExport project) and execute it. By default, all events of unhandled types will be routed to the default UniversalMessaging service, i.e., to the UM instance nsp://localhost:9000.

The installation of DES is required in order to have a valid DES license and initialized type and annotation repositories.

2. Configure the DesEventBroker microservice by opening <MashZone NextGen installation>/VisualAnalytics/config/modules.json and adapting the module specification.

{
"disabled" : true,
"level" : 90,
"impl" : "java:com.softwareag.va.des.impl.DesEventBrokerImpl"
},

3. Configure the temporary DesEventBrokerConfigurationUtility microservice by opening <MashZone NextGen installation>/VisualAnalytics/config/modules.json and adapting the module specification.

{
"disabled" : true,
"level" : 91,
"impl" : "java:com.softwareag.va.des.
DesEventBrokerConfigurationUtility",
"options" : {
"config" : {
"subscriptions" : [
{
"universalMessagingUrl" : "nsp://<node1>:9000",
"eventTypeName" : "<fully qualified
name of the
event type to be
subscribed>"
},
{
"universalMessagingUrl" : "nsp://<node1>:9000",
"eventTypeName" : "<fully qualified name
of another
event type to be subscribed>"
}
]
}
}
},

Enable the microservice by setting the property disabled to false. Additionally configure the UM URL for receiving DES events and the type of the events to be stored. Note that the event type must be available in the type repository. If required add additional subscriptions to the JSON array subscriptions.

4. Start MashZone NextGen Explorer by executing the start script <MashZone NextGen installation>/VisualAnalytics/bin/vaserver. The DesEventBrokerConfigurationUtility microservice will configure the DesEventBroker microservice, i.e., subscribe it for events of the specified types.

5. Deploy a JSON file describing the real-time data source to the <MashZone NextGen installation>/VisualAnalytics/data/auto-deploy/stream for each subscribed DES event type. The JSON file must have the following format.

{
"messageType" : "<fully qualified name of the subscribed event type>",
"windowSize" : 60000
}

Adapt the message type (event type name) according to the previously configured information. If required, adapt the window size for the real-time data source. The default window size defines the minute window (60000 milliseconds).

The DES multi-node scenario is configured and the DES data source can be analyzed in MashZone NextGen Explorer.