There are a set of checks that you can carry out to investigate
why publish/subscribe messages are not being received by a subscription
on a service integration bus, when the messages are being routed through
a remote message point.
About this task
Complete this task as part of
Investigating why publish/subscribe messages are not arriving at a subscription. This task explains
how to investigate the flow of messages in a publish/subscribe messaging
scenario where the messages are being routed through a remote message
point to a nondurable subscription. The following diagrams illustrates
two possible situations. The dotted lines in the diagrams indicate
relationships between publication points, whereas the solid lines
indicate flow of messages. In Figure 1, a bus contains three messaging
engines, ME1, ME2 and ME3. The publishing application is connected
to ME1 and subscribing applications are connected to ME2 and ME3.
ME1 hosts remote publication points that represent the publication
points hosted by ME2 and ME3. In Figure 2, a bus contains three messaging
engines, ME1, ME2 and ME3. The publishing application is connected
to ME1 and the subscribing applications are connected to ME2 and ME3.
ME1 hosts remote publication points that represent the publication
points hosted by ME2 and ME3. Subscribing application B is connected
to ME3 and receives publications from ME1 through a remote subscription
on ME2. The messaging engines are referred to in the following steps.
Figure 1. Point-to-point message production by using a remote message
point 
Figure 2. Publish/subscribe messaging by using a remote message point 
The following steps apply to both the
above scenarios.