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 Source Service Type

Use a JMS source service type to read data from a JMS provider.
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 source service type in the data flow.
You can configure the following properties for a JMS source service type:
Entity Name
Name of the source service. Maximum length is 32 characters.
Description
Description of the source 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
org.apache.activemq.jndi.ActiveMQInitialContextFactory
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:
tcp://jndiserverA:61616
User Name
User name to the connection factory.
Password
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 parameter name and value, click Click to add secure parameters.
Destination Type
The type of destination on which the source service receives JMS messages. You can select one of the following destinations:
  • Topic. The source service receives JMS messages on a topic.
  • Queue. The source service receives JMS messages on a queue.
Durable Subscription Name
Durable subscriptions can receive messages sent while the subscribers are not active. Durable subscriptions provide the flexibility and reliability of queues, but still allow clients to send messages to many recipients. Specify the subscription name if the destination type is topic.
Destination
Name of the queue or topic on the JMS Provider as defined in the JMS Connection Factory created by the JMS Administrator. The source service receives JMS messages from this queue or topic.
Message Type
Type of message that the source service receives. Select one of the following message types:
  • Byte
  • Text
  • Map
Acknowledgment Mode
Specifies the acknowledgement mode for non-transacted sessions. You can select one of the following acknowledgment modes:
  • Auto Acknowledge. The session automatically acknowledges a message when a client receives it.
  • Client Acknowledge. A client acknowledges a message by calling the message's acknowledge method.
Client ID
Client identifier to identify the connection.
Selector
Optional. Criteria for filtering message header or message properties, to limit which JMS messages the source service receives.
Maximum Event Size
Maximum length of data that the source service can read at a time, in bytes. Default is 8192. Minimum value is 1. Maximum value is 51200.
Maximum Event Size
Maximum length of data that the source service can read at a time, in bytes. Default is 8192. Minimum value is 1. Maximum value is 51200.
Retry on Failure
Indicates that the source service should try to open or read from the source if the operation fails the first time.
Number of Retries
The number of times the source service should retry to open or read from the source.
Delay between Retries
Time in milliseconds between successive retries.
Persist Data
Persist the data from the source locally so that the source service can continue to process data even if the target is not available.
Persistence Options
You can configure the following persistence options:
  • batchSizeInBytes. The batch size of the events in bytes after which the data is written to the persistent store. Specify a value of 0 if you want to write the data to the persistent store immediately. Default is 262144 bytes.
  • flushInterval. The interval in milliseconds after which the source services writes data to the persistent store. Default is 5000 milliseconds.
  • maxDataFiles. The maximum number of data files that the source service can keep in the persistent store. After the number of files exceed this number, a rollover occurs. Default is 10.
  • maxDataFileSize. The maximum size of each data file in bytes. When the file reaches the specified size, a file rollover occurs. Default is 1073741824.
  • maxQueueSizeInBytes. The maximum size of data that is unsent or has not received acknowledgment in bytes that can be stored in the persistent store. If the specified size is exceeded, the source service does not read data from the source. If you specify a value of 0, the unsent data can be as much as the value of maxDataFiles times maxDataFileSize. Default is unlimited size.
Statistics
You can collect and monitor the following statistics for the JMS source service:
  • Bytes Sent. Number of bytes sent by the source service.
  • Events Sent. Number of events sent by the source service.
  • Events to be Sent. Number of events that the source service is yet to send.
  • Send Rate (Per Sec). Number of bytes sent every second.
  • Events not Delivered. The number of events not delivered by the source service.


Updated March 19, 2019


Explore Informatica Network