Net8 Getting Started Release 8.0.4 for Windows NT and Windows 95 A55913-01 |
|
This chapter describes optional advanced configuration:
Specific topics discussed are:
External naming refers to service name resolution by using a supported third-party naming service. The NDS Native Naming Adapters resolve service names stored in a native naming service.
Note: To connect from a client using the NDS Native Naming Adapter, the server must be running the NetWare operating system. |
The NDS Native Naming Adapter for Windows NT and Windows 95 clients uses the NDS naming environment to store service names and addresses of Oracle7 NetWare Servers. This lets an NDS user view the entire network under a single NDS directory tree. You can use native name services in addition to, or instead of, Oracle Names or the TNSNAMES.ORA file.
If the NDS Authentication Adapter is also used, a single log on can access a multi-server and multi-database network.
Additional Information:
See:
|
To configure the server:
NAMES.DIRECTORY_PATH = (NOVELL, TNSNAMES, ONAMES)
To configure the client:
NAMES.DIRECTORY_PATH = (NOVELL, TNSNAMES, ONAMES)
To connect from a client with the NDS Native Naming Adapter:
Enter the following command to access an Oracle8 database for NetWare database:
SVRMGR30 SVRMGR> CONNECT USERNAME/PASSWORD@DATABASE_OBJECT_NAME
where DATABASE_OBJECT_NAME identifies the Oracle8 database in NDS.
Net8 provides these authentication adapters:
The NDS Authentication Adapter allows client applications and users to access a NetWare server running Oracle using NDS. A user logged into an NDS directory tree can be automatically authenticated to use an Oracle8 database on a NetWare server in the same NDS directory tree. This lets a user access an Oracle8 database on NetWare without entering an additional user name and password.
If the NDS Naming Adapter is also used, an NDS user can view the entire network under a single NDS directory tree.
Additional Information:
See:
|
To configure the server:
To configure the client:
To connect from a client with the NDS Authentication Adapter:
SVRMGR30 SVRMGR> CONNECT /@SERVICE_NAME
The Windows NT Native Authentication Adapter (automatically installed with Net8 Server and Net8 Client) enables database user authentication through Windows NT. This enables client machines to make secure connections to an Oracle8 database on a Windows NT server. A secure connection is when a Windows NT client user name is retrieved on a Windows NT server through the Windows NT Native Authentication Adapter. The Windows NT server then permits the user name to perform the database actions on the server.
To configure the Windows NT Native Authentication Adapter:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
Oracle does not support any native authentication when connecting from an Oracle8 database to a UNIX authentication server. On the Windows NT machine where the Oracle8 database is located, modify the TNSNAMES.ORA file located in ORACLE_HOME\NET80\ADMIN to include the following:
... (CONNECT_DATA = (SID = SID)) (SECURITY=(AUTHENTICATION_SERVICES=NONE) ...
Note: If you want a secure connection, you can still use ANO's Kerberos, CyberSAFE, or SecurID Authentication Adapter. If you use one of these adapters, do not add this line. |
If you are using Oracle Named Pipes Protocol Adapter with Oracle Names Server, the network listener may not be able to connect to the Oracle Names Server.
Oracle Names Server creates a Names Pipe at startup time. The network listener tries to open the Named Pipe at startup. If it cannot, the network listener uses the default system account "Local System." The network listener service may not be able to open the Named Pipe created by the Oracle Names Server unless the OracleTNSListener80(LSNR) service has a valid user ID and password associated.
To set up the network listener permissions:
The Service dialog box appears.
The Add User dialog box appears.
The user ID appears in the Add Name field.
The Services dialog box appears with the user ID displayed in the This Account field.
This section describes additional Windows NT and Windows 95 tasks that must be performed in order to run ANO that are not described in the Oracle Advanced Networking Option Administrator's Guide and the Oracle Net8 Assistant online help.
Before using the CyberSAFE Authentication Adapter, run the CyberSAFE Challenger Client to get your ticket-granting ticket.
If during the installation of Oracle Enterprise Manager Biometrics Manager, you chose not to allow the installer to set up your Identix TouchSafe II Device Driver, then you can configure it manually as follows.
To install the TouchSAFE II Encrypt device driver for Windows NT:
IoPortAddress = REG_DWORD 0x00000360 for I/O port 0x360
For example:
copy etsiint.sys c:\winnt\system32\drivers -> copy etsiint.sys path\drivers
To use the Kerberos Authentication Adapter, you need to have the root drive :\USR\TMP subdirectory present.
To use the SecurID Authentication Adapter, you need the following from your SecurID administrator:
External procedures are functions written in a third-generation language (3GL) such as C, and callable from within PL/SQL or SQL as if they were a PL/SQL procedure or function. External procedures enable you to take advantage of the strengths and capabilities of a 3GL programming language in a PL/SQL environment.
The following cartridges also require external procedures:
Follow the procedures in the CD insert to install these products on your Windows NT server:
External procedures entries should already be present in the LISTENER.ORa and TNSNAMES.ORA files if you have:
For environments where the configuration files have overwritten, edit your LISTENER.ORA and TNSNAMES.ORA files as follows:
LISTENER = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = IPC) (KEY = INVENTORY) ) (ADDRESS = (PROTOCOL = IPC) (KEY = ORCL) ) (ADDRESS = (PROTOCOL = IPC) (KEY = extproc) ) (ADDRESS = (PROTOCOL = TCP) (Host = INVENTORY) (PORT = 1521) ) ) STARTUP_WAIT_TIME_LISTENER = 0 CONNECT_TIMEOUT_LISTENER = 10 TRACE_LEVEL_LISTENER = ADMIN SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = ORCL) ) (SID_DESC = (SID_NAME = extproc) (PROGRAM = extproc) ) )
INVENTORYDB.WORLD = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (Host = INVENTORY) (PORT = 1521) ) (CONNECT_DATA = (SID = ORCL)) ) extproc_connection_data.world = (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC) (KEY = ORCL) ) (CONNECT_DATA = (SID=extproc)) (SOURCE_ROUTE = YES) )
Please note that the value for KEY must match the KEY value specified in the LISTENER.ORA file. In order to support a multiple Oracle home environment, the Oracle Installer automatically creates unique keys for the external procedures in different Oracle homes.
The network listener now listens for databases services like External Procedure Calls. When a PL/SQL or SQL application calls an external procedure, the Net8 network listener launches a session-specific process called EXTPROC. Through the network listener service, PL/SQL passes the following information to EXTPROC.
EXTPROC then loads the shared library and invokes the external procedure.