Set Up Content Exchange
| Content exchange is an experimental feature: it is currently available only in selected environments and might change in future releases. |
To exchange content between environments or promote assets, you need to define which environments take part in content exchange, allow promotions between them, and assign the required roles.
Prerequisites
-
Review how content exchange works.
-
You have the contentorchestrator-promotion-admin identity provider role.
-
For every environment you want to import packages from, you can access the Ataccama Cloud Portal. If you don’t have direct access to the environment’s Cloud Portal, ask the environment admin for the API client credentials.
Add environments
Add every environment of your organization that should take part in content exchange, source or target. Target environments must be listed before you can allow promotions to them and publish packages, and source environments must be defined before packages can be downloaded from them.
To add an environment:
-
Go to Global settings > Content exchange > Environments.
To access Global settings, select the Ataccama logo. -
Select Add environment.
-
Fill in the environment details. You can find all the values in the environment’s Cloud Portal.
-
Name: A display name for the environment, for example,
Acme Production. -
Tenant name: The tenant name of the environment, for example,
acme-production. -
Domain: The domain the environment runs on, for example,
acme-prod.ataccama.one. Required only for environments you import packages from. -
Client ID and Client secret: Credentials of an API client created in that environment. Required only for environments you import packages from. See Create an API client for promotions.
-
-
Select Save.
-
Select Test connection to verify that the environment can be reached with the stored values.
After you save an environment, the client secret is stored securely and is no longer shown on the page. When you edit the environment later, leave the Client secret field blank to keep the stored secret, or enter a new value to replace it.
Create an API client for promotions
When this environment imports a package from another environment, it authenticates against that environment using an API client.
In the Cloud Portal of the source environment, create a new API client in the Settings > API Clients section, then copy the generated client ID and client secret into the environment details in ONE. The role required for content exchange is assigned to the client automatically.
For step-by-step instructions, see Create an API client.
Configure promotion settings
Promotion settings define which content packages can be promoted from this environment to other environments within your organization. A package can only be published to an environment whose settings allow its contents.
To configure promotion settings:
-
Go to Global settings > Content exchange > Promotion settings.
-
For each target environment, select which area of the platform to export. Currently, only Reference data is available.
-
Select which promotion the environment supports:
-
Allow draft promotions: Packages whose assets are imported as drafts and require approval in the target environment.
-
Allow published promotions: Packages whose assets are immediately published in the target environment.
-
-
For each selected promotion, choose which content the package can include. For reference data, select Structure, Data, or both.
-
Select Save.
For details about how the draft and published modes behave, see Apply modes for reference data.
Review and assign user permissions for content exchange
Review the role configuration and assign any missing roles to ensure all users have the permissions required for their part in the content exchange.
Each stage in the asset promotion has a corresponding role; assign only those the users require for their work. For example, a user who creates exports and also publishes them needs export and promotion roles but no import role.
For role details, see Reserved identity provider roles. For step-by-step instructions about how to assign roles, see Assign identity provider roles to users.
Was this page useful?