Oracle7 Server Distributed Systems Volume I: Distributed Data
Using Network Manager to Configure Your Network
You can configure the following network components, or network objects, in Network Manager:
- MultiProtocol Interchanges
- Oracle Transparent Gateways
- SQL*Net version 1 connect strings
You will find complete instructions for using Network Manager in the Oracle Network Manager Administrator's Guide.
There are three major steps to configuring a network using Network Manager.
1. Create a network definition using Network Manager property sheets. This procedure is described in the Oracle Network Manager Administrator's Guide. Use the online help to get detailed information about using the property sheets as you use Network Manager.
The three part process is illustrated in Figure 3 - 5.
Figure 3 - 5. Configuration Process
Know Your Network
To use Network Manager effectively, you must have detailed information about the network at hand. This section describes the information you must have ready.
Network Manager knows the syntax of the configuration files, and it knows the default values for parameters in those files. However, it knows nothing about your network until you supply that information. In fact, supplying accurate information to the utility is your main task in using it.
Names
Choose names for the following:
- all network listeners, and the computers (nodes) on which they run
- all databases, to act as database service names. Service names are short identifiers for their connect descriptors
Note: With SQL*Net release 2.1 and the Oracle Server release 7.1 and later, the service names you provide must match precisely the unique global database names assigned by the database administrator. To achieve this, it may be necessary to change some of the service names you have been using.
For example, if your previously defined SQL*Net version 2 network has service names that do not match the global database names, those service names must be changed. Similarly, if the network includes some databases that were named before you established your current domain names, their global database names and service names must reflect the current domain structure.
- all MultiProticol Interchange nodes (if any)
- all Names servers, if any, and the node(s) on which they run
- all client profiles (A client profile, or client type is a group of clients with the same communication requirements.)
Even if you have a single-protocol network (a single-community network), you must supply a name for that community.
Addresses
Define addresses for the following:
- all MultiProtocol Interchanges (if any)
- all Oracle Names servers (if any)
The addresses for these components consist of the names of
the communities of which they are a part and any protocol-
specific information.
Protocol-Specific Information
Different protocols require different protocol-specific information. The following table summarizes the keywords for the protocols currently supported in a TNS network.
| Protocol
| Keywords
|
| AppleTalk
| SERVICE
|
| TCP/IP
| HOST
PORT
|
| DECnet
| NODE
OBJECT
|
| SPX/IPX
| SERVICE
|
| NetBIOS
| NTBNAME
|
| Named Pipes
| PIPE
SERVER
|
| Banyan
| ITEM GROUP
ORGANIZATION
|
| DCE
| SERVER_PRINCIPAL
SERVICE
CELL_NAME
|
| OSI4
| NSAP
TSEL
or
HOST
SERVICE
|
| LU6.2/APPC
| LU_NAME
LOCAL_LOOKUP
TP_NAME
|
| ASYNC
| PHONENUMBER
ASYNC_SERVER
LOCAL_LOOKUP
|
Table 3 - 1. Protocol-Specific Keywords
Additional Information: Network Manager provides
default values for many of these protocol-specific keywords. See your Oracle operating system-specific documentation
for information on what values to supply for the
protocol keywords.
Connect Data
Servers also require that you provide the system identifiers (SIDs) for their databases.
SQL*Net Version 1 Connect Strings
If your network includes both SQL*Net versions 1 and 2, have available the names of the files that hold the version 1 connect strings and their aliases. Know where in the file system they are stored.
LISTENER.ORA Parameter File
The LISTENER.ORA file includes a number of required and optional parameters that describe the listener. You should gather the parameter information and have it ready to use with Network Manager.
MultiProtocol Interchange Information
Network Manager creates configuration files specific to the MultiProtocol Interchanges in your network, if any, based on information you supply. The configuration files are described in the Oracle MultiProtocol Interchange Administrator's Guide.
Names Servers
If you are using Oracle Names, Network Manager creates a NAMES.ORA configuration file for each of the Names servers in your network. See the Oracle Names Administrator's Guide for information about this file.
Multiple Network Managers
If your network includes Oracle Names, you may want to provide further information about the naming structure of your network. You may want to include delegated administrative regions, so that widely separated parts of your network have some autonomy in their administration. See the Oracle Names Administrator's Guide for
more information.
Database Links
If you are using Oracle Names, you may also want to include information about global database links. See "Entering Component Information" in the Oracle Network Manager Administrator's Guide.
Using Network Manager with Oracle Names
If you are creating a new network, you may need to store the network definition in a file, create and distribute the configuration files, and start the network. Once the network is up, you can then store the network definition in the database used by Oracle Names.