Oracle Networking Products Getting Started for Windows Platforms Release 8.0.3 A53746-01 |
|
This chapter covers the following areas:
This release of Oracle Networking Products include the new features listed below and are introduced later in this chapter:
New Feature | Description |
---|---|
Graphical Network Configuration Tools |
|
Oracle Net8 Easy Config |
The Java-based Net8 Easy Config tool enables you to graphically set up service names. This tool succeeds the previously available tool called SQL*Net Easy Configuration (SQL*Net Version 2.x). Use this tool for configuring simple networks and testing the configuration. |
Oracle Net8 Assistant |
This Java-based graphical configuration and management tool succeeds Oracle Network Manager and SQL*Net Easy Configuration Tool, included in previous SQL*Net Version 2.x releases. Oracle Net8 Assistant helps you to configure and administer: For more information, see: |
Improved Performance and Scalability |
|
WINSOCK2 Support |
This release of Net8 supports both the WINSOCK 1.1 and WINSOCK2 socket interface. Net8 automatically detects WINSOCK2 on Windows NT and uses it if it is available. WINSOCK2 is a standard feature of the Windows NT Version 4.0 operating system. Oracle uses these WINSOCK2 features in Net8: WINSOCK2 support enables Net8 Multi-Threaded Server features such as: |
Multi-Threaded Server Support (MTS) |
Net8 supports the MTS in TCP/IP network environments. For more information, see: |
Multiplexing (concentration) |
Multiplexing is enabled through the Connection Manager. The Connection Manager acts as vehicle that takes in multiple client connections and "multiplexes" those connections over a single outgoing connection to the destination. Sessions can be multiplexed over a single transport if these conditions are exist:
The result of multiplexing is quicker response time and increased client connections. Note: Multiplexing is only available on TCP/IP networks. For more information, see: |
Connection Pooling |
Connection Pooling allows you to optimize network resources by maximizing the number of physical network connections to a MTS. Connection pooling is enabled by setting parameters in your Oracle Server INITSID.ORA configuration file. Note: Connection pooling is only available with MTS on TCP/IP networks. Connection pooling cannot be enabled multiplexing is used. For more information, see:
|
Multiple protocol support |
This feature enables a client and server with different networking protocols to communicate. This feature replaces functionality previously provided by Oracle Multi-Protocol Interchange (MPI) with SQL*Net Version 2.x. For more information, see: |
Listener Load Balancing |
Listener load balancing distributes the number of incoming sessions over multiple listeners for a single database or for two or more equivalent databases. This feature is configured by defining multiple listeners for each database. To enable multiple listeners for MTS, add the following parameter to the INTISID.ORA configuration file for that server: For more information, see: |
Client Cache Service |
This Oracle Names feature allows a client to store information retrieved from a Names Server in local memory. When a client makes a subsequent connection request, the client first checks the cached list of address information for the database address. If the address information is found before a specified time period (Time to Live or TTL), then the client has saved the time it normally would have spent querying a Names Server. The client cache service is especially advantageous if a Names Server is unavailable. For more information, see: |
Improved Security |
|
The Oracle Security Server, a separate product bundled with Oracle8 and Net8, supports authentication and authorization in an Oracle network environment using public-key cryptography. For more information, see: |
|
Access control (also known as firewall support) allows designated clients access to certain servers in a TCP/IP environment. Connection Manager forwards a client connection request if the client meets certain criteria based on "accept" and "reject" rules specified by the administrator:
For more information, see: |
|
Enhancements for Developers |
|
Net8 OPEN is an application programming interface (API) that allows users to write applications that use Net8 for connectivity. Net8 OPEN:
For more information, see: |
|
New Names Resolution Method |
|
Host Naming Adapter |
Host naming enables clients in a TCP/IP environment to resolve service names by using the host name of the server. This model differs from other naming methods which specify service addresses by using the database service name. The Host Naming Adapter resolves the host name using an IP address translation mechanism such as Domain Name Services (DNS), or a centrally maintained TCP/IP hosts file. For more information, see: |
The table below lists each component of Oracle Networking Products and the Windows platform on which it can be installed.
Oracle Networking Products Release 8.0.3 | NT Server | NT Client | 95 Client |
---|---|---|---|
Net8 |
yes |
yes |
yes |
Supported Protocol Stack Vendors |
|
||
yes |
yes |
yes |
|
yes |
yes |
yes |
|
yes |
yes |
yes |
|
yes |
yes |
no |
|
yes |
yes |
yes3 |
|
Oracle Connection Manager |
yes |
no |
no |
Oracle Advanced Networking Option (ANO)4 |
|
|
|
Network Security and Single Sign-On |
yes |
yes |
yes |
yes |
yes |
yes |
|
yes |
yes |
yes |
|
yes |
yes |
yes |
|
yes |
yes |
yes |
|
DCE Integration |
yes |
yes |
yes |
Authentication Adapters |
|
|
|
no |
yes |
yes |
|
Windows NT Authentication Adapter |
yes |
yes |
yes |
Native Naming Adapter |
|
|
|
NDS Native Naming Adapter |
no |
yes |
yes |
The TCP/IP Protocol Adapter enables client/server conversation over a network using TCP/IP and Net8. This combination of Oracle products enables an Oracle application on a client to communicate with remote Oracle databases through TCP/IP (if the Oracle database is running on a host system that supports network communication using TCP/IP).
Additional Information:
See your operating system documentation. |
The SPX Protocol Adapter enables client/server conversation over a network using SPX/IPX and Net8. This combination of Oracle products enables an Oracle application on a client to communicate with remote Oracle databases through SPX/IPX (if the Oracle database is running on a host system that supports network communication using SPX/IPX). The SPX/IPX protocol is predominantly used in Novell Netware environments.
Additional Information:
See the Novell manual that came with your SPX/IPX software. |
The Named Pipes Protocol Adapter enables client/server conversation over a network using Named Pipes and Net8. This combination of Oracle products enables an Oracle application on a client to communicate with remote Oracle databases through Named Pipes (if the Oracle database is running on a host system that supports network communication using Named Pipes).
The Named Pipes Protocol Adapter is a high-level interface providing interprocess communications between clients and servers (distributed applications). One process (the server side of the application) creates the pipe, and the other process (the client side) opens it by name. What one side writes, the other can read, and vice versa. Named Pipes is specifically designed for PC LAN environments.
The Logical Unit Type 6.2 (LU6.2) Protocol Adapter is part of the IBM Advanced Program-to-Program Communication (APPC) architecture. APPC is the IBM peer-to-peer (program-to-program) protocol for a System Network Architecture (SNA) network. SNA is an IBM reference model similar to the Open Systems Interconnect (OSI) model of the International Standards Organization (ISO).
Program-to-program communication protocols provide services for programs on one computer to initiate processes on another computer, thus establishing a dialogue. Peer-to-peer communication is independent of the following:
APPC architecture lets the client and host communicate over an SNA network without forcing the client to emulate a terminal (as in terminal-to-host protocols). APPC architecture allows peer-to-peer communication; the client can initiate communication with the server.
An SNA network with the LU6.2 and Physical Unit Type 2.1 (PU2.1) protocols provides APPC. The LU6.2 protocol defines a session between two application programs; LU6.2 is a product-independent LU-type.
The LU6.2 Protocol Adapter enables an Oracle application on a PC to communicate with an Oracle database. This communication occurs over an SNA network with the Oracle database on a host system that supports APPC.
In addition to server platforms, LU6.2 is available on operating systems that are client-only platforms.
The Bequeath Adapter enables the client to retrieve information from the database without using the listener. The Bequeath Adapter internally spawns a server process for each client application. In a sense, it does the same operation that a remote listener does for your connection, yet locally.
The Bequeath Protocol Adapter:
Host Naming is a new naming method which enables clients in a TCP/IP environment to resolve service names by using the name of the computer (host name) on which the database exists. This naming method differs from other methods in that the client does not specify service addresses.
The Host Naming Adapter resolves the host name through an IP address translation mechanism such as Domain Name Services (DNS), or a centrally maintained TCP/IP host file.
To use host naming to resolve service names, your configuration must meet these conditions:
The NetWare Directory Services (NDS) Authentication Adapter for clients lets a single login access a multi-server and multi-database network and view the entire network under a single NDS directory tree.
Additional Information: |
The Windows NT Authentication Adapter allows operating system authentication to be performed between a client and an Oracle server on Windows NT.
Additional Information: |
The NetWare Directory Services (NDS) Native Naming Adapter enables you to integrate Oracle service names (or database aliases) and addresses into your existing non-Oracle name services. This feature allows users from multiple points to use a single login to access a multi-server and multi-database network, and view the entire network under a single directory tree.
The NDS Native Naming Adapter uses the NDS naming environment to store service names and addresses of Oracle7 Server for NetWare databases. This environment allows users to connect to Oracle7 databases whose server name is defined as an NDS object name.
To use the NDS Naming Adapter, you must configure your Windows client machine to a Novell NetWare 4.x Workstation.
Additional Information:
See: |
The table below lists the supported protocol vendor for each Oracle Protocol Adapter.
Oracle Names is a transparent naming service product that spans a heterogeneous network with different protocols to resolve names. It stores network names and addresses so that network components can contact each another without regard to their physical locations or specific configurations on the network. Both servers and clients access names and addresses through Oracle Names Servers on the network. Oracle Names Version 8.0 includes
DDO enables servers to register themselves with well-known Names Servers. This option minimizes the size of configuration files. If your network uses a flat naming structure and has a limited number of servers, this option may be appropriate.
DDO features include:
Additional Information:
See "Chapter 4, "Configuring the Network" and Net8 Administrator's Guide. |
This Oracle Names feature allows a client to store information retrieved from a Names Server in local memory. When a client makes a subsequent connection request, the client first checks the cached list of address information for the database address. If the address information is found before a specified time period (Time to Live or TTL), then the client has saved the time it normally would have spent querying a Names Server. The client cache service is especially advantageous if a Names Server is unavailable.