ModuleForge
 

Model

Overview

This document provides an overview of the ControlTier model design used by the Headlines release management system.

Schema

The model schema is based on a type hierarchy and property constraints.

Compositional Structure

The Acme Headlines model uses a standard component hierarchy. The model is layered in roughly three levels.

  1. Mediators: Provide centralized control points for coordinating actions to model sub hierarchies.
  2. Services: Represent deployments with runtime state.
  3. Packages: Represent release artifacts that must be deployed to application components.

The remainder of this document provides detail for the primary domains of the model.

Tomcat Types

Tomcat servers are represented as Services. For each kind of named server, a specific subtype is defined.

Tomcat type Descriptions
NameDescription
JakartaTomcat Subtype of Service, used to control the lifecycle of an Tomcat server.

Package Types

Packages represent release artifacts that are deployed to application components. They are all derived from base types provided by the ControlTier Workbench. The Package base type establishes a common protocol for all package sub-types. The Package type is discussed in more detail here.

Rdb Types

An Rdb type represents a database instance. Rdb instances are composed of RdbSchemas, which in turn are composed of login credentials and optionally database import files.

Rdb type Descriptions
NameDescription
RdbSchema Subtype of Deployment, used to manage a database schema.
MysqlRdbSchema Subtype of RdbSchema, used to manage a mysql database schema.