Configuration plans are used to automatically cleanup environment specific information in a composite.xml file during deployment. Information 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 Composite specific configuration plans that were saved to the ./artifacts/configPlans, during the build step, 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.captured during build in configPlans sub-folder, are available during deploy step along with SCA Jar file.
Configuration plan can be specified using SOA Deploy Config Plan project property and/or Deploy Config Plan plugin input. The plugin input will take precedence over the project property. Deploy Config Plan input can be either an absolute path to a global configuration plan or composite configuration plans file name. Composite configuration plans are placed in FD_TEMP_DIR by FlexDeploy SOA Plugin, but you do not need to qualify it, just provide name when using composite specific configuration plans.
There are two approaches to Configuration Plans:
...