Defining servers
When you are planning your IBM® Sterling Control Center Monitor implementation, you need to identify the number and type of servers that need to be monitored, managed, or both.
Whether you are planning to use IBM Sterling Control Center
Monitor to monitor servers, manage
assets, servers, you need to supply connection information for those servers (unless they are
dynamically discovered, like servers that post events to Control Center via the Open Server
Architecture interface, or are Connect:Direct servers with an agent configured to communicate with
Control Center). Gather information about the servers (based on server type) so that IBM Sterling Control Center
Monitor can access the server resources
necessary for IBM Sterling Control Center
Monitor functions.
Tip: You can use the IBM Sterling Control Center
Monitor Node Discovery feature to assist
with this task for Connect:Direct servers that do not have an Agent.
To further define server
properties, you can define settings such as monitor rest time and time zone settings (to accommodate
servers in different geographic settings). A wizard guides you through the process of adding servers to your IBM Sterling Control Center Monitor configuration. After you add servers, they are displayed in the console in a navigation tree by server type. To access server properties, double-click the server. You can then review and edit the properties for that server.
In the server list, icons are displayed next to each server name to provide visual indicators of
server status.
Note: You will be forwarded to the Web console to view, and if necessary, edit, the
properties of the selected server.
Attention: Automatically discovered servers, such as IBM Global
High Availability Mailbox servers, are onboarded through
automatic discovery when the servers begin posting events to the repository (ER). You do not need to
configure IBM Control Center
Monitor before the
servers post events.