Working with resources under HCL VersionVault source control

You can use UCM or base VersionVault to share your work with a team.

Before you begin

Before you can add resources to HCL VersionVault or work with resources that are under VersionVault source control, you must create a VersionVault view. Because UCM and base VersionVault require different types of views according to the development policy that is in place, you must choose one before you create the views that you will use. You will also need to decide on the type of view that best suits your development environment.

Procedure

To start using the HCL VersionVault Explorer for Eclipse:
  1. Decide whether to use UCM or base VersionVault:
    1. Check with your project manager. Before you can use UCM, the project manager or another user with access to UCM tools on the VersionVault server must create a UCM project and the components it uses. For base VersionVault, the project manager may specify the version selection rules that are to be added to the config spec for the view.
    2. Review additional HCL VersionVault documentation about UCM and base VersionVault.
  2. Decide on the type of view:
    1. Dynamic views require the presence of the VersionVault native (or thick) client and are designed to be used only on Local Area Networks. Dynamic views are not supported on Wide Area Networks. Dynamic views must be mounted and started before use.
    2. Snapshot views also require the VersionVault native (or thick) client and a LAN connection to load resources from the VOB.
    3. Web views are a copy-based system that require a connection to the VersionVault WAN server (although a limited amount of operations are still available when you are disconnected from the server) and may be used in either a WAN or a LAN environment.
    4. Like web views, automatic views are a copy-based system that require a connection to the VersionVault WAN server. They may be used in either a WAN or a LAN environment.