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

Connecting to JMS Providers

Connecting to JMS Providers

When you configure a JMS workflow, you use JNDI and JMS application connections to connect to the provider. JMS providers use JNDI to store their connection information. When you configure a JMS provider to send and receive messages, you configure JNDI information for the provider.
JNDI stores the following connection information:
  • Connection factory.
    Contains information to create a connection to the JMS provider. For example, a connection factory for a WebSphere MQ JMS provider might contain information about a host name and port number for the provider.
  • Destination.
    Contains information about message sources and destinations. For example, a destination for a WebSphere MQ JMS provider might contain information about a queue name and queue manager.
Configure a JNDI application connection to set connection information that enables the PowerCenter Integration Service to connect to the JNDI server. Configure a JMS application connection to provide a connection factory name and a destination name. You also provide a domain for the messages.
The PowerCenter Integration Service connects to the JNDI server based on the JNDI connection information you provide in the JNDI application connection. When it connects to JNDI, it uses the connection factory name you provide in the JMS application connection to retrieve the JMS provider connection information. It also uses the destination name you provide to determine the source and target for JMS messages. It then reads JMS messages or writes JMS messages according to the message domain you specified in the JMS application connection.

0 COMMENTS

We’d like to hear from you!