Configuration of Offline Depot Repository URL with Non-Standard Path in VCF Operations Fleet Management

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When configuring an offline depot for Fleet Management, a custom directory structure is used on the offline depot web server.
Unlike the standard configuration where the repository sits at the root of the web server (e.g. https://xxx.xxx.xxx.xxx/) the repository may sit under a sub-directory (e.g. https://xxx.xxx.xxx.xxx/example) with the standard PROD folder nested under this sub-directory (the full path to files is https://xxx.xxx.xxx.xxx/example/PROD).
It's required to configure this offline depot in VCF Operations. 
This KB is to guide users on how to correctly configure the Repository URL in VCF Operations Fleet Management when the self-built Offline Depot utilizes a non-standard directory structure (a custom path exists before the PROD directory).

Environment

VCF Operations 9.0
VCF Operations Fleet Management  9.0

Resolution

When the Offline Depot is hosted on a web server using a custom context path or alias, the Repository URL field in the Depot Configuration page must include the full path up to (but not including) the PROD directory.

Steps:

1. Identify the base URL of your web server (IP or FQDN) and the port (if not 80 or 443).
2. Identify the custom sub-directory path configured on your web server that precedes the standard folders.
3. Combine these into the Repository URL field.

Note: Do not manually append /PROD to the URL. The Fleet Management service will automatically look for the standard directory structure relative to the URL you provide.

If your browser can access the directory listing at: https://xxx.xxx.xxx.xxx/example/PROD/

Then your Repository URL setting is: https://xxx.xxx.xxx.xxx/example