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

Ultra Messaging Source Type Properties

You can configure the following properties for the Ultra Messaging source service type:
Entity Name
Name for the Ultra Messaging target service. Maximum length is 32 characters.
Description of the source service. Maximum length is 256 characters.
UM Topic Name
Topic on which the UM sending application publishes messages.
UM XML Configuration
UM configurations in XML format that the service uses.
Maximum length is 4000 characters.
You can use the following sample configuration file to configure how the source service reads data:
<um-configuration version="1.0">
   <application name="AppName">
    <context name = "test">
      <options type="context">
         <option default-value=""  name="resolver_unicast_daemon"/>
         <option default-value="18999"  name="request_tcp_port"/>
      <options type="receiver">
         <option default-value="27997" name="transport_lbtru_port_low"/>
         <option default-value="27999" name="transport_lbtru_port_high"/>
For more information about UM configuration, see the Ultra Messaging Configuration Guide.
UM Application Name
UM sending application name that the source service uses to get the configuration.
Context Name
Context name that the source service uses to get the configuration. If you do not specify a name, the source service gets the configuration from a context with no name.
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.
The statistics that you can choose to monitor for the Ultra Messaging source service. You can select the following statistics:
  • 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.
  • Events not Delivered. Number of events that the source service did not deliver.
  • Send Rate (Per Sec). Number of bytes sent every second.

Updated March 19, 2019

Explore Informatica Network