Oracle9i Net Services Administrator's Guide Release 1 (9.0.1) Part Number A90154-01 |
|
This chapter describes how to configure client and server configuration parameters in profiles. A profile is a collection of parameters that specifies preferences for enabling and configuring Oracle Net features on the client or database server. A profile is stored and implemented through the sqlnet.ora
file.
This chapter contains these topics:
You can use a profile to:
Oracle Universal Installer launches Oracle Net Configuration Assistant after software installation on the client and server. Oracle Net Configuration Assistant configures the following:
The computer's network domain is automatically selected as the default domain. This domain is appended to any unqualified net service name given in the connect string, and then compared to net service names stored in a tnsnames.ora
file or Oracle Names server. For example, if the client tnsnames.ora
file contains a net service name of sales.us.acme.com
, the user can enter the following connect string:
CONNECT scott/tiger@sales
sales
gets searched as sales.us.acme.com
.
Configuration with the Oracle Net Configuration Assistant during installation results in the following entries in the sqlnet.ora
file:
NAMES.DEFAULT_DOMAIN=us.acme.com
NAMES.DIRECTORY_PATH=(onames, tnsname
s)
NAMES.DEFAULT_DOMAIN
specifies the network domain, and NAMES.DIRECTORY_PATH
specifies the priority order of the naming methods to use to resolve connect identifiers.
If the installed configuration is not adequate, you can use Oracle Net Manager to enhance the sqlnet.ora
configuration.
The following sections describe available client configuration options:
In environments where the client often requests names from a specific domain, it is appropriate to set a default domain in the client sqlnet.ora
file with the NAMES.DEFAULT_DOMAIN
parameter.
When a default domain is set, it is automatically appended to any unqualified net service name given in the connect string, and then compared to net service names stored in a tnsnames.ora
file or Oracle Names server.
For example, if the client tnsnames.ora
file contains a net service name of sales.us.acme.com
, the user can enter the following connect string:
CONNECT scott/tiger@sales
In this example, sales
gets searched as sales.us.acme.com
.
If the connect string includes the domain extension, such as in CONNECT scott/tiger@sales.us.acme.com
, the domain is not appended. If a net service name in a tnsnames.ora
file or Oracle Names server is not domain qualified and this parameter is set, the net service name must be entered with a dot ("."). For example, if domain is set to us.acme.com
and the client tnsnames.ora
file contains a net service name of sales
, the user would enter the following connect string:
CONNECT scott/tiger@sales.
To specify a default domain:
The sqlnet.ora
file should contain an entry that looks like the following:
NAMES.DEFAULT_DOMAIN
=us.acme.com
After naming methods are configured, as described in Chapter 9, "Configuring Naming Methods" 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 specify the order of naming methods:
Table 11-1 describes the naming method values listed in the Methods tab.
Table 11-1 Naming Method Values
Naming Method Value | Description |
---|---|
TNSNAMES |
Net service names are resolved using the See Also: "Configuring the Local Naming Method" |
LDAP |
Net service names and database service names are resolved through a directory server. |
ONAMES |
Net service names and database service names are resolved centrally through an Oracle Names server. See Also: "Configuring the Oracle Names Method" |
HOSTNAME |
Net service names are resolved using the host naming method. Certain criteria must be met to use host naming. See Also: "Configuring the Host Naming Method" |
|
This naming method is available with Oracle Advanced Security. |
|
Service information is resolved through an existing NIS. See Also: "Configuring NIS" |
The selected naming methods move to the Selected Methods list.
The sqlnet.ora
file updates with the NAMES.DIRECTORY_PATH
parameter:
NAMES.DIRECTORY_PATH=(ldap, tnsnames)
Clients and servers acting as clients can be configured so connection requests are directed to a specific process at all times. Table 11-2 describes the sqlnet.ora
file settings that you can set to route connection requests.
To route connection requests:
You can configure the sqlnet.ora
file to allow access to some clients and deny access to others. Table 11-3 describes the available settings.
To configure database access control:
Table 11-4 describes the advanced sqlnet.ora
file settings that you can set.
To set advanced features for clients:
If you are using Oracle Names as a naming method, you can specify the name and address of preferred Oracle Names servers to take precedence over any other available Oracle Names server addresses. Oracle Net routes name resolution requests to each preferred Oracle Names Server until a response is received.
Preferred Oracle Names servers are an alternative to using the Discover Oracle Names Servers command in Oracle Net Manager or using the Oracle Names Control utility REORDER_NS
command. These commands create 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 during the discovery process. Once you have initially discovered an Oracle Names server, you may want to delete preferred Oracle Names servers.
See Also:
|
To specify a preferred Oracle Names server:
A Preferred Server tab appears.
The sqlnet.ora
file updates with the NAMES.PREFERRED_SERVERS
parameter:
NAMES.PREFERRED_SERVERS= (ADDRESS=(PROTOCOL=tcp)(HOST=namesrv1)(PORT=1575))
Configure required client parameters needed for external naming methods, including Cell Directory Services (CDS) and Network Information Service (NIS), in the profile. Table 11-5 describes the sqlnet.ora
file external naming settings that you can set.
To configure external naming method parameters:
Oracle Advanced Security enables data encryption and integrity checking, enhanced authentication, single sign-on, and support for Distributed Computing Environment (DCE). Oracle Advanced Security also provides centralized user management on LDAP-compliant directory servers and certificate-based single sign-on; this functionality relies on the Secure Sockets Layer (SSL).
To configure a client or server to use Oracle Advanced Security features:
Each Oracle Advanced Security tab page enables you to configure a separate set of parameters.
See Also:
|
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|