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:

...

Viewing the current list of Integrations is achieved by selecting Topology from the menu, then the Integrations tab from the left-hand pane.  There are eleven types of integrations in FlexDeploy, but we will focus on Source Control in this tutorial.

...

...

Select Topology from the menu.  You will see a list of Target Groups. If you click one, you will see the environments that are associated with colored circles representing the Target health.

Color coding represents:

• RED - The Endpoint is not configured

• YELLOW - Some required properties are not set. The Endpoint is configured

• GREEN - all required properties are set and the Endpoint is configured

...

Topology

Navigate to the Topology from the Menu. The Page with the Target Groups, Environments and Endpoints sections will be displayed.

...

Click on SOA1 Target Group and click on the Development Environment

...

Targets Properties

Click on the Development Environment and user will be able to see the target properties and endpoints mapped.

...

Build Execution

FlexDeploy is configured with everything that is required to execute a build and deploy request for the SOA composite, we can execute the first build.  Click on Execution tab to submit the build request for that package. Click on Build.

...

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.

...