Event Service Configuration and Administration
About the Event Service and Event Data
The Event Service that is integrated with MashZone NextGen allows MashZone NextGen to connect to the Event Bus for Software AG and subscribe to events published by other Software AG applications. In most cases, the system acting as the Event Bus is Universal Messaging or the webMethods Broker using a Messaging Service, although other systems and transports may serve as the Event Bus.
The Event Bus handles events published by event producers which may be a variety of Software AG applications. It routes events as they are published to event consumers, such as MashZone NextGen, who have subscribed to specific event types, also known as channels.
MashZone NextGen also uses the Event Service to connect to Apama and to subscribe to and work with events from scenarios (also sometimes called dataviews). Apama scenarios have event data that has been specifically transformed for use in dashboards.
For MashZone NextGen, each Event Bus or Apama subscription feeds an event source which is managed by the Event Service. Event sources receive events for subscriptions, store them in memory and act as the data source for the corresponding EDA or Apama event.
Use Events as Information Sources
To use events as information sources, you must create EDA or Apama event sources. Unlike other sources, only MashZone NextGen administrators can create EDA and Apama event sources for other users to work with.
To create these sources, administrators must:
2. Create event sources of the Event Type Store and/or Apama as needed. MashZone NextGen retrieves event data from these event sources when users run the corresponding EDA or Apama event source. If views for the event source are real-time views, events are pushed to the view automatically.
Create EDA Event Sources