Objective
You have a given SOA composite that was developed in JDeveloper and the source code is managed in a GIT repository. The goal of the tutorial is to automate the deployment of the composite across multiple environments. This automation will include:
...
Scroll through this guide to fill in the blueprint properties. It is a best practice to name the Project with the same name as the SOA Composite, a FlexDeploy property (ProjectName and FD_PROJECT_NAME) will be automatically set and can be utilized during the configuration.
...
Build and Deploy Workflows
...
Project Properties
These properties are project scoped resources and can be changed per project. The plugin operations that were added to the workflows determine the available project properties that can be configured. The property that are updated are the and SOA Composite Name and SOA partition, which is the organizational structure for composites on the SOA server. You can filter out the properties by using the search filter properties in the top.
...
Select Topology from the menu and then select Topology Overview from the left menu. You will see a table that has Instances as the rows and Environments as the columns with colored circles representing the Environment InstanceTarget. Color coding represents:
...
Selecting the GREEN circle for DEV will display the configurable properties/Endpoint and allows for the configuration of the properties.
...
The Build Request Form will appear and we need to:
select the environment we want to build the composite in, the environments that had the Build Environment checkbox will appear in the dropdown
select the SCM Branch that was configured on the project, this will be pre-populated if there is only one configured Branch.
submit the request, this will initiate the soaBuild workflow
...
Upon submission, the build workflow is initiated and the workflow steps are executed on the SOA instance in the Dev environment, utilizing the SOADEV endpoint. Upon completion of the workflow, the execution status will be successful.
...
With the successful execution of the build, a SAR file artifact is created, stored in the artifact repository and marked with the Project Version. Every build will generate a new Project Version. The generated SAR artifact and the discovered project specific config plans can be viewed from the Execution Id link and the Artifacts tab.
...
Now the composite can be deployed to an environment by selecting the icon as shown in the below screenshot.
...
The Deploy Request Form will appear and we need to:
The Project Version will be updated same as the build project version. However, the dropdown will contain all previously create Project Versions
select the Environment that the deployment will be executed in
The Deploy Instance, will be updated same as the deploy instance on the General Configuration. However, Deployments can happen on multiple instances.
submit the request, this will initiate the soaDeploy workflow
...
Upon submission, the deploy workflow is initiated and the workflow steps are executed on the SOA instance in the Dev environment, utilizing the SOADEV endpoint. Upon completion of the workflow, the execution status will be successful. With the successful execution of the deploy, the SAR file artifact will be deployed to the Dev environment.
...
The Execution Id is a link to all of the execution data related to each request, such as
the workflow execution steps
the logs for each workflow
...
step, which can be viewed by clicking on the link under the step
the artifact, which can be downloaded
the project and environment instance property values at the time of execution
...
Congratulations! You have successfully completed the SOA Suite tutorial.
...