deploy (EBS)

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.

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

FDEBS_SOURCE_SCRIPT

Yes

Source Script with full path. 
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

Adding patch to the end is not allowed. This is because it will be added automatically if run is not added and you are deploying.

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.

EBS Database User

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.

EBS Database Password

FDEBS_DB_PASSWORD

Yes

Password to connect for EBS Database User.

EBS System Password

FDEBS_SYSTEM_PASSWORD

For ADOP

SYSTEM Password for AD Online Patching.

Project Properties

Property Name

Property Code

Required

Description

EBS Application Short Name

FDEBS_APPLICATION_SHORT_NAME


App short name (e.g. XXAR). If source includes multiple custom tops, leave it empty and make sure top directory matches top name.
OAF Java Root Destination Directory

FDEBS_JAVA_ROOT_DESTINATION_DIR

No

Target directory for java,class,xml files.
Eg: $JAVA_TOP/MyCompany
Default is $JAVA_TOP

OAF Java Classpath

FDEBS_JAVA_CLASSPATH

No

Set the classpath, if needed for Java Compilation.
Added along with the default classpath while compiling java files.

OAF MDS Root Destination Directory

FDEBS_MDS_ROOT_DESTINATION_DIR

No

Tar