bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Programming WebLogic RMI over IIOP

RMI over IIOP Programming Models

The following sections describe how to use various programming models to develop RMI-IIOP applications:

- Overview of RMI-IIOP Programming Models

- RMI-IIOP Applications with RMI (Java) Clients

- RMI-IIOP Applications with CORBA/IDL Clients

- Developing a WebLogic C++ Client for the Tuxedo 8.1 ORB

- RMI-IIOP Applications Using WebLogic Tuxedo Connector

- Using EJBs with RMI-IIOP

- Code Examples

- RMI-IIOP and the RMI Object Lifecycle

Overview of RMI-IIOP Programming Models

IIOP is a robust protocol that is supported by numerous vendors and is designed to facilitate interoperation between heterogeneous distributed systems. Two basic programming models are associated with RMI-IIOP: RMI-IIOP with RMI clients and RMI-IIOP with IDL clients. Both models share certain features and concepts, including the use of a Object Request Broker (ORB) and the Internet InterORB Protocol (IIOP). However, the two models are distinctly different approaches to creating a interoperable environment between heterogeneous systems. Simply, IIOP can be a transport protocol for distributed applications with interfaces written in either IDL or Java RMI. When you program, you must decide to use either IDL or RMI interfaces; you cannot mix them.

Several factors determine how you will create a distributed application environment. Because the different models for employing RMI-IIOP share many features and standards, it is easy to lose sight of which model you are following. The following table summarizes the components and benefits of each model, we have included the simple RMI model which does not use IIOP to further illustrate the differences between the programming models available.

Table 2-1 RMI Programming Models

Client | Client language | Protocol | Definition | Benefits
--- | --- | --- | --- | ---
RMI | Java | t3 | Client that follows the JavaSoft RMI specification. Designed exclusively for Java programs. | Fast, scalable. Uses optimized WebLogic t3 protocol that improves performance.
RMI over IIOP RMI Client | Java | IIOP | RMI client that utilizes the CORBA 2.3 specification's support for Objects-by-Value. This Java client is developed using the standard RMI/JNDI model. | RMI with Internet-Inter-Orb-Protocol. Use of the IIOP standard. No WebLogic classes required on client.
RMI over IIOP WebLogic RMI Client | Java | IIOP | RMI client that utilizes the CORBA 2.3 specification's support for Objects-by-Value. This Java client is developed using the standard RMI/JNDI model. | RMI with Internet-Inter-Orb-Protocol. Use of the IIOP standard. Fully clusterable, but requires that weblogic.jar be referenced by the client.
RMI-IIOP CORBA/ IDL client | C++, C, Smalltalk, COBOL (Any language that OMG IDL can map to). | IIOP | CORBA client that uses a CORBA 2.3 ORB. Note: Due to name-space conflicts, Java CORBA clients are not supported by the RMI over IIOP specification. | Interoperability between WebLogic Server and clients written in C++, COBOL, etc.
RMI-IIOP Tuxedo Client | C++, C, COBOL, Java (any language to which Tuxedo can map to OMG IDL) | TGIOP (Tuxedo-General-Inter-Orb-Protocol | Tuxedo Client developed with Tuxedo 8.0 Rolling Patch 15 or higher. | Interoperability between WebLogic Server applications and Tuxedo clients/services

RMI Applications Without IIOP

RMI is a Java-to-Java model of distributed computing. RMI enables an application to obtain a reference to an object that exists elsewhere in the network All RMI-IIOP models are based on RMI; however, if you follow a plain RMI model without IIOP, you cannot integrate clients written in languages other than Java. You will also be using T3, a proprietary protocol, and have WebLogic classes on your client. For information on developing RMI applications, seeUsing WebLogic RMI

RMI-IIOP Applications with RMI (Java) Clients

RMI over IIOP with RMI clients combines the features of RMI with the standard IIOP protocol and allows you to work completely in the Java programming language. RMI-IIOP with RMI Clients is a Java-to-Java model, where the ORB is typically a part of the JDK running on the client. Objects can be passed both by reference and by value with RMI-IIOP.

When to Use RMI-IIOP with RMI (Java) Clients

RMI-IIOP with RMI clients is oriented towards the J2EE programming model; it combines the capabilities of RMI with the IIOP protocol. If your applications are being developed in Java and you wish to leverage the benefits of IIOP, you should use the RMI-IIOP with RMI client model. Using RMI-IIOP, Java users can program with the RMI interfaces and then use IIOP as the underlying transport mechanism. The RMI client runs an RMI-IIOP-enabled ORB hosted by a J2EE or J2SE container, in most cases a 1.3 or higher JDK. Note that no WebLogic specific classes are required, or automatically downloaded in this scenario; this is a good way of having a minimal client distribution. You also do not have to use the proprietary t3 protocol used in normal WebLogic RMI, you use IIOP, which based on an industry, not proprietary, standard.

Developing an RMI-IIOP Application with RMI Client

To develop an application using RMI-IIOP with an RMI client:

1. Define your remote object's public methods in an interface that extends java.rmi.Remote.

   This remote interface may not require much code. All you need are the method signatures for methods you want to implement in remote classes. For example, with the Ping example included in your Weblogic installation SAMPLES_HOME/server/src/examples/iiop/rmi/server/wls:

   >     public interface Pinger extends java.rmi.Remote {
   >     public void ping() throws java.rmi.RemoteException;
   >     public void pingRemote() throws java.rmi.RemoteException;
   >     public void pingCallback(Pinger toPing) throws java.rmi.RemoteException;
   >     }

2. Implement the interface in a class named interfaceNameImpl and bind it into the JNDI tree to be made available to clients.

   This class should implement the remote interface that you wrote, which means that you implement the method signatures that are contained in the interface. All the code generation that will take place is dependent on this class file. Typically, you configure your implementation class as a WebLogic startup class and include a main method that binds the object into the JNDI tree. Here is an excerpt from the implementation class developed from the previous Ping example:

   >     public static void main(String args[]) throws Exception {
   >       if (args.length > 0)
   >       remoteDomain = args[0];

   >       Pinger obj = new PingImpl();
   >       Context initialNamingContext = new InitialContext();
   >       initialNamingContext.rebind(NAME,obj);
   >       System.out.println("PingImpl created and bound to "+ NAME);

3. Compile the remote interface and implementation class with a java compiler. Developing these classes in a RMI-IIOP application is no different that doing so in normal RMI. For more information on developing RMI objects, see Using WebLogic RMI.

4. Run the WebLogic RMI or EJB compiler against the implementation class to generate the necessary IIOP stub. Note that it is no longer necessary to use the -iiop option to generate the IIOP stubs:

   >     $ java weblogic.rmic nameOfImplementationClass

   In the case of the Pinger example, the nameOfImplementationClass is examples.iiop.rmi.server.wls.PingerImpl.

   A stub is the client-side proxy for a remote object that forwards each WebLogic RMI call to its matching server-side skeleton, which in turn forwards the call to the actual remote object implementation. Note that the IIOP stubs created by the WebLogic RMI compiler are intended to be used with the JDK 1.3.1_01 or higher ORB. If you are using another ORB, consult the ORB vendor's documentation to determine whether these stubs are appropriate.

5. Make sure that the files you have now created -- the remote interface, the class that implements it, and the stub -- are in the CLASSPATH of the WebLogic Server.

6. Obtain an initial context.

   RMI clients access remote objects by creating an initial context and performing a lookup (see next step) on the object. The object is then cast to the appropriate type.

   In obtaining an initial context, you have two choices when defining your JNDI context factory:

   - weblogic.jndi.WLInitialContextFactory

   - com.sun.jndi.cosnaming.CNCtxFactory

   Use either of these classes when setting the value for the "Context.INITIAL_CONTEXT_FACTORY" property that you supply as a parameter to new InitialContext(). If you use the Sun version, you'll have a Sun JNDI client, which in turn uses the Sun RMI-IIOP ORB implementation of J2SE 1.3; this may be important to you if you wish to minimize the use of WebLogic classes on the client. To take full advantage of WebLogic's RMI-IIOP implementation however, it is recommended that you use the weblogic.jndi.WLInitialContextFactory method.

   When using the Sun JNDI client and the Sun ORB, be aware that the Sun JNDI client supports the capability to read remote object references from the namespace, but not generic Java serialized objects. This means that you can read items such as EJBHomes out of the namespace but not DataSource objects. There is also no support for client-initiated transactions (the JTA API) in this configuration, and no support for security. In the stateless session bean RMI Client example, the client obtains an initial context as is done below:

   >     Obtaining an InitialContext:

   >     * Using a Properties object as follows will work on JDK13
   >     * clients.

   >        */

   >       private Context getInitialContext() throws NamingException {

   >     try {
   >       // Get an InitialContext
   >       Properties h = new Properties();
   >       h.put(Context.INITIAL_CONTEXT_FACTORY,
   >        "com.sun.jndi.cosnaming.CNCtxFactory");
   >       h.put(Context.PROVIDER_URL, url);
   >       return new InitialContext(h);
   >     } catch (NamingException ne) {
   >       log("We were unable to get a connection to the WebLogic server at   "+url);
   >       log("Please make sure that the server is running.");
   >       throw ne;
   >       }

   >     /**

   >     * This is another option, using the Java2 version to get an * InitialContext.
   >     * This version relies on the existence of a jndi.properties file in
   >     * the application's classpath. See * http://edocs.bea.com/wls/docs70/jndi/jndi.html for more * information

   >     private static Context getInitialContext()
   >       throws NamingException

   >     {
   >       return new InitialContext();
   >     }

7. Modify the client code to perform the lookup in conjunction with the javax.rmi.PortableRemoteObject.narrow() method.

   RMI over IIOP RMI clients differ from regular RMI clients in that IIOP is defined as the protocol when obtaining an initial context. Because of this, lookups and casts must be performed in conjunction with the javax.rmi.PortableRemoteObject.narrow() method.

   For example, in the RMI client stateless session bean example (the examples.iiop.ejb.stateless.rmiclient package included in your distribution), an RMI client creates an initial context, performs a lookup on the EJBean home, obtains a reference to an EJBean, and calls methods on the EJBean.

   You must use the javax.rmi.PortableRemoteObject.narrow() method in any situation where you would normally cast an object to a specific class type. A CORBA client may return an object that doesn't implement your remote interface; the narrow method is provided by your orb to convert the object so that it implements your remote interface. For example, the client code responsible for looking up the EJBean home and casting the result to the Home object must be modified to use the javax.rmi.PortableRemoteObject.narrow() as shown below:

   >     Performing a lookup:

   >     /**
   >      * RMI/IIOP clients should use this narrow function
   >      */
   >     private Object narrow(Object ref, Class c) {
   >       return PortableRemoteObject.narrow(ref, c);
   >     }

   >     /**
   >      * Lookup the EJBs home in the JNDI tree
   >      */
   >     private TraderHome lookupHome()
   >       throws NamingException
   >     {
   >       // Lookup the beans home using JNDI
   >       Context ctx = getInitialContext();

   >       try {
   >     Object home = ctx.lookup(JNDI_NAME);
   >     return (TraderHome) narrow(home, TraderHome.class);
   >     } 	catch (NamingException ne) {
   >     log("The client was unable to lookup the EJBHome.  Please
   >     make sure ");
   >     log("that you have deployed the ejb with the JNDI name
   >     "+JNDI_NAME+" on the WebLogic server at "+url);
   >     throw ne;
   >       }
   >     }

   >     /**
   >      * Using a Properties object will work on JDK130
   >      * clients
   >      */
   >     private Context getInitialContext() throws NamingException {

   >       try {
   >     // Get an InitialContext
   >     Properties h = new Properties();
   >     h.put(Context.INITIAL_CONTEXT_FACTORY,
   >     "com.sun.jndi.cosnaming.CNCtxFactory");
   >     h.put(Context.PROVIDER_URL, url);
   >     return new InitialContext(h);
   >       } 	catch (NamingException ne) {
   >     log("We were unable to get a connection to the WebLogic
   >     server at "+url);
   >     log("Please make sure that the server is running.");
   >     throw ne;
   >       }
   >     }

   The url defines the protocol, hostname, and listen port for the WebLogic Server and is passed in as a command-line argument.

   >     public static void main(String[] args) throws Exception {

   >       log("\nBeginning statelessSession.Client...\n");

   >       String url       = "iiop://localhost:7001";

8. Connect the client to the server over IIOP by running the client with a command like:

   >     $ java -Djava.security.manager -Djava.security.policy=java.policy    examples.iiop.ejb.stateless.rmiclient.Client iiop://localhost:7001

9. Set the security manager on the client:

   >     java -Djava.security.manager -Djava.security.policy==java.policy myclient

   To narrow an RMI interface on a client the server needs to serve the appropriate stub for that interface. The loading of this class is predicated on the use of the JDK network classloader and this is not enabled by default. To enable it you set a security manager in the client with an appropriate java policy file. For more information on Java security, see Sun's site at http://java.sun.com/security/index.html. The following is an example of a java.policy file:

   grant {

   // Allow everything for now

   permission java.security.AllPermission;

RMI-IIOP Applications with WebLogic's RMI-IIOP RMI Client

WebLogic Server 7.0 enables the use of a new "fat" RMI-IIOP RMI Client that can be used to develop fully clusterable RMI-IIOP applications. To use this new WebLogic RMI-IIOP RMI Client, you need to have the weblogic.jar (located in WL_HOME/server/lib) on the client side's CLASSPATH, and use the -D weblogic.system.iiop.enableClient=true command line option when starting WebLogic. Otherwise, your steps in developing this client will be the same as above in RMI-IIOP Applications with RMI (Java) Clients.

RMI-IIOP Applications with CORBA/IDL Clients

RMI over IIOP with CORBA/IDL clients involves an Object Request Broker (ORB) and a compiler that creates an interoperating language called IDL. C, C++, and COBOL are examples of languages that ORB's may compile into IDL. A CORBA programmer can use the interfaces of the CORBA Interface Definition Language (IDL) to enable CORBA objects to be defined, implemented, and accessed from the Java programming language.

Using RMI-IIOP with a CORBA/IDL client enables interoperability between non-Java clients and Java objects. If you have existing CORBA applications, you should program according to the RMI-IIOP with CORBA/IDL client model. Basically, you will be generating IDL interfaces from Java. Your client code will communicate with WebLogic Server through these IDL interfaces. This is basic CORBA programming.

The following sections provide some guidelines for developing RMI-IIOP applications with CORBA/IDL clients.

For further reference see the following Object Management Group (OMG) specifications:

- Java Language Mapping to OMG IDL Specification

- CORBA/IIOP 2.4.2 Specification

Working with CORBA/IDL Clients

In CORBA, interfaces to remote objects are described in a platform-neutral interface definition language (IDL). To map the IDL to a specific language, the IDL is compiled with an IDL compiler. The IDL compiler generates a number of classes such as stubs and skeletons that the client and server use to obtain references to remote objects, forward requests, and marshall incoming calls. Even with IDL clients it is strongly recommended that you begin programming with the Java remote interface and implementation class, then generate the IDL to allow interoperability with WebLogic and CORBA clients, as illustrated in the following sections. Writing code in IDL that can be then reverse-mapped to create Java code is a difficult and bug-filled enterprise and WebLogic does not recommend doing this.

The following figure shows how IDL takes part in a RMI-IIOP model:

Figure 2-1 IDL Client (Corba object) relationships

Java to IDL Mapping

In WebLogic RMI, interfaces to remote objects are described in a Java remote interface that extends java.rmi.Remote. The Java-to-IDL mapping specification defines how an IDL is derived from a Java remote interface. In the WebLogic RMI over IIOP implementation, you run the implementation class through the WebLogic RMI compiler or WebLogic EJB compiler with the -idl option. This process creates an IDL equivalent of the remote interface. You then compile the IDL with an IDL compiler to generate the classes required by the CORBA client.

The client obtains a reference to the remote object and forwards method calls through the stub. WebLogic Server implements a CosNaming service that parses incoming IIOP requests and dispatches them directly into the RMI runtime environment.

The following figure shows this process.

Figure 2-2 WebLogic RMI over IIOP object relationships

Objects-by-Value

The Objects-by-Value specification allows complex data types to be passed between the two programming languages involved. In order for an IDL client to support Objects-by-Value, you develop the client in conjunction with an Object Request Broker (ORB) that supports Objects-by-Value. To date, relatively few ORBs support Objects-by-Value correctly.

When developing an RMI over IIOP application that uses IDL, consider whether your IDL clients will support Objects-by-Value, and design your RMI interface accordingly. If your client ORB does not support Objects-by-Value, you must limit your RMI interface to pass only other interfaces or CORBA primitive data types. The following table lists ORBs that BEA Systems has tested with respect to Objects-by-Value support:

Table 2-2 ORBs Tested with Respect to Objects-by-Value Support

Vendor | Versions | Objects-by-Value
--- | --- | ---
BEA | Tuxedo 8.1 C++ Client ORB | supported
Borland | VisiBroker 3.3, 3.4 | not supported
Borland | VisiBroker 4.x, 5.x | supported
Iona | Orbix 2000 | supported (we have encountered issues with this implementation)

For more information on Objects-by-Value, see Limitations of Passing Objects by Value

Developing an RMI-IIOP Application with a CORBA/IDL Client

To develop an RMI over IIOP application with CORBA/IDL:

1. Follow steps 1 through 3 in Developing an RMI-IIOP Application with RMI Client.

2. Generate an IDL file by running the WebLogic RMI compiler or WebLogic EJB compiler with the -idl option.

   The required stub classes will be generated when you compile the IDL file. For general information on the these compilers, refer to Using WebLogic RMI and BEA WebLogic Server Enterprise JavaBeans. Also reference the Java IDL specification at Java Language Mapping to OMG IDL Specification.

   The following compiler options are specific to RMI over IIOP:

   Option | Function
   --- | ---
   -idl | Creates an IDL for the remote interface of the implementation class being compiled
   -idlDirectory | Target directory where the IDL will be generated
   -idlFactories | Generate factory methods for value types. This is useful if your client ORB does not support the factory valuetype.
   -idlNoValueTypes | Suppresses generation of IDL for value types.
   -idlOverwrite | Causes the compiler to overwrite an existing idl file of the same name
   -idlStrict | Creates an IDL that adheres strictly to the Objects-By-Value specification. (not available with ejbc)
   -idlVerbose | Display verbose information for IDL generation
   -idlVisibroker | Generate IDL somewhat compatible with Visibroker 4.1 C++

   The options are applied as shown in this example of running the RMI compiler:

   > java weblogic.rmic -idl -idlDirectory /IDL rmi_iiop.HelloImpl

   The compiler generates the IDL file within sub-directories of the idlDirectoy according to the package of the implementation class. For example, the preceding command generates a Hello.idl file in the /IDL/rmi_iiop directory. If the idlDirectory option is not used, the IDL file is generated relative to the location of the generated stub and skeleton classes.

3. Compile the IDL file to create the stub classes required by your IDL client to communicate with the remote class. Your ORB vendor will provide an IDL compiler.

   The IDL file generated by the WebLogic compilers contains the directives: #include orb.idl. This IDL file should be provided by your ORB vendor. An orb.idl file is shipped in the /lib directory of the WebLogic distribution. This file is only intended for use with the ORB included in the JDK that comes with WebLogic Server.

4. Develop the IDL client.

   IDL clients are pure CORBA clients and do not require any WebLogic classes. Depending on your ORB vendor, additional classes may be generated to help resolve, narrow, and obtain a reference to the remote class. In the following example of a client developed against a VisiBroker 4.1 ORB, the client initializes a naming context, obtains a reference to the remote object, and calls a method on the remote object.

   Code segment from C++ client of the RMI-IIOP example

   >     // string to object
   >     CORBA::Object_ptr o;

   >     cout << "Getting name service reference" << endl;
   >     if (argc >= 2 && strncmp (argv[1], "IOR", 3) == 0)
   >       o = orb->string_to_object(argv[1]);
   >     else
   >       o = orb->resolve_initial_references("NameService");

   >     // obtain a naming context
   >     cout << "Narrowing to a naming context" << endl;
   >     CosNaming::NamingContext_var context = CosNaming::NamingContext::_narrow(o);
   >     CosNaming::Name name;
   >     name.length(1);
   >     name[0].id = CORBA::string_dup("Pinger_iiop");
   >     name[0].kind = CORBA::string_dup("");

   >     // resolve and narrow to RMI object
   >     cout << "Resolving the naming context" << endl;
   >     CORBA::Object_var object = context->resolve(name);

   >     cout << "Narrowing to the Ping Server" << endl;
   >     ::examples::iiop::rmi::server::wls::Pinger_var ping =
   >       ::examples::iiop::rmi::server::wls::Pinger::_narrow(object);

   >     // ping it
   >     cout << "Ping (local) ..." << endl;
   >     ping->ping();

   }

   Notice that before obtaining a naming context, initial references were resolved using the standard Object URL (CORBA/IIOP 2.4.2 Specification, section 13.6.7). Lookups are resolved on the server by a wrapper around JNDI that implements the COS Naming Service API.

   The Naming Service allows Weblogic Server applications to advertise object references using logical names. The CORBA Name Service provides:

   - An implementation of the Object Management Group (OMG) Interoperable Name Service (INS) specification.

   - Application programming interfaces (APIs) for mapping object references into an hierarchical naming structure (JNDI in this case).

   - Commands for displaying bindings and for binding and unbinding naming context objects and application objects into the namespace.

5. IDL client applications can locate an object by asking the CORBA Name Service to look up the name in the JNDI tree of WebLogic Server. In the example above, you run the client by using:

   Client.exe -ORBInitRef NameService=iioploc://localhost:7001/NameService.

Developing a WebLogic C++ Client for the Tuxedo 8.1 ORB

The WebLogic C++ client uses the Tuxedo 8.1 C++ Client ORB to generate IIOP request for EJBs running on WebLogic Server. This client supports object-by-value and the CORBA Interoperable Naming Service (INS).

When to Use a WebLogic C++ Client

You should consider using a WebLogic C++ client in the following situations:

- To simplify your development process by avoiding third-party products

- To provide a client-side solution that allows you to develop or modify existing C++ clients

Although the Tuxedo C++ Client ORB is packaged with Tuxedo 8.1 and higher, you do not need a Tuxedo license to develop WebLogic C++ clients. You can obtain a trial development copy of Tuxedo from the BEA Download Center.

How the WebLogic C++ Client works

The WebLogic C++ client using the following model to process client requests:

- The WebLogic C++ client code requests a WebLogic Server service.

  - The Tuxedo ORB generates an IIOP request.

  - The ORB object is initally instantiated and supports Object-by-Value data types.

- The Client uses the CORBA Interoperable Name Service (INS) to look up the EJB object bound to JNDI naming service. For more information on how to use the Interoperable Naming Service to get object references to initial objects such as NameService, see Interoperable Naming Service Bootstrapping Mechanism.

  Figure 2-3 WebLogic C++ Client to WebLogic Server Interoperability

Developing WebLogic C++ Clients

Use the following steps to develop a C++ client:

1. Use the ejbc compiler with the -idl option to compile the EJB that your C++ client will interoperate with. This will generate an IDL script for the EJB.

2. Use the C++ IDL compiler to compile the IDL script and generate the CORBA client stubs, server skeletons, and header files. For information on the use of the C++ IDL Compiler, see OMG IDL Syntax and the C++ IDL Compiler.

3. Discard the server skeletons as the EJB represents the server side implementation.

4. Create a C++ client that implements an EJB as a CORBA object. For general information on how to create Corba client applications, see Creating CORBA Client Applications.

5. Use the Tuxedo buildobjclient command to build the client.

WebLogic C++ Client Limitations

The WebLogic C++ client has the following limitations:

- Provides security through the WebLogic Server Security service.

- Provides only server-side transaction demarcation.

WebLogic C++ Client Code Samples

WebLogic C++ client samples are provided with the WebLogic Server product. The samples are located in the SAMPLES_HOME\server\examples\src\examples\iiop\ejb directory. A description of each sample and instructions on how to build, configure, and run a sample, are provided in the package-summary.html file. You can modify these code examples and reuse them.

RMI-IIOP Applications Using WebLogic Tuxedo Connector

WebLogic Tuxedo Connector provides interoperability between WebLogic Server applications and Tuxedo services.

When to Use WebLogic Tuxedo Connector

You should consider using WebLogic Tuxedo Connector if you have developed applications on Tuxedo and are moving to WebLogic Server, or if you are seeking to integrate legacy Tuxedo systems into your newer WebLogic environment. WebLogic Tuxedo Connector allows you to leverage Tuxedo's highly scalable and reliable CORBA environment.

How the WebLogic Tuxedo Connector Works

The connector uses an XML configuration file that allows you to configure the WebLogic Server to invoke Tuxedo services. It also enables Tuxedo to invoke WebLogic Server Enterprise Java Beans (EJBs) and other applications in response to a service request.

The following documentation provides information on the Weblogic Tuxedo Connector, as well as building CORBA applications on Tuxedo:

- The WebLogic Tuxedo Connector Guide

- For Tuxedo, CORBA topics

WebLogic Tuxedo Connector Code Samples

WebLogic Tuxedo Connector IIOP samples are provided with the WebLogic Server product. The samples are located in the SAMPLES_HOME\server\examples\src\examples\iiop\ejb directory . A description of each sample and instructions on how to build, configure, and run a sample, are provided in the package-summary.html file. You can modify these code examples and reuse them.

Using EJBs with RMI-IIOP

You can implement Enterprise JavaBeans that use RMI over IIOP to provide EJB interoperability in heterogeneous server environments:

- A Java RMI client using an ORB can access enterprise beans residing on a WebLogic Server over IIOP.

- A non-Java platform CORBA/IDL client can access any enterprise bean object on WebLogic Server.

When using CORBA/IDL clients the sources of the mapping information are the EJB classes as defined in the Java source files. WebLogic Server provides the weblogic.ejbc utility for generating required IDL files. These files represent the CORBA view into the state and behavior of the target EJB. Use the weblogic.ejbc utility to:

- Place the EJB classes, interfaces, and deployment descriptor files into a JAR file.

- Generate WebLogic Server container classes for the EJBs.

- Run each EJB container class through the RMI compiler to create stubs and skeletons.

- Generate a directory tree of CORBA IDL files describing the CORBA interface to these classes.

The weblogic.ejbc utility supports a number of command qualifiers. See Developing an RMI-IIOP Application with a CORBA/IDL Client.

Resulting files are processed using the compiler, reading source files from the idlSources directory and generating CORBA C++ stub and skeleton files. These generated files are sufficient for all CORBA data types with the exception of value types (see Limitations of WebLogic RMI-IIOP for more information). Generated IDL files are placed in the idlSources directory. The Java-to-IDL process is full of pitfalls. Refer to the Java Language Mapping to OMG IDL specification. Also, Sun has an excellent guide, Enterprise JavaBeansTM Components and CORBA Clients: A Developer Guide.

The following is an example of how to generate the IDL from a bean you have already created:

>     > java weblogic.ejbc -compiler javac -keepgenerated
>     -idl -idlDirectory idlSources
>     build\std_ejb_iiop.jar
>     %APPLICATIONS%\ejb_iiop.jar

After this step, compile the EJB interfaces and client application (the example here uses a CLIENT_CLASSES and APPLICATIONS target variable):

>     > javac -d %CLIENT_CLASSES% Trader.java TraderHome.java
>     TradeResult.java Client.java

Then run the IDL compiler against the IDL files built in the step where you used weblogic.ejbc, creating C++ source files:

>     >%IDL2CPP% idlSources\examples\rmi_iiop\ejb\Trader.idl
>     . . .
>     >%IDL2CPP% idlSources\javax\ejb\RemoveException.idl

Now you can compile your C++ client.

For an in-depth look of how EJB's can be used with RMI-IIOP see the WebLogic Server RMI-IIOP examples, located in your installation inside the SAMPLES_HOME/server/src/examples/iiop directory.

Code Examples

The examples.iiop package is included within the WL_HOME/samples/examples/iiop directory and demonstrates connectivity between numerous clients and applications. There are examples that demonstrate using EJBs with RMI-IIOP, connecting to C++ clients, and setting up interoperability with a Tuxedo Server. Refer to the example documentation for more details. For examples pertaining specifically to the Weblogic Tuxedo Connector, see the /wlserver7.0/samples/examples/wtc directory.

The following table provides information on the RMI-IIOP examples provided for WebLogic Server 7.0.

Figure 2-4 WebLogic Server 7.0 IIOP Examples

Example | ORB/Protocol | Requires
--- | --- | ---
iiop.ejb.entity.cppclient Example provides a C++ client which calls an entity session bean in WebLogic Server. | Borland Visibroker 4.1 Borland Visibroker 5.0 | For Borland Visibroker 4.1: Use GIOP 1.0 protocol. Users must add the DefaultGIOPMinorVersion attribute and set its value to "1" in the Server MBean of the config.xml file. For Borland Visibroker 5.0: Specify utf-16/iso-8859-1 as the default native codeset in the Server MBean of the config.xml file. For Borland Visibroker 5.0: Use GIOP 1.2. Use a full corbaloc url which includes the GIOP version such as Client -ORBInitRef NameService=corbaloc:iiop:1.2@localhost:7001/NameService.
iiop.ejb.entity.tuxclient Example provides a Tuxedo client which uses complex valuetypes to call an entity session bean in WebLogic Server. | BEA IIOP | Tuxedo 8.x. Does not require a Tuxedo license.
iiop.ejb.entity.server.wls Example demonstrates connectivity between a C++ client or a Tuxedo client and an entity bean. | Not Applicable |
iiop.ejb.stateless.cppclient Example provides a C++ CORBA client which calls a stateless session bean in WebLogic Server. The example also demonstrates how to make an outbound RMI-IIOP call to a Tuxedo server using WebLogic Tuxedo Connector. | Borland Visibroker 4.1 Borland Visibroker 5.0 | For Borland Visibroker 4.1: Use GIOP 1.0 protocol. Users must add the DefaultGIOPMinorVersion attribute and set its value to "1" in the Server MBean of the config.xml file. For Borland Visibroker 5.0: Specify utf-16/iso-8859-1 as the default native codeset in the Server MBean of the config.xml file. For Borland Visibroker 5.0: Use GIOP 1.2. Use a full corbaloc url which includes the GIOP version such as Client -ORBInitRef NameService=corbaloc:iiop:1.2@localhost:7001/NameService.
iiop.ejb.stateless.rmiclient Example provides an RMI Java client which calls a stateless session bean in WebLogic Server. The example also demonstrates how to make an outbound RMI-IIOP call to a Tuxedo server using WebLogic Tuxedo Connector. | JDK 1.3.1 | JDK 1.3.1 requires a security policy file to access server.
iiop.ejb.stateless.sectuxclient Example illustrates a secure Tuxedo client which calls a stateless session bean from WebLogic. | BEA IIOP | Tuxedo 8.x. Does not require a Tuxedo license.
iiop.ejb.stateless.server.tux Example illustrates how to call a stateless session bean from a variety of client applications through a Tuxedo Server. In conjunction with the Tuxedo Client, it also demonstrates server-to-server connectivity using WebLogic Tuxedo Connector. | Tuxedo TGIOP | Tuxedo 8.x Tuxedo license when used with WebLogic Tuxedo Connector. WebLogic Tuxedo Connector to provide server-to-server connectivity. See Using WebLogic Tuxedo Connector for RMI/IIOP and Corba Interoperability.
iiop.ejb.stateless.server.wls Example demonstrates using a variety of clients to call a stateless EJB directly in WebLogic Server or indirectly through a Tuxedo Server. | Not Applicable |
iiop.ejb.stateless.tuxclient Example provides a Tuxedo client which calls a stateless session bean directly in WebLogic Server or to call the same stateless session bean in WebLogic through a Tuxedo server. The example also demonstrates how to make an outbound RMI-IIOP call from a Tuxedo server to WebLogic Server using WebLogic Tuxedo Connector. | BEA IIOP | Tuxedo 8.x. Does not require a Tuxedo license.
iiop.rmi.cppclient Example contains a C++ client which calls either a Tuxedo Server or a WebLogic Server. It also demonstrates server-to-server connectivity using WebLogic Tuxedo Connector. | Borland Visibroker 4.1 Borland Visibroker 5.0 Orbix 2000 | For Borland Visibroker 4.1: Use GIOP 1.0 protocol. Users must add the DefaultGIOPMinorVersion attribute and set its value to "1" in the Server MBean of the config.xml file. For Borland Visibroker 5.0: Specify utf-16/iso-8859-1 as the default native codeset in the Server MBean of the config.xml file. For Borland Visibroker 5.0: Use GIOP 1.2. Use a full corbaloc url which includes the GIOP version such as Client -ORBInitRef NameService=corbaloc:iiop:1.2@localhost:7001/NameService.
iiop.rmi.rmiclient Example provides an RMI client which demonstrates connectivity to a WebLogic Server. The example also demonstrates how to make an outbound call from WebLogic Server to a Tuxedo server using WebLogic Tuxedo Connector. | Not Applicable | Requires a security policy file to access server.
iiop.rmi.server.tux Example illustrates connectivity from a variety of client applications through a Tuxedo Server. In conjunction with the Tuxedo Client, it also domesticates server-to-server connectivity using WebLogic Tuxedo Connector. | Tuxedo TGIOP | Tuxedo 8.x Tuxedo license when used with WebLogic Tuxedo Connector. WebLogic Tuxedo Connector to provide server-to-server connectivity. See Using WebLogic Tuxedo Connector for RMI/IIOP and Corba Interoperability.
iiop.rmi.server.wls Example illustrates connectivity between a variety of clients, Tuxedo, and WebLogic Server using a simple Ping application. | Not Applicable |
iiop.rmi.tuxclient Example provides a Tuxedo client which demonstrates connectivity to a Tuxedo Server. | BEA IIOP | Tuxedo 8.x. Does not require a Tuxedo license.

RMI-IIOP and the RMI Object Lifecycle

WebLogic Server's default garbage collection causes unused and unreferenced server objects to be garbage collected. This reduces the risk running out of memory due to a large number of unused objects. This policy can lead to NoSuchObjectException errors in RMI-IIOP if a client holds a reference to a remote object but does not invoke on that object for a period of approximately six (6) minutes. Such exceptions should not occur with EJBs, or typically with RMI objects that are referenced by the server instance, for instance via JNDI.

The J2SE specification for RMI-IIOP calls for the use of the exportObject() and unexportObject() methods on javax.rmi.PortableRemoteObject to manage the lifecycle of RMI objects under RMI-IIOP, rather than Distributed Garbage Collection (DGC). Note however that exportObject() and unexportObject() have no effect with WebLogic Server's default garbage collection policy. If you wish to change the default garbage collection policy, please contact BEA technical support.