...
See below some examples of Source Control folder structure and FlexDeploy project organization. These are just some of the recommendations, as there are numerous combinations possible.
| Info |
|---|
Note that FlexDeploy project deploys customizations to one EBS TOP. You can have files in FlexDeploy Project that deploy to multiple EBS TOP but that would require updating various properties manually. |
| Source Control Structure | FlexDeploy Project Setup |
|---|
This is most common Source Control Folder structure. There is a folder for custom top and sub-folders for types of files.  Image Modified
| - Option 1
- You can create FlexDeploy Project named XXHR and point it's source configurations to XXHR folder in Source Control Repository. All files populated in this FlexDeploy project will look like /cp_sql/my.sql, /import/my.ldt.
- Developers can create Package with files they are interested in and deploy to various environments.
- As always, files can also be added to be pulled from EBS instead of Source Control Repository.
- Option 2 (Not Recommended)
- You can create FlexDeploy Application named XXHR with and multiple projects under to include specific set of files or folder. You will still point this project to XXHR folder in Source Control Repository. Only part of the files populated in this FlexDeploy project and they will look like /cp_sql/my.sql, /import/my.ldt.
- You can control files or folders populated in project by using Project File Includes and Project File Excludes property on Project.
- Developers can create Package with files they are interested in and deploy to various environments.
- As always, files can also be added to be pulled from EBS instead of Source Control Repository.
- This is not recommended option as Source Control Structure does not match FlexDeploy project setup, but there are not technical limitations here.
|
|
|