Creating an authorized CI space
In order to control which CI types and attributes are included in authorized CIs, you must build a CI space that defines the CIs, attributes, and relationships that you want to manage.
Creating a CI space is a significant task, requiring a good understanding of the structure of the CIs you plan to manage.
- 1. Authorized CI Classifications
- These classifications define the structure of the authorized configuration items that you will manage in Control Desk.
- 2. Promotion Scopes
- These are templates that contain mappings of classifications between the actual and authorized CI classifications. Promotion scopes are the roadmaps used by Control Desk to promote actual CIs to create authorized CIs.
- 3. Relationship Rules
- These rules define the relationships between the CIs in the authorized space. These rules must be set up correctly within the context of a promotion scope and the authorized classification set in order for Control Desk to properly promote a CI.
You can think of the promotion scopes that you create as templates for your authorized CIs. You can have more than one promotion scope for a particular type of CI. For example, for Computer System you might have one promotion scope for your mail servers and another for database servers. This would enable you to manage different combinations of child CIs and attributes for different types of servers. When you promote one or more actual CIs of a particular type, you can choose one of these promotion scopes, or templates, to be used in the promotion process. The authorized CIs created in this way will have only those attributes that are present both in the actual CI and in the authorized CI classification that you chose.
The best practice for creating a CI space is to use the Deployer's Workbench. The Deployer's Workbench is a self-contained, Eclipse-based tool that is installed separately from Control Desk.