Memsource Translation Plugin for Adobe Experience Manager (AEM)

The Memsource Translation Plugin for AEM 6.2, AEM 6.3, and AEM 6.4 enables users of Memsource to link their Memsource accounts to Multilingual Sites created using the AEM CMS system. The sections below will cover the essentials of configuring the plugin and how to work with it. To find more information about Translating Content for Multilingual Sites, please visit the Adobe documentation (especially the sections concerning Configuring the Translation FrameworkPreparing Content for TranslationIdentifying Content to Translate, and Managing Translation Projects).

Memsource Configuration

The plugin uses the Memsource Automation Widget functionality to create a project in Memsource and send the files from AEM to Memsource. Once the jobs are translated, the Project Manager sets the project to Completed, and the translated files are sent back to AEM.

To successfully link Memsource with AEM, you will need the following:

  • A Memsource account: If you already have a Memsource account yourself, you can use it to link AEM to it. If you plan to order a translation from an LSP, their account can be used instead. 
  • Service:  You can find more information on our dedicated Services page of the documentation.
  • Automation Widget: All the necessary information can be found in our Support Center article dedicated to the Automation Widget.
  • Price list (optional): If you plan to be using Scopes in AEM for price calculation.

Adobe Experience Manager Configuration

Within Adobe Experience Manager, navigate to Deployment, click on Cloud Services, and select Memsource Translation Plugin for AEM. Use the Configure New option to set up a new configuration for the translation of content using Memsource.

  • Fill in the required information to establish a connection:
    • Memsource Home URL: The default URL is but can be different if you or the LSP is using a Custom URL.
    • Username
    • Password
    • Automation Widget: Select the Automation Widget you have prepared for use in AEM. If you wish to use multiple Automation Widgets for different scenarios, you will need to set up multiple configurations. 
    • Service: Select the service that will govern the language setup of projects (orders) in Memsource as well as the Workflow setup of these Memsource projects. If you wish to use multiple languages and Workflow options, you will need to create multiple configurations.
    • Auto Complete Project: This should be ticked if you would like the AEM Translation Jobs to skip the Review step.
    • AEM URL: This is the URL of the site where content for translation is located.

Setting up the Translation Integration

When using the Memsource Translation Plugin for AEM, it is important to keep in mind that all files in the translation jobs will be submitted for translation and thus returned from Memsource. Using the project Translation Integration configuration, you will be able to prevent non-translatable assets or reference materials from being included in the projects.

  • In Deployment, click on Cloud Services, and select Translation Integration. You can create a new configuration specifically for translation in Memsource.
    • Make sure Translate Component Strings and Translate Tags are both unchecked.
    • Translate page assets should be set to Do not translate.
    • On the Assets Tab, you can also set the Translation Workflow to Do not translate.
  • If your project still contains non-translatable assets or reference materials, you can simply mark and Delete them directly in Memsource.

Applying Translation Integration to Content

  • Navigate to the root of the content you wish to translate in Memsource, select it and click Properties.
  • On the Cloud Services Tab, select your newly created configuration as the Translation Integration.
  • Click on the Add configuration label and select the Memsource Translation Plugin for AEM. This will display a dropdown menu with previously created configurations. Select the one you'd like to use for this content.
    • By default, all child pages will inherit these settings. However, you can adjust any page to use a different cloud configuration if needed.

When you add content from these pages, only the translatable content will be added. If you create a project from the References Panel, it will be automatically set up to use the cloud configuration associated with the root page.

For more details on creating translation projects using the References Panel, please see the Managing Translation Projects section of the Adobe documentation.