...
- 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 once and bound to all EBS projects created through using this blueprint.
- The deploy workflow, Deploy EBS, is created once and bound to all EBS projects created through using this blueprint.
- The instance is created based on the EBS verisonversion.
- One instance, EBS 12.1.3, is created and shared by all EBS 12.1.3 projects created through using this blueprint.
- One instance, EBS 12.2, is created and shared by all EBS 12.2 projects created through using this blueprint.
Blueprint Properties
Property Name | Required | Description | How its used |
---|---|---|---|
Module Short Name | Yes | The module short name for the custom top (do not include "_TOP" in the name). e.g. XXHR, XXAR, XXACME |
|
EBS Version | Yes | Whether the project is for Oracle EBS 12.1.3 or 12.2 |
|
Module Description | No | A description for the EBS project |
|
Build
All EBS Customizations are built using FlexDeploy's Oracle EBS Plugin (with Partial Deployment). As such, the only and default build option is Build EBS,and is selected by default.
Build Properties
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).
Tip | ||
---|---|---|
| ||
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 The endpoint must be any node of the application-tier server. If you add more than one endpoint, one of them will be used at build/deploy time. |
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
Property Name | Required | Description | How its used |
---|---|---|---|
EBS Source Script | Yes | Provide environment script with fully qualified path. If EBS 12.2 use run suffix after environment script name for this value. | FlexDeploy environment instance property is configured to this value |
EBS Database User | Yes | This will default to apps, which is correct value. | FlexDeploy environment instance property is configured to this value |
EBS Database Password | Yes | Provider password for apps user in development environment. | FlexDeploy environment instance property is configured to this value |
Tip | ||
---|---|---|
| ||
The endpoint must be any node of the application-tier server. If you add more than one endpoint, one of them will be used at build/deploy time. |