11 Native Oracle JVM Support for JNDI

Namespace

The namespace is represented similarly as in the typical Unix File System structure. The root directory and the directory separator are represented by the slash symbol (/). The root directory is owned by SYS and only SYS can create new subdirectories under it.

The following two directories (DirContexts) are created during the installation process of OJDS:

• /public directory

  The /public directory is a public area for testing and any user can bind, delete, or lookup objects in this directory.

• /etc directory

  The /etc directory is an area for the deployment of all production type objects that a client may need and is protected from any update or removal. The /etc directory is writable only by the SYS user, but is readable by all users.

Oracle Java Directory Service JNDI Name Space Provider

This section describes the following Oracle Java Directory Service concepts:

• Directory Context

• StateFactories

• ObjectFactories

• OJDS URL Support

• Client classpath

import javax.naming.*;
.
.
.
Hashtable env = new Hashtable();
env.put(”java.naming.security.principal”,”HR”);
@ env.put(”java.naming.security.credentials”,”<password>”);
MyObj obj = (MyObj)(new InitialDirContext(env)).lookup(ojds://oci:host1:5521:mysid/one/two/myobj”);

Namespace Browser

The namespace browser enables browsing permissions and properties of objects stored in the OJDS. The existing ojvmjava utility is enhanced to support the operations as described in the following table:

ls Command

The ls command displays the contents of a context.

Syntax

ls [options] [context1] [context2] [obj|context]...

Options

The following table describes the ls command options:

Example

The following command displays contents of the root Context in short format:

$ ls /

etc/      public/

The following command displays contents of the root Context in long format:

$ ls -l
Read      Write    Exec        Owner    Date       Time      Type       Name
PUBLIC    SYS      PUBLIC      SYS      Dec 14     14:59     Context    etc
PUBLIC    PUBLIC   PUBLIC      SYS      Dec 14     14:59     Context    public

cd Command

The cd command changes the working context. This command is similar to the Unix cd command to change directories.

Example

The following command changes the context to root Context

$ cd /

pwd Command

The pwd command lists the current working context.

Example

If the current context is /test/alpha, then the output of the pwd command is the following:

$ pwd

/test/alpha/

chown Command

The chown command changes the ownership of the context or the object.

Syntax

chown [options] {user | role} <object name>

Options

The following table describes the chown command options:

Example

The following command makes HR the owner of the /alpha/beta/gamma command:

$ chown HR /alpha/beta/gamma

mkdir Command

The mkdir command creates a context with the given name.

Options

The following table describes the mkdir command options:

Example

The following command creates a Context called /test/alpha, where the /test context exists already:

mkdir /test/alpha

The following command creates a Context called /test/alpha/beta/gamma, where the /test/alpha/beta context does not exist:

$ mkdir -path /test/alpha/beta/gamma

rm Command

The rm command is analogous to the rm UNIX shell command. This command removes an object or a context, including its contents.

Options

The following table describes the rm command options:

Examples

The following command removes the object /test/bank:

rm /test/bank

The following command removes the context /test/release3 and its contents:

rm -r /test/release3

ln Command

The ln command is analogous to the UNIX ln command. A link is a synonym for a context or an object. When you move a context or an object, the reference to the context or object may become invalid. The ln command creates a link with the old name and makes the object accessible by both the old and the new name.

Syntax

ln [-symbolic | -s] <object> <link>

Options

The following table describes the ln command options:

Example

The following command preserves access to the old object even after the name of the object is changed to new:

$ mv old new
$ ln new old

mv Command

The mv command changes the name (or rebinds old names) of a context or an object to a new name.

Syntax

mv <old> <new>

Example

The following command changes the name of the context /test/foo to /test/bar:

$ mv /test/foo /test/bar

chmod Command

The chmod command is analogous to the chmod UNIX shell command. This command changes the rights of a user or a role on a context or an object.

Syntax

chmod [options] {+|-} {r|w|x} {<user> | <role>, ...} <objectname>

Options

The following table describes the chmod command options:

Example

The following example changes rights for the /alpha/beta/gamma context to HR and NANCY:

$ chmod +x HR,NANCY /alpha/beta/gamma

The following example removes the Write rights of HR for the /alpha/beta/gamma context:

$ chmod -w HR /alpha/beta/gamma

bind Command

The bind command binds an object reference or context into the JNDI namespace.

Syntax

bind <objectname> [options] [-context] [-rebind] {-class | -c <classname>} [-factory | -f <factory>] [-location | -l <URL>][-string <type_name>

<string_value> [-string <type_name> <string_value> ...]] [-binary <type_name> <string_value> [-binary <type_name> <string_value> ...]]

Options

The following table describes the bind command options:

Example

The following binds an object reference into the name space. A string and binary attribute is supplied to the reference.

bind /tmp/myprinter  -class gen.Inkjet  -factory gen.InkjetFactory  -string PRINTERNAME co2  -binary DPI  0X12C

bindds Command

This command binds a DataSource object in the JNDI namespace. This command binds general, XA, or pooled data sources depending on specified options.

Syntax

bindds <object_name> [options] [-help | -h] [-describe | -d] [-version | -v] [-dstype <datasource>]

[-host <hostname> -port <portnum> -sid <SID> -driver <driver_type>] [-url <db_url>]

[-g | -grant {<user> | <role>} [,{<user> | <role>}]...] [-recursiveGrant | -rg {<user> |<role>}

[,{<user> | <role>}]...] [-rebind] [-user | -u <user>]

Options

The following table describes the bindds command options:

Example

The following example binds the ds1 data source into the namespace:

bindds /test/ds1 -host localhost -port 1522 -sid orcl -driver thin
bindds /test/ds1 -url jdbc:oracle:thin:@localhost:1522:orcl

The example uses the JDBC thin driver with a general data source, that is, OracleDataSource.

bindurl Command

The bindurl command binds a URL object in the namespace.

Options

The following table describes the bindurl command options:

Example

The following example binds the URL string http://www.oracle.com to a URL reference /test/myURL within the namespace:

bindurl /test/myURL http://www.oracle.com -rebind

The -rebind option is used to make sure that if the /test/myURL reference previously exists, then it is rebound with the string http://www.oracle.com.

oracle.aurora.jndi.ojds.OjdsClientContext

This class implements the javax.naming.directory.DirContext interface. It establishes connection with the database and performs all functions required to support the OJDS. It supports all the methods described in [DirContext] except the following methods:

• getSchema

• getSchemaClassDefintion

• modifyAttributes

• search

This class is created automatically when an InitialDirContext is created on a JAVA JDK based client. It provides the communication and object transport between the client application and the OJDS.

You must set the following JNDI properties to specific values to complete a connection:

• java.naming.factory.initial to oracle.aurora.jndi.ojds.OjdsIntialContextFactory

• java.naming.security.principal to the name of the connection schema

• java.naming.security.credentials to the schema password

• java.naming.provider.url to a valid OJDS URL

You can set these properties as shown in the following code snippet:

Hashtable env = new Hashtable();
env.put("java.naming.factory.initial", "oracle.aurora.jndi.ojds.OjdsInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "HR");
env.put(Context.SECURITY_CREDENTIALS, "<password>");
env.put(Context.PROVIDER_URL,"ojds://thin:localhost:5521:j3");

oracle.aurora.jndi.ojds.OjdsServerContext

This class implements the javax.naming.directory.DirContext interface. It uses the internal database connection to communicate with the OJDS persistent store. It supports all the methods described in [DirContext] except for the following methods:

• getSchema

• getSchemaClassDefintion

• modifyAttributes

• search

This class is created automatically when an InitialDirContext is created in a database resident application. It uses the database internal JDBC driver to communicate with the OJDS persistent store.

The four environment properties for the OjdsClientContext are ignored for OjdsServerContext because the application runs as the login schema. The connection is made with the kprb [JDBC] internal driver. If the Java stored procedure requires access outside the server, then you must use the OJDS URLContext described in "oracle.aurora.jndi.ojds.OjdsInitialContextFactory" as the value of the java.naming.provider.url property.

oracle.aurora.jndi.ojds.OjdsInitialContextFactory

This class implements the javax.naming.spi.InitialContextFactory interface. The JNDI InitialContext or InitialDriContext classes create either an OjdsClientContext or an OjdsServerContext depending on the execution environment.

oracle.aurora.jndi.ojds.OjdsURLContextFactory

This class supports OJDS style URLs. Depending on the method provided to the URL, this method can return a DirContext or an instance of an object stored in the OJDS.

oracle.aurora.jndi.ojds.OjdsURLContext

This class is an extension of the oracle.aurora.jndi.ojds.OjdsClientContext. It supports extraction of connection information from an OJDS URL and making a connection to the OJDS. It supports the same interfaces as oracle.aurora.jndi.ojds.OjdsClientContext class.

You must set the following parameters to use the OjdsURLContext class:

• javax.naming.security.principal to the connection schema

• javax.naming.security.credentials to the password of the connection schema

• javax.naming.factory.initial to oracle.aurora.jndi.ojds.OjdsInitialContextFactory

You can set these properties as shown in the following code snippet:

Hashtable env = new Hashtable();
env.put("java.naming.factory.initial", "oracle.aurora.jndi.ojds.OjdsInitialContextFactory");
env.put(Context.SECURITY_PRINCIPAL, "HR");
env.put(Context.SECURITY_CREDENTIALS, "<password>");
DirContext dir = 
(new InitialContext(env)).lookup(”ojds://thin:localhost:5521:j3/public./mydir”);