EBS Object Types - Oracle Application Framework (OAF) JAVA

A framework for application development within E-Business Suite. The framework is also available for personalizations, customizations and custom-application development.

Object Type Identification

If a file does not qualify as Java Stored Procedure, but ends in .java, .class, .xml, .zip, .ear, or .jar, it is considered OAF Java type.
If file with .xml extension is in webui folder then it is considered MDS file

File Extensions

Name	Description

Name	Description
.java	Java programming language source file containing Java classes.
.class	Compiled Java class
.xml	Extensible Markup Language file format used to create common information formats and share both the format and the data using standard ASCII text.
.zip	zip file
.ear	Enterprise Application Archive file
.jar	Java Archive file.

Object Type

Name	Code

Name	Code
Oracle Application Framework (OAF) JAVA	`OAF_JAVA`

Object Type Attributes

Name	Code	Description	Default Value	Supported Values

Name	Code	Description	Default Value	Supported Values
Source	`SOURCE`	Object Source Location Type	SCM	SCM
Target Location	`TARGET_LOCATION`	Path to where the file should be deployed to.	$<PROD_TOP>/<package path>
Java Classpath	`CLASSPATH`	Location of user-defined classes and packages.	$CLASSPATH
Target File Permission	`FILE_PERMISSIONS`	Permissions to apply to the file after it is deployed	Defaults to the project property FDEBS_FILE_PERMISSIONS

Related Project Properties

Name	Code	Description	Default Value

Name	Code	Description	Default Value
OAF Java Root Source Directory	`FDEBS_JAVA_ROOT_SOURCE_DIR`	Where java/class/xml file's package resides. (e.g. classes).	java
OAF Java Root Destination Directory	`FDEBS_JAVA_ROOT_DESTINATION_DIR`	Target directory for java,class,xml files.	$JAVA_TOP
OAF Java Classpath	`FDEBS_JAVA_CLASSPATH`	Location of user-defined classes and packages. Set the classpath if needed for Java Compilation.
File Permissions	`FDEBS_FILE_PERMISSIONS`	Target File Permission. Will be set to target file after deployment using chmod. eg: 755

Sample Build Commands

N/A - Build commands not supported for this type.

Sample Deploy Commands

Java - copy and compile

cp "$SOURCE_FILE" "$JAVA_TOP/xxt/oracle/apps/ak/xxperson/webui/";
export CLASSPATH=$CLASSPATH;
javac -Xlint:none -classpath $CLASSPATH "$JAVA_TOP/xxt/oracle/apps/ak/xxperson/webui/xxPersonMainCO.java";

Class, XML - copy only

cp "$SOURCE_FILE" "$JAVA_TOP/xxt/oracle/apps/ak/xxperson/schema/server/";

Considerations

All OAF Java related files must be source 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 or override the Target Location attribute. See example below where xxPersonDetailsEOImpl.java file has package name xxt.oracle.apps.ak.xxperson.schema.server and is placed in xxt/oracle/apps/ak/xxperson/schema/server under java folder.