Manage Site-Specific Data

Starting with version 13, repository data that is specific to a site web application—such as the site's HST configuration and web files—is defined and packaged within the site web application. This includes both configuration and content definitions.

To enable the Configuration Management mechanism to detect and process these definitions, the site web application must identify itself as an "HCM Site." You do this by including a hcm-site.yaml file in the site web application. For details, see Multi Webapp Mode. When Configuration Management detects a site web application with this file, it scans the application for HCM modules and processes them after processing the repository data definitions from the CMS/platform web application.

In the repository, data for each site web application is separated from data for the CMS/platform and from other site web applications. Each site web application has a dedicated HST configuration root node or tree and a unique web file bundle name.

If your project uses Single Webapp Mode, package all repository data definitions in the CMS/platform web application. Do not use the hcm-site.yaml file in this mode.