The following folder structure is recommended for Source Control (SVN, GIT, TFVC, CVS etc). You can follow a different structure than this, but you will need the * Source Directory properties at the FlexDeploy project level to make sure the files are processed correctly. For example, if you put Java code is a different folder, just update EBS Java Root Source Directory property on your project to folder name where you are storing Java files.
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.
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. |
|
In this Source Control setup we have created one folder for each extension which will contain files developed for that specific extension. It is important to note that folder structure under each extension has folders like cp_sql, sql, import, workflows, publisher etc. to identify specific files. The workflows folder can hold both wft and wfx files. Each extension folder will be used to create new FlexDeploy project. |
|