Preface
Introduction to Informatica Edge Data Streaming
- Informatica Edge Data Streaming Overview
- Edge Data Streaming Architecture
- Data Flow Model
- Edge Data Streaming High-Level Process
- Edge Data Streaming Data Flow Process
- Edge Data Streaming User Interface
- Example
Licenses
- Licenses Overview
- Viewing the License Details
- Updating a License
- Removing a License
Using Informatica Administrator
- Using Informatica Administrator Overview
- Manage Tab - Domain View
- Manage Tab - Services and Nodes View
  - Domain
  - Application Services
- Logs Tab
- Security Tab
- Managing Your Account
- Logging In
- Password Management
  - Changing Your Password
- Managing Users and Groups
  - Default Administrator
- Managing Users
  - Creating Users
  - Unlocking a User Account
- Managing Groups
  - Adding a Native Group
- Managing Privileges
  - Domain Privileges
- Roles
- Managing Roles
- Usage Collection Policy
  - Disabling Informatica Data Usage
Creating and Managing the Edge Data Streaming Service
- Creating and Managing the Edge Data Streaming Service Overview
- Creating the Edge Data Streaming Service
  - Creating the Edge Data Streaming Service in the Administrator Tool
  - Creating the Edge Data Streaming Service using Informatica Command Line Program
- Editing the Edge Data Streaming Service
Edge Data Streaming Entity Types
- Edge Data Streaming Entity Types Overview
- Aggregators
  - Aggregator Properties
- Built-in Source Service Types
- Built-in Target Service Types
- Built-in Transformation Types
- Using Parameters in Entity Properties
  - Setting Values for Parameters
  - Examples
- Custom Entity Types
- Advanced Configuration for Entities
- Configuring High Availability for Entities
Edge Data Streaming Nodes
- Edge Data Streaming Nodes Overview
- Node Groups
- Node Group Management Tab
- Working with Node Groups
Data Connections
- Data Connections Overview
- Ultra Messaging Data Connection
- WebSocket Data Connection
  - Configuring an External Load Balancer
  - WebSocket Data Connection Properties
Working With Data Flows
- Working With Data Flows Overview
- Types of Data Flows
- Creating a Data Flow
- Data Flow Design Tab
- Adding Entities to a Data Flow
- Edge Data Streaming Node Mapping
- Deploying a Data Flow
- Undeploying a Data Flow
- Undeploying and Deploying all Data Flows
  - Undeploying All Data Flows
  - Deploying All Data Flows
- Editing Data Flows and Entities
- Cloning a Data Flow
- Removing Data Flows and Entities
- Verifying Entity Properties
- Configuring Targets with Data Connection and Target Service Properties
  - Getting the Topic Name Assigned to a Connection
  - Getting the Receiver Type ID of a Target Service
- Getting Entity Alerts
Managing the Edge Data Streaming Components
- Managing the Edge Data Streaming Components Overview
- Administrator Daemon Management
- Edge Data Streaming Node Management
- Managing the Informatica Domain
Security
- Security Overview
- Authentication
- Component Security
- Secure Communication Within the Components
- Secure Data Storage
  - Update Encryption Keys
  - Updating Security Keys
- Secure Source Services and Target Services
- Privileges and Roles
High Availability
- High Availability Overview
- Restart and Failover
- Resilience
- Configuring High Availability in Edge Data Streaming
  - Design-Time High Availability
  - Run-Time High Availability
    - Entity High Availability
Disaster Recovery
- Disaster Recovery Overview
- Step 1: Replicate the EDS Installation
- Step 2: Back Up Data Flows
- Step 3: Back Up The Node Groups
- Step 4: Set Parameters
- Step 5: Replicate Source Files and Position Files
- Step 6: Restore EDS from the Disaster Recovery Site
Monitoring Edge Data Streaming Entities
- Monitoring Edge Data Streaming Entities Overview
- Viewing the Monitoring Tab
- Monitoring Tab Layout
  - System View
  - Grid View
- Edge Data Streaming Statistics
Appendix A: Troubleshooting
- Troubleshooting Licenses
- Troubleshooting Edge Data Streaming Node Issues
- Troubleshooting Administrator Daemon Issues
- Troubleshooting the Administrator Tool
- Troubleshooting Apache ZooKeeper
- Troubleshooting Component Connectivity Issues
- Troubleshooting Edge Data Streaming High Availability
- Troubleshooting Data Flows
- Troubleshooting Entities
- Troubleshooting Monitoring Tab Views
Appendix B: Frequently Asked Questions
- Frequently Asked Questions About Edge Data Streaming
Appendix C: Regular Expressions
Appendix D: Command Line Program
- Command Line Program Overview
- infacmd eds Plugin
- Running Commands
- infacmd Return Codes
- infacmd eds Command Reference
Appendix E: Configuring Edge Data Streaming to Work With a ZooKeeper Observer
Appendix F: Glossary
- Administrator Daemon
- data flow
- Informatica Administrator
- receiver type ID
- source service
- target service
- topic resolution domain
- unicast topic resolution daemon (LBMRD)
- EDS Node

User Guide

2.4.0
- 2.5.0

Back Next

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: 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"> <applications> <application name="AppName"> <contexts> <context name = "test"> <options type="context"> <option default-value="10.65.43.186:15380" name="resolver_unicast_daemon"/> <option default-value="18999" name="request_tcp_port"/> </options> <options type="receiver"> <option default-value="27997" name="transport_lbtru_port_low"/> <option default-value="27999" name="transport_lbtru_port_high"/> </options> </context> </contexts> </application> </applications> </um-configuration>

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.
Statistics: 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.

Rename Saved Search

Table of Contents

User Guide

User Guide

Ultra Messaging Source Type Properties

Ultra Messaging Source Type Properties