Table of Contents

Search

  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. Appendix A: Troubleshooting
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Regular Expressions
  18. Appendix D: Command Line Program
  19. Appendix E: Configuring Edge Data Streaming to Work With a ZooKeeper Observer
  20. Appendix F: Glossary

User Guide

User Guide

Data Flow Model

Data Flow Model

EDS
uses a data connection to transport data from the source service to the target service. Use the Administrator tool to design the flow of data from the data source to the data target, deploy the data flow, and monitor the data flow.
The following image shows a simple
EDS
data flow:
In the data flow, a source service runs on a EDS Node and a target service runs on another EDS Node. The source service reads data from the data source and publishes the data. The target service receives the data and writes the data to the data target.
The data flow consists of the following components:
Data source
You can read data from the following sources:
  • Event logs
  • Real-time logs
  • Call detail records
  • TCP/UDP applications
  • Syslog sources
  • MQTT brokers
  • HTTP clients
  • JMS providers
  • OPC DA sources
  • Ultra Messaging applications
  • WebSocket clients
EDS Node
The
EDS Node
runs on host machines on which you want to run a source service or a target service. A
EDS Node
can contain the following entities:
  • Source service. A source service collects data from a data source and publishes the data. You can run a source service on a machine that either hosts the data source or can access it.
  • Target service. A target service receives data from one or more source services and writes the data to a data target. You can run the target service on a machine that either hosts the data target or can access it.
  • Aggregator. An aggregator collects data from source services or other aggregators and publishes the data to target services or other aggregators.
  • Transformation. A process that transforms the data that a source service or aggregator publish or the data that a target service or aggregator receive, or both. A transformation runs on the EDS Node that contains the source service, the target service, or the aggregator.
Data target
You can write data to the following targets:
  • Informatica PowerCenter
  • Informatica RulePoint
  • Hadoop Distributed File System (HDFS) cluster
  • HTTP servers
  • Amazon Kinesis streams
  • Apache Kafka publish-subscribe messaging system broker
  • Azure Event Hubs
  • Apache Cassandra
  • JMS providers
  • Ultra Messaging application
  • WebSocket servers
Data connection
EDS Node
s use a data connection to transport data from a source service to a target service. When you design a data flow, you can choose one of the following data connections:
  • Ultra Messaging. If you choose the Ultra Messaging data connection,
    EDS
    uses the Ultra Messaging or the publish/subscribe model to transport data.
  • WebSocket. If you choose the WebSocket data connection,
    EDS
    uses the WebSocket protocol, which provides bi-directional communication over a single TCP connection.

0 COMMENTS

We’d like to hear from you!