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.
If you are still using AEM Touch Connector version 4.0x for AEM 6.3 and lower, consult the configuration procedures here.
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.
If you decide to upgrade from AEM 6.3 or lower, you first need to delete Smartling's existing configuration. If you are installing the AEM Connector for the first time, skip to creating a new configuration.
Delete Smartling's Legacy Configuration
- Open Tools from the AEM Classic UI, and select the following Cloud Service Configuration -> Smartling item
miscadmin#/etc/cloudservices/smartling-translation. - Delete all of your Smartling configurations.
- Ensure that all configurations were deleted via Tools > Cloud Services > Legacy Cloud Services
/libs/cq/core/content/tools/cloudservices.html. There should no longer be any configurations.
You're now all set to create a new Smartling configuration.
Create a New Configuration
You'll be creating two configurations:
- Translation Integration
- Smartling Translation Provider
Create a Translation Integration Configuration
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.
- Open the new Translation Cloud Services (
/mnt/overlay/cq/translation/gui/content/cloudservices.html) - Select conf - global and click Create.
- From the dropdown, select Translation Integration.
- Check your configuration, and set it to the following:
To learn more about available options, see the official AEM documentation.
Make sure that the Auto-execute Translation option is enabled for both the Sites and Assets tabs.
Create Configuration for Smartling Translation Provider
- Open the new Translation Cloud Services
/mnt/overlay/cq/translation/gui/content/cloudservices.html. - Select conf - global and click Create.
- From the dropdown, select Smartling.
- Retrieve your Project ID, User Identifier, and Token Secret from the Smartling Dashboard > API page. (Make sure you've selected the v2.0 tab.)
- Click Edit and enter your Project ID, User Identifier, and Token Secret.
- After saving the configuration, you can verify it by clicking Test connection on the toolbar.
Configure Site for Translation
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.
Associate a Site with a Translation Provider
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.
You should set the configuration for the page that is the parent of your sites (original and localized).
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.
AEM Touch 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 the 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
- In the Web console, open Components (/system/console/configMgr).
- 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.
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.
Send page content with variants
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.
Use Legacy namespaces
Shares duplicate strings across files of the same page.
Use unique namespaces for Experience and Content Fragments
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.
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.
Configure Web Callbacks
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 AEM host URL is specified in Smartling - Callback URL (Touch) OSGi configuration
Also, you need to allow anonymous access to Smartling AEM connector callback endpoint /services/smartling/sync-translation.
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.
