Home
Developing
Learn how to develop software with HCL VersionVault and HCL VersionVault Remote Client.
Developing software with HCL VersionVault Explorer
HCL VersionVault provides two clients for software developers: local and remote. Each client supports different mechanisms for accessing source-controlled filesystem objects. Both clients provide graphical and command-line interfaces.
Working in the team environment with HCL VersionVault
The HCL VersionVault Explorer supports a variety of team development tasks.
Working with resources under HCL VersionVault source control
You can use UCM or base VersionVault to share your work with a team.
Using UCM
Unified Change Management (UCM) is a structured development process that is based on HCL VersionVault tools.
Modifying resources in a VersionVault view
The workflow for modifying resources in a VersionVault view involves checking them out and checking them in.
Checking in resources
Check in resources to commit your modifications to the repository (VOB).

Developing
Learn how to develop software with HCL VersionVault and HCL VersionVault Remote Client.
- Developing software with HCL VersionVault
  HCL VersionVault provides a flexible set of tools that your organization uses to implement its development and change management policies.
- Developing software with HCL VersionVault Explorer
  HCL VersionVault provides two clients for software developers: local and remote. Each client supports different mechanisms for accessing source-controlled filesystem objects. Both clients provide graphical and command-line interfaces.
  - Team software development with VersionVault
    HCL VersionVault provides configuration management services that make it easy for development teams to work with resources in a shared repository. With the HCL VersionVault Explorer, developers can access HCL VersionVault from a variety of network connections, including broadband (WAN) and traditional local area networks (LANs).
  - Working in the team environment with HCL VersionVault
    The HCL VersionVault Explorer supports a variety of team development tasks.
    - Using the HCL VersionVault Explorer
      You can use the HCL VersionVault Explorer with UCM or base VersionVault.
    - Using the HCL VersionVault Explorer for Eclipse
      You can use the HCL VersionVault Explorer for Eclipse with UCM or base VersionVault.
    - Setting HCL VersionVault Explorer preferences
      Before you begin working with the HCL VersionVault Explorer, review and, if necessary, change the application's default preferences.
    - Connecting to an HCL VersionVault (WAN) server
      If you are using a Web view or automatic view, you must connect to an HCL VersionVault (WAN) server to access resources in VersionVault repositories.
    - Disconnecting from a server or user database
      In some circumstances, you might want to disconnect from a VersionVault WAN server.
    - Removing a server
      You can remove a server from the VersionVault Navigator if you no longer want it to appear in the VersionVault Navigator.
    - Creating a VersionVault view
      Create a VersionVault view to access resources in VersionVault repositories.
    - Mounting VOBs
      Mount (or activate) VOBs to access source files from a view.
    - Unmounting VOBs
      When using dynamic views, you may want to unmount (or deactivate) a VOB.
    - Starting Dynamic views
      Start an existing Dynamic view to access source files.
    - Ending Dynamic views
      You can deactivate a Dynamic view by ending it.
    - Exploring VersionVault repositories
      Use the VersionVault Navigator and VersionVault Details view to explore VersionVault repositories and views.
    - Loading resources into a VersionVault view
      To work with resources in a VersionVault Web view or snapshot view that are under VersionVault source control, load them into the view. Load rules are optional for automatic views and inapplicable to dynamic views.
    - Adding resources to HCL VersionVault source control
      Use the Add to Source Control dialog box to add view-private resources to HCL VersionVault.
    - Working with resources under HCL VersionVault source control
      You can use UCM or base VersionVault to share your work with a team.
      - Using UCM
        Unified Change Management (UCM) is a structured development process that is based on HCL VersionVault tools.
        Joining a UCM project and creating UCM views
        Use the Join UCM Project wizard to join a UCM project and create UCM views.
        Exploring VersionVault metadata in UCM project VOBs
        Use the VersionVault Navigator view and the VersionVault Details view to explore VersionVault metadata in UCM component VOBs and project VOBs.
        Using VersionVault Metadata Explorer Navigator
        Use the VersionVault Metadata Explorer Navigator to explore and view the metadata associated with base VersionVault and UCM VOBs.
        Updating a VersionVault view
        Update a VersionVault snapshot, web, or automatic view to load the element versions selected by the view's config spec. Update also synchronizes a UCM view with its stream. Dynamic views never need updating: they are always up to date
        Updating a resource in a VersionVault view
        Update a resource in a VersionVault web view, automatic view, or snapshot view to load the version selected by the view's config spec.
        Viewing the version tree of a resource
        Use the VersionVault Version Tree view to see the version tree of a resource and to perform VersionVault operations (such as check in, check out, and apply label) on specific versions.
        Locating objects in the Version Tree Browser view
        Use the Locate dialog in the VersionVault Version Tree view to find objects in the version tree of a VersionVault resource. You can search for specific versions, branches, labels, or activities that contain the that text you specify.
        Modifying resources in a VersionVault view
        The workflow for modifying resources in a VersionVault view involves checking them out and checking them in.
        Working with UCM activities
        A UCM activity identifies the set of versions created during a specific development task. Every change to a resource in a UCM project must be associated with an activity.
        Checking out resources
        Check out resources when you want to modify them.
        Checking in resources
        Check in resources to commit your modifications to the repository (VOB).
        Canceling a checkout
        Cancel a checkout if it was not needed or to discard your changes.
        Hijacking files
        Hijack a file when you need to modify it when you cannot connect to a server.
        Canceling a hijack
        Cancel a hijack if it was not needed or to discard your changes.
        Converting hijacked files to checkouts
        You must convert hijacked files to checked-out files before you can check them in.
        Finding modified files
        Use VersionVault Search to find files that have been checked out, hijacked, or that have not been added to source control.
        Deleting resources
        You can use the VersionVault Navigator or VersionVault Details view to delete resources under VersionVault source control. On Windows systems, you can also perform this operation from Windows Explorer. The resources are not, in fact, deleted: they are only uncataloged from the current version of the directory and can be recovered from the predecessor version of the directory.
        Moving resources
        You can use the VersionVault Navigator or VersionVault Details view to move resources under VersionVault source control. On Windows systems, you can also perform this operation from Windows Explorer. This operation affects resources (versions) in the local VersionVault view and elements in the VOB.
        Renaming resources
        You can use the VersionVault Navigator or VersionVault Details view to rename resources under VersionVault source control. These operations affects resources (versions) in the local VersionVault view and elements in the VOB.
        Rebasing a UCM stream using Advanced Rebase
        Rebase a UCM stream to update a UCM view with the set of versions selected by the parent stream's recommended baselines, or with a set of versions in baselines that you choose.
        Rebasing a UCM stream using Default Rebase
        Rebase a UCM stream to update a UCM view with the set of versions selected by the parent stream's recommended baselines, or with a set of versions in baselines that you choose.
        Delivering UCM activities using Advanced Deliver
        Delivering UCM activities makes your work available to other members of your team.
        Delivering UCM activities using Default Deliver
        Delivering UCM activities makes your work available to other members of your team.
        Removing components
        Use the Remove Component option in the VersionVault Details view to delete UCM components.
        Showing Pending Changes
        Use the Pending Changes view to show and resolve all incoming and outgoing changes for the current view.
        Accepting incoming changes
        In the Pending Changes view, you can accept incoming changes by performing a rebase operation.
        Integrate outgoing changes
        In the Pending Changes view, you can integrate outgoing changes by performing a deliver operation.
        Synchronizing all changes
        In the Pending Changes view, you can synchronize all changes by performing both a rebase and a deliver operation.
        Resolving all conflicts
        In the Pending Changes view, you can resolve all conflicts by performing merges.
        Listing the history of a resource
        List the VersionVault history of a resource to see comments and other metadata associated with changes to the resource.
        Using tools to compare and merge files and directories
        With the HCL VersionVault Explorer you can compare or merge files and directories.
        Creating a new Compare/Merge provider
        Use the Compare/Merge Providers preferences to create an external, 3rd-party, Compare/Merge Provider.
        Using a new Compare/Merge provider
        Use the Compare/Merge preferences to specify a new Compare/Merge Provider.
      - Using base VersionVault
        Unstructured access to VersionVault tools is provided by base VersionVault.
      - Working disconnected
        When you choose to work disconnected, actions that require a server connection are disabled and you are not prompted to connect when you attempt to perform them. You can work disconnected from a VOB server (in the case of a snapshot view) or from the VersionVault WAN server (in the cases of a web view or automatic view).
    - Working with ACLs
      You can create, edit, and remove ACL policies and rolemaps using the VersionVault Explorer.
    - Creating a working set
      To create a working set in the VersionVault Navigator view, complete the following steps.
    - Maintaining your VersionVault environment
      This section provides descriptions of HCL VersionVault Explorer maintenance tasks.
  - Team support for the HCL VersionVault Explorer interface
    The HCL VersionVault Explorer provides graphical user interfaces to VersionVault tools.

Checking in resources

Check in resources to commit your modifications to the repository (VOB).

Procedure

To check in one or more resources:

Select the resources that you want to check in.
Use the VersionVault Navigator, VersionVault Details view, VersionVault Search Results view, or the VersionVault Version Tree view. If you are working in the Eclipse environment, use any Eclipse view that supports the Team context menu.
To open the Check in dialog box, click the icon on the VersionVault toolbar, or take either of the following actions:
- Select Check In from the context menu in the VersionVault Navigator.
- In the Eclipse environment, select Check In from the Team context menu.
- In the VersionVault Version Tree view, right-click the version decorated with a checked-out icon and select Check In.
Specify checkin options in the Check in dialog box and then click Apply.
If a more recent version of a selected resource is checked in, you must resolve any conflicts between your version and that version before the checkin can proceed. This typically happens only if you are checking in a resource that was checked out unreserved. If the differences do not conflict, the versions can be merged. If there are conflicting changes, you must perform a manual merge using VersionVault merge tools. For more information, see Using tools to compare and merge files and directories.
If there are any HCL VersionVault triggers associated with this operation, you may be prompted to supply additional information or take further action.

Results

After they have been checked in, resources become read-only. If resource decorations have been enabled, checked-in resources are decorated with the icon.

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.