Connector Architecture for JMS and JDBC

In the Admin Console, connector, JMS, and JDBC resources are handled differently, but they use the same underlying Connector architecture. In the Communications Server, all communication to an EIS, whether to a message provider or an RDBMS, happens through the Connector architecture. To provide JMS infrastructure to clients, the Communications Server uses the Sun GlassFish Message Queue software. To provide JDBC infrastructure to clients, the Communications Server uses its own JDBC system resource adapters. The application server automatically makes these system resource adapters available to any client that requires them.

For more information about JMS in the Communications Server, see Chapter 18, Using the Java Message Service. For more information about JDBC in the Communications Server, see Chapter 15, Using the JDBC API for Database Access.