Configuring Smart Tagging Cloud Service

Access UDP from https://www.adobe.io/console.

From the Integrations page, select your organization.

Tap/click New Integration.

In the Create a new integration page, tap/click Continue.

Select Smart Content, and then tap/click Continue.

In the next page, tap/click Continue. 

In the Integration Details page,  specify a name for the integration gateway and add an optional description.

Use the following command to create a public key:

  openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout private.key -out smart-tags-adobe-io.crt

For more information around how to create public keys, see Creating a self-signed certificate.

Upload the file smart-tags-adobe-io to the integration service.

Tap/click Create Integration. The integration is created.

To view integration information, tap/click Continue to integration details.

Use the values for Technical Account ID, Organization Id, Client Secret, Authorization Server, and API key to configure Smart Tagging cloud service in AEM.

Access Configuration Manager from http://<Server>:<Port>/system/console/configMgr.

From the list of configurations, open the AEM Smart Tag Assets Feature Flag configuration.

 Select the Is Active option.

Click Save.

From the AEM UI, navigate to Tools > Deployment > Cloud Service to open the Cloud Services console.

Create a new Assets Smart Tags configuration.

Set the service url to https://mc.adobe.io/marketingcloud/smartcontent.

Set the appropriate URL for the authorization server. Use the host name for the aud key in the payload of the integration that you created earlier.

Set the other values, for example the API Key, Technical Account Id, Organization Id, and Client Secret that you generated in step 10 of UDP Integration.

To create a keystore from the generated keys, run the following command:

Use the following command to set the alias as similaritysearch and a non-empty keystore password.

You can validate the keystore using a tool, such as KeyStore Explorer.

To add the keystore to dam-update-service, go to Tools > Security > Users and open dam-update-service.

Click Create Key Store, and create a key store.

Click Manage Key Store, and then click Add Private Key from Key Store file to add the keystore.p12 file.

Set the key pair alias to similaritysearch.

Provide the keystore password (the password you provided when generating the keystore), private key password, and the private key alias similaritysearch. Then, click Submit to import the keystore.

Review the screen after the keystore is created, and verify the information from the keystore file.

From the AEM Assets UI, go to Tools > Workflow > Models.

From the Models page, select the DAM Update Asset workflow model.

Click Edit.

Drag Smart Tag Asset Process (available under the DAM Workflow section) from side kick, and place it after the Process Thumbnails step.

Double-click the step to edit it.

Under Advanced Settings, ensure that the Handler Advance option is selected.

In the Arguments tab, select Ignore Errors if you want the workflow to complete even if the automatic tagging step fails.

To tag assets when they are uploaded irrespective of whether smart tagging is enabled on folders, select Ignore Smart Tag Flag.

Click OK to close the process step, and then save the workflow.

Access Configuration Manager from http://<Server>:<Port>/system/console/configMgr.

From the list of configurations, open Assets Smart Tags Service.

Set the following parameters:

• Indexed rendition: Can be set to any rendition type
• max.tags.name: Maximum number of smart-tags that can be associated with an asset
• min.tag.confidence.name: The threshold confidence level below which the tags are ignored

Save the changes.

Access Configuration Manager from http://<Server>:<Port>/system/console/configMgr.

Open the Assets Smart Tags Periodic Job configuration.

To trigger the smart tagging workflow on all the folders with the value of autotag set to true at the path /crx/de/index.jsp#/content/dam/{folder_path}/jcr/content, specify a valid cron job expression for scheduler.expression.name.

Save the changes.

Access Configuration Manager from http://<Server>:<Port>/system/console/configMgr.

Open the Assets Smart Tags Management Service configuration.

In the Bulk Smart-tagging batch size box, specify the maximum number of assets for which the the periodic tagging workflow can apply smart tags each time it runs.

Save the changes.

Open the CRX repository.

Navigate to the node /oak:index/damAssetLucene/indexRules/dam:Asset/properties.

Using the index structure specified in the attached XML file as reference, create the following nodes and configure their properties as mentioned below:

• simsearchVersion
  • jcr: primaryType: nt:unstructured
  • name: jcr:content/metadata/simsearchVersion
  • nullCheckEnabled: true
  • propertyIndex: true
• predictedTags
  • index: true
  • isRegexp: true
  • jcr:primaryType: nt:unstructured
  • name: jcr:content/metadata/predictedTags/*/name
  • propertyIndex: false
• predictedTagsConfidence
  • index: true
  • isRegexp: true
  • jcr:primaryType: nt:unstructured
  • name: jcr:content/metadata/predictedTags/*/confidence
  • propertyIndex: false

Navigate to /oak:index/ntBaseLucene/indexRules/nt:base/properties/, create a node damAutoTag, and configure its properties as mentioned below:

• jcr:primaryType: nt:unstructured
• name: jcr:content/autotag 
• ordered: false
• propertyIndex: true
• type: Boolean

Save the changes.