7
Enabling Optional Net8 Features

This chapter describes optional features you can enable.

Specific topics discussed are:

• Modifying Net Service Names

• Configuring a Profile

• Enabling Connection Concentration

• Enabling Multi-Protocol Support

• Enabling Net8 Access Control

• Configuring the Client for Oracle Connection Manager Features

• Enabling Connection Pooling

• Configuring Java Option Connections

• Configuring Non-Oracle Database Services

Modifying Net Service Names

This sections describes the following:

• Modifying Attributes of a Net Service Name

• Renaming a Net Service Name

• Adding a Protocol Address to a Net Service Name

• Deleting a Protocol Address from a Net Service Name

• Deleting a Net Service Name

• Configuring Advanced Connection Attributes for a Net Service Name

• Configuring Multiple Address Options

These changes are saved to the TNSNAMES.ORA file at $ORACLE_HOME/network/admin on UNIX or ORACLE_HOME\network\admin on Windows platforms.

Modifying Attributes of a Net Service Name

To modify attributes of a net service name, such as its name, service name, SID, or protocol address:

1. Start the Net8 Configuration Assistant:
   • On UNIX, run netca at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Configuration Assistant.

2. Select Local Net8 Service Name configuration, then click Next.

3. Click Modify.

4. Follow the prompts in the wizard and online help to modify any of the attributes.

5. Click Finish to save your configuration and dismiss the Net8 Configuration Assistant application.

Renaming a Net Service Name

To change the name of a net service name:

1. Start the Net8 Configuration Assistant:
   • On UNIX, run netca at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Configuration Assistant.

2. Select Local Net8 Service Name configuration, then click Next.

3. Click Rename.

4. Follow the prompts in the wizard and online help to modify any of the attributes.

5. Click Finish to save your configuration and dismiss the Net8 Configuration Assistant application.

Adding a Protocol Address to a Net Service Name

Each connect descriptor can contain one or more listener addresses:

net_service_name= 
(description= 
  (address= (protocol_address_information))
  (address= (protocol_address_information))
  (address= (protocol_address_information))
  (connect_data= 
     (service_name=service_name) 
  ) 
) 

To add an additional protocol address to a net service name:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Net Service Names folder in the directory tree.

3. Select the net service name.

4. Click "+" in the Address Configuration group box.

   A new address tab appears:

   
   
5. Choose the protocol and enter appropriate address information. For more information about protocol address parameters, see "Configuring Protocol Addresses".

6. Order the address according to where it should be in the address list with the "<" and ">" buttons. Unless multiple address options are configured, the first address in the list is contacted first. See "Configuring Multiple Address Options" to configure multiple address options.

7. Choose Save Network Configuration from the File menu.

   The TNSNAMES.ORA file is re-created.

8. Choose Exit from the File menu.

   The Net8 Assistant application exits.

Deleting a Protocol Address from a Net Service Name

To delete a protocol address from a net service name in the TNSNAMES.ORA file:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click the Net Service Names folder in the directory tree.

3. Select the net service name.

4. Click "X" in the Address Configuration group box:

   
   

5. Choose Save Network Configuration from the File menu.

   The TNSNAMES.ORA file is re-created.

6. Choose Exit from the File menu.

   The Net8 Assistant application exits.

Deleting a Net Service Name

To delete a net service name from the TNSNAMES.ORA file:

1. Start the Net8 Configuration Assistant:
   • On UNIX, run netca at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Configuration Assistant.

2. Select Local Net8 Service Name configuration, then click Next.

3. Click Delete.

4. Follow the prompts in the wizard and online help to delete the net service name.

5. Click Finish to save your configuration and dismiss the Net8 Configuration Assistant application.

   If you click Finish, the net service name is deleted, and the TNSNAMES.ORA file is re-created.

Configuring Advanced Connection Attributes for a Net Service Name

A TNSNAMES.ORA's CONNECT_DATA section of a connect descriptor may optionally contain the following features:

Net8 Assistant option	TNSNAMES.ORA Parameter	Description
Instance Name	INSTANCE_NAME	Identifies the database instance to access. The instance name can be obtained from the INSTANCE_NAME parameter in the INITSID.ORA file. Note: Not enabled if Use Oracle8i Release 8.0 Compatible Identification is turned ON. Additional Information: See "Setting Service Names and Instance Names".
Handler Name	HANDLER_NAME	Identifies a service handler, such as an MTS dispatcher, to access. Note: Not enabled if Use Oracle8i Release 8.0 Compatible Identification is turned ON. Note: Not enabled for release 8.1.5.
Session Data Unit (SDU) Size	SDU	If you want to optimize the transfer rate of data packets being sent across the network, you can specify the session data unit (SDU) size to change the performance characteristics having to do with the packets sent across the network. Additional Information: See "Optimizing Data Transfer by Adjusting the Session Data Unit (SDU) Size".
Use a Dedicated Server	SERVER	If you wish for the client connection to bypass multi-threaded server and to use dedicated server, turn this option on.
Use for Heterogeneous Services	HS	If you wish for an Oracle8i server to access a non-Oracle system, turn this option on. Note: Not enabled if Use Oracle8i Release 8.0 Compatible Identification is turned ON. Additional Information: See "Configuring Net8 for Oracle Heterogeneous Services".
Oracle Rdb Settings
Oracle RDB Database	RDB_DATABASE	Specifies the file name of an Oracle RDB database. Additional Information: See "Configuring Net8 for an Oracle Rdb Database".
Type of Service	TYPE_OF_SERVICE	Specifies the type of service to use for an Oracle RDB database. Additional Information: See "Configuring Net8 for an Oracle Rdb Database".
Global Database Name	GLOBAL_NAME	Identifies the Oracle Rdb database. Additional Information: See "Configuring Net8 for an Oracle Rdb Database".

To configure these advanced options:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click the Net Service Names folder in the directory tree.

3. Select the net service name:

   
   

4. Click Advanced in the Service Identification group box.

   The Advanced Service Options dialog box appears:

   
   
5. Enter fields or select options as appropriate, then click OK.

6. Choose Save Network Configuration from the File menu.

   The TNSNAMES.ORA file is re-created.

7. Choose Exit from the File menu.

   The Net8 Assistant application exits.

Configuring Multiple Address Options

When multiple addresses have been configured for a net service name, the following features may be configured:

• Source Route (SOURCE_ROUTE)

• Client Load Balance (LOAD_BALANCE)

• Connect-Time Failover (FAILOVER)

  Option	Description
  Source Route (SOURCE_ROUTE)	Instructs Net8 to use each address in the order presented until the destination reached when set to ON. This parameter is required when reaching the destination requires more than one address stop. This feature is typically used to enable Oracle Connection Manager features. Additional Information: For information about using the SOURCE_ROUTE parameter, see: "Enabling Connection Concentration" "Enabling Multi-Protocol Support" "Enabling Net8 Access Control"
  Connect-Time Failover (FAILOVER)	At connect time instructs Net8 to fail over to a different listener if the first listener fails when set to ON. The number of addresses in the list determines how many addresses are tried. When set to OFF, instructs Net8 to try one address. Connect-time failover is turned ON by default for multiple address lists (ADDRESS_LIST), connect descriptors (DESCRIPTION), and multiple connect descriptors (DESCRIPTION_LIST).
  Client Load Balance (LOAD_BALANCE)	When set to ON, instructs Net8 to progress through the list of listener addresses in a random sequence, balancing the load on the various listeners. When set to OFF, instructs Net8 to try the addresses sequentially until one succeeds. Client load balancing is turned ON by default for multiple connect descriptors (DESCRIPTION_LIST).

You can achieve the following effects from client load balancing and connect-time failover:

Net8 Assistant Option	TNSNAMES.ORA Parameter
Try each address, in order, until one succeeds	FAILOVER=ON for release 8.1 clients SOURCE_ROUTE=OFF for pre-release 8.0 clients.
Try each address, randomly, until one succeeds Note: Not enabled if Use Options Compatible with Net8 8.0 Clients is turned ON.	LOAD_BALANCE=ON FAILOVER=ON
Try one address, selected at random Note: Not enabled if Use Options Compatible with Net8 8.0 Clients is turned ON.	LOAD_BALANCE=ON
Use each address in order until destination reached	SOURCE_ROUTE=ON
Use only the first address Note: Not enabled if Use Options Compatible with Net8 8.0 Clients is turned ON.	LOAD_BALANCE=OFF FAILOVER=OFF SOURCE_ROUTE=OFF

Note: Connect-time failover and client load balancing options and parameters are only available for release 8.1 configurations. Source routing (Use each address in order until destination reached) is available for both pre-release 8.1 and release 8.1 configurations.

Note: It is not possible to set client load balancing or connect-time failover with source routing. While connect-time failover and client load balancing choose an address from a list, source routing connects to each address in the list sequentially.

To enable of disable client load balancing or connect-time failover, use the Net8 Assistant.

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click the Net Service Names folder in the directory tree.

3. Select the net service name.

   
   

4. Click the Advanced in the Address Configuration group.

   The Address List Options dialog box appears:

   
   
5. Select any of the address list options, then click OK.

6. Choose Save Network Configuration from the File menu.

   The TNSNAMES.ORA file is re-created.

7. Choose Exit from the File menu.

   The Net8 Assistant application exits.

In the example below, a TNSNAMES.ORA is configured for client load balancing with the Try each address, randomly, until one succeeds option:

sales= 
 (description= 
  (load_balance=on)
  (address=(protocol=tcp)(host=sales-pc)(port=1521)
  ) 
  (address=(protocol=tcp)(host=hr-pc)(port=1521)
  )
  (connect_data= 
    (service_name=sales.com))
 ) 

In the example below, a TNSNAMES.ORA is configured for connect-time failover with the Try each address, in order, until one succeeds option:

sales= 
 (description= 
  (address_list= 
   (load_balance=off)
   (failover=on)
   (address=(protocol=tcp)(host=hr-pc)(port=1521)
   (address=(protocol=tcp)(host=finance-pc)(port=1521)
   )
  )
  (connect_data=(service_name=sales.com))
 )

Configuring a Profile

A profile on the client configures functionality and defines how Net8 works to establish and maintain connections with services on the network. A profile is stored and implemented through a configuration file called SQLNET.ORA, located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms. A profile allows configuration of:

• naming method prioritization

• tracing and logging features

• connections through specific processes

• security features

This section describes the following profile features:

• Configuring Domains

• Prioritizing Net Service Name Naming Method Resolution

• Configuring Preferred Oracle Names Servers

• Configuring Advanced Profile Information

• Routing Connection Requests

• Configuring Oracle Advanced Security

For a complete list of all available parameters that may be configured in a profile, see "Profile Parameters (SQLNET.ORA)".

Configuring Domains

The NAMES.DEFAULT_DOMAIN parameter in SQLNET.ORA defines the domain from which the client most often requests names. When this parameter is set, the domain name is automatically appended to the net service name in a connect string. If this parameter is set with the Net8 Assistant, the domain is appended to any new net service name created without a domain. For example, if NAMES.DEFAULT_DOMAIN=COM is set, the connect string SCOTT/TIGER@ SALES gets searched in the TNSNAMES.ORA as SALES.COM. If the connect string includes the domain extension, (such as SCOTT/TIGER@SALES.COM), the domain is not appended.

To specify a domain, use the Net8 Assistant.

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose Naming from the drop-down list box.

4. Click the Oracle Names tab:

   
   

5. Enter the domain in the Default Domain field.

6. Choose Save Network Configuration from the File menu.

7. Choose Exit from the File menu to exit the Net8 Assistant application.

   The SQLNET.ORA should contain an entry that looks like the following:

   names.default_domain=com
   

Prioritizing Net Service Name Naming Method Resolution

After naming methods are configured, as documented in Chapter 6, "Configuring Naming Methods and the Listener", they must be prioritized. The naming method at the top of the list is used first to resolve a net service name. If it cannot resolve the net service name, the second method in the list is used to resolve the net service name.

To specify the order of naming methods, use the Net8 Assistant.

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose Naming from the drop-down list box.

4. Click the Methods tab:

   
   

5. Choose from the Available Methods list which naming method you want to use.

6. Order the naming methods according to which method you want Net8 to try first when resolving net service names. Select the naming method in the Selected Methods list, and use the Promote or Demote button to move the selection up or down in the list.

7. Choose Save Network Configuration from the File menu.

8. Choose Exit from the File menu to exit the Net8 Assistant application.

   The SQLNET.ORA should contain an entry that looks like the following:

   names.directory_path=(onames, tnsnames)
   
   

Available naming methods are described below:

Naming Method	Description
ONAMES	Oracle Names Net service names are resolved centrally, through an Oracle Names server.
TNSNAMES	Local Naming Net service names are resolved using the TNSNAMES.ORA file which resides on the client.
HOSTNAME	Host Naming Net service names are resolved using the host naming method. Certain criteria must be met to use host naming names resolution.
CDS	Cell Directory Services This naming method is available with Oracle Advanced Security option. Additional Information: See Oracle Advanced Security Administrator's Guide.
NDS	NetWare Directory Service (NDS)
NIS	Network Information Service (NIS)

Configuring Preferred Oracle Names Servers

A preferred Oracle Names Server is an Oracle Names Server that is preferred by a client for names resolution. It is normally the Oracle Names server that is physically closest to the client, or available over the least expensive network link. Most importantly, a preferred Oracle Names server should be able to resolve the net service names of the services you use most frequently.

If you are using Oracle Names as a naming service (though not necessarily running an Oracle Names Server on your local machine), you can specify the name and addresses of preferred Oracle Names servers to take precedence over any other available Oracle Names server address. Net8 will route connect requests to each preferred Names Server until a response is received.

Note: Preferred Oracle Names servers are an alternative to using the Discover Oracle Names Servers option in the Net8 Assistant or the REORDER_NS command in the NAMESCTL control utility, a newer feature that creates a list of Oracle Names servers based on what is available throughout the network, and ranks them in the order of fastest response time. Preferred Oracle Names servers override any other Oracle Names servers found in the discovery process. Once you have initially discovered a Names Server and generated a Names Server list file, you may want to delete preferred Oracle Names Servers. See "Differences Between Versions of Oracle Names" for a description of how Oracle Names server lists are created.

The NAMES.PREFERRED_SERVERS parameter in SQLNET.ORA specifies the preferred Oracle Names server(s). If you configure preferred Oracle Names server(s), the Oracle Names listening protocol address(es) you configured in NAMES.ORA must match the address(es) you configure with the NAMES.PREFERRED_SERVERS in SQLNET.ORA.

To specify a preferred Oracle Names server:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose Preferred Oracle Names Servers from the drop-down list box:

4. Click New:

   
   

5. Choose the protocol and enter the requested protocol address information for an Oracle Names server configured on that address, as described on "Configuring Protocol Addresses".

6. Choose Save Network Configuration from the File menu.

7. Choose Exit from the File menu to exit the Net8 Assistant application.

   The SQLNET.ORA should contain an entry that looks like the following:

   names.preferred_servers=
     (address= (protocol=tcp) (host=namesrv1)(port=1575)
   

Configuring Advanced Profile Information

The profile configuration file SQLNET.ORA can be configured with the following advanced features:

Net8 Assistant option	SQLNET.ORA Parameter	Description
TNS Time Out Value	SQLNET.EXPIRE_TIME	This option can only be used on the server. Net8 sends a probe periodically to verify that a client-server connection is still active. This is done to ensure that connections are not left open indefinitely, due to an abnormal client termination. If the probe finds a dead connection, or a connection that is no longer in use, it returns an error, causing the server process to exit. Limitations on using the dead connection detection feature are as follows: Dead connection detection is not allowed on bequeathed connections. Though very small, a probe packet generates additional traffic that may downgrade network performance. The server may need to perform additional processing to distinguish the connection probing event from other events that occur, depending on which operating system is in use. This may also result in downgrading network performance.
Client Registration ID	SQLNET.CLIENT_REGISTRATION	Sets a unique identifier for this client machine. This identifier will be passed to the listener with any connection request. The identifier can be any string up to 128 characters long.
Turn Off UNIX Signal Handling	BEQUEATH_DETACH	Since the client application spawns a server process internally through the Bequeath protocol as a child process, the client application becomes responsible for cleaning up the child process when it completes. When the server process completes its connection responsibilities, it becomes a defunct process. Signal handlers are responsible for cleaning up these defunct processes. Setting this parameter configures the client profile to pass this process to the UNIX init process by disabling signal handlers.
Disable Out-of-Band Break	DISABLE_OOB	Disables out of band breaks if the underlying protocol does not support this feature.

To set advanced features for clients, use either or the Net8 Assistant:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose General from the drop-down list box.

4. Click the Advanced tab:

   
   

5. Enter the values for the option(s) you would like to set.

6. Choose Save Network Configuration from the File menu.

7. Choose Exit from the File menu to exit the Net8 Assistant application.

Routing Connection Requests

The client and servers acting as clients can be configured so connection requests are directed to a specific process at all times. The following options in the Net8 Assistant or parameters in SQLNET.ORA file may be specified:

Net8 Assistant option	SQLNET.ORA Parameter	Description
Always Use Dedicated Server	USE_DEDICATED_SERVER	Forces the listener to spawn a dedicated server for all network session from this client.
Prefer Connection Manager Routing	USE_CMAN	Instructs the client to try to use an Oracle Connection Manager whenever possible. If no Oracle Connection Manager addresses are available, connections are routed through any available listener address. Note: If you are using Oracle Connection Manager with Oracle Names, this option must be set on clients and Oracle Names servers.

To route connection requests, use the Net8 Assistant:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose General from the drop-down list box.

4. Click the Routing tab:

   
   

5. Click the preferred way you want connection requests routed.

6. Choose Save Network Configuration from the File menu.

7. Choose Exit from the File menu to exit the Net8 Assistant application.

Configuring Oracle Advanced Security

Oracle Advanced Security is an optional product that works with Net8 and SQL*Net release 2.1.4 and later. It includes the following features:

• Security Services

• Authentication Services

• Oracle DCE Integration

Security Services

Oracle Advanced Security enables Net8 and related products to use network data encryption and checksumming so that data cannot be read or altered. It protects data from unauthorized viewing by using the RSA Data Security RC4 or the Data Encryption Standard (DES) encryption algorithm. To ensure that data has not been modified, deleted, or replayed during transmission, the security services of Oracle Advanced Security can generate a cryptographically secure message digest and include it with each packet sent across the network.

Oracle Advanced Security is supported by Oracle Connection Manager. Clients and servers using different protocols can securely transfer data across network protocol boundaries. For example, clients using LAN protocols such as NetWare (SPX) can share data securely with large servers using different protocols such as LU6.2, TCP/IP, or DECnet.

Authentication Services

Oracle Advanced Security includes enhanced user authentication services such as support for single sign-on. These authentication services enhance the existing security facilities of Oracle7 and Oracle8i such as secure network access control log on, roles, and auditing by providing reliable user identification. No changes to applications are required. Oracle Advanced Security works over all protocols, operating systems, and name services. It also supports token authentication through Security Dynamics ACE Server, Kerberos, RADIUS protocol or RADIUS compatible server, Secure Sockets Layer (SSL), DCE Security Server, and biometrics authentication through Identix.

These services are available to most products that implement Net8, including the Oracle8i, Developer 2000 tools, and any other Oracle or third-party products that support Net8.

Oracle DCE Integration

Oracle Distributed Computing Environment (DCE) Integration is an optional product that works with Net8 and SQL*Net 2.1.6 and later. It enables users to transparently use Oracle tools and applications to access Oracle7 and Oracle8i servers in a DCE environment. It provides authenticated RPC (Remote Procedure Call) as the transport mechanism, which enables multi-vendor interoperability. The DCE security service enables a user logged onto DCE to securely access any Oracle application without having to specify a user name or password. This is sometimes referred to as "external authentication", formerly referred to as "OPS$ support".

Oracle DCE Integration also provides support for DCE Cell Directory Service (CDS), which allows Oracle7 and Oracle8i services to be transparently accessed throughout the DCE environment. Users can connect to Oracle database servers in a DCE environment using familiar Oracle service names. Oracle service names can be managed from a central location with standard DCE tools. For more information, see Oracle Advanced Security Administrator's Guide and your Oracle platform-specific documentation.

Configuration

To configure a client to use Advanced Security option:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Click the Profile icon.

3. Choose Advanced Security Option from the drop-down list box:

   
   

   See Oracle Advanced Security Administrator's Guide for further information about configuration.

4. Choose or edit options as applicable.

5. Choose Save Network Configuration from the File menu.

6. Choose Exit from the File menu to exit the Net8 Assistant application.

Enabling Connection Concentration

Oracle Connection Manager enables you to take advantage of Net8's ability to multiplex or funnel multiple logical client network sessions through a single transport connection to a multi-threaded server destination. This is accomplished through Oracle Connection Manager's connection concentration feature.

Step 1: Configure Oracle Connection Manager

The gateway process, CMGW, accepts connection requests at the following default listening address:"Oracle Connection Manager Processes"

cman=(address=(protocol=tcp)(host=anyhost)(port=1630))

The administrative process, CMADMIN, listens for local and remote administration commands at the following listening address:

cman_admin=(address=(protocol=tcp)(host=anyhost)(port=1830))

If you do not want to use TCP/IP or the ports 1630 and 1830, you must create a CMAN.ORA with the following information, if one does not exist with the address information, at $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT:

cman=(address=(protocol_address_information))
cman_admin=(address=(protocol_address_information))

The Net8 Assistant does not support configuration of CMAN.ORA, so changes must be made manually.

See also the following:

• "Oracle Connection Manager Processes" for further information about CMGW and CMADMIN

• "Configuring Protocol Addresses" for information about proper protocol address parameter usage

Step 2: Configure the Server

Verify that the destination server is configured as a multi-threaded server and that the multiplexing feature is turned on. This is done by setting the MTS_DISPATCHERS parameter in the database initialization file (INITSID.ORA) for that instance with the PROTOCOL and MULIPLEX attribute.

For example:

mts_dispatchers="(protocol=tcp) (multiplex=on)"

Attribute	Description
PROTOCOL (PRO or PROT)	The network protocol (TCP in the example above) for which the dispatcher will generate a listening end point.
MULTIPLEX (MUL or MULT)	Used to enable connection concentration. If 1, ON, YES, TRUE, or BOTH is specified, then connection concentration is enabled for both incoming and outgoing network connections. If IN is specified, the connection concentration is enabled for incoming network connections from the client. If OUT is specified, the connection concentration is enabled for outgoing network connections. If 0, NO, OFF, or FALSE is specified, then connection concentration is disabled for both incoming and outgoing network connections.

For more information about configuring MTS, see Chapter 9, "Configuring Multi-Threaded Server".

Step 3: Configure the Client

Client support is accomplished by setting the Oracle Connection Manager address and listener address through a TNSNAMES.ORA file or an Oracle Names server:

• If using a TNSNAMES.ORA file, the Oracle Connection Manager address and the SOURCE_ROUTE parameter must be set, which creates a source route of addresses through an Oracle Connection Manager to the destination database. To configure the local naming method's TNSNAMES.ORA file, follow the instructions in "Configuring the Client for Oracle Connection Manager Features" of this chapter.

• If using Oracle Names servers, the Oracle Connection Manager automatically updates the addresses in the Oracle Names servers, inserting the address for the Oracle Connection Manager into the existing addresses. In order for Oracle Names servers to send requests to Oracle Connection Manager, USE_CMAN=TRUE must be set in the SQLNET.ORA file on clients and machines where each Oracle Names server resides. To set this parameter, follow the steps in "Routing Connection Requests".

Figure 7-1 shows a comparison of a regular TNSNAMES.ORA file and a TNSNAMES.ORA file with an entry to use the Oracle Connection Manager (Connection Manager entries are shown in boldface text):

Figure 7-1 TNSNAMES.ORA File with and without Oracle Connection Manager

sales= (description= (address= (protocol=tcp) (host=sales-pc) (port=1521) ) (connect_data= (service_name=sales,com) ) )

sales= (description= (source_route=yes) (address= (protocol=tcp) (host=cman=pc) (port=1630) ) (address= (protocol=tcp) (host=sales=pc) (port=1521) ) (connect_data= (service_name=sales.com) ) )

TNSNAMES.ORA Element	Description
source_route=yes	Creates a source route of addresses through an Oracle Connection Manager to the destination database.
(address= (protocol=tcp) (host=cman-pc) (port=1630) )	This first address is to the Oracle Connection Manager. From here, the Oracle Connection Manager connects to the service through the listener.

Enabling Multi-Protocol Support

Note:: If more than one Oracle Connection Manager is used in the connection path (more than 1 hop), you cannot use Oracle Names to connect clients through it.

Oracle Connection Manager also provides multiple protocol support enabling a client and server with different networking protocols to communicate with each other. An Oracle Connection Manager can listen on any protocol that Oracle supports.

Without multi-protocol support, a client that uses SPX cannot connect to a server that uses TCP/IP. If Oracle Connection Manager is configured for TCP/IP, the client can connect to Oracle Connection Manager using SPX, and Oracle Connection Manager can connect to the server using TCP/IP.

Step 1: Configure Oracle Connection Manager

The gateway process, CMGW, accepts connection requests at the following default listening address:

cman=(address=(protocol=tcp)(host=anyhost)(port=1630))

The administrative process, CMADMIN, listens for local and remote administration commands at the following listening address:

cman_admin=(address=(protocol=tcp)(host=anyhost)(port=1830))

If you do not want to use TCP/IP or the ports 1630 and 1830, you must create a CMAN.ORA with the following information, if one does not exist with the address information, at $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT:

cman=(address=(protocol_address_information))
cman_admin=(address=(protocol_address_information))

The Net8 Assistant does not support configuration of CMAN.ORA, so changes must be made manually.

See also the following:

• "Oracle Connection Manager Processes" for further information about CMGW and CMADMIN

• "Configuring Protocol Addresses" for information about proper protocol address parameter usage

Step 2: Configure the Client

Multi-protocol support is accomplished by setting the Oracle Connection Manager address and listener address through a TNSNAMES.ORA file or Oracle Names servers:

• If using a TNSNAMES.ORA file, the Oracle Connection Manager address and the SOURCE_ROUTE parameter must be set, which creates a source route of addresses through an Oracle Connection Manager to the destination database. To configure the local naming method's TNSNAMES.ORA file, follow the instructions in "Configuring the Client for Oracle Connection Manager Features" of this chapter and these tips:
  • Configure the client first with the address of the Oracle Connection Manager, using a protocol available on the client.

  • Configure the client with the address of the listener, using a protocol available on the server.

  • The Oracle Connection Manager machine must contain all the protocols used on the clients and server machines.

• If using Oracle Names servers, the Oracle Connection Manager automatically updates the addresses in the Oracle Names servers, inserting the address for the Oracle Connection Manager into the existing addresses. In order for Oracle Names servers to send requests to Oracle Connection Manager, USE_CMAN=TRUE must be set in the SQLNET.ORA file on clients and machines where each Oracle Names server resides. To set this parameter, follow the steps in "Routing Connection Requests".

Figure 7-2 depicts a client using SPX to connect to an Oracle Connection Manager, and Oracle Connection Manager using TCP/IP to connect to a database server.

Figure 7-2 CMAN Parameter Configured to Use Multi-Protocol Support

cman= 
   (description= 
      (source_route=yes) 
      (address=
            (protocol=spx) 
            (service=cman) 
      ) 
      (address= 
            (protocol=tcp) 
            (host=sales-pc) 
            (port=1521) 
      ) 
      (connect_data= 
            (service_name=sales.com) 
      ) 
   ) 

TNSNAMES.ORA Element	Description
source_route=yes	Creates a source route of addresses through an Oracle Connection Manager to the destination database.
(address= (protocol=spx) (service=cman) )	This first address is from a client using SPX to the Oracle Connection Manager. From here, the Oracle Connection Manager connects to the service using TCP/IP through the listener.

Enabling Net8 Access Control

Oracle Connection Manager also includes a feature which you can use to control client access to designated servers in a TCP/IP environment. By specifying certain filtering rules, you may allow or restrict specific clients access to a server.

This feature requires the release 8.1 Oracle Connection Manager if there are release 8.1 services in the network.

Step 1: Configure Oracle Connection Manager

To configure the Oracle Connection Manager:

1. Create a CMAN.ORA file, if one does not already exist, in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows NT. The Net8 Assistant does not support configuration of CMAN.ORA.

2. If you do not want to use the default listening port 1630 for the CMGW process, add the following:

   cman=(address=(protocol=tcp)(host=anyhost)(port=port))
   
   

   See "CMGW" for further information about CMGW.

3. If you do not want to use the default listening port 1830 for the CMADMIN process, add the following:

   cman=(address=(protocol=tcp)(host=anyhost)(port=port))
   
   

   See "CMADMIN" for further information about CMGW.

4. Add a CMAN_RULES section with the following parameters:

   cman_rules= 
      (rule_list= 
           (rule= 
               (src=shost) 
               (dst=dhost) 
               (srv=service) 
               (act=accept | reject) 
           ) 
        )  
   

   Parameter	Description
   SHOST	source host name or IP address (client)
   DHOST	destination host name or IP address (server)
   SERVICE	SERVICE_NAME (obtained from the INITSID.ORA file) value of release 8.1 service or SID pre-8.1 service
   ACCEPT | REJECT	accept or reject the incoming requests based on the above three parameters.

   Multiple RULEs can be defined within the RULE_LIST. The action (ACT) in the first matched RULE is applied to the request. When CMAN_RULES exists, the Oracle Connection Manager adheres to the principle that which is not expressly permitted is prohibited. If the CMAN_RULES are not defined, then everything is permitted.

   The example below shows restriction to service SALES.COM for a client machine of CLIENT1-PC, and access to service DB1 for client 144.25.23.45.

   cman_rules= 
        (rule_list= 
         (rule=(src=client1-pc)(dst=sales-pc)(srv=sales.com)(act=reject)) 
         (rule=(src=144.25.23.45)(dst=144.25.187.200)(srv=db1)(act=accept)) 
        )
   

Step 2: Configure the Client

Client support is accomplished by setting the Oracle Connection Manager address and listener address through a TNSNAMES.ORA file or an Oracle Names server:

• If using a TNSNAMES.ORA file, the Oracle Connection Manager address and the SOURCE_ROUTE parameter must be set, which creates a source route of addresses through an Oracle Connection Manager to the destination database. To configure the local naming method's TNSNAMES.ORA file, follow the instructions in "Configuring the Client for Oracle Connection Manager Features" of this chapter and these tips:
  • Configure the client first with the address of the Oracle Connection Manager, using only TCP/IP.

  • Configure the client with the address of the listener, using a protocol available on the Oracle Connection Manager machine.

  • Configure the client with SOURCE_ROUTE=YES to creates a source route of addresses through a Connection Managers to the destination database.

• If using Oracle Names servers, the Oracle Connection Manager automatically updates the addresses in the Oracle Names servers, inserting the address for the Oracle Connection Manager into the existing addresses. In order for Oracle Names servers to send requests to Oracle Connection Manager, USE_CMAN=TRUE must be set in the SQLNET.ORA file on clients and machines where each Oracle Names server resides. To set this parameter, follow the steps in "Routing Connection Requests".

Configuring the Client for Oracle Connection Manager Features

Note: Oracle Corporation recommends not setting client load balancing or connect-time failover when using the Oracle Connection Manager, as the address list order has a specific order and meaning. When SOURCE_ROUTE is set, the first address is for the client connection to an Oracle Connection Manager and the second address is for the Oracle Connection Manager connection to a listener. Client load balancing and connect-time failover are disabled when SOURCE_ROUTE is set.

Note:: If more than one Oracle Connection Manager is used in the connection path, you cannot use Oracle Names to connect clients through it.

Configuring the client involves routing client connection requests you want concentrated to the database server through that a Connection Manager. This is achieved by setting the Oracle Connection Manager address through a TNSNAMES.ORA file or an Oracle Names server:

• If using Oracle Names servers, the Oracle Connection Manager automatically updates the addresses in the Oracle Names servers, inserting the address for the Oracle Connection Manager into the existing addresses. In order for Oracle Names servers to send requests to Oracle Connection Manager, USE_CMAN=TRUE must be set in the SQLNET.ORA file on machines where each Oracle Names server resides. To set this parameter, follow the steps in "Routing Connection Requests".

• If using a TNSNAMES.ORA file, the Oracle Connection Manager address and the SOURCE_ROUTE parameter must be set, which creates a source route of addresses through an Oracle Connection Manager to the destination database. To configure the local naming method's TNSNAMES.ORA file, follow these steps:

  Step 1: Configure an Oracle Connection Manager Address

  Step 2: Configure the Listener Address

Step 1: Configure an Oracle Connection Manager Address

To configure an Oracle Connection Manager address in TNSNAMES.ORA:

1. Start the Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Net Service Names folder in the directory tree.

3. Select Create from the Edit menu or click on the "+" button to create a new net service name. The Net Service Name Wizard starts.

4. Enter any name in the Net Service Name field, then click Next:

   
   

5. Select the protocol the CMGW process is configured to listen on, then click Next. By default this protocol is TCP/IP.

   
   

6. Enter network protocol information for the Oracle Connection Manager, then click Next. If you are using TCP/IP, the default port for UNIX operating systems is 1630.

   
   

   For further information about protocol parameters, see "Configuring Protocol Addresses".

7. If the destination database is release 8.1, click Oracle8 Version 8.1, enter a service name in the Service Name field, then click Next:

   
   

   The service name is typically the global database name. See "Setting Service Names and Instance Names" for further information about the service name string to use.

   If destination service is prior to release 8.1, click Oracle8 Version 8.0 or Previous, enter a SID in the Database SID field, then click Next.

8. Click Next.

   Note: Do not click Test, as the connection will fail at this point.

9. Click Finish to save your configuration and dismiss Net Service Name Wizard.

   The new net service name and the Oracle Connection Manager address is added to the Net Service Names folder and the TNSNAMES.ORA.

Step 2: Configure the Listener Address

After the Oracle Connection Manager address is specified, create an address for the listener, so the Oracle Connection Manager can connect to the server.

To configure the listener address in TNSNAMES.ORA:

1. Double-click the Net Service Names folder.

2. Click on the net service name you created in "Step 1: Configure an Oracle Connection Manager Address".

   Notice the Oracle Connection Manager address is displayed in the Address 1 tab:

   
   
3. Click "+".

   A new address tab displays.

4. Select the protocol, then enter protocol information for the listener. If you are using TCP/IP, the default port number is 1521:

   
   

   For further information about protocol parameters, see "Configuring Protocol Addresses".

5. Click Advanced in the Address Configuration group box.

   The Address List Options dialog box appears:

   
   
6. Click Use each address in order until destination reached to ON.

   This option creates tells the client to connect to the first address, the Oracle Connection Manager, and from the first address to the second address, the listener.

7. Click OK to dismiss the dialog box.

8. Choose Save Network Configuration from the File menu.

9. Choose Exit from the File menu to exit the Net8 Assistant.

   The listener address is added to the TNSNAMES.ORA file.

Enabling Connection Pooling

Connection pooling is a resource utilization feature that allows you to maximize the number of physical network connections to a multi-threaded server. This is achieved by sharing or pooling a dispatcher's set of connections among multiple client processes.

Verify that the destination server is configured as a multi-threaded server and that the connection pooling parameters are set. This is accomplished by setting the MTS_DISPATCHERS parameter in the database initialization file (INITSID.ORA) with the PROTOCOL, DISPATCHERS, POOL, and CONNECTIONS attributes.

For example:

mts_dispatchers="(protocol=tcp) (dispatchers=2) (pool=yes) (connections=2)"

Attribute	Description
CONNECTIONS (CON or CONN)	The maximum number of network connections to allow for each dispatcher. The default is 1022.
DISPATCHERS (DIS or DISP)	The initial number of dispatcher to start. The default is 1.
PROTOCOL (PRO or PROT)	The network protocol (TCP in the example above) for which the dispatcher will generate a listening end point.
POOL	If a number is specified, then connection pooling is enabled for both incoming and outgoing network connections and the number specified is the timeout in ticks for both incoming and outgoing network connections. If ON, YES, TRUE, or BOTH is specified, then connection pooling is enabled for both incoming and outgoing network connections and the default timeout of 10 will be used for both incoming and outgoing network connections.
TICKS	The size of a network tick in seconds. The default is 15 seconds. This parameter is optional for connection pooling.

For more information about configuring MTS, see Chapter 9, "Configuring Multi-Threaded Server".

Configuring Java Option Connections

The Java option in Oracle8i can be programmed in three different ways:

• Java Stored Procedures -- traditional database stored procedures, functions, triggers and object methods implemented in Java (or SQLJ)

• Enterprise Java Beans (EJBs) -- standard server-oriented Java components

• CORBA Servers -- standard CORBA 2.0 compliant servers implemented in Java.

EJBs and CORBA clients are invoked via the CORBA Internet Inter-Orb Protocol (IIOP) protocol.

Java Stored Procedures can run either in dedicated server mode or multi-threaded server (MTS) mode. EJBs and CORBA Servers run only in the MTS configuration. If you are primarily developing Java Stored Procedures, you may run them in the dedicated server configuration. If you are combining both EJBs and CORBA Servers along with Java stored procedures in a single application, you may configure your database to support EJBs and CORBA Servers in an MTS configuration and support stored procedures in dedicated server configuration.

If your network requires configuration of Java Stored Procedures in dedicated server mode and EJBs or CORBA Servers in MTS mode, see "Configuring Both Multi-Threaded Server and Dedicated Server Modes".

This section covers the following topics:

• Java Stored Procedure Configuration

• Enterprise JavaBeans and CORBA Configuration

• Using the Default Configuration of Oracle8i for EJBs and CORBA through the Listener

• Using a Non-Default Configuration

• Using SSL with EJBs and CORBA

Java Stored Procedure Configuration

To configure the database to run Java Stored Procedures only, you must decide whether you want the database to run in dedicated server mode or MTS mode. If you are only planning to use Java stored procedures in dedicated server mode, you need to configure the database and clients, as described in the Oracle8i Java Stored Procedures Developer's Guide.

If you want to run Java Stored Procedures in MTS mode, you need to go through the steps associated with configuring the server for MTS mode with the MTS_DISPATCHERS parameter, as described in Chapter 9, "Configuring Multi-Threaded Server".

Enterprise JavaBeans and CORBA Configuration

In configuring Oracle8i for Enterprise JavaBeans and CORBA Servers, you need to be aware of the following issues:

• IIOP Clients

• Session-Based IIOP and Configuration Issues

• Access through Listeners vs. Dispatchers (Connection Load Balancing)

• SSL Support with CORBA and EJB

IIOP Clients

Clients access EJBs and CORBA Servers in the database via the Inter-Orb Protocol (IIOP) protocol. To support IIOP, the database must be configured in MTS mode with the General Inter-Orb Protocol (GIOP) presentation protocol. (IIOP is an implementation of GIOP over TCP/IP). Oracle8i provides a GIOP service implementation. The Oracle8i Java VM is a session-oriented Java VM. This means that each session in the database effectively gets its own VM as a private server. The Java VM, ORB, and database presentation layers are modeled to allow CORBA communication from multiple clients to EJBs and CORBA Servers running in the same or different sessions. For more information, see the Oracle8i Enterprise JavaBeans and CORBA Developer's Guide.

Session-Based IIOP and Configuration Issues

To support Oracle8i's session-oriented behavior, the GIOP facilities in the database have been structured to support two presentation protocols. Depending on which presentation you want to use, you need to choose the appropriate presentation handler:

• oracle.aurora.server.SGiopServer is provided for session-based IIOP connections. EJBs and CORBA are distinguished based on the session in which they live in addition to the standard IIOP semantics. Session-based IIOP is far more scalable than standard IIOP connections. Oracle Corporation recommends you use session-based IIOP connections. (Default)

• oracle.aurora.server.GiopServer for regular IIOP connections

To support IIOP, the appropriate presentation must be specified in the PRESENTATION attribute of the MTS_DISPATCHERS parameter. To handle session-based IIOP (which is the default behavior), oracle.aurora.server.SGiopServer is registered as the presentation handler in the PRESENTATION attribute of the MTS_DISPATCHERS parameter.

For more information about presentations and session IIOP, see the Oracle8i Enterprise JavaBeans and CORBA Developer's Guide.

Access through Listeners vs. Dispatchers (Connection Load Balancing)

Finally, EJB and CORBA clients that communicate with the database via IIOP can communicate with the database either by accessing a dispatcher directly or accessing it via a listener. There are benefits and trade-offs to both approaches.

• Access through a listener

  For scalability, clients may connect to the Java option through the listener. The 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 not just listen on a port for the TTC protocol but to also handle GIOP/and session-based GIOP connections. The listener load balances client requests among the dispatchers. While this configuration is more complex, it can also scale easily to support more than 1,000 concurrent connections.

• Access a dispatcher directly

  The dispatcher is configured with the a well-known port number. The client uses this port number to connect directly to the dispatcher. This configuration has an easy setup, but scalability may become an issue if you need to support more than 1,000 concurrent connections.

Oracle Corporations recommends access through a listener.

SSL Support with CORBA and EJB

Oracle8i also supports the use of authentication data such as certificates and private keys required for use by SSL in combination with both types of GIOP protocols-- regular GIOP and session-based GIOP. To use SSL with GIOP, you need to carry out two steps:

1. Configure the listeners and dispatchers to accept SSL by specifying TCPS as the protocol in the listener's address list.

2. Specify the SSL wallet to be used when configuring both the listener and dispatcher. For more information see "Using SSL with EJBs and CORBA".

Using the Default Configuration of Oracle8i for EJBs and CORBA through the Listener

During a Typical or Minimal installation of the server, or if you choose the Java VM Option using the Oracle Database Configuration Assistant, MTS will be configured automatically for session-based IIOP connections through the listener using TCP/IP.

The INITSID.ORA file is configured in the following manner:

mts_dispatchers="(protocol=tcp)(presentation=oracle.aurora.server.SGiopServer)"

The default attributes are described in the table below:

Parameter	Description
PROTOCOL (PRO or PROT)	Specifies the TCP/IP protocol, which the dispatcher will generate a listening end point.
PRESENTATION (PRE or PRES)	Enables support of GIOP. Valid values for GIOP presentation values include: oracle.aurora.server.SGiopServer for session-based GIOP dispatcher connections. This presentation is valid for TCP/IP and TCP/IP with SSL. oracle.aurora.server.GiopServer for standard GIOP dispatcher connections. This presentation is valid for TCP/IP and TCP/IP with SSL. See the Oracle8i Enterprise JavaBeans and CORBA Developer's Guide for further information.

The LISTENER.ORA file is configured in the following manner:

listener=
  (description_list=
   (description=
      (address_list=
        (address=(protocol=tcp)(host=sales-pc)(port=1521))
      )
   )
   (description=
      (protocol_stack=
        (presentation=giop)
        (session=raw)
      )
      (address_list=
        (address=(protocol=tcp)(host=sales-pc)(port=2481))
      )
   )
  )

LISTENER.ORA Element	Description
PROTOCOL_STACK	Identifies the presentation and session layer information for a connection.
(PRESENTATION=GIOP)	Identifies a presentation of GIOP for IIOP clients. GIOP supports both oracle.aurora.server.SGiopServer or oracle.aurora.server.GiopServer using TCP/IP.
(SESSION=RAW)	Identifies the session layer. There is no session-layer for IIOP clients.
(ADDRESS=...)	Specifies a listening address that uses TCP/IP on port 2481.

Using a Non-Default Configuration

If you are unable to use the default configuration, you can configure IIOP connections to the Java option through the listener or directly to the dispatcher with your own settings. This section covers the following topics:

• Non-Default Configuration for Access through a Listener

• Configuring a Non-Default Listener

• Configuration to Access a Dispatcher Directly

Non-Default Configuration for Access through a Listener

To configure IIOP client connections to the Java option through a listener, follow these steps:

Step 1: Enable MTS and Configure IIOP in the INITSID.ORA File

Step 2: Configure the Listener

Step 3: Configure Clients

Step 1: Enable MTS and Configure IIOP in the INITSID.ORA File

MTS must be configured in the INITSID.ORA file in the following manner:

mts_dispatchers="(protocol=tcp | tcps)
(presentation=oracle.aurora.server.SGiopServer | 
oracle.aurora.server.GiopServer)"

The attributes are described below:

Parameter	Description
PROTOCOL (PRO or PROT)	Specifies the TCP/IP or TCP/IP with SSL protocol, which the dispatcher will generate a listening end point for. Valid values: TCP (for TCP/IP) or TCPS (for TCP/IP with SSL)
PRESENTATION (PRE or PRES)	Enables support for GIOP. Valid values for GIOP presentation values include: oracle.aurora.server.SGiopServer for session-based GIOP dispatcher connections. This presentation is valid for TCP/IP and TCP/IP with SSL. oracle.aurora.server.GiopServer for standard GIOP dispatcher connections. This presentation is valid for TCP/IP and TCP/IP with SSL. See the Oracle8i Enterprise JavaBeans and CORBA Developer's Guide for further information.

Step 2: Configure the Listener

Use the Net8 Assistant to modify any of the listener settings:

1. Start Net8 Assistant.
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Double-click on the Listeners folder.

3. Click on a listener.

4. Choose Listening Locations from the drop-down list box.

   
   

5. Choose TCP/IP or TCP/IP with SSL from the Protocol drop-down menu.

6. Enter the host name of the database in the Host field.

7. Enter port 2481 if chosen protocol is TCP/IP in the Port field, or enter port 2482 if the chosen protocol is TCP/IP with SSL in the Port field.

   If you do not use port 2482 or 2483, follow the procedure in "Configuring a Non-Default Listener".

8. Choose IIOP Client from the Client drop-down list box.

9. Choose Save Network Configuration from the File menu.

10. Choose Exit from the File menu to exit the Net8 Assistant.

Step 3: Configure Clients

Use port number 2481 for TCP/IP or 2482 for TCP/IP with SSL for IIOP presentations. See the Oracle8i Enterprise JavaBeans and CORBA Developer's Guide documentation for further information.

Configuring a Non-Default Listener

In addition to the steps described in "Non-Default Configuration for Access through a Listener", perform the following steps for a non-default listener:

• Step 1: Configure Additional INITSID.ORA Configuration

• Step 2: Resolve the Listener Name

Step 1: Configure Additional INITSID.ORA Configuration

The non-default listener must be configured in the INITSID.ORA. How it is configured depends upon whether it is a local listener or a remote listener. Both scenarios are described in this section.

Local Listener

If you want the connection to go through a non-default local listener, INITSID.ORA must also be configured with the LOCAL_LISTENER parameter or the MTS_DISPATCHERS parameter's LISTENER attribute.

Note: The Oracle Database Configuration allows you to configure the LISTENER attribute. LOCAL_LISTENER must be configured manually.

LOCAL_LISTENER parameter configuration is shown below:

local_listener=local_listener_name
mts_dispatchers="(protocol=tcp | tcps)
(presentation=oracle.aurora.server.SGiopServer | 
oracle.aurora.server.GiopServer)"
MTS_DISPATCHERS parameter's LISTENER attribute configuration is shown 
below:

mts_dispatchers="(protocol=tcp | tcps)
(presentation=oracle.aurora.server.SGiopServer | 
oracle.aurora.server.GiopServer)(listener=local_Listener_name)"

Parameter	Description
LISTENER (LIS or LIST)	Specifies the network name of the listener with which the dispatchers will register. It should be set to a name which is resolved through a naming method.

Remote Listener

If you want the connection to go through a remote listener, INITSID.ORA must be also configured with the MTS_DISPATCHERS parameter's LISTENER attribute:

mts_dispatchers="(protocol=tcp | tcps)
(presentation=oracle.aurora.server.SGiopServer | 
oracle.aurora.server.GiopServer)(listener=remote_listener_name)"

Parameter	Description
LISTENER (LIS or LIST)	The network name of the listener with which the dispatchers will register. It should be set to a name which is resolved through a naming method. This attribute should be only specified if the listener is at a remote location or is in another Oracle home. The LISTENER attribute makes it easier to administer multi-homed hosts.

Step 2: Resolve the Listener Name

In order for the dispatcher to register its information with a non-default listener, the listener name you specified for the LOCAL_LISTENER parameter or the MTS_DISPATCHERS parameter's LISTENER attribute must be resolved through a naming method, such as a TNSNAMES.ORA on the server or an Oracle Names server.

The entry should only contain the address of the listener, not the service name information in the CONNECT_DATA portion.

Configuring a TNSNAMES.ORA File

The Net8 Assistant does not allow you to configure a TNSNAMES.ORA without the CONNECT_DATA information. Therefore, Oracle Corporation recommends you create the TNSNAMES.ORA manually. For example, if you configured a listener named LISTENER1 with TCP/IP on port 2481, the entry in the TNSNAMES.ORA would look similar to the entry below:

listener1.us.oracle.com= 
(description= 
  (address= 
     (protocol= tcp)
     (host= sales-pc) 
     (port= 2481)
  )

)

Multiple addresses are supported, but multiple address connect-time failover and client load balancing features are not supported. Oracle Connection Manager's SOURCE_ROUTE parameter is supported.

Configuring an Oracle Names Server

An entry for the listener can be made through an Oracle Names server through the Net8 Assistant:

1. Start Net8 Assistant:
   • On UNIX, run netasst at $ORACLE_HOME/bin.

   • On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Select the Oracle Names Servers folder.

3. Click on an Oracle Names server.

4. Select Manage Data from the drop-down list box.

5. Select the Advanced tab:

6. Click Add, and enter the listener name in the Name field, A.SMD record type in the Type field, and enter the address in the Value field, such as:

   (address=(protocol= tcp)(host= sales-pc)(port= 2481))
   
   

7. Choose Save Network Configuration from the File menu.

8. Choose Exit from the File menu to exit the Net8 Assistant.

Configuration to Access a Dispatcher Directly

To configure IIOP client connections to the Java option through a dispatcher, follow these steps:

• Step 1: Enable MTS and Configure IIOP in the INITSID.ORA File

• Step 2: Configure Clients

Step 1: Enable MTS and Configure IIOP in the INITSID.ORA File

MTS must be configured in the INITSID.ORA file in the following manner:

mts_dispatchers="(address=(protocol=tcp | tcps)(host=server_
host)(port=port))(dispatchers=1)(presentation=oracle.aurora.server.SGiopServer | 
oracle.aurora.server.GiopServer)"

The attributes are described below:

Parameter	Description
ADDRESS (ADD or ADDR)	Specifies the network address that the dispatchers will listen on. The network address may include either the TCP/IP (TCP) or the TCP/IP with SSL (TCPS) protocol, the host name of the server, and a GIOP listening port, which may be any port you choose that is not already in use.
DISPATCHERS (DIS or DISP)	The initial number of dispatchers to start.
PRESENTATION (PRE or PRES)	Enables support for GIOP. Valid values for GIOP presentation values include: oracle.aurora.server.SGiopServer for session-based GIOP dispatcher connections. This presentation is valid for TCP/IP and TCP/IP with SSL. oracle.aurora.server.GiopServer for standard GIOP dispatcher connections. This presentation is valid for TCP/IP and TCP/IP with SSL. See the Oracle8i Enterprise JavaBeans and CORBA Developer's Guide for further information.

Step 2: Configure Clients

Configure the same port on the client as you used to configure MTS to access the dispatcher directly. See the Oracle8i Enterprise JavaBeans and CORBA Developer's Guide for further information.

Using SSL with EJBs and CORBA

Oracle8i also supports the use of authentication data such as certificates and private keys required for use by SSL in combination with both types of GIOP protocols - regular GIOP and session-based GIOP. To use SSL with GIOP, you need to carry out two steps:

1. Configure the listeners and dispatchers to accept SSL by specifying TCPS as the protocol.
   • If you want clients to access the database through the listener, follow the procedures in "Non-Default Configuration for Access through a Listener".

   • If you want clients to access the database through a dispatcher directly, follow the procedures in "Configuration to Access a Dispatcher Directly". Optionally, you can uncomment the following lines in the INITSID.ORA file that the Oracle Database Configuration Assistant creates for session-based IIOP and regular IIOP for TCP/IP with SSL:

     #mts_dispatchers="(address=(protocol=tcp)(host=server_host)(port=5555)) 
     (dispatchers=1) (presentation=oracle.aurora.server.SGiopServer)"
     #mts_dispatchers="(address=(protocol=tcp)(host=server_host)(port=5556)) 
     (dispatchers=1) (presentation=oracle.aurora.server.GiopServer)"
         
     
              

     If you uncomment these lines, ensure the client is configured with same port number.

2. Specify the SSL wallet to be used by setting the SQLNET.ORA parameters as follows for both the listener and the dispatcher.
   • To configure the listener you specify:

     ssl_client_authentication=false 
     ssl_version=undetermined 
     
     

   • To configure the dispatcher, you specify:

     oss.source.my_wallet=  
        (source=
           (method=file)
           (method_data=  
             (directory=wallet_location)))
     

See the Oracle Advanced Security Administrator's Guide for further information about configuring the SSL wallet.

Configuring Non-Oracle Database Services

Net8 supports connections to non-Oracle database services, including:

• Configuring Net8 for External Procedures

• Configuring Net8 for Oracle Heterogeneous Services

• Configuring Net8 for an Oracle Rdb Database

Configuring Net8 for External Procedures

The network listener may also be statically configured to listen for External Procedure Calls. When a PL/SQL or SQL application calls an external procedure, the Net8 network listener launches a network 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.

External procedures are configured by default after installation.

For environments where the external procedure information does not exist, edit the LISTENER.ORA and TNSNAMES.ORA files, located in $ORACLE_HOME/network/admin on UNIX and ORACLE_HOME\network\admin on Windows platforms, as follows:

1. Configure either a TCP/IP or IPC listener address. For example:

   listener=
     (address=
        (protocol=ipc)
        (key=extproco0) 
      )
   

   For more information about configuring listener protocol addresses, see "Configuring Listener Protocol Addresses".

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

   sid_list_listener_name
     (sid_list=
       (sid_desc=                        
        (sid_name=plsextproc)
        (oracle_home=d:\orant)
         (program=extproc)                                                     
      )
     ) 
   

   Parameter	Description
   SID_NAME	external procedure identifier
   ORACLE_HOME	location of program executable
   PROGRAM	external procedure program name

   For more information about configuring listener protocol addresses, see "Configuring a Listener with Service Information".

3. Add a net service name description entry for EXTPROC in the server's TNSNAMES.ORA file, using SID rather than SERVICE_NAME in the CONNECT_DATA section. For example:

   extproc_connection_data=                  
    (description=                           
      (address=(protocol=ipc)(key=extproc0))                      
                     
      (connect_data=
       (sid=plsextproc)) 
      ) 
   

   For more information about creating a net service name, see "Configuring the Network with the Local Naming Method".

Configuring Net8 for Oracle Heterogeneous Services

Heterogeneous Services is an integrated component within the Oracle8i server, and provides the generic technology for accessing non-Oracle systems from the Oracle server. Heterogeneous Services enables you to:

• Use Oracle SQL to transparently access data stored in non-Oracle systems as if the data resides within an Oracle server.

• Use Oracle procedure calls to transparently access non-Oracle systems, services, or application programming interfaces (APIs), from your Oracle distributed environment.

While Heterogeneous Services provides the generic technology in the Oracle8i server, a Heterogeneous Services agent is required to access a particular non-Oracle system.

To initiate a connection to the non-Oracle system, the Oracle8i server starts an agent process through the Net8 listener on the gateway. For the Oracle8i server to be able to connect to the agent, perform the following steps:

1. On the Oracle8i database, set up a net service name to connect to the listener on the gateway. The connect descriptor must also include the HS=OK clause to make sure the connection uses Heterogeneous Services:
   1. Start the Net8 Assistant:

      -On UNIX, run netasst at $ORACLE_HOME/bin.

      -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

   2. Create a net service name that will be used for connections from the Oracle8i server to a non-Oracle system.

      See "Step 1: Configure Net Service Names".

   3. Double-click on the Net Service Names folder in the directory tree.

   4. Select the net service name.

   5. Click Advanced in the Service Identification group box.

      The Advanced Service Options dialog box appears:

      
      
   6. Click Use for Heterogeneous Service, then click OK.

   7. Choose Save Network Configuration from the File menu.

      The TNSNAMES.ORA file is re-created.

      In the example below, a net service names in a TNSNAMES.ORA is configured for heterogeneous services:

      megabase6_sales=
        (description=
          (address=
             (protocol=tcp)
             (host=dlsun206)
             (port=1521)
          )
          (connect_data= 
           (service_name=sales6)
           (hs=ok) 
          ) 
        ) 
      

2. The listener on the gateway must be set up to listen for incoming requests from the Oracle8i server, and spawn heterogeneous services agents. The LISTENER.ORA file must be modified to set up the listener to start heterogeneous services agents, and the listener must be (re-)started. The features that must be set in the LISTENER.ORA include:

   Net8 Assistant option	LISTENER.ORA Parameter	Description
   Program Name	PROGRAM	Defines the name of the agent executable.
   Oracle Home	ORACLE_HOME	The location of the agent executable. The agent executable must reside in the $ORACLE_HOME/bin directory.
   SID	SID_NAME	Specifies the Oracle System Identifier (SID) for the non-Oracle database.

   To provide a listener with a new name use the Net8 Assistant:

   1. From the Net8 Assistant, double-click on the Listeners folder.

   2. Click on a listener.

   3. Choose Other Services from the drop-down list box.

   4. Click Add Service:

      
      

   5. Enter the program name that gets executed to create a gateway, the Oracle home for the executable, and the SID or service name of the non-Oracle system.

   6. Choose Save Network Configuration from the File menu.

      The LISTENER.ORA file is re-created.

      An excerpt of a LISTENER.ORA file configured for heterogeneous service in the SID_LIST_listener_name section is shown below:

      
           
      sid_list_listener=(sid_list=
       (sid_desc=
        (sid_name=salesdb)
        (oracle_home=/home/oracle/megabase/8.1.5)
        (program=tg4mb80)
        )
       )
      
               

   7. Choose Exit from the File menu.

      The Net8 Assistant application exits.

For more information about Heterogeneous Services, see Oracle8i Distributed Database Systems.

Configuring Net8 for an Oracle Rdb Database

Oracle Rdb is a database for Digital's 64-bit platforms. With Net8, Oracle Rdb servers appears the same way to clients as Oracle8i databases. Because Oracle Rdb has its own listener, the client interacts with Rdb in the same manner as it does with Oracle7.

To initiate a connection to an Oracle Rdb, set up a net service name to connect to the Oracle Rdb database using the following features:

Net8 Assistant option	TNSNAMES.ORA Parameter	Description
RDB Database	RDB_DATABASE	Specifies the file name of an Oracle RDB database. Embed this parameter in the CONNECT_DATA section.
Type of Service	TYPE_OF_SERVICE	Specifies the type of service to use for an Oracle RDB database. It is used by Rdb interface tools. This feature should only be used if the application supports both an Oracle Rdb and Oracle database, and you want the application to randomly choose (load balance). Embed this parameter in the DESCRIPTION.
Global Database Name	GLOBAL_NAME	An optional feature, it identifies the Oracle Rdb database. Embed this parameter in the CONNECT_DATA section.

For further configuration information, see your Oracle Rdb documentation.

To configure a client for an Oracle Rdb database, use the Net8 Assistant:

1. Start the Net8 Assistant:

   -On UNIX, run netasst at $ORACLE_HOME/bin.

   -On Windows NT, choose Start > Programs > Oracle - HOME_NAME > Network Administration > Net8 Assistant.

2. Create a net service name that will be used for connections from the client to the Oracle Rdb.

   "Step 1: Configure Net Service Names".

3. Double-click on the Net Service Names folder in the directory tree.

4. Select the net service name.

5. Click Advanced in the Service Identification group box.

   The Advanced Service Options dialog box appears:

   
   
6. Enter the file name of an Oracle RDB database in the Rdb Database field.

7. Optionally, enter the global database name in the Global Database Name field, and, if needed, specify the type of service in the Type of Service field, then click OK.

8. Choose Save Network Configuration from the File menu.

   The TNSNAMES.ORA file is re-created.

In the example below, a net service name in a TNSNAMES.ORA is configured for an Oracle Rdb database:

alpha5=
  (description=
    (address= ...)
    (connect_data= 
      (service_name=generic)
      (rbd_database= [.mf]mf_personnel.rdb)
     (global_name= alpha5)))
    

        

In the example below, TYPE_OF_SERVICE is used to load balance between an Oracle Rdb database service or Oracle8i database service:

alpha5=
 (description_list=
  (description=
    (address= ...)
    (connect_data= 
     (service_name=generic)
     (rbd_database= [.mf]mf_personnel.rdb)
     (global_name= alpha5)))
 (description=
   (address= ...)
    (connect_data= 
     (service_name=sales.com))
    (type_of_service=oracle8_database))

---