XDF is used to store high-dimensional data and information related to it in compact XML format. The purpose is to have interchangeable and high-quality format that can be used as a main archive format for this kind of data.
Object Type Identification
Files with extension .xdf are considered regardless of location.
File Extensions
File content is also further analyzed by populate process.
Name | Description |
|---|---|
.xdf | XML Definition File for storing high-dimensional data and related information. |
Object Type
Name | Code |
|---|---|
XML Definition Files (XDF) |
|
Object Type Attributes
Name | Code | Description | Default Value | Supported Values |
|---|---|---|---|---|
Source |
| Object Source Location Type | SCM | SCM |
Target Location |
| Path to where the file should be deployed to. | $<PROD_TOP>/patch/115/xdf/ | |
Primary Object Schema Property |
| FlexDeploy property to use as the user to connect to the database with. | If the xdf file contains "Primary Object Schema Name :" then the value becomes
|
| |||
Primary Object Password Property |
| FlexDeploy property to use as the password for the DB User Property. | If the xdf file contains "Primary Object Schema Name :" then the value becomes
|
| ||||
JDBC Protocol |
| Driver type for the database. | thin | thin | oci8 |
Object Type |
| XDF Object Type | all | all | table | qtable | mview | mviewlog | sequence | type | trigger | view | policy |
XSL Directory |
| Path to where the xsl folder is located. | $FND_TOP/patch/115/xdf/xsl | |
Target File Permissions |
| Permissions to apply to the file after it is deployed | Defaults to the project property FDEBS_FILE_PERMISSIONS |
| Note |
|---|
note1If the FDEBS_SCHEMA${SCHEMA_NAME}_DB_USER and FDEBS_SCHEMA${SCHEMA_NAME}_DB_PASSWORD properties are used, these properties need to be added to the workflow as user defined Targets properties and then configured on the topology screen. |
Related Project Properties
Name | Code | Description |
|---|
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.
Note1
If the FDEBS_SCHEMA${SCHEMA_NAME}_DB_USER and FDEBS_SCHEMA${SCHEMA_NAME}_DB_PASSWORD properties are used, these properties need to be added to the workflow as user defined environment/instances properties and then configured on the topology screen.
Sample Deploy Commands
| Code Block | ||||
|---|---|---|---|---|
| ||||
cp "$SOURCE_FILE" "$XXHR_TOP/patch/115/xdf/"; java oracle.apps.fnd.odf2.FndXdfCmp $FDEBS_DB_USER $FDEBS_DB_PASSWORD $FDEBS_DB_USER $FDEBS_DB_PASSWORD thin "$AD_APPS_JDBC_URL" all "$XXHR_TOP/patch/115/xdf/POS_BANK_PAYEE_BO.xdf" $FND_TOP/patch/115/xdf/xsl |