Versions Compared

Old Version 7

changes.mady.by.user Karl Henselin

Saved on

compared with

New Version Current

changes.mady.by.user Perepa Sai Sri Mukhi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Deploys an Oracle APEX application (produced by a build workflow using the buildAPEX plugin operation) to a target database. This operation manages deployment of builds produced by both the Full Deployment and Partial Package-Based Deployment models. 

Any supporting database objects for the application are outside the scope of this operation , but can be managed in a separate project and workflows using the JDBC or Oracle Database Plugin.

...

  • If the application has never been deployed and you do not currently have an offset, the plugin can generate the offset. Just select Use APEX Offset (FDAPEX_USE_OFFSET), make sure you note the offset value used and set the propertyAPEX Offset Value (FDAPEX_OFFSET) for the next deployment.  

  • If you know the offset, select Use APEX Offset (FDAPEX_USE_OFFSET) and set the property APEX Offset Value (FDAPEX_OFFSET).

Target Properties

Property Name

Property Code

Required

Description

Oracle SQLcl Home

FD_SQLCL_HOME

Yes

Folder where SQLcl is installed.

Use JDK 8 for Endpoint Java due to SQLcl requirements.

APEX User

FDAPEX_USER

Yes

Provide database user APEX_xxxxx (APEX user requires INHERIT Privilege) or owner (parsing schema) of the application for export and import operations. You can use system user as well.

APEX Password

FDAPEX_PASSWORD

Yes

Password for APEX User.  

Run Application Only

FDAPEX_RUN_APPLICATION_ONLY

No

Deploy with Run Application Only as build status.

Oracle Database URL

FDORA_URL

Yes

JDBC URL for Oracle database. For example:

  • jdbc:oracle:thin:@HOSTNAME:PORT:SID or

  • jdbc:oracle:thin:@//HOSTNAME:PORT/SERVICENAME

Include Page
Using wallet with oracle database
Using wallet with oracle database

Project Properties

FDAPEX_OFFSET

Property Name

Property Code

Required

Description

APEX Workspace Name

code

FDAPEX_WORKSPACE_NAME

Yes

APEX Workspace Name. Provide uppercase name. This defaults to FD_INSTANCE_CODE expression, so if you keep instance code same as your workspace, you will not need to change default value.

If Workspace id is different in each environment, FlexDeploy will still be able to handle that situation by deriving workspace id from workspace name provided.

Parsing Schema

FDAPEX_DB_SCHEMA

No

Parsing schema (owner) of APEX application.

If not provided, value in exported sql file will be used, which means that schema name will be same in all environments.

APEX Application Id

code

FDAPEX_APPLICATION_ID

No

Identifying number of the application. If not specified, workspace name and application name is used to query application id, otherwise new application id will be generated.

APEX Application Name

code

FDAPEX_APPLICATION_NAME

No

The name of the application to deploy. This is used to derive application id if application id is not provided.

APEX Application Alias

FDAPEX_ALIAS

No

Application alias is set on the application being imported. If not provided, then alias set in exported sql files will be used.

Use APEX Offset

code

FDAPEX_USE_OFFSET

No

Determines if the plugin will attempt to set the Offset.

APEX Offset value

Code Block

No

The offset value during application import. This value is used to ensure that the metadata for the Application Express application definition does not collide with other metadata on the instance.

Inputs

...

Input Name

...

Input Code

...

Required

...

Description

Outputs

Output Name

Required

Description

Artifacts

This operation consumes artifacts from the artifacts repository.

...