> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flexagon.com/llms.txt
> Use this file to discover all available pages before exploring further.

# exportWorkspaceStaticFiles

> Exports Oracle APEX Workspace Static Files from an APEX workspace and generates a deployment artifact containing a single SQL file with the definition

Exports Oracle APEX Workspace Static Files from an APEX workspace and generates a deployment artifact containing a `single SQL file` with the definitions and content of all workspace static files in the workspace. This operation is intended to be used with the corresponding `importWorkspaceStaticFiles` operation to migrate workspace static files between APEX environments.

# Target Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>APEX User</td><td>`FDAPEX_USER`</td><td>Yes</td><td>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. </td></tr><tr><td>APEX Password</td><td>`FDAPEX_PASSWORD`</td><td>Yes</td><td>Password for APEX User. </td></tr><tr><td>Oracle SQLcl Home</td><td>`FD_SQLCL_HOME`</td><td>Yes</td><td>Folder where SQLcl is installed.Make sure that the endpoint Java Home is a high enough version for your SQLcl version.</td></tr><tr><td>Oracle Database URL</td><td>`FDORA_URL`</td><td>Yes</td><td>JDBC URL for Oracle database. For example:<ul local-id="2a62593a-92e8-4f4a-876d-55309161acfa"><li local-id="8700e82c-3a7b-47e3-aca1-796e4c3119e8">jdbc:oracle:thin:@HOSTNAME:PORT:SID or</li><li local-id="a658ac56-ac9b-4bea-b41a-31120e1b8e61">jdbc:oracle:thin:@//HOSTNAME:PORT/SERVICENAME*.*</li></ul>Connecting to Oracle Autonomous DatabaseYou will need client credential zip file (wallet) to connect with Oracle Autonomous Database on Oracle cloud. You can download wallet zip file from Oracle Cloud, you will need admin userid and password to perform this download. See [Download Client Credentials (Wallets)](https://docs.oracle.com/en-us/iaas/autonomous-database/doc/download-client-credentials.html) for more details on how to download wallet file.<ul local-id="f3f9e490-60da-41a3-8410-3b028a9ae07e"><li local-id="68da8c32-6ceb-4270-9ba7-bd4085171b20">**Since FlexDeploy 9.0.0.9 with Oracle Wallet Credential Type :** Instead of maintaining the wallet zip file under the file system, you can now store the wallet zip as an Oracle Credential Type in FlexDeploy. This allows for secure storage and use of the wallet.<ul local-id="7da0a8af-60e4-4024-a755-917d0536fc75"><li local-id="695d9364-bd12-4234-9451-d7484b140103">Use the URL syntax in the following format: `jdbc:oracle:thin:@service_low?TNS_ADMIN={{FDORACLE_WALLET_FILE}}` is replaced with the temporary wallet folder path during execution. Once execution is completed, the temporary file is cleaned up automatically.</li></ul></li><li local-id="e951792e-23fa-461e-aa73-0e417053b9a3">**Before FlexDeploy 9.0.0.9**<ul local-id="63078d06-ca95-46ef-aa61-2fa5eeba8ada"><li local-id="4e253825-706e-473f-9bcb-db213cdd0fd8">You must make sure that only authorized users have access to these wallet files. Unzip the client credentials zip file (**wallet\_*****databasename*****.zip**) on FlexDeploy server and/or endpoint where it will be used. For example, /home/flexdeploy/.wallets/\<**wallet\_*****databasename***> is folder where specific wallet file was unzipped. Make sure to secure this folder to FlexDeploy and/or Endpoint user, so that it is not readable by all users.</li><li local-id="c40a016c-c58e-4a4e-925f-d9cde55683c4">We recommend using Oracle Wallet Credential Type for better security and easier management of Wallet usage.</li><li local-id="1af0cf51-228f-4941-ae8a-f6301c991cdb">**Database URL Syntax **: jdbc:oracle:thin:@service\_high?TNS\_ADMIN=/home/flexdeploy/.wallets/\<**wallet\_*****databasename***><ul local-id="355a1934-400e-4e4b-9ff2-29975e19e48f"><li local-id="0b46662e-807c-47fb-8faa-6b94ee89ea92">service\_high is one of the entries in the tnsnames.ora file where client credentials zip file was unzipped. See [Predefined Database Service Names for Autonomous Database](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/connect-predefined-generic.html) for details on services.</li><li local-id="96ab31b2-27d7-464c-8142-331e640dc7fa">TNS\_ADMIN value in URL points to the location of the **unzipped client credentials zip file**.</li></ul></li><li local-id="8bc166a1-6797-4470-a963-717c3903692f">**Database URL Long Connection String Format Syntax **: `jdbc:oracle:thin:@(description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=<hostname>))(connect_data=(service_name=<serice_name>))(security=(ssl_server_cert_dn="CN=<hostname>,OU=Oracle BMCS US,O=Oracle Corporation,L=Redwood City,ST=California,C=US")))`<ul local-id="6cf5f77d-d0fc-4705-a557-3da4c035c35e"><li local-id="18ac0b32-0c07-4fe4-bd53-ce4c5f634525">Examples for the same can be found [here](https://www.oracle.com/database/technologies/java-connectivity-to-atp.html).</li></ul></li></ul></li></ul>If using the Oracle Database Plugin with ADW or ATP databases , use the \_low connection. The \_medium and \_high connections can sometimes throw error** ORA-12839: cannot modify an object in parallel after modifying it.**</td></tr><tr><td>Oracle Wallet File</td><td>`FDORACLE_WALLET_FILE`</td><td>No</td><td>**Since 9.0.0.9** - Provide the Oracle Wallet file, see[Credential Type - Oracle Wallet](https://docs.flexagon.com/flexdeploy-11-1-documentation/flexdeploy-users-guide/administration/credentials/credential-types/credential-type-oracle-wallet.md) for more details.</td></tr></tbody></table>

# Project Properties

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Property Name**</th><th>**Property Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>APEX Workspace Name</td><td>`FDAPEX_WORKSPACE_NAME`</td><td>Yes</td><td>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.</td></tr></tbody></table>

# Inputs

<table><colgroup><col /><col /><col /><col /></colgroup><tbody><tr><th>**Input Name**</th><th>**Input Code**</th><th>**Required**</th><th>**Description**</th></tr><tr><td>Workspace Name</td><td>`FDAPEX_INP_WORKSPACE_NAME`</td><td>No</td><td>APEX workspace name from which workspace static files will be exported.</td></tr></tbody></table>

# Artifacts

This operation doesn’t consume or produce any artifacts.

# Endpoint Selection

This operation will select all available endpoints associated to the Target. You can use any Endpoint where SQLcl is installed and has connectivity to database using JDBC URL. We recommend use of LOCALHOST endpoint if connectivity can be established between FlexDeploy and your APEX database.

# Endpoint Execution

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