Creating Channel Joins
Joining channels using the Enterprise Manager creates a physical link between a source channel and a destination store (a channel or a queue). After you create a join, any events published to the source channel are republished to the destination store. You can create a join between the following sources and destinations:
A channel on a realm and a store on another realm federated with the source realm.
A channel on a clustered realm and a store in the same cluster. A non-cluster-wide channel can be joined to a cluster-wide store, but not the other way round.
A channel in one cluster and a channel in another cluster by using an inter-cluster join. You must first create an inter-cluster connection between the two clusters.
A source channel and a destination queue. Universal Messaging does not support joins where the source is a queue.
You can join channels programmatically or by using the Enterprise Manager.
To create a channel join in the Enterprise Manager
1. In the namespace tree of a realm, select the channel that you want to use as a source and right-click it.
2. From the drop-down menu, select Join channel channel_name.
3. Specify the following join attributes:
a. In the To Realm field, select the realm that holds the destination store.
b. In the To Store field, type the name of the destination store.
c. Click OK.
4. (Optional) Specify any of the following additional join attributes:
In the
Filter field, specify a filter, so that only specific events published to the source channel, which match certain search criteria, will be routed to the destination store. For example, if you type
CCY='EUR', only events with the event property CCY equal to 'EUR' occurring on the source channel will be published to the destination store.
In the
Hop Count field, specify the number of join hops through which an event can travel. The default is
10.
Select the
Allow Purge option to purge events when the source channel is purged.
Select the
Archival option to create an archival join, which is created only between a channel and a destination queue. With an archival join, events on the queue are not checked for duplication, which may result in duplicate events if the queue has multiple sources.
5. Click OK.
The Enterprise Manager creates an outgoing join on the source channel and an incoming join on the destination store. You can view the newly created joins and any existing joins on the Joins tab of a channel or queue.