9

Overview of Oracle DCE Integration

This chapter provides brief descriptions of the Distributed Computing Environment (DCE) and the Oracle DCE Integration product. For more detailed information, see the list of related books and papers in "Related Publications" in the Preface of this guide.

This information includes the following:

9.1 System Requirements

Oracle DCE Integration requires Net8 or higher and Oracle8.0.3. It enables Oracle applications and tools to access Oracle8 servers in a DCE environment.

Note:

Oracle DCE Integration is based on the Open Software Foundation (OSF) DCE V1.0 and V1.1, and will be compatible with OSF's future DCE releases.

Note:

OSF recently merged with another standards group,
X/OPEN, to form The Open Group. This group will continue to support DCE.

9.2 Backward Compatibility

Oracle servers running DCE Integration 2.3.2 and later are backward compatible with clients running SQL*Net/DCE 2.1.6 or 2.2.3; however, the 2.1.6 clients will not be able to take advantage of external roles.

A DCE Integration 2.3.2 or later client will not be able to connect to a SQL*Net/DCE 2.1.6 or 2.2.3 server. A DCE Integration release 2.3.2 or later client requires a 2.3.2 or later server in order to connect to a database.

9.3 Overview of Distributed Computing Environment (DCE)

The Distributed Computing Environment (DCE) from the Open Software Foundation (OSF) is a set of integrated network services that work across multiple systems to provide a distributed environment. The network services include remote procedure calls (RPCs), directory service, security service, threads, distributed file service, diskless support, and distributed time service.

DCE is the middleware between distributed applications and the operating system/network services and is based on a client/server model of computing. By using the services and tools that DCE provides, users can create, use, and maintain distributed applications that run across a heterogeneous environment.

For more detailed information on DCE, see "Related Publications" in the Preface of this guide.

9.4 Overview of Oracle DCE Integration

Oracle DCE Integration enables users to use Oracle tools and applications to access Oracle8 servers in a DCE environment. Oracle's DCE Integration product is comprised of the following parts:

9.4.1 DCE Communication/Security Adapter

The DCE Communication/Security Adapter component includes:

Authenticated RPC-Oracle DCE Integration provides authenticated RPC (Remote Procedure Call) as the transport mechanism which enables multi-vendor interoperability. RPC also uses some of the other DCE services, including directory and security services, to provide location transparency and secure distributed computing.
Integrated Security and Single Sign-On-Oracle DCE Integration works with the DCE Security service to provide security within DCE cells. It enables a user logged onto DCE to securely access any Oracle database without having to specify a username or password. This is sometimes referred to as external authentication to the database. It is also known as single sign-on. Clients and servers that are not running DCE authentication services can interoperate with systems that have DCE security by specifying an Oracle password.

Data Privacy and Integrity-Oracle DCE Integration uses the multiple levels of security that DCE provides to ensure data authenticity, privacy and integrity. For example, users have a range of choices from no protection to full encryption for each connection, with a guarantee that no data has been modified in transit.

Note:

For parts of your network that do not use DCE, you may want to use the other security and authentication services included with the Oracle Advanced Networking Option. These services (formerly included in Secure Network Services) work with SQL*Net release 2.1 and above. They provide message integrity and data encryption services in non-DCE environments, allowing administrators to ensure that all network traffic is protected against unauthorized viewing or modification, regardless of the start or end point. For more information on these services see Part I, "Oracle Advanced Networking Option Security and Single Sign-On", of this guide.

9.4.2 DCE CDS Native Naming Adapter

The DCE CDS Native Naming adapter component includes:

Naming and Location Transparency-DCE Integration registers Oracle8 connect descriptors in the DCE Cell Directory Service (CDS), allowing them to be transparently accessed across the entire DCE environment. Users can connect to Oracle database servers in a DCE environment using familiar Oracle service names.
The DCE Cell Directory Service offers a distributed, replicated repository service for name, address and attributes of objects across the network. Because servers register their name and address information in the Cell Directory Service (CDS), Oracle clients can make location-independent connections to Oracle8 servers. Services can be relocated without any changes to the client configuration. An Oracle utility is provided to load the Oracle service names (with corresponding connect descriptors) into CDS. After this is done, Oracle connect descriptors can be viewed from a central location with standard DCE tools.

For location of services across multiple cells, either of the following options may be used:
- DCE Global Directory Service (GDS)
- Internet Domain Naming Service (DNS)

For more information about the DCE CDS Native Naming Adapter see the following:

To configure DCE to use the CDS naming adapter, see Chapter 10, "Configuring DCE for Oracle DCE Integration".
To configure Oracle clients and servers to use CDS, see Chapter 11, "Configuring Oracle for Oracle DCE Integration".
To read about how Oracle Native Naming adapters work with other Oracle name services, refer to the Net 8 Administrator's Guide.

9.4.3 Flexible DCE Deployment

Oracle Advanced Networking Option provides you flexibility in your use of DCE services. You have the following options:

You can use full DCE Integration in your environment to integrate with all the DCE Secure Core services (RPC, directory, security, threads) described in this part of the guide.
You can choose to use only the DCE directory services by using the DCE CDS Native Naming Adapter, along with any conventional protocol adapter, such as TCP/IP. Configuration of the CDS Native Naming adapter is described in Chapter 10, "Configuring DCE for Oracle DCE Integration" and Chapter 11, "Configuring Oracle for Oracle DCE Integration" in this guide. For an overview of how Native Naming adapters work with other Oracle name services, refer to the Net 8 Administrator's Guide.
You can use only DCE authentication services by using the DCE GSSAPI authentication adapter described in Chapter 8, "Configuring the DCE GSSAPI Authentication Adapter" of this guide. This requires OSF DCE 1.1.

9.4.4 Limitations in This Release

Only one listener address that uses the DCE protocol is allowed per node.
Database links must specify a username and password to connect.
This release of the DCE Integration adapter does not support the Oracle MultiProtocol Interchange.
This release does not work with the Oracle Multi-Threaded Server (MTS).

9Overview of Oracle DCE Integration