Oracle8i Enterprise JavaBeans Developer's Guide and Reference Release 3 (8.1.7) Part Number A83725-01 |
|
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.
dbassist
at $ORACLE_HOME/bin
.
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"
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. EJB and 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:
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.
Both steps are described in more detail below.
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:
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)"
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.
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:
|
![]() Copyright © 1996-2000, Oracle Corporation. All Rights Reserved. |
|