To transport data, the UM data connection uses Ultra Messaging. EDS generates a topic name for every data connection in the data flow. Source services that use the data connection read data in blocks and publish messages on the topic. Target services subscribe to that topic, receive the data in the form of events, and send the data to the data target.
You can choose the Ultra Messaging data connection when you want to send data to one or more target services in a LAN environment, that is, use a publish/subscribe model.
The following image shows a sample data flow that uses an Ultra Messaging data connection:
When you configure the Ultra Messaging data connection, you can configure source services to use the streaming, load balancing, or persistence messaging mode to publish data.
You can also configure security for the data connection. The Ultra Messaging data connection uses TSL/SSL protocols to secure events. The TSL/SSL protocols use cipher suites or symmetric and asymmetric encryption algorithms to establish a secure communication. When you configure security for the Ultra Messaging data connection, specify the certificate details and optionally specify the cipher suites. The data connection uses the same set of certificates for both the source services and the target services.
Transport Topic Name
When you choose the Ultra Messaging data connection, you can specify the topic name for the transport on which the source service publishes data. This topic is known as well-known topic. If you do not specify a well-known topic name, the data connection uses an autogenerated topic name.
If you create custom source services or transformations, you can partition or shard events to separate the processing of large event streams. When you configure the Ultra Messaging data connection, you can specify comma-separated transport topic names.
You can specify comma-separated transport topic names when you configure data connections between the following entities:
Source services and target services
Transformations running on a source service or aggregator and targets
You can partition or shard events only when you publish data to Ultra Messaging, PowerCenter and RulePoint target services.
For example, if you have a source service that publishes secure and nonsecure events, you can publish secure events on one topic and nonsecure events on another topic. To achieve this, select
in the Transport Topic Name property. Specify the two topic names separated by a comma in the
Custom Topic Name
property as follows:
The following image shows a sample
Custom Topic Name
For more information about custom source services, see the