Infrastructure components

An infrastructure component is a type of component that contains information about the environment to which an application is deployed. You can use an infrastructure component to create dynamic environments for applications.
Infrastructure components typically contain the following artifacts:
Application definition files
Application definition files are Weaver files that describe the application in logical terms. These files describe the nodes, components, and users for the application without specifying the infrastructure for them.

An application definition file does not specify information about the infrastructure for the application or specific details of the deployment. Instead, the application definition file describes the logical organization of the application in terms of the application nodes and the relationships between those nodes. When you create an environment file, you realize the elements in the application definition to elements in the infrastructure file.

Infrastructure patterns
Infrastructure patterns are local Weaver representations of virtual system patterns on cloud hosts. Normally, you do not refer to these files directly. Instead, you use a façade file to provide a simplified way of working with the virtual system pattern. Infrastructure patterns are generated from virtual system patterns and are not intended to be edited.
Façade files
Façade files are simplified forms of infrastructure patterns. They provide a layer of abstraction that lets you customize the infrastructure pattern without editing the pattern directly. For example, façade files let you assign human-readable names to the nodes and parameters in infrastructure patterns.
Environment definition files
Environment definition files represent a deployment scenario for the application. Each file merges information from the façade file with information from the application definition file. The environment definition file also provides parameter values, such as passwords. You can have many different environment definitions for deploying the application in different configurations.
properties.yml
This file stores properties for the infrastructure component, such as the host name of the cloud system that hosts the dynamic environments.
weaver_provisioner.rb
This file contains instructions for requesting dynamic environments and deploying applications to those environments. In most cases, do not edit this file.
lib/ folder
This folder contains dependencies for the Weaver runtime.
For information about creating infrastructure components, see Specifying dynamic infrastructure with infrastructure components.

Feedback