Apama Documentation : Connecting Apama Applications to External Components : Standard Connectivity Plug-ins : The Universal Messaging Transport Connectivity Plug-in : Replacing the deprecated Universal Messaging integration
Replacing the deprecated Universal Messaging integration
When using the new Universal Messaging connectivity plug-in to mimic the deprecated Universal Messaging integration, then 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 depends on your previous Universal Messaging configuration:
Deprecated configuration
New 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
In the deprecated configuration, it was possible to configure some channels (without a prefix) to be looked up on Universal Messaging but not created, while also specifying a prefix under which channels would be created. This specific use case is not possible to directly port to the new-style configuration.
Copyright © 2013-2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback