A framework for application development within E-Business Suite. The framework is also available for personalizations, customizations and custom-application development.
Object Type Identification
- Files with extensions .jpx, are included regardless of location
- Files with extensions .xml, are included if they are in the webui folder.
File Extensions
| Name | Description |
|---|---|
| .xml | Extensible Markup Language file format used to create common information formats and share both the format and the data using standard ASCII text. File path must contain webui for xml file to be qualified as OAF MDS type. |
| .jpx | Jbo project metadata file |
...
| Name | Description | Default Value | Supported Values |
|---|---|---|---|
| Source | Object Source Location Type | SCM (**populating from SCM) EBS (**manual creation) | SCM | EBS |
| Target Location | Path to where the file should be deployed to. | $<PROD_TOP>/mds | |
| Root Directory | Location of user-defined classes and packages. | $<PROD_TOP>/mds |
...
| Name | Description | Default Value |
|---|---|---|
| EBS Java Root Source Directory Sub-directory within project's SCM source path which contains AOLs | Where java/class/xml file's package resides. (e.g. classes) Default is java. | java |
| EBS Java Root Destination Directory | Sub-directory within project's deploy path to contain AOLsTarget directory for java,class,xml files. Default is $JAVA_TOP. (e.g. $JAVA_TOP/MyCompany). | $JAVA_TOP |
| EBS Java Classpath | Location of user-defined classes and packages. |
...
- All OAF MDS related files must be sourced controlled under a directory structure matching the Java package structure. This is a requirement to ensure the generated deploy commands copy them to the correct location under the $JAVA_TOP. If this requirement is not met, you will need to modify each of the target location paths and re-evaluate the commands. See example below where xxPersonMainPG.xml file is placed in xxt/oracle/apps/ak/xxperson/webui under java folder.
