Oracle E-Business Suite

FlexDeploy provides broad and flexible support for managing the build and deployment of customizations across Oracle E-Business suite implementations.

To name a few, FlexDeploy has support for:

  • EBS 11.5.10, 12.1.x, and 12.2.x (with or without online patching)
  • One or many custom EBS Tops
  • Source your customizations from either an SCM repository or a development EBS instance. 
  • Automated change detection on deployment
  • Continuous Integration
  • Flexible Build options
  • Integration with FlexDeploy PIpeline & Release features

While this tutorial will not cover all features or design patterns for managing EBS customizations, its aim is to provide an end to example for a common use case.  Where applicable, we will call out different options, why you would consider them, and the potential benefits to your overall process.


You have a global instance of Oracle E-Business Suite with customizations in a custom top called XXHR.  The goal of this tutorial is to configure FlexDeploy to manage the lifecycle of building and deploying the customizations across the environments in your organization.  It this tutorial we will source the customizations from a GitHub repository, and deploy into three EBS instances (two instances are EBS 12.1.3 and other is EBS 12.2.6).

We will define the following constructs in FlexDeploy to accomplish this goal:

  • Topology - logical and physical architecture of your EBS implementation
  • Workflows - implementation of the build and deploy steps for EBS
  • Projects - representation of the EBS objects which we will build & deploy

Once the configuration is complete we will walk through the build and deployment life-cycle for managing your EBS software delivery.

Docker Image

A Docker image containing a fully configured FlexDeploy instance for this tutorial is available hereBe sure to select the appropriate tag based the version of the tutorial.  This image includes FlexDeploy running on Tomcat and an Oracle XE database with the completed configuration described in this tutorial.  The configuration is pointing to private EBS endpoints which you will not have access to.  You can review the configuration without executing, or use the tutorial as a reference to configure endpoints pointing to your own EBS instances.

The following macros are not currently supported in the footer:
  • style