You can monitor Subscriber Service channel query processing using Trace. When the channel is enabled on a driver, Identity Manager prints the trace output similar to the following:
Oracle FanOut Driver SST:Injecting User Agent XDS command document into Subscriber service channel. [10/27/16 01:15:05.940]Oracle FanOut Driver SST:Applying command transformation policies. [10/27/16 01:15:05.940]Oracle FanOut Driver SST:Applying policy: %+C%14CNETQJFOMNSIS-sub-ctp-HandleMSGWQueries%-C. [10/27/16 01:15:05.940]Oracle FanOut Driver SST:Applying policy: %+C%14CNETQFOUTCOMM-sub-ctp-UpdateAddDocWithCurrentStateOfUser%-C. [10/27/16 01:15:05.940]Oracle FanOut Driver SST:Applying policy: %+C%14CNETQFOUTCOMM-sub-ctp-TransformAssociationsinAddEvent%-C. [10/27/16 01:15:05.941]Oracle FanOut Driver SST:Applying policy: %+C%14CNETQJFOENTIS-sub-ctp-FanOutEntiImpl-I%-C.
In this trace output, the Subscriber Service channel is depicted by SST. The channel is traced at the same level that is configured for the driver for which the channel is enabled.
Identity Manager also provides a separate trace file for monitoring the Subscriber Service channel operations. For example, if the name of the driver trace file is driver.log, another file is created as driver_svc.log. This file captures entries for out of band queries.
Trace messages are tagged based on the execution of Publisher or Subscriber threads. For example, when a Subscriber Service channel thread executes, the thread is traced with SST tag.
There is no change in the Remote Loader trace.