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 Deployment models.
...
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
| Oracle SQLcl Home | FD_SQLCL_HOME | Yes* | Folder where SQLcl is installed. |
| APEX User | FDAPEX_USER | Yes* | Provide database user APEX_xxxxx 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. |
| Oracle Database URL | FDORA_URL | Yes* | JDBC URL for Oracle database. For example:
|
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
APEX Workspace Name | FDAPEX_WORKSPACE_NAME | Yes | The name of the workspace to deploy the application toAPEX Workspace Name. Provide uppercase name. Required if application id not providedThis defaults to FD_INSTANCE_CODE expression, so if you keep instance code same as your workspace, you will not need to change default value. |
| APEX Application Id | FDAPEX_APPLICATION_ID | No | Identifying number of application. If not specified, workspace name and application name must be provided. |
| APEX Application Name | FDAPEX_APPLICATION_NAME | No | The name of the application to deploy. Required if application id not provided. |
| APEX Application Alias | FDAPEX_ALIAS | No | APEX alphanumeric identifier unique within a workspace and page. If alias is not provided APEX Application Id will be used |
| APEX Offset value | FDAPEX_OFFSET | 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. |
| Use APEX Offset | FDAPEX_USE_OFFSET | No | Determines if the plugin will attempt to set the Offset. |
...