Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Configuration plans are used to automatically cleanup environment specific information in a composite.xml file during deployment.  Information that can be changed includes URL hosts and retry values, to name a few items.  Configuration plans can utilize property replacement to utilize FlexDeploy properties.  Utilizing FlexDeploy properties allows configuration plans to become re-usable.

The configuration plans that were saved to the ./artifacts/configPlans will be copied to the ./temp directory. Configuring the Deploy Config Plan input can be either an absolute path to a global configuration plan or a relative path to one of the copied configuration plans based on the ./temp directory.

Configuring the SOA Deploy Config Plan project property will require that the Deploy Config Plan input is not set. The input will take precedence over the project property

  • No labels