This monitor can be used to setup adapter bridges which allow an adapter connected to one correlator to be shared with other correlators.
The bridge provides a client correlator access to an adapter hosted on the server correlator. To work correctly the bridging bundle must be injected into both correlators. On the server side a server side bridge must be configured and on the client side, a client side bridge. This is done using the ConfigureServerSide and ConfigureClientSide events. The two correlators must be engine_connected together for the bridges to work. This will involve using channels. The actual channels connected must match those specified in the bridge configuration events.
The bridging service doesn't actually do the bridging work itself. Instead it creates separate bridging service instances for each protocol com.apama.statusreport, com.apama.marketdata, com.apama.oms. Those bridges forward events between the correlators. They also monitor the correlator to correlator connection so as to report errors. To make that possible an IAFConnectionMonitor and IAFStatusFaker needs to be created in each correlator. This bridging service also creates the required instances of the IAFConnectionMonitor and IAFStatusFaker services.
com.apama.connection.IAFStatusFaker - This service is used to allow correlator connections to be monitored as though they were IAF instances. The IAFStatusFaker, fakes the IAF's protocol.
com.apama.adapters.IAFConnectionMonitor - The market data, oms, and status bridges all monitor the connections of the two correlators. They do so using this service.