Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Edge Data Streaming 2.4.0
  • All Products

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

Back Next

Ultra Messaging Data Connection Properties

Ultra Messaging Data Connection Properties

To add an Ultra Messaging data connection, use the Ultra Messaging data connection type when you connect a source service to a target service in a data flow.
You can configure the following properties for the Ultra Messaging data connection type:
Entity Name
Name of the data connection. Maximum length is 32 characters.
Description
Description of the data connection. Maximum length is 256 characters.
Topic resolution type
Type of topic resolution that you want to use.
You can choose one of the following topic resolution types:
  • Multicast. Data connection uses multicast topic resolution.
  • Unicast. Data connection uses the unicast resolver daemon (LBMRD) for topic resolution.
Resolver daemon
Address of the topic resolution daemon if you choose unicast topic resolution type.
Resolver address
Multicast address that you want to use.
Messaging mode
Mode in which the source service distributes data to the target service.
You can choose one of the following messaging modes:
  • Load Balancing. The source service uses load balancing to send data.
  • Streaming. The source service uses streaming to distribute data.
  • Persistence. The source service uses persistence to distribute data. Select this messaging mode to use the default persistence store. If you want to use an external persistence store, specify the configuration in the
    UM XML Configurations
     property.
Connection Type
Type of connection.
You can select one of the following connection types:
  • UM. The data connection uses a nonsecure connection to publish events.
  • UM Secure. The data connection uses a secure connection to publish events.
Cipher suites
The cipher suite that the Ultra Messaging data connection uses to secure data.
Certificate
The certificate file name that the Ultra Messaging data connection uses to secure data. Specify the certificate if you select the
UM Secure
 connection type.
Certificate key
The certificate key file name that the data connection uses. Ultra Messaging supports certificates that are in PEM or ASN1 format.
Specify the certificate key file name if you select the
UM Secure
 connection type.
This file is located in the
<EDS installation directory>/node/certificates
 directory.
Certificate key password
Password to the key file. Specify the certificate if you select the
UM Secure
 connection type. Select a secure parameter if you have already created it. To specify a key and value, click
Click to add secure parameters
.
This file is located in the
<EDS installation directory>/node/certificates
 directory.
Trusted certificates
The trusted certificates file that the Ultra Messaging data connection uses. Specify the file name if you select the
UM Secure
 connection type.
This file is located in the
<EDS installation directory>/node/certificates
 directory.
Resolver port
Optional. The unicast or multicast UDP port used by the UM transport for topic resolution.
Specify the port if you want to open fixed ports in a firewall.
If you specify the port, the default port ranges used by EDS are overwritten. You must map each entity in the data flow to a unique EDS node instance.
TCP request port
Optional. The port on which to listen for responses from requests. Each UM context binds to a TCP port for requests when it is initialized.
Specify the port if you want to open fixed ports in a firewall.
TCP Transport Port
Optional. The preferred TCP port for the topic that the UM application publishes on. All receivers interested in the topic establish a connection to this port.
Specify the port if you want to open fixed ports in a firewall.
UM XML Configuration
The UM configuration that the data connection uses. Specify the configuration in the following format: 
<template name="entity-user-template">
<options type="source">
<option name="umq_ulb_flight_size" default-value="1000"/>
</options>
<options type="context">
</options>
<options type="receiver">
</options>
</template>
Maximum length is 4000 characters.
To configure intragroup or intergroup stability, you can use the following sample configuration:
Intragroup stability 
<template name="entity-user-template">
<options type="source">
<option default-value="all-stores"  name="ume_retention_intragroup_stability_behavior"/>
</options>
<options type="context"></options>
<options type="receiver"></options>
</template>
Intergroup stability 
<template name="entity-user-template">
<options type="source">
<option default-value="all"  name="ume_retention_intergroup_stability_behavior"/>
<option default-value="0:3"  name="ume_store_group"/>
<option default-value="1:3"  name="ume_store_group"/>
</options>
<options type="context"></options>
<options type="receiver"></options>
</template>
You can use the following sample configuration to use an external persistence store if you select the Persistence messaging mode: 
<template name="entity-user-template"> 
					<options type="source">
    					<option name="ume_store_name" default-value="VDS230Store1"/>
						   <option name="ume_store_name" default-value="VDS230Store2"/>
						   <option name="ume_store_name" default-value="VDS230Store3"/>
					</options>
					<options type="context">
					</options>
					<options type="receiver">
					</options>
			</template>
You can use the following sample configuration for the external persistence store if you select the Persistence messaging mode: 
<?xml version="1.0" encoding="UTF-8"?>
<!--
  - A simple configuration file for a UME store daemon that listens on port
  - 14567 for registration. Logs are appended to the file ume-example-stored.log
-->
<!DOCTYPE umestore SYSTEM "umestore.dtd">
<ume-store version="1.2">
    <daemon>
        <lbm-config>C:\Informatica\UM\UMP_6.8\config\ump.cfg</lbm-config>
        <log>ump.out</log>
        <pidfile>umestored.pid</pidfile>
        <web-monitor>*:15304</web-monitor>
        <lbm-license-file><Path to license>\UMQLicense.txt</lbm-license-file>
    </daemon>
    <stores>
        <store name="EDS Store A" port="14567">
            <ume-attributes>
                <option type="store" name="disk-cache-directory" value="C:\Informatica\UM\UMP_6.8\cache1"/>
                <option type="store" name="disk-state-directory" value="C:\Informatica\UM\UMP_6.8\state1"/>
                <option type="store" name="allow-proxy-source" value="1"/>
                <option type="store" name="context-name" value="VDSStoreA"/>
            </ume-attributes>
            <topics>
                <topic pattern="." type="PCRE">
                    <ume-attributes>
		          <option type="store" name="repository-type" value="disk"/>
                        <option type="store" name="repository-size-threshold" value="104857600"/>
                        <option type="store" name="repository-size-limit" value="209715200"/>
                        <option type="store" name="repository-disk-file-size-limit" value="1073741824"/>
                        <option type="store" name="source-activity-timeout" value="30000"/>
                        <option type="store" name="receiver-activity-timeout" value="604800000"/>
                        <option type="store" name="retransmission-request-forwarding" value="0"/>
                    </ume-attributes>
                </topic>
            </topics>
        </store>
        <store name="EDS Store B" port="14568">
            <ume-attributes>
                <option type="store" name="disk-cache-directory" value="C:\Informatica\UM\UMP_6.8\cache2"/>
                <option type="store" name="disk-state-directory" value="C:\Informatica\UM\UMP_6.8\state2"/>
                <option type="store" name="allow-proxy-source" value="1"/>
                <option type="store" name="context-name" value="VDSStoreB"/>
            </ume-attributes>
            <topics>
                <topic pattern="." type="PCRE">
                    <ume-attributes>
		          <option type="store" name="repository-type" value="disk"/>
                        <option type="store" name="repository-size-threshold" value="104857600"/>
                        <option type="store" name="repository-size-limit" value="209715200"/>
                        <option type="store" name="repository-disk-file-size-limit" value="1073741824"/>
                        <option type="store" name="source-activity-timeout" value="30000"/>
                        <option type="store" name="receiver-activity-timeout" value="604800000"/>
                        <option type="store" name="retransmission-request-forwarding" value="0"/>
                    </ume-attributes>
                </topic>
            </topics>
        </store>
        <store name="EDS Store C" port="14569">
            <ume-attributes>
                <option type="store" name="disk-cache-directory" value="C:\Informatica\UM\UMP_6.8\cache3"/>
                <option type="store" name="disk-state-directory" value="C:\Informatica\UM\UMP_6.8\state3"/>
                <option type="store" name="allow-proxy-source" value="1"/>
                <option type="store" name="context-name" value="VDSStoreC"/>
            </ume-attributes>
            <topics>
                <topic pattern="." type="PCRE">
                    <ume-attributes>
		          <option type="store" name="repository-type" value="disk"/>
                        <option type="store" name="repository-size-threshold" value="104857600"/>
                        <option type="store" name="repository-size-limit" value="209715200"/>
                        <option type="store" name="repository-disk-file-size-limit" value="1073741824"/>
                        <option type="store" name="source-activity-timeout" value="30000"/>
                        <option type="store" name="receiver-activity-timeout" value="604800000"/>
                        <option type="store" name="retransmission-request-forwarding" value="0"/>
                    </ume-attributes> 
                </topic>
            </topics>
        </store>
    </stores>
</ume-store>
0 COMMENTS
We’d like to hear from you!