soaBuild
- Copy Page Tree
- Chandresh Patel
- Dan Reynebeau
Compiles and generates an SCA artifact for the composite that can be deployed to the server. 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 operation should be run on a SOA server. To accomplish this, Flexagon recommends checking the "Build Environment" checkbox for Development environment that is mapped to your SOA Instance. You do not have to create a special build environment for this purpose.
Generated SCM artifact can 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 DEV, QA, PRODUCTION environments, then Build workflow can be executed in DEV environment and generated project version can be deployed to DEV, QA and PRODUCTION at appropriate times. If version in FlexDeploy state 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, build operation will discover and save them in configPlans folder under artifacts and will be available at deploy time as well. You can indicate configuration plan to use during deploy at project level or globally in workflow, for more details see soaDeploy operation.
@Since 5.1.0.1, this operation detects XML files containing word cfgplan in name as artifacts to use during deploy operation even when these files are not in root folder of composite.
Environment/Instance Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| 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 |
Project Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
SOA Composite Name | FDSOA_COMPOSITE_NAME | Yes | Name of the composite that is being built and 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.
Endpoint Selection
This operation will select all available endpoints associated to the Environment/Instance.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
This operation doesn't perform any property replacement since the environment is unknown at build time.
Utilize the SOA Extend Classpath environment variable to extend the plugin classpath to allow the compile to succeed with custom java classes or xpath functions.
Configuration plans
During the build workflow, all configuration plans within the checked-out composite are discovered and saved in FlexDeploy artifacts under configPlans sub-folder. All artifacts, including the configuration plans, will be saved in the artifact repository for use during Deploy workflow executions.
- style