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 Micro Focus ALM Octane. Readers will learn how Smartfacts CDCM references local configurations from Octane to define configuration items. The section includes detailed steps for establishing the connection and highlights important integration aspects.

Details

Understanding the Integration

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

  • Versions: Dynamic configurations that may be updated over time.

  • Baselines: Static configurations that remain fixed.

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

The integration leverages the OSLC Connector for Octane, ensuring adherence to OSLC standards and enabling seamless connectivity.

Steps to Add a Connection to Octane

To connect Smartfacts CDCM to an Octane instance, follow these steps:

  1. Navigate to the Administration Panel:

    • Open Administration > Storage Location within Smartfacts CDCM.

  2. Add a New Storage Location:

    • Click the "+ Add Storage Location" button.

  3. Select the Storage Type:

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

  4. Enter the Root Service URI:

    • Input the root service URI for the Octane connector.

  5. Automatic Retrieval of Connector Name:

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

  6. Verify the Connection:

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

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

Best Practices

  • Ensure the accuracy of the root service URI to prevent connection errors.

  • Use baselines for finalized configurations that require stability and versions for iterative updates.

  • Stay informed about updates to enable working sets once they are supported.

  • Periodically review storage locations to ensure all connections are functional and up-to-date.

Related Topics

  • Storage Locations

  • OSLC Configuration Management Overview