Learn how to connect AEM to a translation service.
In the previous document of the AEM headless translation journey, Get started with AEM headless translation you learned how to organize your headless content and how AEM’s translation tools work and you should now:
This article builds on those fundamentals so you can take the first configuration step and set up a translation service, which you will use later in the journey to translate your content.
This document helps you understand how to set up an AEM connector to your chosen translation service. After reading you should:
AEM’s Translation Integration Framework (TIF) integrates with third-party translation services to orchestrate the translation of AEM content. It involves three basic steps.
The following sections describe these steps in more detail.
The first step is to choose which translation service you wish to use. There are many choices for human and machine translation services available to AEM. Most providers offer a translator package to be installed. See the Additional Resources section for a selection of options available.
The translation specialist is generally responsible for choosing which translation service to use, but the administrator typically is responsible for installing the required translation connector package.
For the purposes of this journey, we use the Microsoft Translator which AEM provides with a trial license out-of-the-box. See the Additional Resources section for more information about this provider.
If you choose another provider your administrator must install the connector package as per the instructions provided by the translation service.
Using the out-of-the-box Microsoft Translator in AEM does not require additional setup and works as-is without additional connector configuration.
If you choose to use the Microsoft Translator connector for testing purposes, you do not need to carry out the steps in the next two sections: Creating a Translation Integration Configuration and Associate the Configuration with Your Content. However you are advised to read them so that you are familiar with the steps for when you need to configure your preferred connector.
The trial license of the Microsoft Translator connector is not intended for production purposes and if you decide to license it, the system administrator must follow the steps detailed in the Additional Resources section at the end of this document so you can configure that license.
After the connector package for your preferred translation service is installed, you must create a Translation Integration Framework configuration for that service. The configuration includes the following information:
To create a new translation configuration:
In the global navigation menu, click or tap Tools -> Cloud Services -> Translation Cloud Services.
Navigate to where you wish to create the configuration in your content structure. This is often based on a particular project or can be global.
Provide the following information in the fields and then click or tap Create.
Tap or click Create and the Edit Configuration window appears where you can configure the configuration properties.
Remember that Content Fragments are stored as assets in AEM. Tap or click the Assets tab.
Provide the following information.
Tap or click Save & Close.
You have now configured the connector to your translation service.
AEM is a flexible and powerful tool and supports multiple, simultaneous translation services via multiple connectors and multiple configurations. Setting up such a configuration is beyond the scope of this journey. However this flexibility means that you must specify which connectors and configuration should be used to translate your content by associating ths configuration with your content.
To do this, navigate to the language root of your content. For our example purposes this is
Now that you have completed this part of the headless translation journey you should:
Build on this knowledge and continue your AEM headless translation journey by next reviewing the document Translate content, where you will learn how to use your configuration so far to actually translate your content.
While it is recommended that you move on to the next part of the headless translation journey by reviewing the document Configure translation rules the following are some additional, optional resources that do a deeper dive on some concepts mentioned in this document, but they are not required to continue on the headless journey.