A DSM implementation architecture can have up to two management tiers: the upper level is known as the enterprise, the lower level is known as the domain.
Agents can be configured to report asset information to a domain manager. The domain manager can be used to monitor the relationship between components, including scalability servers and agents.
In a sufficiently large organization, where several domain managers exist, a single point of management for these domains, an enterprise manager, can be installed. An enterprise manager can be used to collectively manage assets that span multiple DSM domains.
Each manager, domain or enterprise, stores information about assets in its scope in the CA management database (MDB). The MDB provides a unified structure to store information across CA products and platforms.
This is the domain data repository for all assets.
All management constructs such as Queries, Policies, or Groups, as well as all asset-related information like inventory or job definitions, are stored within the MDB.
The enterprise MDB is an centralized repository above the domain level. A subset of data is replicated from domain MDBs up to the enterprise MDB, as well as down from the enterprise MDB to the various domain MDBs
Enterprise-level administrators will find a Domains folder under the Control Panel node within the DSM Explorer. This contains all the domains that have been linked to the enterprise.
Important! Default policies can generally be changed at the top level of a manager hierarchy. However, when a domain manager is linked to an enterprise manager, the default policy can no longer be changed: The default policy will always be replicated from the enterprise manager. Therefore, if a default policy is locally changed, it will be overwritten when a domain is linked to an enterprise.
|
Copyright © 2013 CA.
All rights reserved.
|
|