Versions Compared

Version Old Version 1 New Version 2
Changes made by

Christoph Bergner

Christoph Bergner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

This page provides guidance on integrating Smartfacts CDCM (Cross Domain Configuration Management) with PREEvision. Users will learn how Smartfacts CDCM references local configurations from PREEvision to define configuration items. The section includes detailed steps for establishing the connection and highlights key integration features.

Details

Understanding the Integration

Smartfacts CDCM integrates with PREEvision by referencing local configurations as external work products. These configurations can be:

  • Versions: Configurations that can change over time.

  • Baselines: Fixed configurations that remain unaltered.

Note: Support for working sets will be introduced in future versions of Smartfacts CDCM.

The integration leverages the OSLC Connector for PREEvision, ensuring compliance with OSLC standards and facilitating seamless connectivity.

Steps to Add a Connection to PREEvision

To connect Smartfacts CDCM to a PREEvision instance, follow these steps:

  1. Navigate to the Administration Panel:

    • Go to Administration > Storage Location within Smartfacts CDCM.

  2. Add a New Storage Location:

    • Click on the "+ Add Storage Location" button.

  3. Select the Storage Type:

    • Choose "OSLC Configuration Provider" from the list of available options.

  4. Enter the Root Service URI:

    • Provide the root service URI for the PREEvision connector.

  5. Automatic Retrieval of Connector Name:

    • Once the root service URI is entered, the system will automatically retrieve and display the name of the connector.

  6. Verify the Connection:

    • The new storage location will appear in the list of storage locations.

    • You can now select "OSLC Connector for PREEvision" as the target when adding a PREEvision local configuration as a configuration item.

Best Practices

  • Ensure the root service URI is accurate to avoid connectivity issues.

  • Use baselines for configurations requiring stability and versions for evolving configurations.

  • Monitor updates to enable working sets as they become available in future releases.

  • Regularly review the list of storage locations to ensure connections remain active and valid.

Related Topics

  • Storage Locations

  • OSLC Configuration Management Overview