soaDeploy
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. You must have built SCA artifact or the patch artifact (12.2.1+ only) as part of soaBuild operation prior to running deploy, i.e. soaBuild execution generates artifact file and is recorded in FlexDeploy as project version and then deployment is done using that project version to specific environments. Composite specific configuration plans or global configuration plans can be used during deploy, see information on project property and plugin input below.
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.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
SOA Server Host |
| Yes | Host name of the SOA managed server. |
SOA Server Port |
| Yes | Port number of the SOA managed server. |
Weblogic Admin User |
| Yes | Admin user name for WebLogic server. |
Weblogic Admin Password |
| Yes |
|
MDS UserID |
| Yes | User name for MDS access. |
MDS Password |
| Yes | Password for |
MDS JDBC URL |
| Yes | Database URL for MDS access. |
Oracle SOA Home |
| Yes | Oracle SOA Home, indicates where SOA Suite is installed. |
SOA Extend Classpath |
| No | Ability to extend the plugin classpath for external java classes or custom xpath functions |
Composite Revisions To Keep | FDSOA_REVISIONS_TO_KEEP | No | Number of composite revisions to retain on the server after successful deployment |
Project Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
SOA Composite Name |
| Yes | Name of composite that is being deployed. |
SOA Deploy Config Plan |
| No | Ability to define config plan specific to a composite. (see soaDeploy#configurationplans section below). 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 |
SOA Partition |
|