Connector to Oracle Analytics Cloud (OAC)

With the Oracle® Analytics Cloud® connector, you can use commands in a chain to interact with Oracle Analytics Cloud (OAC). For example, with this connector, you can:

• Load dimensions to Essbase® cubes
• Download or delete artifacts from cubes
• Execute calculations, multidimensional expressions (MDX), or MaxL scripts
• Import or export cube artifacts as Lifecycle Management (LCM) ZIP files

Note: This connector is built by Workiva and connects to a third-party system. While our Support team can help configure this connector within your workspace, we are unable to troubleshoot or otherwise assist with any issues that originate outside of the Workiva platform.

Prerequisites

To enable the connection, the connector uses the OAC REST API. To set up the connector, you'll need:

• A designated integration user set up in OAC for the connector, with appropriate roles for the commands the connector will perform
• The integration user's authentication credentials
• The base URL of the OAC instance to connect to

Note: In the OAC URL, the base is the portion that ends with oraclecloud.com.

Set up the Oracle Analytics Cloud connector

Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.

1. From Chain Builder, click Connections  compare_arrows, and then Create at the top right.
2. Under BizApp Connection, select Oracle Analytics Cloud and the default CloudRunner.
   
3. Under Basic Info, enter a unique name and description to help identify the connection.
4. Under Properties, enter the connector's details:
   
   

   Property	Details
   User name	Enter the username of the connector's OAC integration user.
   OAC password	Enter the password for the User Name property.
   OAC base URL	Enter the base URL for the OAC instance to connect to, including the https://. Note: In the OAC URL, the base is the portion that ends with oraclecloud.com.

   Note: All sensitive credentials are automatically encrypted and stored at Advanced Encryption Standard (AES)-256 encryption.

5. Select the environments to use with the connection, and click Save.
6. To test the connection, create and run a chain with the connector's List Applications command, and verify it returns a valid output.

Troubleshooting

If the connection to OAC fails:

• Verify the authentication credentials of the connector's OAC integration user.
• Check the base URL of the OAC instance to connect to.