Oracle8i CORBA Developer's Guide and Reference Release 3 (8.1.7) Part Number A83722-01 |
Library | Service | Contents | Index

## Manual Install and Configuration

If you did not install JServer through either the Typical or Custom install options, you can add JServer to an existing database with the `initjvm.sql` script. See the Oracle8i Java Developer's Guide for more information on this script.

Once you have installed JServer, you can configure your IIOP connections either through the tools--Database Configuration and Net8 Assistants--or by manually editing the initialization files.

### Configuring Through Tools

1. Configure the database for IIOP through the Database Configuration Assistant. To start up the Database Configuration Assistant, do the following:

   - On UNIX, run `dbassist` at `$ORACLE_HOME/bin`.

   - On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Database Administration > Database Configuration Assistant.

   After starting up the Database Configuration Assistant, choose the JServer option. For information on what this does to your initialization files, see "Oracle8i Custom Installation"

2. Configure the listener for IIOP through the Net8 Assistant. These steps are described in "Net8 Assistant".

### Configuring Through Editing Initialization Files

The presentation layer within the database identifies the type of connection your client is using to access the database. To identify the GIOP presentation, you use `oracle.aurora.server.SGiopServer`, which is the configuration for session-based IIOP connections. CORBA applications can activate objects within multiple sessions and are not limited to objects within the single session that the client initiated. These connections identify both a session and the standard IIOP semantics.

``To configure an IIOP connection, you specify the GIOP presentation in the following initialization files:

1. Configure the IIOP connection in the database initialization file--You configure the PRESENTATION attribute of the MTS_DISPATCHERS parameter.

   This section describes only the PRESENTATION attribute for the MTS_DISPATCHERS parameter. For a full description of MTS configuration, see the Net8 Administrator's Guide.

2. Configure the Net8 listener for IIOP connections.

Both steps are described in more detail below.

#### 1. Configure the IIOP Connection in the Database Initialization File

To configure an IIOP connection within the database, you can manually edit the database initialization file.

The following is the syntax for the MTS_DISPATCHERS parameter:

    mts_dispatchers="(protocol=tcp | tcps)

    	(presentation=oracle.aurora.server.SGiopServer)"

The attributes for MTS_DISPATCHER are described below:

Attribute | Description
--- | ---
PROTOCOL (PRO or PROT) | Specifies the TCP/IP or TCP/IP with SSL protocol, which the dispatcher will generate a listening end point for. Valid values: TCP (for TCP/IP) or TCPS (for TCP/IP with SSL)
PRESENTATION (PRE or PRES) | Enables support for GIOP. Supply the following value for a GIOP presentation: `oracle.aurora.server.SGiopServer` for session-based GIOP connections. This presentation is valid for TCP/IP and TCP/IP with SSL.

Note: If you configure several MTS_DISPATCHERS within your database initialization file, each MTS definition must follow each other. You should not define any other configuration parameters between the MTS_DISPATCHER definitions.

For example, to configure MTS for session-based IIOP connections through the listener using non-SSL TCP/IP, add the following within your database initialization file:

    mts_dispatchers="(protocol=tcp)(presentation=oracle.aurora.server.SGiopServer)"

#### 2. Configure a Listener for the Incoming Connection

Each listener is configured to listen on a well-known port number, and the client communicates with the listener using this port number. To support CORBA and EJB, the listener must be configured to listen for IIOP clients on either ports 2481 or 2482.

You can either use the Net8 Assistant to configure your listener or manually configure the listener within the `listener.ora` file. Oracle recommends that you use the Net8 Assistant. See "Net8 Assistant" for information on the Net8 Assistant.

To configure the listener manually, you must modify the listener's DESCRIPTION parameter within the `listener.ora` file.

##### Modify the LISTENER.ORA DESCRIPTION Parameter

You must configure the listener with a GIOP listening address. The following example configures a GIOP presentation for non-SSL TCP/IP with port number 2481. You use port 2481 for non-SSL and port 2482 for SSL.

For GIOP, the PROTOCOL_STACK parameter is added to the DESCRIPTION when configuring an IIOP connection to `sales-server`:

    listener=
      (description_list=
       (description=
         (address=(protocol=tcp)(host=sales-server)(port=2481))
         (protocol_stack=
            (presentation=giop)
            (session=raw))))

The following table gives the definition for each of the GIOP parameters:

Attribute | Description
--- | ---
PROTOCOL_STACK | Identifies the presentation and session layer information for a connection.
(PRESENTATION=GIOP) | Identifies a presentation of GIOP for IIOP clients. GIOP supports `oracle.aurora.server.SGiopServer` using TCP/IP.
(SESSION=RAW) | Identifies the session layer. There is no specific session-layer for IIOP clients.
(ADDRESS=...) | Specifies a listening address that uses TCP/IP on either port 2481 for non-SSL or port 2482 for SSL. If non-SSL, the protocol should be TCP; for SSL, the protocol should be defined as TCPS.

| Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
Library | Service | Contents | Index