Tutorial eBooks PDF File Download

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. RMI Communication in WebLogic Server RMI communications in WebLogic Server use the T3 protocol to transport data between WebLogic Server and other Java programs, including clients and other WebLogic Server instances. A server instance keeps track of each Java Virtual Machine (JVM) with which it connects, and creates a single T3 connection to carry all traffic for a JVM. See “ Configure T3 protocol ” in Administration Console Online Help. For example, if a Java client accesses an enterprise bean and a JDBC connection pool on WebLogic Server, a single network connection is established between the WebLogic Server JVM and the client JVM. The EJB and JDBC services can be written as if they had sole use of a dedicated network connection because the T3 protocol invisibly multiplexes packets on the single connection.