What you can do with CMDB Solution

Article:HOWTO64093  |  Created: 2011-12-20  |  Updated: 2011-12-20  |  Article URL http://www.symantec.com/docs/HOWTO64093
Article Type
How To


Subject


What you can do with CMDB Solution

See About CMDB Solution.

CMDB Solution has many features and uses, including the following:

Define organizational groups and hierarchy.

Organizational configuration items such as departments and cost centers mirror the structure and hierarchy of your organization. CMDB Solution hierarchy features and child to parent relationships specify standard settings throughout an organizational hierarchy. For example, a task that is applied to a parent department can be automatically pushed down to child departments. Setting up organizational configuration items should be the first thing you do with CMDB Solution.

When you set up associations between configuration items during the CMDB Solution installation, organizational views are automatically created with the same hierarchy and membership.

See Setting up your organizational structure.

Define configuration items.

Configuration items such as assets and contracts are entered into the database using predefined templates called configuration item types. The base configuration item types should be used when possible. The base configuration item types leverage other configuration item types. They provide summary data on the created configuration items and include associated reports and functionality that is not available in custom configuration item types. If none of the base configuration item types meet your needs, you can create a new configuration item type.

You can specify default configuration item type values so that all configuration items based on a configuration item type are created with predefined values. When you enter data for assets, certain fields have the same value for many assets of a particular asset type. You can populate these fields with a default value. For example, users in a particular location have the same phone number prefix. You can save time by having the prefix already entered into the appropriate field.

See Creating and editing a configuration item.

Add data to the CMDB.

Importing is the easiest and the most efficient method of entering data into the system. You can also enter data manually. As you set up a configuration item management system, there is certain data that makes sense to enter before other data. For example, most configuration items rely on the availability of organizational data.

See Automatically creating configuration items for network devices.

See About importing configuration item data from other systems.

See Creating and editing a configuration item.

Track the associations and relationships of configuration items.

You can track where an asset is located, who owns an asset, and which assets are associated with each owner. The Resource Association Diagram feature lets you view the relationships of configuration items in a graphical format.

You can specify the format, the filter, and the number of levels and nodes to display. To customize and easily recreate the display for your environment, you can save the display options and filters.

See Tracking the associations of a configuration item.

Clean up and configure data management with ready-made configuration items.

See About CMDB configuration tasks.

Create customized item actions and CMDB rules to manage data.

CMDB rules target a group of assets based on their type and properties, and then make changes to these assets. Out of the box configuration items address the most commonly required configuration item management policies. CMDB rules provide the flexibility to create custom policies for individual configuration item management needs.

See About CMDB rules.

Configure security.

If multiple users work with configuration items, for example entering and editing data, then you should configure security. CMDB Solution includes predefined security roles. You can modify predefined security roles or you can create your own roles. You can also restrict or allow access to configuration item types and data classes. Hierarchy features are used to set and enforce security settings throughout a hierarchy.

With the role-specific views, you can choose to show or hide menu items depending on a user's security role. For example, you can give a user access to the Reports menu but not to the Manage menu. You can also add menus and customize sub-menus.

See Managing security on an organizational group.


Legacy ID



v49934176_v61794899


Article URL http://www.symantec.com/docs/HOWTO64093


Terms of use for this information are found in Legal Notices