Learn how to connect AEM to a translation service.
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. 🔗
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. 🔗
If you choose another provider your administrator must install the connector package as per the instructions provided by the translation service.
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:
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.
Remember that Content Fragments are stored as assets in AEM.
Provide the following information.
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: