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.5.0
- 2.4.0

Back Next

Troubleshooting Monitoring Tab Views

A EDS Node appears inactive on the Monitoring tab of the Administrator tool.: A
EDS Node
appears inactive in the following situations:
The
EDS Node
might not be running. Verify the status of the
EDS Node
. If the
EDS Node
is not running, start it.
If the
EDS Node
is running, navigate to the following directory:

<EDS Node Installation Directory>/node/logs/

View the
<node name>-node.log
file for exceptions and correct them.

The
Administrator Daemon
might not be running. Verify the status of the
Administrator Daemon
. If the
Administrator Daemon
is not running, start it.
If the
Administrator Daemon
is running, navigate to the following directory:

<Administrator Daemon Installation Directory>/admind/logs/

Check the
admind.log
file for exceptions and correct them.

The
EDS Node
is configured incorrectly.
Navigate to the following directory:

<EDS Node Installation Directory>/node/config/

Verify that the
zkservers
field in the
node.cnf
file is pointing to the correct Apache ZooKeeper server URL.

A source service or a target service appears inactive on the Monitoring tab.: This can occur if the source service or a target service is configured incorrectly.

Navigate to the following directory:

<EDS Node Installation Directory>/node/logs/

View the
<node name>-node.log
file exceptions in source or target, and correct them.

The monitoring data indicates that the source statistics are increasing continuously, but the target statistics received are not increasing.: This error occurs in the following situations:
The
Topic resolution type
field is set to
Unicast
in the data flow properties, and LBMRD is not running on the address specified in the
Resolver daemon
field. In the
Data Flows
pane, click the data flow whose properties you want to view. The
Entity Details
pane appears. Click
Connections
tab and click the connection. Verify that LBMRD is running on the address specified in the
Resolver daemon
field.
The
Topic resolution
field is set to
Multicast
in the data flow properties, and the source service and target service are on different machines. Verify that the machines running the source service and target service have multicast enabled. Also verify that the machines are configured in the same multicast group.
The transformation might not be applied correctly. Verify that you have configured the transformation correctly.

To determine whether multicast is enabled in your environment, perform the multicast capability test.

For more information about the multicast capability test, see the article
Informatica MTools
on MySupport at https://community.informatica.com/solutions/1470.
I use a Static File source service in my data flow and have specified the processed file directory. The files have been moved to the processed file directory, but the data is not received by the target service.: This situation occurs when the data is not sent to the target service because the files have been ignored. The Static File source service moves the files sent to the target service and the ignored files to the processed file directory. The Static File source service ignores the files in the following situations:
The delimiter is EOF and the value of the
Maximum Event Size
property is less than the size of the file the source service is reading from.
The files are older than the files already processed by the Static File source service.
The transformation statistics in the Grid view of the Administrator tool show a higher value in the events received column compared to the value in the events sent column.: This discrepancy might occur when the source service splits the events into multiple events based on the delimiter settings that you have specified for the source service. When the transformation receives the events from the source service, it also includes the split events in the events received statistic. As a result, the events received column of the transformation table displays a higher value than the value that appears in the events sent column of the source entity table.
You can ignore the difference in values as it has no impact on the functionality of the source service.
The monitoring data indicates that the Bytes Received, Events Received, Bytes Sent, and Events Sent statistics are displaying less than expected values.: This behavior occurs if you restart the EDS Node that the source service or target service is associated with. There is no workaround for this behaviour.