Oracle® Enterprise Manager Configuration Change Console Installation Guide 10g Version 10.2.0.4 for Windows or UNIX Part Number E12914-02 |
|
|
PDF · Mobi · ePub |
The installation of the Configuration Change Console and its components must be executed in the order documented below:
Oracle database installation and configuration
Configuration Change Console Server installation and configuration
Configuration Change Console Agent installation
When you have completed the installation, refer to Chapter 6, "Overview of Configuration Change Console Agent" or Chapter 12, "Securing the Configuration Change Console" for more information about installing your agent component.
The specific operating system requirements for the Configuration Change Console server are contingent on the size of your deployment.The following table lists some suggestions for various sizes of environments. These can change depending on many factors in a specific customer environment, but can be used as a rough guideline to follow.
Table 3-1 Recommended Sizes for Environments
Deployment Size Recommended | Host | CPU/Host | Physical Memory | Minimum Disk Space Recommended |
---|---|---|---|---|
25 Agents (typical rate change) |
1 (no clustering) |
1 (3 Ghz) |
2 GB |
15 GB |
250 Agents (typical rate change) |
1 (no clustering) |
2 (3 Ghz) |
4 GB |
20 GB |
1000 Agents (typical rate change) |
3 (clustered) 1 primary, 2 secondaries |
4 (3 Ghz) |
4 GB |
50 GB |
10,000 Agents (typical rate change) |
6 (clustered) 1 primary, 5 secondaries |
4 (3 Ghz) |
4 GB |
50 GB |
Deployment sizes are based on the sizing section in the database prerequisites chapter of this install guide. For clustered environments, the primary server does not process incoming messages as it does in the non-clustered installation, but handles all other processing. This means that typically you would have at least 2 secondaries if you were using a clustered environment.
These sizing guidelines are assuming minimum hardware desired for the environment. There can be more secondaries than needed and the benefit is not only better load balancing but also failover if one secondary cannot process incoming events from agents.
In a production environment with 250 agents, although minimum requirement would be one server host, it is recommended that you use clustering with one primary and 2 secondaries so that you have a secondary available to process events in case one of them is down.
The following browser versions are compatible with the Configuration Change Console:
Browser | Version |
---|---|
Internet Explorer | 7.0 and above |
Firefox | 1.2 and above |
The server on which the Configuration Change Console Server will be installed should be running Windows 2000 Server, Windows 2003 Enterprise Edition, or Windows XP.
The device on which the Configuration Change Console Server will be installed should always have the latest Service Pack and Patches.
The display colors should be set to 256 or more colors. The resolution should be 1280 x 768 or higher.
The following information applies to all supported platforms in the Microsoft Windows family. This includes Windows 2000 and Windows 2003. The Configuration Change Console Server must be installed by a user with Administrator permissions. Additionally, all files that are created by this Administrator must have NT Authority/SYSTEM change permissions. The services that are created during installation will be run as the SYSTEM user as is normal with Windows services. By default, all NT Administrators are granted NT Authority/SYSTEM change permissions. If they have been modified, you must assign NT Authority/SYSTEM change permissions to the entire installation directory.