Oracle Enterprise Manager Configuration Guide Release 2.1 A75685-01 |
|
With its three-tiered architecture, Oracle Enterprise Manager is more scalable than ever in maintaining performance and automating routine tasks in rapidly growing, distributed environments.
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. In an environment with multiple Oracle Management Servers, a set of Management Servers share the same repository.
Multiple Oracle Management Servers provide fault tolerance for each other. If an Oracle Management Server fails, the other Management Servers continue to perform and operate. The clients that registered with the failed Management Server can immediately log in again, registering with any of the other Management Servers administering 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.
To improve performance when the number of managed nodes increases, Oracle recommends either (1) adding one Management Server per 50 nodes managed or (2) increasing CPU capacity on the Management Server machine/s.
This chapter describes how to set up or add a Management Server to manage an already existing repository.
Note: If you do not need to set up or add a management server to manage an already existing repository, skip this chapter. |
You must install the additional Oracle Management Server from the Oracle Server CD-ROM on any machine where there are no other Management Servers installed. Refer to the installation guide provided with the database release for detailed instructions.
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-4.
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.
Change the parameters you want.
Enter the user name of the existing repository which you wish this machine's Management Server to administer.
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.
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.
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; if they are missing, the Management Server prompts you for the 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 "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.
|
![]() Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|