Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

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 

NameDescription
.javaJava programming language source file containing Java classes.
.classCompiled Java class
.xmlExtensible Markup Language file format used to create common information formats and share both the format and the data using standard ASCII text.
.zipzip file
.earEnterprise Application Archive file
.jarJava Archive file.

Object Type Code

OAF_JAVA

Attributes

NameAttribute CodeDescriptionDefault ValueSupported Values
SourceSOURCEObject Source Location Type

SCM

SCM
Target LocationTARGET_LOCATIONPath to where the file should be deployed to.

$<PROD_TOP>/<package path>


Java ClasspathCLASSPATHLocation of user-defined classes and packages.$CLASSPATH
Target File PermissionFILE_PERMISSIONSPermissions to apply to the file after it is deployedDefaults to the project property FDEBS_FILE_PERMISSIONS

Related Project Properties

Name
DescriptionDefault Value
EBS Java Root Source DirectoryFDEBS_JAVA_ROOT_SOURCE_DIRWhere java/class/xml file's package resides. (e.g. classes).java
EBS Java Root Destination DirectoryFDEBS_JAVA_ROOT_DESTINATION_DIRTarget directory for java,class,xml files.$JAVA_TOP
EBS Java ClasspathFDEBS_JAVA_CLASSPATHLocation of user-defined classes and packages. Set the classpath if needed for Java Compilation.
File PermissionsFDEBS_FILE_PERMISSIONSTarget File Permission. Will be set to target file after deployment using chmod. eg: 755Target 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 & JPX - 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.



  • No labels