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

Creating the Edge Data Streaming Service in the Administrator Tool

Create the Edge Data Streaming Service in the Manage tab in Administrator tool and create, manage, deploy and undeploy, and monitor data flows.

Start the

Administrator Daemon

and Apache ZooKeeper before you create the service.

In the

Administrator tool

, click the

Services and Nodes

tab.

Click

Actions

New

Edge Data Streaming Service

The

New Edge Data Streaming Service

window appears.

Enter the following general properties for the service:

Name: Name of the Edge Data Streaming Service. The name is not case sensitive and must be unique within the Informatica domain. The characters must be compatible with the code page of the associated repository. The name cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special characters:

` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
Description: Description of the service. The description cannot exceed 765 characters.
Location: Name of the Informatica domain and folder where you want to create the service. Optionally, click
Browse
to select another folder in the Informatica domain.
License: License assigned to the service. Select from the list of
EDS
licenses available.
Assign: Node on which the service runs. Select
Single Node
to assign the service to a node.
Node: The host name or machine name where the service runs.

Click

Enter the following database properties for the service:

Database Type: The type of database that contains the
EDS
repository.
You can select one of the following databases:
DB2
Oracle
SQLServer
Sybase
Kerberos Authentication: Indicate that the database uses Kerberos authentication. This option is supported only for SQLServer.
Username: The database user.
Password: Database password corresponding to the database user.
JDBC Connect String: The connection string used to connect to the database.
IBM DB2.
jdbc:informatica:db2://<host name>:<port>;DatabaseName=<database name>

Microsoft SQL Server.
Server: jdbc:informatica:sqlserver://<host name>:<port>;DatabaseName=<database name>

Kerberos-enabled Microsoft SQL Server.
jdbc:informatica:sqlserver://<host name>:<port>;DatabaseName=qadb;integratedSecurity=true;authenticationScheme=JavaKerberos;encrypt=false

Oracle.
jdbc:informatica:oracle://<host name>:<port>;ServiceName=<service name>

Sybase.
jdbc:informatica:sybase://<host name>:<port>;DatabaseName=<database name>
Secure JDBC Parameters: Secure JDBC parameters that you want to append to the database connection URL.

Use this property to specify secure connection parameters such as passwords. The Administrator tool does not display secure parameters or parameter values in the Edge Data Streaming Service properties. Enter the parameters as name=value pairs separated by semicolon characters (;). For example:

param1=value1;param2=value2

If secure communication is enabled for the database, enter the secure JDBC parameters in this property.
Database Schema: The schema name for the Microsoft SQL Server database.
Database Tablespace: Tablespace name for IBM DB2 database. When you specify the tablespace name, the
Edge Data Streaming
Service creates all repository tables in the same tablespace. You cannot use spaces in the tablespace name.