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).
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.
Export
You can export a specified version of a co-managed set to the destination folder. This command applies only to a single managed cellview.

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.
        Artifact check-ins
        You can check in design artifacts (libraries, cells, and cell views) and non-design artifacts (property files, category files, and so on) in HCL VersionVault by using the Library Manager user interface or the gdmci command in the command-line interface.
        Artifact check-outs
        You can check out design artifacts (libraries, cells, and cellviews) and non-design artifacts (property files, category files, and so on) by using the Library Manager user interface or the gdmco command-line interface command.
        Check-out cancellations
        You can cancel check-outs of design artifacts (libraries, cells, cellviews) and non-design artifacts (property files, category files, and so on) by using the gdmcancel command or the Library Manager user interface.
        Automatic check-ins and check-outs
        By default, the integration software checks out and checks in properties, files, and cellviews. You can configure these behaviors.
        Artifact deletion
        You can delete design artifacts (library, cells, cellviews) and non-design artifacts (property files, category files, and so on) in HCL VersionVault by using the Library Manager user interface or the gdmdelete command.
        Status queries for managed or unmanaged design artifacts
        This query command returns the design management status of files.
        Export
        You can export a specified version of a co-managed set to the destination folder. This command applies only to a single managed cellview.
        Rollbacks
        You can roll back to any artifact version that is not the latest version on the current branch. This operation creates a new version in the current branch, which is the same branch you rolled back to.
        Restricting the operation of VersionVault
        The integration interfaces set the CLEARCASE_EDA environment variable to Cadence Virtuoso when they are called.
      - 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.

Export

You can export a specified version of a co-managed set to the destination folder. This command applies only to a single managed cellview.

Command-line interface command: gdmexport

Usage

gdmexport [ –cdslib file ] [ –recurse ] [ –xtra str ]: [ –lib lib.cell:view/file ] [–file file ] ... [–destination path ]; [ –version identifier ] [ –complete ] [ –export paths ] [ –help ]

Description

Use this command to export the specified version of a co-managed set of operated cellview to the destination folder. This command applies to only a single managed cellview.

Options and arguments

-cdslib <file>: This option specifies the library definition file to use for mapping library names to library directories.
-destination <path>: This option specifies the location to export the co-managed set of cellview to.
-lib <lib.cell:view>: This option specifies the cellview to export.
-file <file>: This option does not apply to this command.
-version <identifier>: This option requires a string that represents the version of the files to export.
-recurse: This option does not apply to the command.
-xtra <str>: This option does not apply to the command.
-complete: This option does not apply to the command.
-exportpaths: This option does not apply to the command.
-help: This option displays information about the command and its arguments.

User interface actions for exporting versions

To copy a version:

Open the Library Manager.
Select the cellviews or files to copy.
Select Design Manager—Version Info.
The Version Information window opens.
From the list, select the version of the cellview to copy. The Copy Cellview Version window opens. The window fields contain default values that include the name of the source library, cell, view, and the cellview version number. The fields in the To section also include the same default values. However, the view name is appended with an incremented version number as the destination (copied) cellview version.
Enter the name of the library to copy the cellview version into.
Select Use Options to pass options that are specific to your design management system.

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.