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 7, "Overview of Configuration Change Console Agent" or Chapter 14, "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
| Number of Agents | Change Rate | Server Hosts | CPU/Host | Physical Memory | Minimum Disk Space per Host |
|---|---|---|---|---|---|
|
100 |
Nominal |
1 host (no clustering) |
1 dual-core 3 GHz |
4 GB |
30 GB |
|
1000 |
Nominal |
1 host (no clustering) |
2 dual-core 3 GHz |
4 GB |
30 GB |
|
5000 |
Nominal |
3 hosts (clustered with 1 primary, 2 secondaries, 2 Messaging brokers) |
2 dual-core 3 GHz |
8 GB |
100 GB |
|
15,000 |
Nominal |
4 hosts (clustered with 1 primary, 3 secondaries, 2 Messaging brokers) |
2 dual-core 3 GHz |
8 GB |
100 GB |
|
1000 |
Very High |
4 hosts (clustered with 1 primary, 3 secondaries, 2 Messaging brokers) |
2 dual-core 3 GHz |
8 GB |
100 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 a small number of agents and change rate, although minimum requirement would be one server host, you can use clustering with 1 primary and 2 secondaries and 2 Messaging Brokers so that you have a secondary available to process events in case one of them is down.
Any host that has a Messaging Broker should have enough disk space available to allow for the broker to queue up messages from agents that cannot be processed in a timely manner by the servers. Configuration Change Console is designed to allow agent messages queue up into the messaging broker servers, so that if the primary, secondary servers, and database are under high load, the agent messages are not lost and can be processed at a later time. For a production environment, it is best to provide at least 50GB of disk space for each messaging broker to ensure messages from agents are not lost when the servers cannot process bursts of events.
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 Oracle Enterprise Linux V4, V5 or equivalent. There is a separate installer for the Windows and Linux platforms.
When running the Configuration Change Console server, the X Windows subsystem is required for graph generation. If X Windows is not installed/configured properly or if the shell under which the server starts does not have a DISPLAY set, then graph generation will fail throughout the product.
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.
The following information applies to all Unix platforms on which Configuration Change Console server can be installed.
The Configuration Change Console server should be installed as root if you want the server to register a service that can start at the time your server starts. Also, to be able to specify certain ports (for example: port 80 and 443) for the web-based console, you need to have the proper privilege when running the server.
The product relies on the X-Windows subsystem for its graph generation code so the user that the Configuration Change Console server runs as must have access to this subsystem.