con_composite-content-views-overview.adoc

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:

• {RHEL} (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 {endash} example_software on PostgreSQL
example_software (Application)
PostgreSQL (Database)
{RHEL} (Operating System)

Example Composite Content View for a MariaDB:

Composite Content View 2 {endash} example_software on MariaDB
example_software (Application)
MariaDB (Database)
{RHEL} (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

Docker repositories cannot be included more than once in a Composite Content View. For example, if you attempt to include two Content Views using the same docker repository in a Composite Content View, {ProjectServer} reports an error.