Using JNDI and IIOP

You publish CORBA objects in the Oracle database using the OMG CosNaming service. In addition, you can access these objects using Oracle's JNDI interface to CosNaming.

Figure 1-1 shows, in a schematic way, how applications access remote objects published in the database using JNDI.

Figure 1-1 Remote Object Access

IIOP

Oracle8i offers a Java interpreter for the IIOP protocol. Oracle embeds a pure Java ORB of a major CORBA vendor (VisiBroker for Java version 3.4 by Inprise) and repackaging the Visigenic Java IIOP interpreter to run in the database.

Because Oracle8i is a highly scalable server, only the essential components of the interpreter are necessary--namely, a set of Java classes that do the following:

• decode the IIOP protocol

• find or activate the relevant Java object

• invoke the method the IIOP message specifies

• write the IIOP reply back to the client

Oracle8i does not use the ORB scheduling facilities. The Oracle multi-threaded server performs the dispatching, enabling the server to process IIOP messages efficiently and in a highly scalable manner.

On top of this infrastructure, Oracle8i implements the EJB and CORBA programming models.

---