WebLogic RMI over IIOP | BEA WebLogic Platform 7

A significant enhancement of WebLogic RMI is support for use over Internet Inter-ORB Protocol (IIOP) . This support exposes the RMI remote interface to CORBA clients . CORBA, which stands for Common Object Request Broker Architecture was developed by the Object Management Group (OMG) . Please refer to the http://www.omg.org web page for more information on CORBA. The CORBA clients and servers can be implemented in a variety of languages including C++ and Java. CORBA objects communicate using the IIOP. By providing the capability to run RMI over IIOP, CORBA clients written in C++ can invoke methods on Java remote objects. This enhancement to the WebLogic application server solves a number of business needs. WebLogic provides the platform to migrate from CORBA to J2EE, as well as allowing continued support for legacy clients written using CORBA. Recall that the underlying architecture of EJB is RMI. WebLogic RMI over IIOP therefore enables CORBA clients to use Enterprise Java Beans directly. This is accomplished through a Java-to-IDL mapping. The remote interface for CORBA is defined by a platform-neutral language called the Interface Definition Language (IDL) . The IDL is compiled into stubs and skeletons that are used by the client and server, respectively. As in RMI, the stubs and skeletons are responsible for marshaling the parameters and return values of the remote method calls. The Java-to-IDL mapping defines how the IDL is derived from an RMI remote interface. The WebLogic RMI compiler uses the -idl command-line option to produce an IDL equivalent of the remote interface. The resulting IDL is compiled with an IDL compiler to generate the classes used by the CORBA client. The WebLogic server implements a CosNaming service that parses IIOP requests and dispatches them into the RMI runtime.

The WebLogic implementation of RMI-IIOP now includes the following features, as well as numerous performance enhancements:

Support for Object-Transaction-Services 1.2 (OTS 1.2), which adds transactional support to RMI-IIOP. It can be used to invoke remote objects hosted in foreign application servers.
CSIv2 (Common Secure Interoperability, version 2) provides client authentication, delegation, and privilege functionality; it also works with foreign application servers.
A WebLogic IIOP client that is fully able to cluster. You simply use the following command-line parameter with weblogic.rmic to enable support for the WebLogic IIOP client:
```
 
```
```
 -Dweblogic.system.iiop.enableClient=true 
```
Hot code generation of IIOP stubs. You no longer need to use the -iiop flag with ejbc or rmic .
Support for the entire CosNaming API.