> ## 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.

# exportConnectionPoolsJSON (OAC)

> Exports the connection pools json file for an environment to a given location using the OAC Client tools installed on an endpoint. The intention of th

Exports the connection pools json file for an environment to a given location using the OAC Client tools installed on an endpoint.

The intention of this operation is to export it using a utility project, then modify any values that are different in each environment to be in FlexDeploy Property Replacement format, \$\{\{VAR\_NAME}}.

Then, store it in Source control, or the endpoint which has the OAC\_TOOLS installed.

Finally reference the file while deploying the RPD in the plugin input to update the connection pool after deployment.

Property Replacement is executed on the json files during deployment, so if storing the file on the endpoint, copy it to the FD\_TEMP\_DIR before running the deploy or export operation.

# 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>OAC Account</td><td>`FDOAC_CLOUD_ACCOUNT_CODE`</td><td>Yes</td><td>The OAC account includes essential properties such as the URL, Username, Password, and OAuth details for the OAC instance. Cloud account credentials are required for downloading or uploading catalog items.You can manage the OAC account via the **Integrations > Cloud** page.See [Configuring OAC Cloud Account](https://docs.flexagon.com/flexdeploy-11-0-documentation/flexdeploy-plugin-guides/flexdeploy-oracle-analytics-cloud-plugin-guide/oac-appendix/configuring-oac-cloud-account.md) for additional details.</td></tr><tr><td>OAC RPD Name</td><td>`FDOAC_RPD_NAME`</td><td>For RPD Migration</td><td>The RPD will be exported with this filename.e.g. `rpd.rpd`</td></tr><tr><td>OAC RPD Password</td><td>`FDOAC_RPD_PASSWORD`</td><td>For RPD Migration</td><td>The RPD password on the OAC server in the current environment.</td></tr><tr><td>Oracle BI Service Instance Name</td><td>`FDOAC_SERVICE_INSTANCE_NAME`</td><td>For RPD Migration</td><td>The Oracle BI Service instance name.(e.g. bootstrap).</td></tr><tr><td>OAC Trust Store</td><td>`FDOAC_TRUST_STORE`</td><td>For RPD Migration</td><td>The OAC Trust Store.e.g. `/u01/java17/lib/security/cacerts`Required to establish an SSL connection to the OAC server.</td></tr><tr><td>OAC Trust Store Password</td><td>`FDOAC_TRUST_STORE_PASSWORD`</td><td>For RPD Migration</td><td>The OAC Trust Store Password.Required to establish an SSL connection to the OAC server.</td></tr><tr><td>OAC Tools Directory</td><td>`FDOAC_TOOLS_DIR`</td><td>For RPD Migration</td><td>Download OAC tools to your endpoint. Reference the path here.e.g. `C:\oracle\Oracle_Home\bi`e.g. `/u01/Oracle_Home/bi`The folder you specify should be the parent of the bitools/bin folders.</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>OAC RPD Connection Replacement JSON</td><td>`FDOAC_RPD_CONNECTION_POOL_JSON`</td><td>No</td><td>After deployment, the connection pools can be updated by a json file at this location.Property replacement is performed on the file.You can use the ExportConnectionPoolsJSON operation to get the json from the environment.</td></tr></tbody></table>

# Artifacts

This operation produces an archive file of the RPD artifact. The archive file is suitable for the importRPD operation.  

# Endpoint Selection

This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the Target. Selecting a specific resource will result in selection of endpoints associated to the Target which have that resource defined.

# Endpoint Execution

This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to "All" to will result in execution on all selected endpoints.