For an Apama application to use Universal Messaging channels, the default behavior requires you to use Universal Messaging Enterprise Manager or Universal Messaging client APIs to create those channels. You can change the default behavior by setting missingChannelMode to create so that a Universal Messaging channel can be automatically created if it does not already exist when an Apama application needs to use it. See also Configuring the dynamicChainManagers.

The recommendation is to use the same Universal Messaging configuration properties file for all Apama components.

When a Universal Messaging channel is automatically created it has the attributes described in Setting up Universal Messaging for use by Apama. If you want a Universal Messaging channel to have any other attributes then you must create the channel in Universal Messaging before any Apama component sends to or subscribes to the channel.

You can specify the ACL (access control list) permissions for the channel being created in a YAML configuration file using the createChannelPermissions option. See Configuring the dynamicChainManagers.