AEM Touch | AEM Cloud Connector

AEM Touch Connector Configuration 4.0x

AEM Touch Connector version 5.0 will only work with AEM 6.4 and above.
AEM Touch Connector version 4.0x will only work with AEM 6.3 and below.
Both AEM on-premise and AEM Cloud are supported

In the following procedures, references to AEM Touch Connector version 5.0 are indicated.

Smartling’s AEM Touch Connector allows you to submit content for translation and automatically download the content to Adobe AEM once translations are complete. It also provides dynamic context for your content so that translators can see how each string will fit into your translated sites.

Once the connector is installed, you can manage your translations through Adobe Experience Manager’s translation projects. Adobe's Translating Content for Multilingual Sites Documentation includes steps to:

  • Connect your provider.
  • Create a translation integration configuration (also see the steps below).
  • Associate pages with the translation service.
  • Identify the type of content to translate.
  • Prepare content for translation.
  • Create and manage translation projects in AEM.

If you need to update the connector version, simply repeat the installation steps. Find the latest version in our Downloads documentation.

Important: If you customized Smartling Language Mapping, then you have to make a backup and restore it after installation. The connector installer will reset Language Mapping to its default state. Language Mapping can be found here:  /apps/granite/translation/connector/config/smartling/languageMapping

To ensure no metadata is lost when updating Smartling's AEM Touch Connector to the latest version, install the latest version first. Ensure there is content currently in progress in Smartling. Once the latest version has been successfully installed and you are waiting for translations to be returned from Smartling, from the More dropdown, click on Other Versions, select the previous package to open it, then click on More > Uninstall.

Configure Smartling and Translation Integration Cloud Services

If you are using AEM 6.4 or above, you need to use AEM Touch Connector version 5.0. To configure, see AEM Touch Configuration for Version 5.0.

Otherwise, if you are using AEM 6.3 or below, follow the configuration procedures below.

Create a Translation Integration Configuration

To specify how to translate your content, create a translation integration framework configuration. The configuration includes the following information:

  • The translation service provider to use.
  • Whether or not to translate other content that is associated with a page or asset, such as tags.
  1. Open Cloud Services /libs/cq/core/content/tools/cloudservices.html.
  2. Scroll to Translation Integration and add a new configuration.
  3. Check your configuration, and set it to the following:

To learn more about available options, see the official AEM documentation.

Important: Make sure that the “Auto-execute Translation” option is enabled for both the Sites and Assets tabs.

Create Configuration for Smartling Translation Provider

  1. Open Cloud Services /libs/cq/core/content/tools/cloudservices.html.
  2. Find the Smartling service and add a new configuration.
  3. Retrieve your Project ID, User Identifier, and Token Secret from the Smartling Dashboard > API page. (Make sure you've selected the v2.0 tab.)
  4. Click Edit and enter your Project ID, User Identifier, and Token Secret.
  5. After saving the configuration, you can verify it by clicking Test connection on the toolbar.

Configuring Site for Translation

If you are using AEM 6.4 or above, you need to use AEM Touch Connector version 5.0. To configure, see AEM Touch Configuration for Version 5.0.

Otherwise, if you are using AEM 6.3 or below, follow the configuration procedures below.

To configure the translation of your source pages into other languages, associate the pages with the following cloud configurations:

  • The cloud configuration that connects AEM with the Smartling provider.
    The Smartling configuration that configures the details of the translation.

When you associate a page with a cloud configuration, the descendants of the page inherit the association.

Associating a Site with a Translation Provider

Associate a page with the Smartling provider that you are using to translate the page and descendent pages.

  1. In the Sites console, select the top page of your site to configure it, and click Properties.

    Important: You should set the configuration for the page that is the parent of your sites (original and localized).

  2. Select the Cloud Services tab.
  3. Click Add Configuration > Translation Integration.
  4. Select the Smartling provider to use.
  5. Click Add Configuration > Smartling.
  6. Select the Smartling configuration to use.
    If the locales configured in you AEM site need to be remapped to different Smartling locales, see the AEM Touch Connector FAQ page for the locale remapping guide.

Context Configuration

The AEM Touch Connector uses a Smartling Project ID and API Key for connecting to the Smartling Context service. Only one Adobe instance can provide context to each Smartling project. If you need to use context on multiple CQ instances (for example, development, quality assurance and/or staging servers), use a different Smartling Project ID and API Key for each. This only applies for providing context and doesn’t limit uploading content from different CQ instances into a single Smartling project.

The Smartling Context configuration includes following settings:

  • Server URL: The domain name of your author server.
  • User: The AEM account name that should be used for capturing context. You can use an account with read-only or limited permissions.

Configure Context

  1. In the Web console, open Components (/system/console/configMgr).
  2. Find the context component “Smartling - Context Preview Settings”. No defaults are provided. An AEM Administrator must explicitly configure the Context Preview Settings.

Configure String Sharing 

By default, Smartling will treat strings as being unique to each page - that is, if identical strings are included on multiple pages, Smartling will capture the string for translation each time. This gives you flexibility to translate a string differently for different context or space requirements. If you want your pages to share strings - to capture a string only once for your whole site and duplicate the translation wherever that string appears, you can enable string sharing by navigating to the Smartling - String Duplicates Processor component and unchecking Send page content with variants.

Configure Fields for Custom Components

Create custom components and define these custom component fields as translatable within the Adobe translation framework.

  • Go to the Translation Configuration in AEM



  • From here, configure each property as translatable, inherit, and define how each property should be parsed by Smartling. For example, HTML components should be parsed as HTML. 

For more information, read Content Parsing.



Additional Smartling Configuration

The Smartling Adobe Touch connector provides some additional configuration settings.

Configure Custom Placeholders

By default, the connector captures and masks any placeholders used by the Java MessageFormat, to Translators.

If you want to mask other blocks of your content, you can use a Java Regular Expression to define content that should be captured as a placeholder. Add your Regular Expression in the web console in the Smartling - Translatable Content Configuration (Touch) component.

Note: It's best to do this as you do your initial setup. If you change this setting once you have started translating, it may change how your strings are captured and cause you to need to redo translations.


Was this article helpful?