Programming Stand-alone Clients
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
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 Developing T3 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 following CORBA client models:
The following table lists the types of clients supported in a WebLogic Server environment, and their characteristics, features, and limitations.
Table 2-1 WebLogic Server Client Types and Features
Languages that OMG IDL maps to, such as C++, C, Smalltalk, COBOL |
|||||
![]() ![]() |
![]() |
![]() |