Protocol Compatibility Overview of the JMS Thin Client JMS Thin Client Functionality

Developing a Thin Client 5-5

5.3 Protocol Compatibility

For information on interoperability between this WebLogic Server release and previous WebLogic Server releases, see WebLogic Server Compatibility in Information Roadmap for Oracle WebLogic Server . 5-6 Programming Stand-alone Clients for Oracle WebLogic Server 6 WebLogic JMS Thin Client 6-1 6 WebLogic JMS Thin Client The following sections describe how to deploy and use the WebLogic JMS thin client: ■ Section 6.1, Overview of the JMS Thin Client ■ Section 6.2, JMS Thin Client Functionality ■ Section 6.3, Limitations of Using the JMS Thin Client ■ Section 6.4, Deploying the JMS Thin Client

6.1 Overview of the JMS Thin Client

The JMS thin client the wljmsclient.jar deployed with the wlclient.jar, provides Java EE and WebLogic JMS functionality using a much smaller client footprint than a WebLogic Install or Full client, and a somewhat smaller client footprint than a Thin T3 client. The smaller footprint is obtained by using: ■ A client-side library that contains only the set of supporting files required by client-side programs. ■ The RMI-IIOP protocol stack available in the JRE. RMI requests are handled by the JRE, enabling a significantly smaller client. ■ Standard Java EE APIs, rather than WebLogic Server APIs. For more information on developing WebLogic Server thin client applications, see Section 5, Developing a Thin Client.

6.2 JMS Thin Client Functionality

Although much smaller in size than a WebLogic Full client or WebLogic Install, the JMS thin client the wljmsclient.jar and wlclient.jar provides the following functionality to client applications and applets: ■ Full WebLogic JMS functionality—both standard JMS and WebLogic extensions—except for client-side XML selection for multicast sessions and the JMSHelper class methods ■ EJB Enterprise Java Bean access ■ JNDI access ■ RMI access indirectly used by JMS ■ SSL access using JSSE in the JRE ■ Transaction capability 6-2 Programming Stand-alone Clients for Oracle WebLogic Server ■ Clustering capability ■ HTTPHTTPS tunneling ■ Fully internationalized

6.3 Limitations of Using the JMS Thin Client