About configuration management
IBM® Control Center can manage many types of IBM Sterling Connect:Direct® server configuration objects.
These objects include:
- Functional authorities (UNIX, Microsoft Windows, and z/OS)
- Initialization parameters (UNIX, Microsoft Windows, and z/OS)
- Netmap nodes (UNIX, Microsoft Windows, and z/OS)
- Netmap modes (Microsoft Windows)
- Netmap communication paths (Microsoft Windows)
- IBM Sterling Connect:Direct Secure Plus nodes (UNIX, Microsoft Windows, and z/OS)
- Sterling Connect:Direct Secure Plus key certificates (UNIX, Microsoft Windows, and z/OS)
- Sterling Connect:Direct Secure Plus trusted certificates (UNIX, Microsoft Windows, and z/OS)
- Sterling Connect:Direct Secure Plus cipher suites (UNIX, Microsoft Windows, and z/OS)
- User proxies (UNIX and Microsoft Windows)
You can also use the IBM Control Center API (CCAPI) to programmatically create and maintain objects.
IBM Control
Center stores
versions of managed server objects locally. The number and age of
versions kept by IBM Control
Center is
controlled through the Services tab in System Settings. You can set
up IBM Control
Center,
through the Services system settings, to know whether and when to
look for local updates to managed objects, and, if a change to those
objects is detected, how to create a new, local version of them.
Note: When
you are performing configuration management on a node, that node must
be up and contacted. When you are using the object from another node
as a starting place for configuration, the object comes from the IBM Control
Center database.
As a result, IBM Control
Center does
not contact that node; therefore, the status of that node is not relevant.