Table of Contents

  1. Preface
  2. Introduction to Informatica Edge Data Streaming
  3. Licenses
  4. Using Informatica Administrator
  5. Creating and Managing the Edge Data Streaming Service
  6. Edge Data Streaming Entity Types
  7. Edge Data Streaming Nodes
  8. Data Connections
  9. Working With Data Flows
  10. Managing the Edge Data Streaming Components
  11. Security
  12. High Availability
  13. Disaster Recovery
  14. Monitoring Edge Data Streaming Entities
  15. Troubleshooting
  16. Frequently Asked Questions
  17. Regular Expressions
  18. Command Line Program
  19. Configuring Edge Data Streaming to Work With a ZooKeeper Observer
  20. Glossary

User Guide

User Guide

JMS Target Service Type

Use a JMS target service type to receive data from source services and write data to a JMS provider.
The EDS installation package includes Active MQ JAR files. If your JMS provider is IBM MQ, you must include the IBM MQ client libraries in the <EDS installation directory>/node/lib directory before you use the JMS target service type in the data flow.
You can configure the following properties for a JMS target service type:
Entity Name
Name of the source service. Maximum length is 32 characters.
Description of the target service. Maximum length is 256 characters.
JNDI Context Factory
The JMS provider specific initial JNDI context factory implementation for connecting to the JNDI service. This value is a fully qualified class name of the Initial Context Factory.
For example, the class name of the Initial Context Factory for ActiveMQ is:
For more information, see the documentation of the JMS provider.
JMS Connection Factory
The name of the object in the JNDI server that enables the JMS Client to create JMS connections.
For example, jms/QCF or jmsSalesSystem.
Connection URL
The location and port of the JMS provider on which to connect. For example:
User Name
User name to the connection factory.
The password of the user account that you use to connect to the connection factory.
Select a secure parameter if you have already created it. To specify a key and value, click Click to add secure parameters.
Retry on Failure
Indicates that the target service should try to write to the target if the operation fails the first time.
Number of Retries
The number of times the target service should retry to write to the source.
Delay between Retries
Time in milliseconds between successive retries.
You can collect and monitor the following statistics for the JMS target service:
  • Bytes Received. The number of bytes the target service receives.
  • Events Received. The number of events the target service receives.
  • Receive Rate (Per Sec). The number of bytes the target service receives every second.
  • Events Reassigned. The number messages that the source service resends to the target service when it has not received acknowledgment from the target service.
Destination Type
The type of destination on which the target service sends JMS messages. You can select one of the following destinations:
  • Topic. The target service sends JMS messages on a topic.
  • Queue. The target service sends JMS messages on a queue.
Name of the queue or topic on the JMS Provider as defined in the JMS Connection Factory created by the JMS Administrator. The target service sends JMS messages to this queue or topic.
Priority Level
Priority of the message. The priority level ranges from 0 to 9.
Expiration Time(ms)
Time in seconds after which the message expires.
Message Type
Type of message that the target service sends. Select one of the following message types:
  • Byte
  • Text
  • Map
Delivery Mode
Specifies the delivery mode for the messages. You can select one of the following delivery types:
  • Persistent.
  • Non-Persistent

Updated March 19, 2019

Explore Informatica Network