Mapping Apama events and JMS messages

After you specify which Apama events you want to associate with JMS messages, you need to create mapping rules that associate Apama event fields with parts of the JMS messages. Apama's adapter editor in Software AG Designer provides a visual mapping tool to create the mapping rules. There are several approaches for how to map Apama events to the JMS messages.

Simple mapping for JMS messages — Use this approach when a simple Apama event field can be associated with a corresponding value in the JMS message.

Using expressions in mapping rules — Use this when sending or receiving JMS messages and you need to write a customized JUEL expression for a mapping rule.

Template-based XML generation — Use this when sending JMS messages that contain XML. You assign a template that will be used to generate an XML document. The template contains placeholders for each of the source event fields whose values will replace the placeholders.

Specifying an XPath transformation for JMS messages — Use this when receiving JMS messages containing XML to specify values from the XML document that are to be used to populate the fields in the target Apama event.

Specifying an XSLT transformation for JMS messages — Use this when receiving JMS messages containing XML, to change or simplify the structure of the XML document.

Convention-based XML mapping — Use this to parse or generate XML documents by using event definitions that follow specific conventions to implicitly encode the structure of the XML document. This approach allows mapping of sequences to elements of the same type. It avoids the need for XPath, but does impose some limitations on the XML naming and structure.

Using EDA events in Apama applications — Use correlator-integrated messaging for JMS to consume and publish EDA events.

Implementing a custom Java mapper — If the mapping tools provided with Apama do not meet your needs then you can implement your own Java mapper class and use that instead.