The System Queue provides a subsystem similar to Java™ Message Service (JMS) for IBM Security Directory Integrator. It is designed for storing and forwarding general messages and IBM® Security Directory Integrator Entry Objects, between IBM Security Directory Integrator Servers and AssemblyLines. You can use the information provided here to know more about System Queue Connector.
The System Queue Connector is the mechanism for AssemblyLines to interface with the System Queue. To learn more about the System Queue and its configuration, refer to the System Queue section in the Installing and Administering.
The System Queue Connector uses the Server API to access the System Queue. The Connector uses both the local and remote interfaces of the Server API, allowing the Connector to operate on an IBM Security Directory Integrator System Queue running on a remote computer. The Connector's ability to operate on a remote computer, coupled with the System Queue's capability to connect to remote JMS servers, results in the ability to use some quite complex deployment scenarios. For example: an IBM Security Directory Integrator server and a System Queue Connector deployed on machine A, working through the remote Server API with the IBM Security Directory Integrator server and System Queue on machine B, which in turn interface with a JMS server deployed on machine C.
In IBM Security Directory Integrator, ActiveMQ is used as the default System Queue and is enabled by the install process. Default settings of ActiveMQ can be altered in the <tdi install dir>/etc/activemq.xml file.