...
Select Topology from the menu and choose a Target Group on the left. You will see a list of Environments on the right with colored circles representing each Target.
...
Color coding represents:
...
select the environment we want to build the application 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 applicationBuild workflow.
...
Upon submission, the build workflow is initiated and the workflow steps are executed on the ADF instance in the Build environment, utilizing the JDEV endpoint. Upon completion of the workflow, the execution status will be successful.
...
With the successful execution of the build, an EAR 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 EAR artifact can be viewed from the Execution Id link and the Artifacts tab.
...
Select the Project Version. The form will default to the latest Project Version but the dropdown will contain all previously create Project Versions.
Select the Environment that the deployment will be executed in.
Select the Deploy Instance, which will be defaulted from the Project configuration. Deployments can happen on multiple instances.
Submit the request, which will initiate the application Deploy workflow.
...
Upon submission, the deploy workflow is initiated and the workflow steps are executed on the ADF instance in the Dev environment, utilizing the ADFDEV 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
...