Deploys EBS Artifacts to the specified EBS server. This operation checks each file for changes and only deploys each file if it has changed or is set to forced. This operation is equal to apply phase if you are using adop phases for applying manual changes. The environment/instance property for the source script can be used to choose what patch mode is used. If the source script is just the path to the source script, the deployment is equivalent to apply_mode=online, and the files are applied to the patch edition. If instead, " run" is appended to the source script, the deployment can be done equivalently to either downtime or hotpatch apply_mode by either leaving the server running, or stopping it before the operation. If you do not wish to use ADOP, append the " run" to the end of the source script.
Files will be deployed in the order saved in the build step. If the order of deployment must be adjusted, perform a new build. See the build operation for more information about ordering files or search the wiki for more information.
If you need to execute the SQL files other than the default user (EBS Database User
), you need to prefix the file name with SCHEMAXXX_. Eg: SCHEMAPOS_PER_SQF.sql and define a pair of properties on your workflow as below:
- FDEBS_DB_SCHEMAPOS_USER
- FDEBS_DB_SCHEMAPOS_PASSWORD
If you need to execute the XDF files other than default user, please create the pair of properties for primary schema as above.
See also EBS Object Types Reference for a list of supported EBS object types.
Info |
---|
If performing clone operations between environments, consider using the Post Refresh utilities of flexDeploy. Read more on the Post Refresh Requests page. (new in 5.0) |
...
Deploys EBS Artifacts to the specified EBS server. This operation checks each file for changes and only deploys each file if it has changed or is set to forced. This operation is equal to apply phase if you are using adop phases for applying manual changes. The environment/instance property for the source script can be used to choose what patch mode is used. If the source script is just the path to the source script, the deployment is equivalent to apply_mode=online, and the files are applied to the patch edition. If instead, " run" is appended to the source script, the deployment can be done equivalently to either downtime or hotpatch apply_mode by either leaving the server running, or stopping it before the operation. If you do not wish to use ADOP, append the " run" to the end of the source script.
Files will be deployed in the order saved in the build step. If the order of deployment must be adjusted, perform a new build. See the build operation for more information about ordering files or search the wiki for more information.
If you need to execute the SQL files other than the default user (EBS Database User
), you need to prefix the file name with SCHEMAXXX_. Eg: SCHEMAPOS_PER_SQF.sql and define a pair of properties on your workflow as below:
- FDEBS_DB_SCHEMAPOS_USER
- FDEBS_DB_SCHEMAPOS_PASSWORD
If you need to execute the XDF files other than default user, please create the pair of properties for primary schema as above.
See also EBS Object Types Reference for a list of supported EBS object types.
Info |
---|
If performing clone operations between environments, consider using the Post Refresh utilities of flexDeploy. Read more on the Post Refresh Requests page. (new in 5.0) |
Environment/Instance Properties
Property Name | Property Code | Required | Description | ||
---|---|---|---|---|---|
EBS Source Script |
| Yes | Source Script with full path. If you would like to apply changes directly to run edition for EBS R 12.2+, specify the run param after the script. By default it connects to patch edition when performing the deploy operation. All other operations are sourced from run by default. e.g.
| ||
EBS Database User |
| Yes | DB User to connect with privileges. | ||
EBS Database Password |
| Yes | Password to connect for | ||
EBS System Password |
| For ADOP | SYSTEM Password for AD Online Patching. |
Project Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
EBS |
Application Short Name |
|
|
Yes
| App short name (e.g. |
/u1/apps/apps_st/appl/APPSorcl_ebs01.env
If you would like to apply changes directly to run edition for EBS R 12.2+, specify the run param after the script. By default it connects to patch edition when performing the deploy operation. All other operations are sourced from run by default.
e.g. /u1/apps/apps_st/appl/APPSorcl_ebs01.env
run
Tip |
---|
If you are adding more than one endpoint for an environment/instance, this file must be same location for all endpoints. If necessary you should create symbolic links on each endpoint, so location of environment file is same. |
FDEBS_DB_USER
Yes
DB User to connect with privileges.
eg: Apps.
Make sure you have permission to execute sqls with this user for all schemas.
FDEBS_DB_PASSWORD
Yes
Password to connect for EBS Database User
.
FDEBS_SYSTEM_PASSWORD
For ADOP
SYSTEM Password for AD Online Patching.
Project Properties
Property Code
Required
Description
FDEBS_STOP_ON_ERROR
No
Stop deploying, if any error occurs. If false or not specified, deploying of other files will be continued.
FDEBS_JAVA_CLASSPATH
No
Set the classpath, if needed for Java Compilation.
Added along with the default classpath while compiling java files.
FDEBS_WORKFLOW_CLASSPATH
No
Set the classpath, if needed for Workflow Load (WFXLoad).
FDEBS_FORMS_CLASSPATH
No
Set the classpath, if needed for Forms compilation.
FDEBS_SQL_RETRY_COUNT
No
Retry count for SQLs and PL/SQLs. Default is 5
XXAR). If source includes multiple custom tops, leave it empty and make sure top directory matches top name. | |||
OAF Java Root Destination Directory |
| No | Target directory for java,class,xml files. |
OAF Java Classpath |
| No | Set the classpath, if needed for Java Compilation. |
OAF MDS Root Destination Directory |
| No | Target directory for MDS files (webui xmls). Default is PROD_TOP/mds. (e.g. $XXHR_TOP/mds). |
Concurrent Program SQL Root Destination Directory |
| No | Target directory for Concurrent Program's SQLs (Not executed after deploy). |
Java Stored Procedure Root Destination Directory |
| No | Target directory for Java Stored Procedure files. |
SQL Root Destination Directory |
| No | Target directory for SQL and PLS files. |
SQL Retry Count |
| No | Retry count for SQLs and PL/SQLs. Default is 5 |
SQL Ignore Compile Errors |
| No | Ignore SQL compilation errors. |
SQL*Loader Root Destination Directory |
| No | Target directory for control (ctl) files. |
FDEBS_AOL_ROOT_DESTINATION_DIR | No | Target directory for AOL (ldt) files. | |
Forms Root Destination Directory |
| No | Target directory for |
form files ( |
fmx) |
. |
$XXAR_TOP/ |
forms |
$PROD_TOP/ |
forms | |
Forms Root Stage Directory |
|
|
| No |
Stage directory for |
form files (fmb). |
$XXAR_TOP/ |
forms. |
AU_TOP/ |
forms. | |||
Forms Classpath |
| No | Set the classpath, if needed for Forms compilation. |
Reports Root Destination Directory |
|
| No | Target directory for |
report files. |
$XXAR_TOP/ |
reports |
$PROD_TOP/ |
reports |
Workflow Root Destination Directory |
|
| No | Target directory for |
workflow files. |
$XXAR_TOP/ |
workflow |
$PROD_TOP |
/patch/115/import | |
Workflow Upload Mode | FDEBS_ |
WORKFLOWS_ |
UPLOAD_ |
FDEBS_FORMS_ROOT_STAGE_DIR
No
Stage directory for form files (fmb).
Eg: $XXAR_TOP/forms.
Default is AU_TOP/forms.
MODE | No |
Target directory for form files (fmx).
Eg: $XXAR_TOP/forms
Default is $PROD_TOP/forms
Upload Mode for WFLOAD. [UPLOAD, UPGRADE, FORCE] Default is UPLOAD. | |||
Workflow Classpath |
| No | Set the classpath, if needed for Workflow Load (WFXLoad). |
Libraries Root Destination Directory | FDEBS_ |
LIBRARIES_ROOT_DESTINATION_DIR | No | Target directory for |
form library files (plx). |
Default is PROD_TOP/ |
Default is $PROD
forms. (e.g. $XXAR_TOP/ |
forms). | |
Publisher Root Destination Directory |
|
| No | Target directory for |
Publisher files. |
$XXHR_TOP/publisher. |
Default is $OA_MEDIA
FDEBS_HTML_ROOT_DESTINATION_DIR
No
Target directory for html files.
Eg: $XXAR_TOP/html
Default is $OA_HTML.
/patch/115/publisher. | |||
Publisher Default Custom Mode | FDEBS_PUBLISHER_CUSTOM_MODE | No | When populating or evaluating files deployed with XDOLoader, set the CUSTOM_MODE of publisher files to this. [FORCE, NOFORCE] Default is FORCE. |
Fonts Root Destination Directory |
| No | Target directory for font files. |
Scripts Root Destination Directory |
| No | Target directory for script files. |
Perl Module Root Destination Directory |
| No | Target directory for perl modules. |
Media Root Destination Directory |
|
| No | Target directory for |
image files. |
$XXAR_TOP/ |
media |
$OA_MEDIA | |
HTML Root Destination Directory |
|
| No | Target directory for |
html files. |
$XXAR_TOP/ |
html |
FDEBS_DAT_ROOT_DESTINATION_DIR
No
Target directory for Dat files.
Eg: $XXHR_TOP/admin/import.
Default is PROD_TOP/patch/115/import.
FDEBS_SQL_LDR_ROOT_DESTINATION_DIR
No
Target directory for control (ctl) files.
Eg: $XXHR_TOP/admin/bin.
Default is PROD_TOP/bin.
FDEBS_LOAD_JAVA_ROOT_DESTINATION_DIR
No
Target directory for Java Stored Procedure files.
Eg: $XXHR_TOP/java.
Default is JAVA_TOP.
FDEBS_ PUBLISHER_ROOT_DESTINATION_DIR
No
Target directory for Publisher files.
Eg: $XXHR_TOP/publisher.
Default is PROD_TOP/patch/115/publisher.
FDEBS_WORKFLOWS_UPLOAD_MODE
Upload Mode for WFLOAD. [UPLOAD, UPGRADE, FORCE]
Default is UPLOAD.
FDEBS_PUBLISHER_CUSTOM_MODE
When populating or evaluating files deployed with XDOLoader, set the CUSTOM_MODE of publisher files to this.
[FORCE, NOFORCE]
Default is FORCE.
FDEBS_IGNORE_ERRORS_FILE_LIST
No
List of files (allowing wildcards) to ignore errors. (e.g: DropHRTables.sql, CreateTables.sql, *_ddl.sql)
FDEBS_JSP_COMPILE
The selected option will be used while generating deploy command for JSP files.
Default is No. Jsp files will not be compiled.
If set to Compile, the JSP files will be compiled.
The other option is Compile with Flush which will compile all deployed jsp files and their parents.$OA_HTML. | |||
FDEBS_JSP_COMPILE | No | The selected option will be used while generating deploy command for JSP files. Default is No. Jsp files will not be compiled. If set to Compile, the JSP files will be compiled. The other option is Compile with Flush which will compile all deployed jsp files and their parents. | |
Stop on Error |
| No | Stop deploying, if any error occurs. If false or not specified, deploying of other files will be continued. |
Ignore Errors File List |
| No | List of files (allowing wildcards) to ignore errors. (e.g: DropHRTables.sql, CreateTables.sql, *_ddl.sql) |
| Target File Permission. The target file will be set to this permission level after deployment using chmod. eg: 755 | ||
| List of files to exclude while Building. Only used in Full Deployment Mode. (e.g. server.xml,web.xml). | ||
| Controls files included in Project Files. Enter expressions separated by ##. Leave empty to select all files. Begin or end the expression with * for simple wildcards. Otherwise, regex is used. (e.g. /java/*##*.java##*person*##/java/.*[tT]est.*\.java) | ||
| Controls files excluded from Project Files. Enter expressions separated by ##. Leave empty to select all files. Begin or end the expression with * for simple wildcards. Otherwise, regex is used. (e.g. /java/*##*.java##*person*##/java/.*[tT]est.*\.java) |
Inputs
Input Name | Input Code | Required | Description |
---|---|---|---|
Force Files |
| No | List of files to force to be deployed even if they haven't changed. The value This is used by Full Deployment Projects only. |
Skip Files | FDEBS_INP_SKIP_FILES | No | Skip files from Package. Separate files with comma. Not applicable for Full Deployment. Use ALL to skip all files. |
Include Object Types |
| No | Select types that should be deployed. If nothing selected, all types will be deployed. Partial Deployments only. Select one or more object types. This option is useful when files are deployed selectively across application tier nodes. |
Exclude Object Types |
| No | Select types that should not be deployed. Partial Deployments only. Select one or more object types. This option is useful when files are deployed selectively across application tier nodes. |
...