Application model

 

BMC Release Process Management has a mechanism to model application, components and track changes happening in various environments over time. While users can get started with basic request model with 'Default' application, users can typically evolve a application model for their custom solution.

Applications (Apps)

'apps' model is a collection of components which make up the application. It also associates to all the environments where the application is deployed. 

1. application_components - this model describes which components make up the application.
2. apps_requests - this model holds information about all the requests which are pertaining to an application. An application associates with only one request at a time.
3. apps_procedures - re-usable procedures get associated to one or more application.
4. apps_business_processes - an application associates with one business process.

Components

Represents and hold all information about unique components in a given custom solution. These components can be re-used across multiple applications.

1. component_properties - using this model components can hold additional parametrized information that can later be used in requests. This is a useful feature especially if the request is going to has automation configured.
2. installed_components - this model holds information about the places where the component is deployed at and the component version that is deployed.
   1. icsas - this model holds information about all server aspects the component is deployed on.
   2. icsags - this model holds information about all server aspect groups the component is deployed on.
   3. installed_component_servers - this model holds information about all servers the component is deployed on.
3. version_tags - this model holds version history of each component across various application and environments.