8
Performing Advanced Configuration

This chapter describes optional advanced configuration:

Specific topics discussed are:

• Using the External Naming Method
• Configuring Authentication Adapters
• Configuring Security for the Named Pipes Protocol Adapter
• Configuring ANO
• Configuring External Procedure Calls

Using the External Naming Method

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:  Oracle Advanced Networking Option Administrator's Guide for more information about the Native Naming Adapter  Novell NetWare documentation for further information about NDS  Oracle8 NetWare documentation

   

NetWare Server Configuration

To configure the server:

1. Install and configure Net8 for NetWare on the server.
2. Log into the NDS tree.
3. Add NDS to the NAMES.DIRECTORY_PATH parameter in the SQLNET.ORA file:

NAMES.DIRECTORY_PATH = (NDS, TNSNAMES, ONAMES)

Client Configuration

To configure a client:

1. Install and configure the NDS Native Naming Adapter and Net8 on the client.
2. When you configure the NDS Native Naming Adapter, add NOVELL to the NAMES.DIRECTORY_PATH parameter in the SQLNET.ORA file:

NAMES.DIRECTORY_PATH = (NOVELL, NDS, TNSNAMES, ONAMES)

---

Note: 
To support backward compatibility, NOVELL may be specified in addition NDS. 

---

Client Connection

To connect from a client with the NDS Native Naming Adapter:

Enter the following command at the MS-DOS command prompt to access an Oracle8 database for NetWare database:

C:\>SVRMGR30
SVRMGR> CONNECT USERNAME/PASSWORD@DATABASE_OBJECT_NAME

where DATABASE_OBJECT_NAME identifies the Oracle8 database in NDS.

Configuring Authentication Adapters

Net8 provides these authentication adapters:

• NDS Authentication Adapter
• Windows NT Native Authentication Adapter

NDS Authentication Adapter

Note:   To connect from a client using the NDS Authentication Adapter, the server must be running the NetWare operating system.

   

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:  "Authentication Servers for Identix" in this chapter for more information about ANO NDS Native Naming Adapter  Novell NetWare documentation for more information about NDS  Oracle8 NetWare documentation

   

NetWare Server Configuration

To configure the server:

1. Install and configure Net8 for NetWare on the server.
2. Add the following entry to the SQLNET.ORA file:

SQLNET.AUTHENTICATION_SERVICES = (NDS)

Client Configuration

To configure a client:

1. Install and configure the Net8 on a client.
2. Add the following entry to the SQLNET.ORA file:

SQLNET.AUTHENTICATION_SERVICES = (NDS)

Client Connection

To connect from a client with the NDS Authentication Adapter:

1. Log into the NDS tree.
2. Enter the following command to access an Oracle8 database for NetWare database:

C:\>SVRMGR30
SVRMGR> CONNECT /@SERVICE_NAME

Windows NT Native Authentication Adapter

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:

1. For both clients and server, add the following entry to the SQLNET.ORA file:

SQLNET.AUTHENTICATION_SERVICES = (NTS)

Follow the instructions in "Connecting Without a Password as a Nonprivileged Database User" in Chapter 11, "Authenticating Database Users Through Windows NT", of your Getting Started guide.

   

Configuring Security for the Named Pipes Protocol Adapter

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:

1. From the Control Panel window, double-click Services.

The Services window appears.

2. Select the OracleHOME_NAMETNSListener80(LSNR) service and double-click.

The Service dialog box appears.

3. Choose the:
• This Account option button
• "..." button next to the This Account option button

The Add User dialog box appears.

4. Select your log on ID (user ID) from the Names list box and choose the Add button.

The user ID appears in the Add Name field.

5. Click OK.

The Services dialog box appears with the user ID displayed in the This Account field.

6. Enter your password in the Password field.
7. Retype the same log on ID password in the Confirm Password field.
8. Click OK.

Configuring ANO

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.

CyberSAFE Authentication Adapter

Before using the CyberSAFE Authentication Adapter, run the CyberSAFE Challenger Client to get your ticket-granting ticket.

Additional Information:   See the CyberSAFE Application Security Toolkit documentation.

   

Identix Authentication Adapter

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:

1. Change directory to ORACLE_HOME\IDENTIX
• If you are using the default I/O port number 280 and the default Windows NT directory, go to Step 4.
• If you are not using the default I/O port number 280, go to Step 2.
• If you are not using the default Windows NT directory WINNT35\SYSTEM32\DRIVERS, go to Step 3.
2. Modify the IoPortAddress parameter in ETSIINT.INI to the current TouchSafe II Encrypt I/O port setting. For example:

IoPortAddress = REG_DWORD 0x00000360  for I/O port 0x360

3. Modify the Windows NT directory setting in ETSIINT.BAT with your Windows NT directory.

For example:

copy etsiint.sys c:\winnt\system32\drivers   
-> copy etsiint.sys path\drivers

4. Run the batch file ETSIINT.BAT.
5. Use the SetKey utility in the Identix demo program to set a hash key in Hex. Set the key to C001BABY for example (do not use this value!). Make sure the hash key matches exactly the one set in the DEFAULT Security policy.
6. Reboot the system, and the device driver will start to work.
7. To make sure the device driver is running, check the Device Control Panel after reboot. The device ETSIINT should be started already.

Authentication Servers for Identix

If you are using Identix adapter you may need to use NONE authentication between Oracle8 database and Identix 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)
 ...

 

Kerberos Authentication Adapter

To use the Kerberos Authentication Adapter, you need to have the root drive:\USR\TMP subdirectory present.

SecurID Authentication Adapter

To use the SecurID Authentication Adapter, you need the following from your SecurID administrator:

• SDCONF.REC file present in the root drive:\VAR\ACE
• port numbers and service names present in the Windows NT SERVICES file

Configuring External Procedure Calls

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:

• Image Cartridge
• Time Series Cartridge
• VIR Cartridge

Oracle8 External Procedures Requirements

Follow the procedures in the CD insert to install these products on your Windows NT server:

• Oracle8
• PL/SQL, from which external procedures are called, and the PL/SQL external procedure program (EXTPROC), which executes external procedures
• Net8 Client, Net8 Server, and Oracle Protocol Adapter

Configuring Net8 for External Procedures

External procedures entries should already be present in the LISTENER.ORA and TNSNAMES.ORA files if you have:

• a new Oracle8 installation
• migrated from SQL*Net Version 2.x to Net8
• installed Net8 into the same Oracle home as your SQL*Net Version 2.x.

For environments where the configuration files have been overwritten, edit the LISTENER.ORA and TNSNAMES.ORA files as follows:

1. Add a system identifier (SID) name and a program name for EXTPROC in the server's LISTENER.ORA file (entries are shown in boldface text):

 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)                  
              )                                    
        )

2. Add a service name entry for EXTPROC in the server's TNSNAMES.ORA file (entries are shown in boldface text):

     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))
        ) 

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.

How Do External Procedure Calls Work?

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.

• shared library name
• external procedure name
• parameters (if necessary)

EXTPROC then loads the shared library and invokes the external procedure.

---