The following AEM Touch Connector version 5.0 configuration procedures are for AEM 6.4 and higher. If you would like to migrate to AEM 6.4 and be able to use AEM Touch Connector version 5.0, you'll need to follow the procedures below.

In AEM 6.4, Adobe restructured the repository, and moved the Translation Cloud Services configuration to a new location.

Adobe also changed the way that the translation configuration is assigned to sites\pages. We recommend deleting existing Smartling configuration(s) for AEM version 6.3 and below, and create a new one according to the steps outlined in the following sections. Highlighted in the screenshot below is where you can find legacy and new translation configurations.

You're now all set to create a new Smartling configuration.
​

You'll be creating two configurations:

You can create a new configuration (folder). To do this, open Configuration Browser.

Now you can create a configuration folder where you will add two translation configurations.

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

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

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

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

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

3. Select the Advanced tab.

4. Select the /conf/global configuration.

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.

You can only have one Smartling project configuration in AEM. This project has source and target locales that are mapped to the source and target locales of the project in Smartling. Each project in Smartling can have only one source locale.

To translate AEM content in Smartling from multiple source locales, you can add a source locale override to the Smartling project configuration, and map that source locale to the appropriate AEM project in Smartling. This allows you to translate AEM content from multiple source languages, within a single AEM instance.

To add multiple source locales, do the following:

Add as many source locales overrides as required. Ensure each override is mapped to a Smartling project with the AEM locale as the source locale.

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 the following settings:

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.

To configure string sharing, open the Smartling - String Duplicates Processor.

To access the Smartling - String Duplicate Processor, open <aem_url>/system/console/configMgr, and click Smartling - String Duplicates Processor (Touch).

Alternatively, open <aem_url>/system/console/configMgr/com.smartling.aem.connector.core.impl.config.StringDuplicatesProcessor directly.
​

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 unchecking Send page content with variants.

Shares duplicate strings across files of the same page.

Sends strings for AEM Experience Fragments and Content Fragments with unique namespace, meaning strings will not be shared. Pages with the same fragments strings can be translated independently and delivered separately.

This option overrides the use of legacy namespace option.

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

You can set a character limit for a property mapping. This feature was introduced in version 5.8.66. We recommend using it with plain text strings. The character limits will be visible to linguists working on translations in the CAT Tool.

When translation of a file is completed, Smartling sends an HTTP request to the AEM Touch Connector, and the Connector then asks AEM to sync the translation with Smartling.

To configure web callbacks, ensure that the proper URL is specified in Smartling - Callback URL (Touch) OSGi configuration.

The connector can also validate the signature of an incoming callback request with a shared secret. To enable this feature, the customer should contact their Smartling Representative to enable signed callbacks for your account.

Then update AEM Smartling - Callback URL (Touch) OSGi configuration with the URL and Shared secret (that was used for account configuration).

​ Also, you need to allow anonymous access to Smartling AEM connector callback endpoint /services/smartling/sync-translation.
​

The Smartling Adobe Touch connector provides some additional configuration settings.
​

​

When you create a translation Job in AEM, you must authorize the Job in Smartling to initiate translation. This can be automated with Auto Authorize.

The Auto Authorize setting can be found in the OSGi configuration, as shown:

Enabling this setting will make it enabled by default when you create a translation Job in the Smartling Translate modal, as shown:

You can control which strings are added to a job when you request content for translation. Three options are available:

Once a file is fully published, the AEM connector delivers translations to AEM, but any subsequent edits to those published translations are not automatically sent back. With this setting enabled, the connector automatically resubmits content when published translations are edited and republished after the original AEM job completed, eliminating manual resubmission when translators fix content post-delivery.

The feature is managed in the OSGi configuration.

The connector runs a background job on a configurable schedule. At each interval, it checks whether any translation updates have been made to previously submitted content, using metadata saved at the time of the original upload. If updates are detected, the connector automatically resubmits the content to the same Smartling job using the original request parameters: job, target language, and custom fields. If the original job no longer exists, the connector creates a new job.

Requires AEM Touch Connector version 5.8.85 or later.
​

By default, every user with access to the connector sees the Translate button. You can use the smartling:translationButton permission to control which users and groups can see it. This is useful when only certain teams, such as project owners or localization managers, should submit content for translation.
​

The permission only controls the visibility of the Translate button. Users who don’t have the permission can still request translations through the References panel.

This feature is optional and is turned off by default. The connector grants the permission by default to the Smartling Projects Owners group (smartling-projects-owners), with allow on the path /content.
​

​How to use this feature

An AEM administrator must first enable the feature in the OSGi configuration. It is off by default.
​

After that, an administrator can assign the permission to a specific user or group.

For example, to hide the Translate button for the Experience and Products sections of your site, set the permission to deny for the relevant user or group on those paths. An explicit deny on a path hides the button there, even if the user has broader access elsewhere.
​

In this example, the Translate button is not available on the Experience and Products pages.
​

This feature works for Sites, DAM, Forms, and Page Editor UIs.

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.

Approving, promoting, and deleting an AEM Translation project can be automated.

Go to the translation project settings to configure these settings, as shown:

The configuration is applied to any translation project created by Smartling dialog accordingly, as shown:

The connector makes HTTP connection to Smartling with socket timeout set to 40000 milliseconds by default. If you experience errors related to SocketTimeoutException, you can adjust this value in the OSGi settings.

By default, the "Add to Job" tab displays up to 100 jobs. This limit can be adjusted in the OSGi configuration.

Please follow these steps after upgrading to a new version of the connector.

After connector installation, cache for these UI files should be invalidated:

Use these tools to clear UI cache: