SBM Orchestration Guide → Raising Events Using JMS Queues → Event Manager Queue Adapter Architecture
This section describes the EMQA architecture. The architecture consists of three main components: 1) the JMS servers and queues, 2) the EMQA, and 3) Serena Business Manager.
Figure 1. The following figure shows the relationship among the three components of the EMQA.
The client application produces messages in the form of XML documents and sends them to one or more queues hosted by a JMS server. The JMS server then delivers the XML documents to one of the JMS listeners configured on the EMQA. Any number of JMS server and queue combinations can be configured to run with the EMQA.
The EMQA is made up of the following three components:
EMQA Setup Service
Establishes the JMS connections between the JMS servers and the EMQA and adds JMS listeners for specified JMS queues. (See Using the EMQA Setup Service.)
Event Dispatch Properties
Provides the product values for the event SOAP messages. (See Configuring the Event Dispatch Properties.)
Creates event SOAP messages using the XML documents that it reads from the JMS queues, along with the event dispatch properties, and sends them to SBM for processing.
The EMQA sends the process app events that it creates to the SBM endpoint. The events are first processed by the Event Manager and then by the SBM Orchestration Engine.
Copyright © 2007–2015 Serena Software, Inc. All rights reserved.