Deploying and Managing Apama Applications > Correlator-Integrated JMS Messaging > Mapping Apama events and JMS messages
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. The Apama Studio adapter editor 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 containing XML; you assign a template to generate an XML document, containing placeholder values substituted in from fields in the source event.
*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.
Copyright © 2013 Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.