1.1.2 Understanding Manageability

Oracle Net Services offers several manageability features to configure and manage networking components.

• About Service Name and Location Transparency
  Each database is represented by one or more services. A service is a program that responds to requests from various clients or performs some operation.
• About Centralized Configuration and Management
  To manage large networking environments, administrators can access a centralized repository to specify and modify the network configuration.
• About Quick Installation and Configuration
  Networking elements for the Oracle Database server and clients are preconfigured for most environments.

1.1.2.1 About Service Name and Location Transparency

Each database is represented by one or more services. A service is a program that responds to requests from various clients or performs some operation.

A service is identified by a service name, for example, sales.us.example.com. A client uses a service name to identify the database it must access. The information about the database service and its location in the network is transparent to the client because the information needed for a connection is stored in a repository.

The repository is represented by one or more naming methods. A naming method is a resolution method used by a client application to resolve a connect identifier to a connect descriptor when attempting to connect to a database service. Oracle Net Services offers several naming methods that support localized configuration on each client, or centralized configuration that can be accessed by all clients in the network.

For example, in the following figure, a company has three databases that clients can access. Each database has a distinct service name, such as sales.us.example.com, hr.us.example.com, and mktg.us.example.com.

1. The client uses the repository to find the information it needs for sales.us.example.com.

2. After the client has the information it needs, it connects to the database.

Figure 1-6 Service Information Repository

Description of "Figure 1-6 Service Information Repository"

1.1.2.2 About Centralized Configuration and Management

To manage large networking environments, administrators can access a centralized repository to specify and modify the network configuration.

You can store the Oracle Net Services configuration in one of the following centralized repositories:

• LDAP-Compliant Directory Server

  Support of LDAP-compliant directory servers provides a centralized vehicle for managing and configuring a distributed Oracle network. The directory can act as a central repository for all information about database network components, user and corporate policies, and user authentication and security, thus replacing client-side and server-side localized configuration files. All computers on the network can refer to the directory for information.

  When using the LDAP directory server, you can choose to specify LDAP parameters either in external configuration files (ldap.ora and sqlnet.ora) or directly in the connect identifier.

  The following diagram shows clients, Oracle Database servers, and other servers (such as application web servers) connecting to a centralized directory server:

  Figure 1-7 Centralized Storage of Network Configuration with a Directory Server

  
  Description of "Figure 1-7 Centralized Storage of Network Configuration with a Directory Server"

• Centralized Configuration Provider

  You can centralize connect descriptors and optionally database credential references in a Centralized Configuration Provider, such as Azure App Configuration store or Oracle Cloud Infrastructure (OCI) Object Storage as a JSON file.

  This naming method stores network service names and addresses in a single location, facilitating administration (addition, deletion, or modification) of connect descriptors. This also enables you to centrally manage password change policies for all stored database user names and passwords.

1.1.2.3 About Quick Installation and Configuration

Networking elements for the Oracle Database server and clients are preconfigured for most environments.

The Easy Connect naming method is enabled by default, and does not require a repository. Clients connect using the hostname of the database. As a result, clients and servers are ready to connect out-of-the-box using Easy Connect, giving users the benefits of distributed computing.