Configuring a CMS integration with Asset Picker
You can configure third-party CMS with Asset Picker. Currently, Asset Picker only supports images from the CMS. When you create partitions in Unica Centralized Offer Management, an entry for Asset Picker resides in each partition. For example, if Unica Centralized Offer Management has three partitions, you can configure Asset Picker for all the partitions of Unica Centralized Offer Management.
About this task
To create partitions in Unica Centralized Offer Management, see the Unica Centralized Offer Management Installation Guide.
You can configure a third-party application that contains the artifacts, which can be accessed using the Unica Centralized Offer Management URL picker tool.
To configure a third-party CMS for integration with Asset Picker, complete the following steps:
Procedure
-
Select
.The Configuration page appears.
-
From the Configuration categories panel, select .
- Offer - The name provided to Unica Centralized Offer Management application.
- partition <n> - Here <n> represents the number of partitions. For example, if Unica Centralized Offer Management has two partitions, then partition <n> can be partition 1 or partition 2.
The Create category from template page for (CMS Configuration Template) appears. -
Provide values for the following fields:
- New category name - A name to identify the Asset Picker so that you can categorize the various assets.
- System Identifier - An internal name for
identification.Note: The System Identifier name must match the
systemId
used in the respective Asset Picker plugin. For more information onsystemID
, see Unica Asset Picker Developer's Guide. - User credentials - Specify the user credential
selection strategy for the target system. The available options are:
- Default user - If you select Default user, the data source for defaultUserCredentials account is used while calling APIs of the target CMS.
- Logged-in user - If you select Logged-in user, the data source of Unica's signed-in user account is used while calling APIs of the target CMS.
- Hierarchical - If you select Hierarchical, the data source of Unica's signed-in user account is considered first. If the Unica's signed-in user account does not contain a data source, the defaultUserCredentials will be considered.
- defaultUserCredentials - The default Marketing
Platform user having the target CMS credentials. The system uses this
configuration when:
- the User Credential strategy is the Default User.
- the User Credential strategy is Hierarchical, but the logged-in user does not have the datasource associated. In such a case, the default user will be considered for credential selections.
- Data source name for credentials - The data source assigned to the Marketing Platform account. This data source authenticates the target system's REST API, database, etc.
- Anonymous Content Access - Select
Yes if the target system accepts anonymous
access to content or select No if the target
system does not accept anonymous access to content.Note:
- Asset Picker framework works with the protected APIs of the target CMS system. However, in this release, the target CMS should be configured for allowing anonymous guest user access to the content URLs.
- The 12.0 release only supports images in content type.
-
Note: If you have not provided credentials for the target system, or if the provided credentials are incorrect, the target system will decline the connection request. Before saving the changes, ensure that you have provided the credentials and that they are accurate.Click Save changes.A new entry, for example <CMSName>, appears under Data sources for the configured CMS. Expand the entry to see the following entries:
- <CMSName> | HTTP Gateway - contains a configuration.
- <CMSName> | HTTP Gateway | REST - contains a configuration.
- <CMSName> | QOS - does not contain configurations.
- <CMSName> | QOS | Retry Policy - contains configurations.
-
To configure HTTP Gateway, complete the following
steps:
-
To configure HTTP Gateway | REST, complete the following
steps:
-
To configure QOS | Retry Policy, complete the following
steps:
What to do next
- If you have made changes to configurations, you should restart the Asset Picker application for the changes to come into effect.
- Updates to user data source does not require a restart.
- Configure the out-of-the-box integrations like Adobe Experience Manager (AEM) and HCL Digital Experience (DX or WCM). For more information, see Configuring the out-of-the-box integrations offered by Asset Picker.