/
Oracle E-Business Suite

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, it’s aim is to provide an end 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.

Objective

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.  In this tutorial, we will source the customizations from a GitHub repository, and deploy them to a Development Environment.

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

Checklist

Checklist

Description

Checklist

Description

Tomcat

Recommended install option contains Tomcat (no separate install required)

SCM provider

Git provider : GitHub, Gitlab, BitBucket, Azure Devops, Oracle etc.

Other supported source control management:

  • Subversion

  • Git

  • Microsoft TFS Version Control

  • PVCS

  • CVS

  • Perforce

  • File System

SCM repository URL

The URL of the source control management repository.

SCM account user name

The username to login to the repository.

SCM account password

The password to login to the repository.

Review existing SCM directory structure

Recommended source control structure Source Control Folder Structure .

EBS Custom TOP name

Name of the custom top you will deploy to.

EBS Environment File (e.g. EBSapps.env)

The Fully qualified path to the environment file. This is the environment file outside of fs1/fs2 filesystem.

Apps Password

The password for apps user.

User id which runs EBS (e.g. applmgr)

FlexDeploy will connect to target server using this user.

Password for user id

Password to connect to the target server.

JDK home for primary app-tier host

Recommend JDK 1.8 installed outside of fs1/fs2.

If EBS 12.2.x, do you deploy customizations using ADOP?

If using EBS 12.2.x, check whether you have any ADOP patching phases.

Create EBS Project using Blueprint

The assumption is that you have FlexDeploy installed and ready for use. When logged into the FlexDeploy, you will see the Home page. Click on the + icon on the top and click “Create Project” to create a new project.