Managing web repositories

This topic provides an overview of web repositories.

A web repository is a storage location that can host binaries for software payloads.  TrueSight Server Automation supports the generic-local type of web repositories provided by JFrog. For more information about JFrog, see the JFrog (https://jfrog.com/) documentation. 

You can add a software package to the Depot by specifying the path to a payload that exists on a configured web repository. After adding a software package to the Depot, you can deploy it using a Deploy Job.

Permissions

You must have the following permissions:

• Ensure that you have the user name, password, and URL of the web repository that you want to use. You can either use a unique id or a shared id to access the web repository. The URL of the web repository is the JFrog REST API URL and it must be of the following format:
  http://<hostname>:<port>/artifactory/<repository_path> or https://<hostname>:<port>/artifactory/<repository_path>
  For example, http://clm-ind-xxxxx:9091/artifactory/api/storage/bmc-local
• Ensure that you have the appropriate read permissions to access the web repository directories and installable files. 

• Ensure that the TrueSight Server Automation role have the required authorizations to manage and use web repositories in TrueSight Server Automation.  The following table lists the required authorizations:
  
  

The following authorizations are added in TrueSight Server Automation:

• 
  
  • WebRepositoryConfig.Read
  • WebRepositoryConfig.Modify 
  • WebRepositoryConfig.Delete 
  • WebRepositoryConfig.CreateACL 
  • WebRepositoryConfig.ModifyACL

The web repository configurations must be protected by ACLs in TrueSight Server Automation so that only the specific user can use a configuration using the RBAC mechanism. You can either use a user-specific local repository configuration or global configuration that can be used by all the users.

Using the web repository

Using the web repository includes the following steps:

1. Set up a web repository configuration in TrueSight Server Automation by adding the web repository URL and user credentials for the web repository. This enables TrueSight Server Automation to access the web repository. You can add multiple instances of the same repository. However, the name of the web repository must be unique across all the users. You cannot create two web repository instances having same name.
2. Add the installable file to the Depot from the list of saved web repositories. You can use one of the following options:
   1. The Application Server uses the web repository URL to access the specified installable files and copies them to a staging directory on the agent during the staging phase of a Deploy Job.
   2. The Application Server uses the web repository URL to access the specified installable files and copies them to the file server.

3. Create a Deploy Job. 
   
   

   Note: Importing web repository objects

   If you import an object that includes references to a web repository, ensure that you create a web repository configuration with the same name and base URL as created while exporting the object. For information about how to create a web repository, see Working-with-web-repositories.

Log information

Information about each access to the web repository is added to the appserver.log file. A log file entry contains the following information:

• 
  
  • System Time
  • Program Module 
  • TrueSight Server Automation user and role
  • Web repository URL ( if applicable)
  • Web repository user (if applicable)

The log file entries are displayed as shown in the following example:

Where to go from here

To know how to create, edit, view, and delete web repositories, see Working-with-web-repositories.

To know how to add software to the Depot, see Adding-software-to-the-Depot-from-web-repository.

To know how to create a deploy job, see Creating-a-Deploy-Job.