Managing the RM Repo

As an Administrator, you may want to configure an automated cleanup process to delete obsolete artifact sources stored in the RM Repo.

To Configure the RM Repo Connection Settings

On this page you can override the values defined in the VARA configuration files.

Important! The RM Repo background workflows (e.g. automatic cleanup, disk usage) will be only triggered if the Agent and Login Full Access configuration parameters have been defined.

  • Repository.Path

    Path to the internal repository (RM repo).

    Default: -

  • Repository.Agent

    Agent used to connect to the repository.

    Default: -

  • (Mandatory) Repository.Login.FullAccess

    Login used to upload the artifact files to the RM-Repo. For more information, see: Consolidating Artifacts in CDA with the RM Repository

    Default: -

  • Repository.Login.ReadOnly

    Login used in the GetArtifact action during the deployment. For more information, see: GetArtifact Action

    If this parameter is not defined, the value entered in Login.FullAccess will be used instead.

    Default: -

  • Repository.Folder

    Name of the repository folder.

    Default: SYSTEM

Important! In the Cache Storage Size field you can define a maximum space allocated on Targets to store temporary artifact files.

To Set Up an Automated Cleanup Process

  1. Open the Administration perspective.
  2. Navigate to Release Automation Management > RM-Repo Management.
  3. Select the Automatic Cleanup checkbox.
  4. Select the cleanup frequency. Options: daily, weekly.
  5. If a weekly frequency is defined, select one or more weekdays on which the cleanup should be performed.
  6. Select a time and a timezone.

    The system displays the planned date and time for the next execution of the cleanup workflow.

  7. Save your changes.

To See the History Records of the RM-Repo

  1. Open the Administration perspective.
  2. Navigate to Release Automation Management > RM-Repo Management.
  3. Click the History button in the toolbar. Here you can see the cleanup execution IDs, the number of orphaned blobs deleted and the changes made to the properties of the RM-Repo Artifact Source.

Handling large archive files

If you are working with large archive files containing many files or archives with long nested paths, we do not recommend selecting the "Unpack archived files" option on upload. Nevertheless, if you need to work with extensive archives containing 2000 files or more using the "Unpack archived files" option, set the MAX_REPORT_SIZE value in the UC_HOSTCHAR_DEFAULT system variable to a higher value. For details about setting this value, see MAX_REPORT_SIZE.

Note: Path lengths are limited to 260 characters.