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.
To enable the connection, the connector uses the OCE REST API. To set up the connector, you'll need:
- The domain of your OCE instance when open in a browser, such as
- The domain of your Oracle Identity Cloud Service (IDCS) console, such as
- The primary audience domain of your OCE instance, such as
- 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.
- In Chain Builder, click Connections and Add Connection .
- Under BizApp Connection, select Oracle Content and Experience and the default CloudRunner.
- Under Basic Info, enter a unique name and description to help identify the connection.
- 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,
IDCS domain Enter the domain of your IDCS console, such as
Primary audience domain Enter the primary audience domain of the OCE instance, such as
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.
- Select the environments to use with the connection, and click Save.
- To test the connection, create and run a chain with the connector's Get File Information command, and verify it returns a valid output.
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.