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

Maintaining Transactional Consistency for JMS Targets

Maintaining Transactional Consistency for JMS Targets

The PowerCenter Integration Service can maintain transactional consistency when writing data to JMS targets. When the PowerCenter Integration Service maintains transactional consistency, it commits messages to JMS targets after all documents in a transaction group are loaded to the targets. A transaction group consists of all documents that the PowerCenter Integration Service commits when it reaches a commit point.
To ensure transactional consistency, all JMS targets in the same pipeline must belong to the same target connection group. JMS targets that are in the same target connection group receive data from the same transactional source. Additionally, two or more JMS targets are in the same target connection group if they have the same value for each of the following connection properties in JMS and JNDI application connections:
  • JNDI Context Factory
  • JNDI Provider URL
  • JNDI UserName
  • JNDI Password
  • JMS Destination Type
  • JMS Connection Factory Name

0 COMMENTS

We’d like to hear from you!