Compiles and generates an SCA artifact for the composite that can be deployed to the server. This . You should checkout or export code for Composite project (not entire JDeveloper application) from SCM prior to running this operation. Checkout or Export can be easily done if you configure project with Source details by using operations like exportProjectSources, cloneProjectSources etc. depending on SCM being used by Project.
It is good practice to create FlexDeploy project with name that matches composite name. You can create projects for all composites from same JDeveloper Application under one FlexDeploy application.
This artifact may be a full composite SAR file or it may be a sparse patch SAR file (12.2.1+ versions only), if a patch.xml file is detected in the checked out code. This
This operation should be run on a SOA server. To accomplish this, Flexagon recommends adding the SOA instance to a build environment rather than checking the "Build Environment" checkbox in a deployment environment. This will reduce the number of environments that show up when you choose to build.
Generated SCM artifact will be deployed to subsequent environments using configuration plans, so no additional compilation is done prior to deployment. You can create SOA instance in FlexDeploy and associate it to BUILD, DEV, QA, PRODUCTION environments, then Build workflow can be executed in BUILD environment and generated version can be deployed to DEV, QA and PRODUCTION at appropriate times. If version in FlexDeploy is same in all environments that means that same version of composite is deployed in all environments. If you are using composite specific configuration plans, they are discovered and saved in configPlans folder under artifacts and will be available at deploy time as well.
Environment/Instance Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| MDS UserID |
| Yes | User name for MDS access. |
| MDS Password |
| Yes | Password for MDS UserID. |
| 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 |
Project Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
SOA Composite Name | FDSOA_COMPOSITE_NAME | Yes | Name of composite that is being deployed. |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation produces a SCA composite jar as the artifact that will be stored in the artifacts repository.
...
During the build workflow, all configuration plans within the checked-out composite are discovered and saved in a separate folder (./artifacts/configPlans) under the artifacts directoryFlexDeploy artifacts under configPlans sub-folder. All artifacts, including the configuration plans, will be saved in the artifact repository for use during Deploy workflow executions.