4
JNDI Connections and Session IIOP Service

This chapter describes in detail how clients connect to an Oracle8i server session and how they authenticate themselves to the server. The term client, as used in this chapter, includes client applications and applets running on a network PC or a workstation, as well as distributed objects such as EJBs and CORBA server objects that are calling other distributed server objects and, thus, acting as clients to these objects.

In order to execute CORBA objects, you must first publish these objects in a Oracle8i database instance, using a CORBA CosNaming service. Then, you can retrieve the object reference either through a URL-based JNDI interface to CosNaming or straight to the CosNaming service. JNDI is recommended as it is easy for clients written in Java to locate and activate published objects.

In addition to authentication, this chapter discusses security of access control to objects in the database. A published object in the data server has a set of permissions that determine who can access and modify the object. In addition, classes that are loaded in the data server are loaded into a particular schema, and the person who deploys the classes can control who can use them.

This chapter covers the following topics:

• JNDI Connection Basics

• The Name Space

• Execution Rights to Database Objects

• URL Syntax

• Using JNDI to Access Bound Objects

• Session IIOP Service

• Retrieving JServer Version Number

• Activating In-Session CORBA Objects From Non-IIOP Presentations

• Accessing CORBA Objects Without JNDI

---