The Message VPN bridge feature can be used to permit published messages to be delivered from one Message VPN to another to fulfill specific topic subscriptions. A Message VPN bridge can be uni-directional (messages pass over the bridge in only one direction) or bi-directional (messages pass over the bridge in both directions).
The following basic steps are required to configure a uni-directional bridge between Message VPNs:
- Create a bridge in a local Message VPN.
Refer to Configuring VPN Bridges.
- Configure the remote Message VPN that the bridge will connect to.
- If you want to transport Direct messages over the bridge, set topic subscriptions for the bridge.
- If you want to transport Guaranteed Messages over the bridge, specify an existing durable queue that is provisioned on the remote Message VPN to associate with the bridge. Refer to Configuring Message Spool Queues.
- (Optional) Enable SSL encryption for communication over the bridge.
- Enable the access for the bridge to the specified remote Message VPN. Refer to Enabling Access to Remote VPN Bridge Connections.
- Enable the bridge. Refer to Starting/Stopping Bridge Connections.
- (Optional) If you want to establish a bi-directional bridge between the Message VPNs (that is, for messages pass over the bridge in both directions), you must repeat steps 1 through 6 to configure another bridge that uses the same Message VPNs but in the reverse order.
Refer to Configuring Remote Message VPNs.
Refer to Configuring Remote Subscription Topics.
The provisioned queue must have the appropriate topic subscriptions assigned to it Adding Topic Subscriptions to Queues), and it must have an exclusive access type (refer to Configuring Access Types).
That is, this second bridge must be created in the Message VPN that was previously specified as the remote Message VPN, and the remote Message VPN this second bridge is to link to must be the Message VPN that was previously specified as the local Message VPN.