8.6. Composite Content Views Overview
A Composite Content View combines the content from several Content Views. For example, you might have separate Content Views to manage an operating system and an application individually. You can use a Composite Content View to merge the contents of both Content Views into a new repository. The repositories for the original Content Views still exist but a new repository also exists for the combined content.
If you want to develop an application that supports different database servers. The example_application appears as:
| example_software |
|---|
| Application |
| Database |
| Operating System |
Example of four separate Content Views:
- Red Hat Enterprise Linux (Operating System)
- PostgreSQL (Database)
- MariaDB (Database)
- example_software (Application)
From the previous Content Views, you can create two Composite Content Views.
Example Composite Content View for a PostgreSQL database:
| Composite Content View 1 - example_software on PostgreSQL |
|---|
| example_software (Application) |
| PostgreSQL (Database) |
| Red Hat Enterprise Linux (Operating System) |
Example Composite Content View for a MariaDB:
| Composite Content View 2 - example_software on MariaDB |
|---|
| example_software (Application) |
| MariaDB (Database) |
| Red Hat Enterprise Linux (Operating System) |
Each Content View is then managed and published separately. When you create a version of the application, you publish a new version of the Composite Content Views. You can also select the Auto Publish option when creating a Composite Content View, and then the Composite Content View is automatically republished when a Content View it includes is republished.
Repository Restrictions
You cannot include more than one of each repository in Composite Content Views. For example, if you attempt to include two Content Views using the same repository in a Composite Content View, Satellite Server reports an error.
