In the context of this document, a stand-alone client is a client that has a runtime environment independent of WebLogic Server. (Managed clients, such as Web Services, rely on a server-side container to provide the runtime necessary to access a server.) Stand-alone clients that access WebLogic Server applications range from simple command line utilities that use standard I/O to highly interactive GUI applications built using the Java Swing/AWT classes. The following sections provide an overview:
IIOP can be a transport protocol for distributed applications with interfaces written in Java RMI. For more information, see:
For more information, see “ Using RMI over IIOP” in Programming WebLogic RMI.
A T3 client is a Java RMI client that uses BEA’s proprietary T3 protocol to communicate with WebLogic Server. See:
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 following CORBA client models:
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.
A stand-alone WebServices client uses WebLogic client classes to invoke a Web Service hosted on WebLogic Server or on other application servers. See Invoking a Web Service from a Stand-alone Client in Programming Web Services for WebLogic Server.
The following table lists the types of clients supported in a WebLogic Server environment, and their characteristics, features, and limitations.
Note: | In this release, client applications should use the wlfullclient.jar file to provide the WebLogic Server specific functionary previously provided in the weblogic.jar file. You can generate the wlfullclient.jar file for client applications using the JarBuilder tool. See Using the WebLogic JarBuilder Tool
. |
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
|||||
|
For WebLogic Server 10.0 and higher releases, client applications need to use the wlfullclient.jar
file to provide the WebLogic Server specific functionary previously provided in the weblogic.jar
file. You can generate the wlfullclient.jar
file for client applications using the JarBuilder tool. See Using the WebLogic JarBuilder Tool.