Export (APEX)

Export single APEX application to a SQL file. You must setup Apex Application Id on Project Properties for Export operation.

This operation will export application and save SQL artifact as Artifact in FlexDeploy artifact repository, which will be eventually used by Deploy operation.

Environment/Instance Properties

Property Name

Property Code

Required

Description

APEXExport Path

FDAPEX_APEXEXPORT_PATH

Yes

Directory path to the APEXExport class for example : C:\oracle\apex\utilities

Target JDBC Driver Path.
FDORA_DRIVER_PATH
YesPath containing JDBC driver for target database (e.g. /u01/app/oracle/product/12.1.0/dbhome_1/jdbc/lib/ojdbc6.jar)
Oracle Database URL
FDORA_URL
Yes

The URL for the target Oracle database. (e.g. localhost:1521:xe)

As of version 4.0.3.5, complete JDBC URL (e.g. jdbc:oracle:thin:@localhost:1521:xe) is also allowed. Versions of the plugin before 4.0.3.5 require the shorter syntax. This can cause a problem if an Oracle Database Plugin operation is used on the same instance. In that case, upgrading to the latest version of the plugin available on the support site is recommended.

Oracle Database User
FDORA_USER
YesThe username that will be used to connect to the target Oracle Database.
Oracle Database Password
FDORA_PASSWORD
YesThe password for Oracle Database User.

Project Properties

Property Name

Property Code

Required

Description

APEX Application Id
FDAPEX_APPLICATION_ID
YesThe application id for the application to be exported.

Inputs

Input Name

Input Code

Required

Description





Outputs

Output Name

Required

Description




Artifacts

This operation produces a deployable APEX sql file artifact that will be stored in the artifacts repository.

Endpoint Selection

This operation will select all available endpoints associated to the environment/instance. You must make sure that APEX Server (database) Endpoint is added to the Environment Instance as it requires uses of APEX utility.

Endpoint Execution

This operation will execute on any one of the selected endpoints and will be random in the determination of which one.

Special Considerations

This operation requires that APEXExport command line utility is available on the endpoint.


The following macros are not currently supported in the footer:
  • style