Communicating with the correlator over Universal Messaging
Note:
Use of
Universal Messaging from the IAF is deprecated and will be removed in a future release. It is recommended that you now change any IAF-based adapter configurations using
Universal Messaging with a
<universal-messaging> element in the configuration file to use an
<apama> element to talk directly to the correlator. See
Apama correlator configuration.
The correlator must be using the
Universal Messaging transport connectivity plug-in (see
The
Universal Messaging
Transport Connectivity Plug-in), and this connectivity plug-in must be configured to be equivalent to the
Universal Messaging properties you have configured for the IAF.
You should use a single dynamicChains definition:
dynamicChains:
UMString:
- apama.eventString:
suppressLoopback: true
description: "@{um.rnames}"
remoteAddress: "@{um.rnames}"
- stringCodec
nullTerminated: true
- UMTransport:
channelPattern: ".*"
The configuration of the chain manager should be equivalent to certain properties defined in the IAF:
IAF configuration | Connectivity plug-in configuration |
um.channels.prefix=UM_
um.channels.mode=precreate | managerConfig:
channel:
prefix: UM_
includePrefixOnUM: true
missingChannelMode: ignore |
um.channels.prefix=UM_
um.channels.mode=autocreate | managerConfig:
channel:
prefix: UM_
includePrefixOnUM: true
missingChannelMode: create |
um.channels.prefix=UM_
um.channels.mode=mixed | managerConfig:
channel:
prefix: UM_
includePrefixOnUM: true
missingChannelMode: create |
um.channels.mode=precreate | managerConfig:
channel:
prefix: ""
missingChannelMode: ignore |