Effectively using the IBM Sterling Control Center Monitor console
Review the following general guidelines related to using a console:
- Use a non-secure connection between the engine and console, unless you are connecting to the engine over the internet. If you are using the internet, use a secure connection.
- To reduce the overhead on the Console, increase the Auto Refresh
settings using one of the following methods:
- Change the Default Console Auto Refresh System Setting in seconds setting ( ).
- Specify a new value for the Change Auto Refresh to: setting ( ).
- To reduce the number of data requests to the engine, require manual refresh for users who do not need to actively monitor managed servers. Set up roles that use the Manual option for the Console Auto Refresh Permission.
- When you are not using the console, log out of it. When the console is connected, the engine is going to process fewer events per second because it is going to be updating at the same time.
- To further improve the engine performance, set up alerts to send email notifications as alert conditions occur instead of requiring users to monitor alerts using the Console.
- When monitoring a large number of servers, use the option, IBM® Sterling Control Center Monitor Console - Large Configuration (Greater Than 512 MB, Less Than 1 GB), on the IBM Sterling Control Center Monitor Launch Page. The large configuration allocates up to 1 GB max heap size, which will improve performance.
- When monitoring a large number of servers, avoid using VPN to connect to the engine. VPN connections are secure and encrypted and as a result, are 2 to 3 times slower than non-secure connections. When you open an activities monitor which covers a large number of managed servers and activities on those servers, a lot of data has to be transferred over the secure connection, which will slow down performance.