Workiva Support Center

Oracle has stated that the Oracle Content Manager Cloud Service will reach its end of life and cease operation on December 31, 2025, at 11:50 p.m. Pacific Standard Time.
Following the termination of services, customers will have 60 days to retrieve their content in accordance with their Hosting & Delivery policies. 
Oracle is not providing a replacement managed cloud service for Oracle Content Management Cloud Services, but is offering the Oracle WebCenter product family as an alternative. If this is not a viable solution for your operations, Workiva recommends that you consider using the Workiva HTTP(S) connector to make the relevant calls as described in the Oracle WebCenter Content REST API v1.1.

With the Oracle® Content and Experience connector, you can use commands in a chain to manage files and folders in Oracle Content and Experience (OCE). For example, with this connector, you can share documents from OCE with your other systems of record.

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 OCE REST API. To set up the connector, you'll need:

• Ensure the steps noted in OCE's Working with OAuth 2 to Access the REST API have been completed.
• The domain of your OCE instance when open in a browser, such as dev-example.cec.ocp.oraclecloud.com
• The domain of your Oracle Identity Cloud Service (IDCS) console, such as idcs-abcdefg01234567890.identity.oraclecloud.com
• The primary audience domain of your OCE instance, such as 1230ABCDEF012345.cec.ocp.oraclecloud.com
• The client ID and secret of the dedicated OAuth token created in IDCS for the connector

Set up the Oracle Content and Experience 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 Connector Connection, select Oracle Content and Experience 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
   Instance domain	Enter the domain of the OCE instance to connect to, such as when open in a browser; for example, dev-example.cec.ocp.oraclecloud.com.
   IDCS domain	Enter the domain of your IDCS console, such as idcs-abcdefg01234567890.identity.oraclecloud.com.
   Primary audience domain	Enter the primary audience domain of the OCE instance, such as 1230ABCDEF012345.cec.ocp.oraclecloud.com.
   OAuth client ID	Enter the client ID of the OAuth token created in IDCS for the connector.
   OAuth client secret	Enter the client secret of the OAuth token created in IDCS for the connector.

   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 Get File Information command, and verify it returns a valid output.

Troubleshooting

If the connection to OCE fails:

• Verify the domains of the OCE instance and your IDCS console.
• Verify the client ID and secret of the OAuth token created in IDCS for the connector.
• Verify the steps from Oracle Identity Cloud Service for Working with OAuth 2 to Access the REST API have been followed.