4
Adding Additional Management Servers

In an environment with multiple Oracle Management Servers, a set of Management Servers share the same repository.

This chapter describes how to set up or add a Management Server to manage an already existing repository and explains why multiple Management Servers may be needed.

Note: If you do not need to set up or add a management server to manage an already existing repository, skip this chapter.

As the number of nodes and managed services in your network increases or if the current Management Server is overloaded, you can add more Oracle Management Servers to the middle tier to share and balance the workload.

Multiple Oracle Management Servers provide fault tolerance for each other. If an Oracle Management Server fails, the other Management Servers continue to operate. The clients that registered with the failed Management Server can immediately log in again, registering with any of the other Management Servers using or sharing the same repository, and work continues with the remaining available Oracle Management Servers. Any clients that had been configured to register with a different Oracle Management Server than the one that failed are unaffected.

If the available Management Servers are CPU-bound (the CPU usage is exhausted), adding additional Management Servers is an alterative to increasing the capacity of the nodes that run the Management Servers.

Note: All Management Servers connecting to the same repository must reside in the same DNS Domain.

Installing an Additional Management Server

If you want to run an Oracle Management Server on a specific machine, you must first install the Oracle Management Server software on that machine.

Refer to the installation guide provided with the database release for detailed instructions.

Setting Up an Additional Management Server

When you add a new management server, you must run the Enterprise Manager Configuration Assistant to update the configuration file for that node.

For information about starting the Enterprise Manager Configuration Assistant, refer to "Starting the Enterprise Manager Configuration Assistant" on page 2-6.

Step 1 "Configuration Operation"

When you start the Enterprise Manager Configuration Assistant, the "Configuration Operation" page appears.

Select "Edit the Configuration Parameters" from the list of configuration operations and press Next to Continue. The "Configuration Parameters" page appears.

Step 2 "Configuration Parameters"

Change the parameters you want.

User Name

Enter the user name of the existing repository which you wish this machine's Management Server to use.

Password

Enter the password for the above user name. The information will be used on the next Management Server start up.

If you change the password, you must also change the Confirm field so that it matches the password you changed.

Service

Enter the service where the repository resides.

This information will be used when this machine's Management Server next starts up. If any of the information is invalid, then the Management Server will not start successfully.

Do not save username and password

You can choose whether to save the user name and encrypted password in the omsconfig.properties file, which is read by the Management Server on startup. If the user name and encrypted password are stored in the file, the Management Server uses them to login to the repository.

On Windows NT or Windows 2000, if they are not saved, you can enter them in the Control Panel's Startup Parameters field when you start the Management Server. If you do not enter the repository credentials in the Startup Parameters field, you will be prompted for them in a dialog.

On UNIX, if they are not saved, the Management Server will prompt you for a user name and password before it starts up.

If you do not want to save the user name and password, check the "Do not save username and password" checkbox. The option of not storing your repository credentials is referred to as the secure Management Server mode.

Note: In order to progress to the next page, you must change at least one of the parameters in this page. If the Next button is pressed without changing anything, an error message appears: "There were no changes to the configuration parameters. Make changes or cancel." In this case, the Enterprise Manager Configuration Assistant does not allow navigation to the next page.

Step 3 "Modify Configuration Parameters"

The "Modify Configuration Parameters" page provides a summary of all the information supplied during the modify configuration parameters wizard operation. Click Finish to initiate the change or click Back to return to previous pages to change your information.