Configuring the out-of-the-box integrations offered by Content Integration

Content Integration offers the following out-of-the-box integrations: Adobe Experience Manager (AEM), HCL WCM, HCL Digital Experience (DX), HCL Commerce & Microsoft Azure (for cognitive services).

Before you begin

See Configuring a third-party CMS for integration with Unica Content Integration.

About this task

To configure Adobe Experience Manager (AEM), HCL WCM, HCL DX, HCL Commerce & Microsoft Azure, complete the following steps:

Procedure

Setting up Adobe Experience Manager
1. Select Settings > Configuration.
  The Configuration page appears.
2. From the Configuration categories panel, expand Offer > partitions > partition <n> > Content Integration > Data Sources > (System Configuration Template).
  The Create category from template for the (System Configuration Template) appears.
3. Provide values for the following fields and click Save changes:
  - New category name - Specify an appropriate name to identify the new CMS. For example, AEM.
  - System Identifier - AEM.
  - User credentials
  - defaultUserCredentials
  - Data source name for credentials
  - Anonymous Content Access - When this field is set to No, then under CMS configuration, the content preview will not show the download icon. When set to Yes, it will show the download icon.
  For more information about the fields, see Configuring a third-party CMS for integration with Unica Content Integration.
4. In the Configuration properties pane, expand AEM and select HTTP Gateway.
  The Settings for 'HTTP Gateway' page appears.
5. Select Edit settings.
  The (HTTP Gateway) Edit Settings page appears.
6. For the AEM Base URL field, see Configuring a third-party CMS for integration with Unica Content Integration.
7. Click Save changes.
8. In the Configuration properties pane, expand HTTP Gateway and select REST.
  The Settings for 'REST' page appears.
9. Select Edit settings.
  The (REST) Edit Settings page appears.
10. For the Authentication Type field, select the value Basic. If your AEM instance is set up to use a different authentication method, use a different value. For more information about the available values, see Configuring a third-party CMS for integration with Unica Content Integration.
11. Click Save changes.
12. In the Configuration properties pane, expand QOS and select Retry Policy.
  The Settings for 'Retry Policy' page appears.
13. Select Edit settings.
  The (Retry Policy) Edit Settings page appears.
14. For the Retry policy configurations, see Configuring a third-party CMS for integration with Unica Content Integration.
15. Click Save changes.
Publish status filter for Adobe Experience Manager
Note: From version 12.1.0.4 onwards, if you plan to upgrade Unica Content Integration, ensure that you create custom-plugin-services.yml, and store the customized configurations. After update two files will be created:
- plugin-services.yml (for out of the box plugins)
- custom-plugin-services.yml (for custom plugins)
Installer will never overwrite custom-plugin-services.yml file since it will contain the service declarations for custom plugins as well as customization for out of the box services.
1. In the plugin-services.yml file, available under <ASSET_PICKER_HOME>/conf directory, there exists a configuration for AEM under "systems" section. Under "AEM", the contentFilters configuration parameter contains a child parameter named publishStatus. This parameter filters search items by their published status. The parameter accepts only one of the following values: Published or Unpublished. Provide the required value.
2. If you do not provide a value or if you provide an incorrect value, AEM returns matching content, irrespective of its published status. This is the default behavior because the publishStatus parameter, by default, is commented out.
Setting up WCM
1. Select Settings > Configuration.
  The Configuration page appears.
2. From the Configuration categories panel, expand Offer > partitions > partition <n> > Content Integration > Data Sources > (System Configuration Template).
  The Create category from template for the (System Configuration Template) appears.
3. Provide values for the following fields and click Save changes:
  - New category name - Specify an appropriate name to identify the new CMS. For example, WCM.
  - System Identifier - WCM.
  - User credentials
  - defaultUserCredentials
  - Data source name for credentials
  - Anonymous Content Access - Set this to Yes.
  For more information about the fields, see Configuring a third-party CMS for integration with Unica Content Integration.
4. In the Configuration properties pane, expand WCM and select HTTP Gateway.
  The Settings for 'HTTP Gateway' page appears.
5. Select Edit settings.
  The (HTTP Gateway) Edit Settings page appears.
6. For the WCM Base URL field, see Configuring a third-party CMS for integration with Unica Content Integration.
7. Click Save changes.
8. In the Configuration properties pane, expand HTTP Gateway and select REST.
  The Settings for 'REST' page appears.
9. Select Edit settings.
  The (REST) Edit Settings page appears.
10. For the Authentication Type field, select the value Basic. If your WCM instance is set up to use a different authentication method, use a different value. For more information about the available values, see Configuring a third-party CMS for integration with Unica Content Integration.
11. Click Save changes.
12. In the Configuration properties pane, expand QOS and select Retry Policy.
  The Settings for 'Retry Policy' page appears.
13. Select Edit settings.
  The (Retry Policy) Edit Settings page appears.
14. For the Retry policy configurations, see Configuring a third-party CMS for integration with Unica Content Integration.
15. Click Save changes.
Publish status filter for WCM

Note: If you plan to upgrade Unica Content Integration, ensure that you back up the file plugin-services.yml, if you have customized the files. The installer overwrites the file and your customizations will be lost.
1. In the plugin-services.yml file, available under <ASSET_PICKER_HOME>/conf directory, there exists a configuration for WCM under systems section. Under WCM, the contentFilters configuration parameter contains a child parameter named publishStatus. This parameter filters search items by their published status. The parameter accepts only one of the following values: DRAFT, PUBLISHED, or EXPIRED. Provide the required value.
2. If you do not provide a value or if you provide an incorrect value, WCM returns matching content, irrespective of its published status. This is the default behavior because the publishStatus parameter, by default, is commented out.
3. If you activate the publishStatus parameter or modify its value, an application restart is mandatory.
Setting up HCL Digital Experience (DX)
1. Select Settings > Configuration.
  The Configuration page appears.
2. From the Configuration categories panel, expand Offer > partitions > partition <n> > Content Integration > Data Sources > (CMS Configuration Template).
  The Create category from template for the (CMS Configuration Template) appears.
3. Provide values for the following fields and click Save changes:
  - New category name - Specify an appropriate name to identify the new CMS. For example, DX-CORE.
  - System Identifier - DX-CORE.
  - User credentials
  - defaultUserCredentials
  - Data source name for credentials
  - Anonymous Content Access - Set this to Yes.
  For more information about the fields, see Configuring a third-party CMS for integration with Unica Content Integration.
4. Click Save changes.
5. Create another category with the value DX for the fields New category name and System Identifier by repeating Step a through Step d. For this new category, ensure that the Data source name for credentials field is blank.
6. Perform Step g through Step r for both DX-CORE and DX category.
7. In the Configuration properties pane, expand DX-CORE / DX and select HTTP Gateway.
  The Settings for 'HTTP Gateway' page appears.
8. Select Edit settings.
  The (HTTP Gateway) Edit Settings page appears.
9. For the description of DX-CORE / DX Base URL field, see Configuring a third-party CMS for integration with Unica Content Integration.
  For the Base URL field, you must configure a different URL for the DX-CORE category and the DX category. The Base URL configured for DX-CORE category is for authenticating DX credentials, and the Base URL configured for DX category is for accessing the DX media library only after successful authentication.
10. Click Save changes.
11. In the Configuration properties pane, expand HTTP Gateway and select REST.
  The Settings for 'REST' page appears.
12. Select Edit settings.
  The (REST) Edit Settings page appears.
13. For the Authentication Type field, select the value Basic. If DX instance is set up to use a different authentication method, use a different value. For more information about the available values, see Configuring a third-party CMS for integration with Unica Content Integration.
14. Click Save changes.
15. In the Configuration properties pane, expand QOS and select Retry Policy.
  The Settings for 'Retry Policy' page appears.
16. Select Edit settings.
  The (Retry Policy) Edit Settings page appears.
17. For the Retry policy configurations, see Configuring a third-party CMS for integration with Unica Content Integration.
18. Click Save changes.
Setting up Azure
1. Select Settings > Configuration.
  The Configuration page appears.
2. From the Configuration categories panel, expandOffer > partitions > partition <n> > Content Integration > Data Sources > (CMS Configuration Template)
  The Create category from template for the (CMS Configuration Template) appears.
3. Provide values for the following fields and click Save Changes
  - New category name - Azure
  - System Identifier - Azure
  - User credentials
  - defaultUserCredentials
  - Data source name for credentials
    Note: Data source password must contain the valid Azure subscription key. Username of the data source can be set to user.
  - Anonymous Content Access
  - Additional Parameters
4. Click Save changes
5. In the Configuration properties pane, expand Azure and select HTTP Gateway.
  The settings for HTTP Gateway appear.
6. Select Edit Settings.
  - Base URL - End point of deployed cloud azure service. For Example: https://<xxxxx>.cognitiveservices.azure.com
  - contentBaseUrl
  - bypassProxy
7. Click Save changes.
8. In the Configuration properties pane, expand HTTP Gateway and select REST.
  The Settings for REST page appears
9. Select Edit settings
  The (REST) Edit Settings page appears.
10. For the Authentication Type field, select the value None
11. Click Save changes.
Setting up HCL Commerce
1. Select Settings > Configuration.
  The Configuration page appears.
2. From the Configuration categories panel, expandOffer > partitions > partition <n> > Content Integration > Data Sources > (CMS Configuration Template)
  The Create category from template for the (CMS Configuration Template) appears.
3. Provide values for the following fields and click Save Changes
  - New category name - Specify an appropriate name to identify the new CMS. For example, Emerald.
  - System Identifier - Commerce Emerald.
    Note: Multiple stores can be onboarded by prefixing the identifier with Commerce, followed by a space and the store name. Example: Commerce Sapphire, Commerce Store 1, Commerce Store 2 and so on.
  - User credentials
  - defaultUserCredentials
  - Data source name for credentials
  - Anonymous Content Access
  - Additional Parameters - Each parameter should be separated by new line. Make sure to add a space after colon [:] while editing the values. Contact commerce admin to obtain the required values.
    - storeId: 11
    - contractId: 11005
    - langId: -1
    - currency: USD
4. Click Save changes
5. In the Configuration properties pane, expand HTTP Gateway and select REST.
  The Settings for REST page appears.
  Select Edit settings.
6. Select Edit settings.
  The (REST) Edit Settings page appears.
7. For the Authentication Type field, select the value None.
8. Click Save changes.
Note: For commerce products, deep search is not supported at category level. Commerce is looking into this limitation (ticket no: HC-8872) and it will be addressed in future versions.