Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

The Oracle EBS Customizations blueprint will create the topology, workflows, source control repository connection, and project for managing the build and deployment of an EBS custom TOP. 

  • The Development environment is both the build environment and the single target environment mapped to for deployment.
  • The build instance instance is also used for deployment.
  • The build workflow, Build EBS, is created/linked and bound to all EBS projects created through this blueprint.
  • The deploy workflow, Deploy EBS, is created once and bound to all EBS projects created through this blueprint.
  • The instance is created based on the EBS verison. 
    • One instance, EBS 12.1.3, is created and shared by all EBS 12.1.3 projects created through this blueprint.
    • One instance, EBS 12.2, is created and shared by all EBS 12.2 projects created through this blueprint.


Blueprint Properties

Property NameRequiredDescriptionHow its used
Module Short NameYesThe module short name for the custom top (do not include "_TOP" in the name).  e.g. XXHR, XXAR, XXACME
  • FlexDeploy project is named using this value
  • FlexDeploy project property is configured to this value
EBS VersionYesWhether the project is for Oracle EBS 12.1.3 or 12.2
  • FlexDeploy instance is created using this value
  • FlexDeploy project is mapped to the instance
Module DescriptionNoA description for the EBS project
  • FlexDeploy project's description is set to this value

Build

All EBS Customizations are built using FlexDeploy's Oracle EBS Plugin (with Partial Deployment).  As such, the only build option is Build EBS,and is selected by default. 

There are no Build Properties for this blueprint.

A single Development endpoint is created and linked to all EBS Customization projects for each instance (12.1.3/12.2).

Which endpoint?

If you will be sourcing all EBS customization files from source control the build endpoint can really be any server.  If you will source some of the EBS customizations from the EBS development server itself, you will need to set the build endpoint to be the primary node of the EBS application-tier in development.


Deploy

All EBS Customizations are deployed using FlexDeploy's Oracle EBS Plugin (with Partial Deployment).  As such, the only build option is Deploy EBS, and is selected by default. 

Deploy Properties

  • No labels