Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange Adapters for PowerCenter 10.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for JMS
  3. Configuring PowerExchange for JMS
  4. Working with JMS Sources and Targets
  5. Creating and Configuring JMS Workflows
  6. Appendix A: JMS Datatype Reference
  7. Appendix B: Glossary of Terms

PowerExchange for JMS User Guide for PowerCenter

PowerExchange for JMS User Guide for PowerCenter

Back Next

Working with JMS Sources and Targets Overview

Working with JMS Sources and Targets Overview

Every JMS source and target definition contains JMS message header fields. Source definitions contain the header fields used to read messages from JMS sources. Target definitions contain the header fields used to write messages to JMS targets.
The following table shows the message header fields that JMS source and target definitions contain:
JMS Message Header Field
JMS Source Definition
JMS Target Definition
JMSCorrelationID
Yes
Yes
JMSMessageID
Yes
No
JMSType
Yes
Yes
JMSDestination
Yes
Yes
JMSReplyTo
Yes
Yes
JMSDeliveryMode
Yes
Yes
JMSExpiration
Yes
No
JMSTimeToLive
No
Yes
JMSPriority
Yes
Yes
JMSTimestamp
Yes
No
JMSRedelivered
Yes
No
JMS source and target definitions can also contain message property and body fields depending on which JMS message type the source or target definition represents. JMS source and target definitions can represent metadata for several types of JMS messages.
The following table shows the types of JMS messages that source or target definitions can represent:
Message Type
Description
Message
JMS source and target definitions should represent the message type Message when the source or target messages only need to contain header and property fields. Messages of the type Message cannot contain body fields.
TextMessage
JMS source and target definitions should represent the message type TextMessage when the source or target messages contain XML data. Source and target definitions that represent messages of the type TextMessage contain a single body field and can have multiple property fields.
BytesMessage
JMS source and target definitions should represent the message type BytesMessage when the source or target messages contain a stream of uninterpreted bytes. Source and target definitions that represent messages of the type BytesMessage contain a single body field and can have multiple property fields.
MapMessage
JMS source and target definitions should represent the message type MapMessage when the source or target messages contain name/value pairs. Source and target definitions that represent messages of the type MapMessage can contain any number of body and property fields.
JMS sources and targets that you define represent messages of the type Message by default. Since JMS messages of the type Message do not contain body fields, default source and target definitions do not contain body fields. The default source definition also does not contain property fields. However, you can add property fields to the source definition since JMS messages of the type Message can contain property fields.
0 COMMENTS
We’d like to hear from you!