You can set properties as they are required. For example, a deployment might fail if properties are not defined for scripts that rely on them during the deployment.

For example, to run an Apache Tomcat server, Java is required and the JAVA_HOME property value must be set.

When a property is marked as required, a value must be provided in at least one of the life cycle stages of the property, such as the catalog, blueprint, or deployment profile. For example, a catalog administrator can define a required property, mark it as overridable, and not set any value for the property in the catalog. The application architect must provide a value for this property in the blueprint or mark it as overridable in the deployment profile. If the application architect has not set a value for this property, the deployer is required to set a value for this property in the deployment profile before deploying the application.