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

Troubleshooting Data Flows

The data flows do not appear correctly in the Administrator tool.: This error might occur if you have updated the Enterprise license to a Free license, and the EDS Node name is not the same as the host name. A license error occurs in the
<EDS installation folder>/node/logs/<node name>-node.log
file. When you start the EDS Node, use the host name as the EDS Node name.

The data flows are deployed, but the target services do not receive any data.: This error might occur if the network interfaces are not configured correctly. A
no interfaces matching criteria
exception occurs in the
<EDS installation folder>/node/logs/<node name>-node.log
file. Configure the correct interface in the
networkInterface
property in the
<EDS installation folder>/node/config/node.cnf
file.

The data flows are deployed, the source services and the target services are running but the target services do not receive any data.: This error might occur if the data flow uses
UM Secure
connection type in the data connection and the security related fields are not configured correctly. The EDS Node logs a security related error in the EDS Node log file. Specify correct values for the security related fields for the data connection and redeploy the data flows.

When I deploy a data flow, not all messages in the data flow are sent.: This error might occur if the machine on which the EDS Node is running is low on memory. An
OutOfMemoryError: Direct buffer memory error
occurs in the
<EDS installation folder>/node/logs/<node name>-node.log
file. Increase the system memory or free up some memory by closing applications that are occupying more memory before you deploy the data flow.

In a deployed data flow, there is discrepancy in the bytes sent and bytes received.: This discrepancy in statistics might occur if you restart the source EDS Node associated with the data flow when the data flow is deployed. When you stop and start the EDS Node, the statistics are not reported for the interval during which the EDS Node is down.

The data flows are deployed but there is a discrepancy in the data that is sent and received.: This discrepancy might occur in case of database or ZooKeeper corruption. The data flows that you create and deploy using the corrupt data might be in inconsistent states or contain stale data. In this case, recover the data manually. As the data flows are not automatically refreshed, you must manually recover them.

To recover the states of the data flows, perform the following tasks:
Undeploy all data flows. To clear the ZooKeeper configuration or corrupted data from the data flows, perform a force clean when you undeploy all data flows.
Deploy all data flows.

I am using a Syslog UDS source in the data flow and unable to log in to the machine on which the node is installed.: This issue might occur if the Syslog UDS source has stopped publishing messages after the target service turns inactive.

To resolve this issue, undeploy the data flow and change the messaging mode from load balancing to streaming.

I have configured a WebSocket data connection to connect to an external load balancer. I see that the source service is not sending data to the load balancer and I get the following error message in the EDS Node log file for the source services:: java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method)

This issue occurs if all the machines hosting the EDS Nodes for the target services are down.

To resolve this issue, perform the following steps:

If deployed, undeploy the data flow.
Start the EDS Nodes on the machines for the target services.
Deploy the data flow.

When I deploy a data flow that has multiple sources and targets and that uses an Ultra Messaging data connection, I get the following error:: ERROR [src1-104] com.informatica.vds.reader.SourceWrapper - Exception in source com.latencybusters.lbm.LBMEOPException: CoreApi-5688-3230: could not find open TCP server port in range [14371-14390]

This issue might occur because of the configuration of the Ultra Messaging connection.

To resolve this issue, specify the following configuration for the Ultra Messaging connection and deploy the data flow again:

<template name="entity-user-template"> <options type="context"> <option name="transport_tcp_port_high" default-value="30000"/> <option name="transport_tcp_port_low" default-value="29000"/> </options> </template>

Rename Saved Search

Table of Contents

User Guide

User Guide

Troubleshooting Data Flows

Troubleshooting Data Flows