Blog
FlexDeploy DevOps Loves Oracle Fusion Middleware

FlexDeploy Loves Oracle Fusion Middleware: Overview

Continuous integration and continuous delivery (CI/CD) are increasingly popular DevOps practices where code changes are frequently committed to a source control management (SCM), and automatically built, tested and submitted to a release pipeline for deployment.

The initial stage of the release pipeline will deploy the changes to a development environment where it can be tested. Upon successful completion of the test, the changes will be propagated through a sequence of environments based on environment entry criteria.

Over the course of an upcoming blog series I’ll show how these concepts, along with release automation are implemented within FlexDeploy, breaking down the details for SOA, MDS, OSB, and WebLogic Resource Management. The following blogs are part of the overall Oracle Fusion Middleware series.

If you’re interested in getting a preview, check out this webinar recording. You will get a deep dive of FlexDeploy’s support for the SOA Suite, WebLogic resources, and the Oracle Integration Cloud.

Next Blog

4 thoughts on “FlexDeploy Loves Oracle Fusion Middleware: Overview”

  1. Sudhakar Verma

    Hi ,
    I am trying to build the SOA composite but getting below error.

    StepId: 2
    Error Code: FDSV-00454
    Error Detail: FDSV-00454: Endpoint Call Failed.
    flexagon.fd.core.exceptions.FlexRemotePluginException: java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildListener

  2. Sudhakar Verma

    Thanks Dan for the quick response, i am applying the suggestion provided by you. Quick question from my side is, While building the SOA composite , it looks like SOA composite code needs to be on the SOA server endpoint.

    1. Yes, all code needs to be available on the end point for the build. The GIT plugin will handle the retrieval of the respective code and then the SOA plugin knows where the extracted code resides and build it with no manual intervention. Once the composite is built, the SAR file will be returned to FlexDeploy and the repository as an artifact that can be used for the deployment.

      Dan

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top