CORBA Clients JMX Clients JMS Clients

Overview of Stand-alone Clients 2-3

2.4 CORBA Clients

If you are not working in a Java-only environment, you can use IIOP to connect your Java programs with Common Object Request Broker Architecture CORBA clients and execute CORBA objects. IIOP can be a transport protocol for distributed applications with interfaces written in Interface Definition Language IDL or Java RMI. However, the two models are distinctly different approaches to creating an interoperable environment between heterogeneous systems. When you program, you must decide to use either IDL or RMI interfaces; you cannot mix them. WebLogic Server supports the CORBA client models described in the following chapters: ■ Chapter 10, Developing a CORBAIDL Client ■ Chapter 11, Developing Clients for CORBA Objects ■ Chapter 12, Developing a WebLogic C++ Client for a Tuxedo ORB

2.5 JMX Clients

You can use a JMX client to access WebLogic Server MBeans. See Accessing WebLogic Server MBeans With JMX in Developing Custom Management Utilities With JMX for Oracle WebLogic Server.

2.6 JMS Clients

WebLogic Server provides a number of JMS clients that provide Java EE and WebLogic JMS functionality. See the topics listed in Table 2–1 : Table 2–1 JMS Client Types that Provide Java EE and WebLogic JMS Functionality Client For more information, see . . . WebLogic Thin T3 client Chapter 3, Developing a WebLogic Thin T3 Client WebLogic Full client Chapter 4, Developing a WebLogic Full Client WebLogic Install client Section 2.2.3, WebLogic Install Client JMS thin client Chapter 6, WebLogic JMS Thin Client JMS SAF client Chapter 7, Reliably Sending Messages Using the JMS SAF Client JMS C client WebLogic JMS C API in Programming JMS for Oracle WebLogic Server JMS .NET client Using the WebLogic JMS Client for Microsoft .NET for Oracle WebLogic Server WebLogic AQ JMS client Stand-alone WebLogic AQ JMS Clients in Configuring and Managing JMS for Oracle WebLogic Server . The WebLogic AQ JMS client obtains destination information using WebLogic Server JNDI and provides direct access to Oracle data base AQ JMS destinations using an embedded driver. It does not provide access to WebLogic Server JMS destinations. Tip: Oracle recommends using an efficient T3 protocol capable Java client -- either the Install, Full, and Thin T3. The Thin java client uses the slower IIOP protocol and is only recommended when the Thin T3 client is considered to be too large for your use case. 2-4 Programming Stand-alone Clients for Oracle WebLogic Server

2.7 Web Services Clients