Home
Integrating
Learn how to integrate HCL VersionVault with other products.
Integrating HCL VersionVault with other products
Learn how to integrate HCL VersionVault with other products.
HCL VersionVault integrations with vendor products
HCL VersionVault can be integrated with other vendor products.
The HCL VersionVault integration with Cadence Virtuoso
The HCL VersionVault-Cadence integration supports a number of commands (data management operations, such as check-in and check-out) and features (such as the Configuration Specification editor and the Work Area Manager).
Logs and traces
Apart from the Cadence logging in CDS.log and libManager.log files, you can set the following environment variables to control the output and to enable tracing and logging for the integration.

Integrating
Learn how to integrate HCL VersionVault with other products.
- Integrating HCL VersionVault with other products
  Learn how to integrate HCL VersionVault with other products.
  - The UCM integration with HCL Compass
    If your project uses the UCM integration with HCL Compass, your project manager has set up an HCL Compass user database to store information about the work that you do in UCM activities.
  - HCL VersionVault integrations with vendor products
    HCL VersionVault can be integrated with other vendor products.
    - The HCL VersionVault integration with Visual Studio
    - The HCL VersionVault integration with Cadence Virtuoso
      The HCL VersionVault-Cadence integration supports a number of commands (data management operations, such as check-in and check-out) and features (such as the Configuration Specification editor and the Work Area Manager).
      - Integrating VersionVault with Cadence Virtuoso
        Before you set up the HCL VersionVault integration with Cadence Virtuoso, review the following information.
      - Data management operations
        You can check in, check out, cancel check-outs, delete artifacts, and automatically check in or check out artifacts by using the Library Manager.
      - The Configuration Specification editor
        Use the Configuration Specification editor to specify custom version-selection rules for designs and to configure your workspaces accordingly.
      - The VersionVault Work Area Manager
        The VersionVault Work Area Manager (WAM) offers designers an interface that presents the information in a format most suitable with the workflow of designers.
      - The VersionVault integration with Cadence cellview editors
        The HCL VersionVault integration with Cadence schematic, layout, and other such design editors is referred to as cellview editors (CVEs). Version information, which is displayed on the cellview editor's title bar, includes the current design management (DM) state and the version of the design artifacts that are loaded in the work area.
      - The schematic diff tool
        With the schematic diff tool, designers can graphically browse and review changes that are made in versions of the same schematic design.
      - The Hierarchy Manager
        The Hierarchy Manager is similar to the Work Area Manager in certain graphical user interface (GUI) respects but the Hierarchy Manager presents a list of cellviews that constitute a design hierarchy.
      - Logs and traces
        Apart from the Cadence logging in CDS.log and libManager.log files, you can set the following environment variables to control the output and to enable tracing and logging for the integration.
      - VersionVault preferences store for cellview editors
        Designers can set VersionVault preferences for cellview editors. Once set, these preferences remain persistent.
      - Graphical design management API
        To graphically carry out common design management operations, you can use the application program interface (API) that is available in the VersionVault-Cadence integration.

Logs and traces

Apart from the Cadence logging in CDS.log and libManager.log files, you can set the following environment variables to control the output and to enable tracing and logging for the integration.

CCASE_CDS_VERBOSITY

By default, all standard output is printed in the command-line interface and in the Library Manager console in the user interface. You can set the CCASE_CDS_VERBOSITY environment variable to these values:


Value	Description
`0`	Print error messages only.
`1`	Print error and warning messages.
`2`	Print OK, warning, and error messages. (Printing these messages is the default behavior.)
`3`	Print OK, error, warning, and trace messages. The trace-message output is verbose.

A log file is created with the following name in the current directory: case_cds.log.<timestamp>. One log file is created for one session of the Library Manager. For every gdm command, a separate log file is created.

CCASE_CDS_LOG_DIR

If the value of the CCASE_CDS_VERBOSITY environment variable is 3, by default the log file is created in the current working directory. Use the CCASE_CDS_LOG_DIR environment variable to specify a different directory for the log file to be written to.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.