Performs environment specific property replacement, determines next composite revision and deploys the SCA artifact or the patch artifact (12.2.1+ only) to the server or cluster. Choose any managed server to deploy the composite to all managed servers in the cluster.
Composite revision purging is an optional feature that allows the developer to control the number of revisions actively deployed on the server upon successful deployment of the composite.
This operation should be run on any SOA managed server endpoint.
Configure SOA Server Host and Port for any SOA managed server and after deployment composite will be available on all managed servers in the SOA cluster.
|SOA Server Host|
Host name of the SOA managed server.
|SOA Server Port|
Port number of the SOA managed server, which will be the SSL Listen Port or Listen Port based on whether you desire to connect using SSL.
|SOA Use SSL|
|No||Whether or not to use SSL when connecting to the SOA Server. Is unchecked by default. If checked, SOA Server Port must be set to the SSL Listen Port and Weblogic Domain Directory must be set. @Since 22.214.171.124|
|Weblogic Admin User|
Admin user name for WebLogic server.
|Weblogic Admin Password|
Weblogic Admin User password for WebLogic server.
|Weblogic Domain Directory|
|Yes*||Weblogic Domain Directory for the WebLogic server. *Only required if SOA Use SSL option is checked. @Since 126.96.36.199|
User name for MDS access.
|MDS JDBC URL|
Database URL for MDS access.
|Oracle SOA Home|
Oracle SOA Home, indicates where SOA Suite is installed.
|SOA Extend Classpath|
Ability to extend the plugin classpath for external java classes or custom xpath functions
|SOA Deploy Config Plan|
Ability to define config plan specific to a composite (see special considerations).
|Composite Revision To Keep|
|No||Number of composite revisions to retain on the server after successful deployment|
|SOA Composite Name|
Name of composite that is being deployed.
|SOA Deploy Config Plan|
Ability to define config plan specific to a composite. (see Configuration Plans).
When using composite specific configuration plans, they are stored in configPlans folder in artifacts, but you do not need to specify configPlans folder in this property value, just provide name of the configuration plan file as appropriate. You can also override this property for various environments to use different value for each environment. For example, mycomposite-cfgplan.xml
Name of the partition to hold the composite on the server.
|SOA Overwrite Revision|
Flag to indicate if the composite revision on the server should be overwritten or a new revision created (see special considerations).
|SOA Make Default Revision|
Flag to indicate if the deployed composite should be marked as the default revision.
|Deploy Config Plan|
Deployment config plan that is to be used for the composite. Takes a Wildcard expression or filename. Can be a relative or absolute path (see special considerations).
Provide the composite revision, this input will override the
SOA Overwrite Revision project property (see special considerations).
|Stop On Purge Failure|
|No||Provides the ability to control whether a failed purge stops the workflow (default is False)|
|Activate Purge On Deploy|
|No||Activates the composite revision purge on deploy feature (default is False)|
|Preview Mode For Purge|
|No||Activates the purge preview mode. If purge is activated, preview mode will show in the logs the composite revisions that would have been purged with no purge occurring. (default is False) see Composite Revision Purge for examples|
Revision of the composite for this deployment.
Revision of the composite for the previous default revision.
This operation consumes an SCA composite jar from the artifacts repository.
This operation will select all available endpoints associated to the Environment/Instance.
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
SOA Extend Classpath environment variable to extend the plugin classpath to allow the compile to succeed with custom java classes or xpath functions.
When patching a long running process revision that isn't the default revision, the patching process will make the patched revision the default revision.
The revision for a composite is calculated unless either
Composite Revision (plugin input) is used or
SOA Overwrite Revision (project property) is checked. The input will override all revision logic and use the value that is passed in. If the input is empty and the project property is unchecked, then the plugin will determine the largest revision on the server and increment the revision before deploying. The revision format is
N.nn[.nn][.nn] with an initial value of 1.0, with
N – initial segment that will increment with no limitation
nn – 0 through 99, when segment hits 100 it rolls to the next higher segment
|Current revision||Next revision|
Composite Revision Purge
The composite revision purge will undeploy specific revisions based on the "Composite Revisions To Keep" environment/instance property, defaulted to 1. The retained revisions will start at the default revision and retain composites until the property value is met. If there are more recent revisions than the default revision, those recent revisions will also be retained but will not count against the property value. Default revision is bold and Composite Revisions To Keep is 2.
|Revision Ex 1||Action||Revision Ex 2||Action|
|1.02||purged||1.02||kept due to property count|
|1.03||purged||1.03||kept due to default revision|
|1.04||kept due to property count||1.04||kept due to more recent than default revision|
|1.05||kept due to default revision||1.05||kept due to more recent than default revision|
In addition, the Preview Mode For Purge input can activate the preview feature that will show the revisions that would have been purged in the logs. No purge will occur in preview mode.
See Configuration Plans
See the Appendix.