Oracle Network Manager Administrator's Guide

Library

Product

Contents

Index

Quick Steps to Configure a Network

Sample Networks
A Single Protocol for All Clients and Servers
Two Communities with One Interchange
A Network with Oracle Names

This chapter shows you the simplest possible way to create the most common networks. It shows you the property sheets to use and the basic information you must provide in them. It accepts all defaults; that is, it does not illustrate alternatives for information that is optional.

If you are planning to configure a network like one of those described in this chapter, just follow these step-by-step instructions. You may later want to go back and tune your network by changing some of the default parameters. However, following these samples will get you up and running as quickly as possible.

Note: This chapter provides similar guidance to that provided by the online walk-through option. Each time you create a new network definition you are asked if you want to use the walk-through option.

Sample Networks

This chapter provides step-by-step instructions for three types of networks:

a single protocol network (that is, a one community network) used by all clients and servers

a network with two communities and one Interchange

a network with Oracle Names

Select the sample that matches your network and follow the instructions. If you need more detailed information, refer to the online help system or Chapter 5.

A Single Protocol for All Clients and Servers

Step 1

If an empty Tree View window is not displayed, select New from the File drop-down menu in the Oracle Network Manager menu bar, or select the New icon from the Command Tool Bar. You will be asked if you want to have a walk through. If you select Yes, you will receive on-screen instructions as you use Network Manager.

Step 2

Select the Community icon or select Community from the Create Menu to bring up a property sheet for a new community. Use this property sheet to provide information about the community the clients and servers share.

In the General page of the Community property sheet:

In the Name field, enter the name of the community.

From the Protocol drop-down list, select the protocol.

Select OK to close the property sheet and hold the data you have entered in temporary memory. The data are not saved to disk until you explicitly select Save or Save As from the File menu.

Step 3

Select the Node icon or select Node from the Create Menu to bring up a property sheet for a new node. Use this property sheet to provide information about the node the Oracle server is on.

In the Node property sheet:

Enter the name of the Oracle server node.

Select the operating system from the Type drop-down list.

Select the Communities page, then select the community and Add it to the Selected list. Click OK to close the page and place the node on the community.

Note: If the network has more than one node, repeat these steps as necessary to create other nodes. Define all nodes that contain an Oracle Server, Oracle Names Server, or Oracle MultiProtocol Interchange. You do not need to create nodes for clients.

Note: You can also select a Node icon and drag it onto a Community icon in the Tree View or the Map View. When you do, that community is selected on the Node's Communities page.

Step 4

Select the listener icon or select Listener from the Create Menu to bring up a property sheet for a new Listener. Use this property sheet to provide information about the listener for the Oracle server.

In the Listener property sheet:

The default name LISTENER appears; you do not need to change it unless there is more than one listener for the server. If there are multiple listeners for a server, each listener must have a unique name.

If only one node has been defined, it appears in the Node field; you do not need to change it. If more than one has been defined, select the down arrow and select the desired node from the drop-down list box that appears.

Select the Addresses page and press Create. A Service Address property sheet appears in which to define the protocol-specific address of the listener. For many common protocols (for example, TCP/IP, DECnet, and SPX/IPX), the address of the listener has already been entered; you need to do nothing more. Other protocols may require further information. For example, if you are using the OSI protocol, you may need to enter a LOCAL_LOOKUP parameter in the User Defined text box. See the Oracle operating system-specific documentation for your platform for more information about the requirements of various protocols.

Select OK to close the Service Address property sheet. You will see a short form of the new address on the Addresses page.

Select the Databases page and select Create. A property sheet to enter information about the Oracle database appears.

In the Name field, enter the service name for the database. (This is the global database name defined in the database initialization parameter file.)

In the Node field, the name of the Node you selected in the Listener window appears; do not change it.

In the SID field, enter the SID of the database.

In the operating system-specific details area, enter the location of the Oracle executables. (The format of your entry in this field depends on the operating system of the listener node.)

Note: Services on some less common operating systems may require user-defined environmental variables and values. If the database is on one of these, use the Location Details page to enter these parameters.

Select OK to close the Database property sheet.

Select OK to close the Listener property sheet and hold the data in temporary memory.

Note: If the network has more than one listener, repeat these steps as necessary to create other listeners and databases.

Step 5

(Optional but recommended.) Select Validate from the File menu of the Oracle Net Manager window to verify that the information you entered is consistent and complete.

Step 6

Save the data you have entered into a network definition file by selecting Save from the File menu.

Step 7

Select Generate from the File menu or select the Generate icon from the Command Tool Bar to create the configuration files for your network. From the Generate Definition window that appears, select File System.

Step 8

Distribute the files to the appropriate locations on your network. See Chapter 6 for further information.

Two Communities with One Interchange

The steps to create this network configuration are very similar to the steps in the previous example. In this network, make two communities, and configure a node that runs both protocols with an Interchange to join the two communities.

Step 1

Select New from the File menu or select the New icon from the Command Tool Bar. Choose to use the walk-through if you wish.

Step 2

Select the Community icon or select Community from the Create Menu to bring up a property sheet for a new community. Use this property sheet to provide information about one of the communities in the network.

In the Community property sheet:

In the Name field, enter the name of the community.

From the Protocol drop-down list, select the protocol.

Select OK to close the property sheet and hold the data you have entered in temporary memory. The data are not saved to disk until you explicitly select Save or Save As from the File menu.

Step 3

Repeat Step 2 to create the other community.

Step 4

Select the Node icon or select Node from the Create Menu to bring up a property sheet for a new node. Use this property sheet to provide information about the node the Oracle server is on.

In the Node property sheet:

Enter the name of the Oracle server node.

Select the operating system from the Type drop-down list.

Select the Communities page, select the community this node is on, then Add it to the Selected list. Click OK to close the page and place the node on the community.

Select OK to close this property sheet and hold the data you have entered in temporary memory.

Step 5

Create the node for the Interchange.

Attention: The Interchange must be on a node that is on two or more communities.

In the Node property sheet:

Enter the name of the node the Interchange is on.

Select its operating system from the Type drop-down list.

Select the Communities page, select the communities this node is on, and Add them to the Selected list. Click OK to close the page.

Note: The Interchange and the database server can be on the same node. If they are, the database server could have two addresses, because the node would be a member of two communities. However, you would have to configure each address. The database could have a listener on only one address if you so choose.

Select OK to close the property sheet and hold the data in temporary memory.

Step 6

Select the Interchange icon or select Interchange from the Create Menu to bring up the Interchange property sheet on which to define the Interchange on the network, with its General page displayed.

A name for the Interchange appears automatically. You can change it if you wish.

Select a node for the Interchange from the drop-down list box. Note that only nodes that are members of two or more communities appear in the list box. If only one node has been defined to be on two communities, it appears in the field automatically and you do not need to do anything.

A checkbox to indicate whether the Interchange is stoppable by the Interchange Control Utility is selected by default. You do not have to change it.

Select the Addresses page and press Create. A Service Address property sheet appears in which to define one of the protocol- specific addresses of the Interchange.

Select one community from the Community list box. The protocol of that community determines the format of the protocol-specific parameters that appear below it. For many common protocols (for example, TCP/IP, DECnet, and SPX/IPX), the address of the listener is entered automatically; you need to do nothing more. Other protocols may require further information. For example, if you are using the OSI protocol, you need to enter an NSAP and TSEL. See the Oracle protocol-specific documentation for your platform for more information.

When you have entered whatever information you need for one protocol-specific address, press OK. You will return to the Addresses page, where a short form of the address you created will appear.

Press Create again to define the address for the other community.

Select OK to close the property sheet and hold the information in temporary memory. The data is not saved to disk until Save or Save As is explicitly selected from the File menu.

If you wish, save the network definition file now by selecting Save from the File menu in the Oracle Network Manager window.

Step 7

Select the listener icon or select Listener from the Create Menu to bring up a property sheet for a new Listener. The General page is displayed. Use this property sheet to provide information about the listener for the Oracle server.

In the Listener property sheet:

The default name LISTENER appears; you do not need to change it unless there is more than one listener for the server. If there are multiple listeners for a server, each listener must have a unique name.

If only one node has been defined, it appears in the Node field; you do not need to change it. If more than one has been defined, select the arrow and select the desired Node from the drop-down list box that appears.

Select the Addresses page and press Create. A Service Address property sheet appears in which to define the protocol-specific address of the listener. For many common protocols (for example TCP/IP, DECnet, and SPX/IPX), the address of the listener has already been entered; you need to do nothing more. Other protocols may require further information. For example, if you are using the OSI protocol, you may need to enter a LOCAL_LOOKUP parameter in the User Defined text box. See the Oracle operating system-specific documentation for your platform for more information about the requirements of various protocols.

Select OK to close the Service Address property sheet. You will see a short form of the new address on the Addresses page.

Select the Databases page and select Create. A property sheet to enter information about the Oracle Server appears, with the General page displayed.

In the Name field, enter the service name for the database. (This is the global database name defined in the database initialization file.)

In the Node field, the name of the Node you selected in the Listener window appears; do not change it.

In the SID field, enter the system identifier (SID) of the database.

In the operating system-specific details area, enter the location of the Oracle executables. (Your entry in this field depends on the operating system of the listener node.)

Select OK to close the Listener property sheet and hold the data in temporary memory.

Note: If the network has more than one listener or database, repeat these steps as necessary to create other listeners and databases.

Step 8

Save the network definition to disk by selecting Save from the File menu.

Step 9

Select Generate from the File menu or select the Generate icon to create the configuration files for your network. From the Generate Definition window that appears, select File System.

Step 10

Distribute the files to the appropriate locations on your network. See Chapter 5 for further information.

Note: Refer to Appendix A for an example of the generated files for a network of this type.

A Network with Oracle Names

To include Oracle Names in the network, you must configure at least one Oracle Names Server. You must also save the network definition to a database. Both of these steps are described in this section.

Note: If you are using SQL*Net 2.3 and Oracle Names 2.0 and the Dynamic Discovery Option (DDO), you may not need to use Oracle Network Manager at all. New SQL*Net 2.3 services will register themselves with well-known Names Servers, and very few configuration files will be needed. See Oracle Names Administrator's Guide for more information.

Use the Names Server Property Sheet

Oracle Names requires a Names Server in each community. Assuming that you have centralized administration and only one domain, you can configure your network with Oracle Names using just one additional property sheet.

Note: In multi-community networks, the Names Server must be available on each community defined in your network. Oracle Corporation recommends that this be achieved by placing a Names Server on each node that has an Interchange.

After defining the listeners on your network, select the Names Server icon or select Names Server from the Create Menu. Use the property sheet to define the Names Server.

In the Name field, a default name appears; you can enter a different name for the Names Server if you wish.

In the Node field, select the node for the Names Server from the choices in the drop-down list.

Select the Addresses page to define the Names Server address. If it is on a node in a single community, you only need to create one address. If the Names Server is on multiple communities, you must create an address for each of them.

Select OK to close the property sheet and hold the data in temporary memory.

Save the network definition to a database. Select Save from the File menu or select the Save icon. Select Database from the Save Network Definition window that appears.

Select Generate from the File menu or select the Generate icon to create the configuration files for your network. From the Generate Definition window that appears, select Oracle Names.

Note: For information about more complex configurations of Oracle Names, see the online help system, Chapter 5 of this Guide, and the Oracle Names Administrator's Guide.

Overview of Steps to Start a Network that Includes Oracle Names

The network definition of a network using Oracle Names must be stored in a database. However, because the network must be up before the network definition can be stored in the database, some extra steps are needed. This section provides a list of steps required to use Oracle Names on a network.

Step 1

Create the network definition, as described in the preceding sections.

Step 2

Generate the configuration files to the file system.

Step 3

Distribute the files. (TNSNAMES.ORA will be one of the files.)

Step 4

Start up the listeners and databases on the network.

Step 5

Again run Network Manager, open the network definition, and save it to a database.

Step 6

Generate the files again, this time to Oracle Names and the File System.