Configure the Translation Connector

Learn how to connect AEM to a translation service.

The Story So Far

🔗

  • Understand the importance of content structure to translation.
  • Understand how AEM stores headless content.
  • Be familiar with AEM's translation tools.

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.

Objetivo

This document helps you understand how to set up an AEM connector to your chosen translation service. After reading you should:

  • Understand the important parameters of the Translation Integration Framework in AEM.
  • Be able to set up your own connection to your translation service.

The Translation Integration Framework

AEM's Translation Integration Framework (TIF) integrates with third-party translation services to orchestrate the translation of AEM content. It involves three basic steps.

  1. Connect to your translation service provider.
  2. Create a Translation Integration Framework configuration.
  3. Associate the configuration with your content.

The following sections describe these steps in more detail.

Connecting to a Translation Service Provider

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. 🔗

OBSERVAÇÃO

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.

OBSERVAÇÃO

Using the out-of-the-box Microsoft Translator in AEM does not require additional setup and works as-is without additional connector configuration.

🔗 🔗

🔗

Creating a Translation Integration Configuration

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:

  • Which translation service provider to use
  • Whether human or machine translation is to be performed
  • Whether to translate other content that is associated with the Content Fragment such as tags

To create a new translation configuration:

  1. 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.

    • For example, in this case, a configuration could be made globally to apply to all content, or just for the WKND project.

  2. Remember that Content Fragments are stored as assets in AEM.

  1. Provide the following information.

    1. For the purposes of this journey we assume machine translation.

You have now configured the connector to your translation service.

Associate the Configuration with Your Content

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

/content/dam/<your-project>/en
  1. 🔗

What's Next

Now that you have completed this part of the headless translation journey you should:

  • Understand the important parameters of the Translation Integration Framework in AEM.
  • Be able to set up your own connection to your translation service.

🔗

Recursos adicionais

🔗

Nesta página