Integration for Adobe Experience Manager - Recent Threads

New Product Release: New RWS Connector for AEM Cloud - February 2026

Rastko Ladinek — Wed, 25 Feb 2026 09:35:46 GMT

We would like to announce that we have released the new version of the RWS AEM Cloud connector where all deprecated dependencies have been addressed and replaced. We have also implemented minor improvements of the functionality.

We have also created a Java 21 specific version since Java 11 is planned to become deprecated by Adobe as well.

The latest Java 11 version is 1.9.18 and the latest Java 21 version is 1.9.24.

New Product Release: New RWS Connector for AEM Cloud - September 2025

Rastko Ladinek — Mon, 22 Sep 2025 12:39:25 GMT

RWS AEM Cloud Connector v1.9.15

Release Date: September 2, 2025
Compatible with: Adobe Experience Manager (AEM as a Cloud Service)

🚀 Executive Summary

The RWS Cloud Connector v1.9.15 brings several key enhancements aimed at improving compatibility, simplifying setup, and increasing transparency for users. This release introduces:

Support for legacy SDL project folders
Automatic default language mappings
UI visibility of the connector version

🔧 New Features & Enhancements

1. Support for Existing SDL Projects

Projects created in earlier versions (prior to v1.9.14) under /content/projects/sdl are now fully supported.
All lifecycle phases of these legacy projects are restored, ensuring seamless continuity for ongoing translation workflows.

2. Automatic Default Language Mappings

Once cloud configurations are added and the connection is successfully tested, default language mappings are automatically applied.
No need to manually upload a language mapping file during initial setup.
Custom mappings can still be applied if needed, offering flexibility while simplifying the default configuration process.

3. Connector Version Display on UI

The connector version is now always visible in the UI.
This improves transparency and makes it easier for users to identify the version in use, especially during troubleshooting or support interactions.

New Product Release: New RWS Connector for AEM Cloud - July 2025

Rastko Ladinek — Fri, 01 Aug 2025 07:36:05 GMT

We’re excited to announce the release of SDL Cloud Connector version 1.9.14, available as of July 21, 2025. This update brings powerful enhancements to support Adobe Experience Manager (AEM) as a Cloud Service, with a focus on performance, scalability, and reliability.

🌟 New Feature: Support for AEM’s Asynchronous Translation API

This release introduces compatibility with AEM’s Asynchronous Translation API, enabling:

High-performance, non-blocking translation project creation
Efficient handling of large-scale content trees
Seamless support for multiple language copies
Improved system stability and scalability

Translation jobs are now submitted in asynchronous mode, allowing background processing and better performance under high load conditions.

⚠️ Note: This feature requires AEM Cloud SDK version 2025.4.0 or newer.

🔧 Improvements

Resolved an issue with Tag and Dictionaries translation (still using the legacy Adobe translation API)
Enhanced retry mechanisms for large payloads
Improved logging and status tracking for translation job submissions

using a the sdl cloud

Former Member — Sun, 20 Apr 2025 01:12:27 GMT

"Are there any free courses to learn how to use cloud software and translate a project in the cloud, not an app?"

New Product Release: New SDL Connector for AEM - January 2025

Rastko Ladinek — Tue, 28 Jan 2025 08:31:20 GMT

We have just released a new version of the integration for Adobe Experience Manager. New versions have been released both for the on-premise version of AEM and for AEM Cloud.

AEM 6.5 on premise: version 1.2.33

AEM Cloud - version 1.9.8.1

The new release includes the ability to select and send tags for translation as well as several small bug fixes and functionality improvements.

If you wish to upgrade to the latest version of the connector, please contact your account manager or the project management team.

New Product Release: New SDL Connector for AEM 6.5 - June 2024

Rastko Ladinek — Fri, 21 Jun 2024 10:20:33 GMT

We have just released a new version of the integration for Adobe Experience Manager 6.5, version 1.2.29. The anterior versions were all internal releases, not released publicly. The new release includes several small bug fixes and functionality improvements. Details of changes are listed below:

SDL Release 1.2.24 (There was no 1.2.23 release because of a conflict):

DTNL-11088 - Supporting nested cloudconfigs
DTNL-11093 : Display all language codes for a supported mapping

SDL Release 1.2.25

DTNL-11083 - Replace admin user on on-prem connector with appropriate group permissions for the technical user
DTNL-11637 - AEM on-prem connector - Cloud configuration not displayed in detailed Project information

SDL Release 1.2.26

DTNL-12924: added empty status code for status "New"

SDL Release 1.2.27

DTNL-13101 - Preventing empty init for mantraclient
DTNL-13098 - Ignoring unknown statuses from RWS file status
DTNL-13313 - Skip preview file upload if path exceeds 200 or more chars

SDL release notes 1.2.28

DTNL-13102 - improving logging to be able to investigate issues better
DTNL-13664 – workaround for AEM bug where project do not go into Complete status

SDL Release 1.2.29

DTNL-13663 - Preselect previous source language + preselect source language based on the configuration + update front-end with clear message + update configuration table size
Update IntegrationTypeHeader

New Product Release: New SDL Connector for AEM 6.5 - October 2023

Rastko Ladinek — Fri, 13 Oct 2023 11:29:22 GMT

We have just released a new version of the integration for Adobe Experience Manager 6.5, version 1.2.22. The new release includes several small bug fixes and functionality improvements. Among the most notable ones is the introduction of timeouts on all httpclient calls, which should help with the stability and speed of translation projects on environments that have a large number of translation projects in progress or environments that are under heavy load due to authoring.

We have also introduced a list of all languages and file types supported by the LC configuration, which should help with identifying appropriate language mapping entries:

We have also introduced a frequently requested option to define on the configuration screen whether a master project template is to be used or whether the connector should by default create the project only for the current user.

If you wish to upgrade to the latest version of the connector, please contact your account manager or the project management team.

AEM Cloud changes affecting RWS Connector

Rastko Ladinek — Wed, 13 Sep 2023 12:40:59 GMT

Adobe have introduced a change recently in AEM Cloud, where translation projects now utilize a bucketing system which should decrease the system load, especially with larger products. Sadly, we were not informed of the change in advance and this has caused the connector to stop functioning on AEM Cloud environments after applying the update. We have already made the necessary changes to the connector code to account for this, so if you have issues with the connector not functioning (the main symptom is that the project will remain in Committed for Translation and not proceed), do contact support or your account manager to receive the updated connector

translating Wordpress wpml files with SDL Studio

Sonia Gouin — Thu, 02 Mar 2023 20:38:29 GMT

I have a client who designs websites. He'd like my help to translate his Wordpress sites. I found a page on Wordpress that discusses this: https://wpml.org/translation-service/sdl-language-cloud/ and I'm curious t know if anyone has tried this and if results were successful. Thanks for any feedback.

Sonia

How to download the SDL Connector for AEM

Justin Wang — Tue, 07 Feb 2023 01:32:20 GMT

One of our customer is using SDL Managed Translation and AEM. We would like to know how to download the latest version of SDL Connector for AEM.

New Product Release: New SDL Connector for AEM 6.5 - December 2022

Rastko Ladinek — Fri, 16 Dec 2022 12:06:38 GMT

We have just released a new version of the Adobe Experience Manager integration, version 1.2.19. The new release includes only one new feature, namely, better handling of assets in translation projects when assets metadata and tags need to be translated. The integration will now not upload the binary assets into the translation management system, but will instead mark them as completed directly within AEM if the checkbox for not translating assets is cleared.

Please contact your account managers, in particular if you are interested in translating metadata and tags for binary assets that are part of your pages.

Important Product Release - New AEM connector for AEM 6.5 - September 2022

Rastko Ladinek — Fri, 23 Sep 2022 10:19:12 GMT

We have just released a new version of the AEM integration, version 1.2.18. In the latest Service Pack, Service Pack 14 that Adobe has released this month there is the FasterXML JSR310 artifact missing which will cause issues with refreshing project status with all previous versions of the AEM integration. This new version must therefore be used on all AEM environments that have been upgraded with AEM service pack 14.

Please get in touch with your account manager or service delivery team if you have updated your AEM environment or are planning to do so, to receive the installation package.

Product Update: RWS Integration for AEM - December 2021

Rastko Ladinek — Tue, 21 Dec 2021 10:53:32 GMT

Dear Community,

We have just released a new version of the RWS Integration for AEM (v 1.2.10). This release includes 2 small updates:

- we have migrated the proxy support for customers with AEM behind firewall

- we have included an update for cases where pages are being removed during a launch post AEM 5.5.10 release.

Please contact your account manager to upgrade to the latest version.

Product Release: New SDL Connector for AEM 6.5 - February 2020

Nigel Watson — Tue, 25 Feb 2020 15:23:07 GMT

Dear Community,

We released a brand new connector solution for AEM 6.5. The previous SDL solutions (AEM 6.1-6.5) contine to be maintained and supported, and any updates will be provided under a seperate post.

This new release brings an entirely new user experience inside AEM, with many front-end and back-end features to support translation project creation and management.

Version AEM 6.5 - 1.2.0

Key features with this release are:

New, intuitive UI for project creation
- Select multiple AEM pages
- Support custom attributes
- Multilingual job creation in SDL
- Edit projects

New project synchronization
- Detailed information of project status
- Improved error prevention/handling to end user and admin
- Automation for job archiving
- Project multi-threading in AEM

New connector runs in parallel to old connector
- no translation freeze required
- Future updates install easily without complex uninstall processes

Configurable options:
- Pre-fill Project name from page properties
- Pre-fill cloud config from page properties
- Pre-fill target languages from cloud config
- Pre-fill target languages from previous selection

Create Project Wizard

Translation Project Overview

Translation Project Detail

Note: the new solution supports SDL Managed Translation/TMS only and does not support SDL WorldServer.

Product Update: SDL Integration for AEM - November 2019

Nigel Watson — Thu, 05 Dec 2019 11:46:20 GMT

Dear Community,

The December 2019 update for the SDL Integration for AEM is now available.

The following updates are included in the below connector versions:

AEM 6.2:

SDL Product Branding updates
Modified connector configuration dialog :
- "OK" button is now disabled until the test connection is made
- if some value from configuration fields is changed ,"OK" button will be disabled again until another test connection with the modified values is made, in this way we force users to test connection after something is changed in configuration
Improved logs and exception handling.
Modified the type of Client Secret input field from connector configuration dialog to password
Project Name Type dropdown, user has the option to select how the project name should be created in WS or Mantra ( Translation Job's name ,Project's name or both Translation Job's + Project's name)
Added Project Description character limit (254 characters), if you enter a longer description, the connector will send to translation system only the first 254 characters of it.
Added characters limit for Project Name(50 characters)
Connector version for ManTra and World Server 6.2.0-1.5.10

AEM 6.3:

SDL Product Branding updates
Modified connector configuration dialog :
- "OK" button is now disabled until the test connection is made
- if some value from configuration fields is changed ,"OK" button will be disabled again until another test connection with the modified values is made, in this way we force users to test connection after something is changed in configuration
Improved logs and exception handling.
Modified the type of Client Secret input field from connector configuration dialog to password
Project Name Type dropdown, user has the option to select how the project name should be created in WS or Mantra ( Translation Job's name ,Project's name or both Translation Job's + Project's name)
Added Project Description character limit (254 characters), if you enter a longer description, the connector will send to translation system only the first 254 characters of it.
Added characters limit for Project Name(50 characters)
Connector version for ManTra and World Server 6.3.0-1.6.9

AEM 6.4:

SDL Product Branding updates
Improved logs and exception handling.
Modified the type of Client Secret input field from connector configuration dialog to password
Improved logs by adding detailed information’s(wrong : ManTra or WorldServer URL, username, password, client_id, client secret, project option, language pair)
Project Name Type dropdown, user has the option to select how the project name should be created in WS or Mantra ( Translation Job's name ,Project's name or both Translation Job's + Project's name)
Added Project Description character limit (254 characters), if you enter a longer description, the connector will send to translation system only the first 254 characters of it.
Added characters limit for Project Name(50 characters)
Connector version for ManTra and World Server 6.4.0-1.2.9

AEM 6.5:

SDL Product Branding updates
Improved logs and exception handling.
Modified the type of Client Secret input field from connector configuration dialog to password
Improved logs by adding detailed information’s(wrong : ManTra or WorldServer URL, username, password, client_id, client secret, project option, language pair)
Added health check status error message for ManTra or WorldServer URL
Added Project Description character limit (254 characters), if you enter a longer description, the connector will send to translation system only the first 254 characters of it.
Added characters limit for Project Name(50 characters)
Project Name Type dropdown, user has the option to select how the project name should be created in WS or Mantra ( Translation Job's name ,Project's name or both Translation Job's + Project's name)
Connector version for ManTra and World Server 6.5.0-1.0.4

User Feature

In the configuration settings for all connectors, the user can now choose an option for which name the project is given in the SDL Translation System - AEM Project Name, AEM Translation Job Name or a combination of both concatenated together.

Installers can be downloaded from your usual location, contact your SDL Account team for details, if you are migrating to this version.

SDL Connector Team

Product Update: SDL Integration for AEM - June '19

Nigel Watson — Fri, 28 Jun 2019 10:52:46 GMT

Dear Community,

The June 2019 update for the SDL Integration for AEM brings support for the latest AEM 6.5 version.

The integrations for both SDL Managaed Translation/SDL TMS and SDL Worldserver have been updated to support this latest release.

There are no significant feature updates in the connector, but there were changes in the AEM Translation Framework that required support.

Installers can be downloaded from your usual location, contact your SDL Account team for details, if you are migrating to this version.

SDL Connector Team

Product Roadmap - SDL Integration for AEM

Nigel Watson — Tue, 18 Jun 2019 11:44:36 GMT

The following article describes the product roadmap for the SDL Integration for AEM.

Q1 2020

A new connector release for AEM 6.5 - completely re-designed using SDL custom UI and project creation and management wizards.

More to come in January 2020

AEM Preview

Nigel Watson — Tue, 18 Jun 2019 10:27:01 GMT

Translation Preview in AEM allows the translator and reviewer in SDL TMS, SDL Managed Translation and SDL Worldserver to see a preview of the webpage in-context to the content they are translating/reviewing.

Adobe provide a solution for creating translation preview packages on the fly during the AEM project creation process. This is managed entirely on the AEM side.

Preview is supported in the following AEM versions:

AEM 6.3.3.3
AEM 6.4.4
AEM 6.5

To enable this feature in AEM, set the Enable Preview option in the SDL Connector Cloud Services Configuration to Enable.

Go to the Site properties, Advanced tab and delete the Design property field.

The preview solution will be creating its own designs for the preview package on the fly, thus having any entries in here will override this.

Follow the steps in the install guides to set up the preview on the SDL side.

Product Update: SDL Integration for AEM - September '18

Nigel Watson — Fri, 28 Sep 2018 16:22:17 GMT

Dear Community,

The September '18 update for the SDL Integration for AEM is now available from your given download location.

The following updates are included in the below connector versions:

AEM 6.4.0-1.2.5

New/Updated Features

Proxy Configurations supported in AEM 6.4 (see details from the July Release for AEM 6.3)

Fixed Issues

Translation Token in Translation API
SRQ-9280 Load client details
Translation API Update-Version 1.0.9
Extended Maven Profile to split connector configurations
- ignore the Mantra configuration when the connector sources are build with the profiles for WorldServer
- ignore the WorldServer configurations when the connector sources are build with the profiles for Mantra

AEM 6.3.0-1.6.5

Fixed Issues

Translation Token in Translation API
Translation API Update-Version 1.0.9

AEM 6.2.0-1.5.6

Fixed Issues

Translation Token in Translation API
Translation API Update-Version 1.0.9

Release Notes - January to April 2018: SDL Integration for AEM 6.3

Nigel Watson — Tue, 21 Aug 2018 12:49:26 GMT

Dear Community,

The below update covers release notes from January to April 2018 for the SDL Integration for AEM version 6.3. It is for information to those customers wanting to know what changes have been made this year as we develop the integration, and whether they shoudl upgrade to the latest versions.

Prerequisites

Starting with version 6.3.0-1.1.8 the WorldServer API for the WorldServer environment should be updated with CU5 or above.

Version 6.3.0-1.4.6

Translation API

The Post request in the Translation API was not setting up correctly the encoding to UTF-8 when posting content to either WorldServer environment or TMS environment. Therefore if the description field or the reject translation comment contained any special characters they were not being posted correctly to either WorldServer environment or TMS environment.

This aspect has been fixed by setting up the encoding of the StringEntity to UTF-8.

Version 6.3.0-1.4.5

Caching

Introduced the concept of the refresh token when making requests to the TMS environment through Mantra API.

The refresh token will have an initial life cycle of 1199 seconds(approximately 20 minutes) and it will be stored in the cache from where it will be taken and used in all the subsequent calls that will be made to the TMS environment.

The initial life cycle of the cache is 2160 hours (90 days).

Upon every installation of the connector the cache will be cleared out and reinitialized.

The duration of the cache is configurable and can be changed if the user will access CRX editor under /apps/sdlmantra/config/configurations/cache.If the user wants to change the duration of the cache he needs to change the value in updatedExpirationTime. Upon successfully changing this value the entire cache will be cleared out and reinitialized with the new value.

The caching and the refresh token are needed because in this way the connector won't do an authentication request before every operation through Mantra API hence improving the performance of the application.

For the WorldServer environment the cache is in place but because its API does not support a refresh token concept we always generate a session id before every operation through WorldServer API.

The path for the cache configuration can be found under /apps/sdlws/config/configurations/cache.

Configuration Paths

Couple of settings have been moved under configurations node as follow:

Mantra

/apps/sdlmantra/config/configurations

cache

WorldServer

/apps/sdlws/config/configurations

cache
basicAuthentication
routingLanguages

Version 6.3.0-1.4.4

Extended File Extensions Support

Changed the approach in detecting the file extensions:

the connector will try to detect the file extensions based on the mime type of the object
if the file extension is not found the connector will try to detect the file extension from the source path of the translation object
if the file extension is is still not found the connector will try to detect the file extension with Apache Tika
if no extension is found for the file the connector will throw exception.

Version 6.3.0-1.4.3

Logging

Review the logging in AEM 6.3 connector and Translation API. Made sure that all the sensible information that should be protected are removed from the logging instructions.

More details can be found on the following Jira ticket: LC-353 - Embedded connectors - Personally identifiable information CLOSED

Version 6.3.0-1.4.2

Preview Custom Attribute

Fixed the serialization of project request in Translation API version 1.0.8 in case that the custom attribute for uploading preview packages was not set up at all in the WorldServer environment.

Version 6.3.0-1.4.1

Translation API 1.0.8

Updated Translation API used by AEM 6.3 connector to version 1.0.8.

Please note: starting with this version of the connector if a user has multiple locales configuration for the same ISO code in the WorldServer environment he needs to use the routing language mechanism to configure the target language for the translation project.

This is needed because the new API is smart enough to detect all the languages for the duplicate ISO code from the WorldServer environment and it will create a project group with multiple projects inside it. This is problematic for AEM platform because in AEM platform there is only one target language per translation projects and not n target languages per translation project.

As a precaution measure if the user has the same ISO code configured in WorldServer environment for multiple languages and if he won't make use of the routing language mechanism in the connector the connector will throw an exception, breaking the creation of the translation project.

Resource Resolver Service

When reading information from the JCR the connector was using both resource resolver and session to read information from the JCR.

Changed the implementation to make use only of a Resource Resolver in order to read the information from the JCR repository.This should avoid any race conditions when instantiating the resource resolver for reading information from the JCR.

The dependencies for the Apache Sling API have been updated to the version recommend by Adobe for AEM 6.3 connector.Currently the version for the Apache Sling API is greater then 2.5.0 and is taken from uber-jar artifact provided by Adobe.

The update was needed because Apache Sling API version 2.5.0 was outdated for AEM 6.3 platform.

Reject Translation Comment

When rejecting a translation in AEM platform the user had the possibility to enter also a reject translation comment.

The comment was not being sent correctly to either WorldServer environment or TMS environment and it was not visible even though the user entered it correctly.

This aspect has been fixed and the reject translation comment should be visible in WorldServer/TMS environment.Please see an example of multiple reject translation comments in WorldServer environment:

Mantra API Reject Translation

Implemented endpoint to reject translation in AEM connector through Mantra API.

Version 6.3.0-1.3.4

Apache Sling Service User Mapper Service

Eliminated the Apache Sling Service User Mapper Service configurations that the connector was writing during its installation.

These configurations are not needed anymore because the connector will make use only of the written configurations in Apache Sling User Mapper Service Amendment.

When installing the connector the following will happen:

A bootstrap-service user will be created that will get reading/writing rights under content.
In Apache Sling User Mapper Service Amendment a writeAccessResourceResolver service will be defined that will make use of the bootstrap-service user.The writeAccessResourceResolver will be used to instantiate the resource resolver in connector.Therefore, according to the nature of the connector an AEM user should find one of these entries in Apache Sling User Mapper Service Amendment: com.adobe.granite.translation.connector.sdlws:writeAccessResourceResolver=bootstrap-service,com.adobe.granite.translation.connector.sdlmantra:writeAccessResourceResolver=bootstrap-service.If the connector for Mantra is installed together with the connector for WorldServer connector on the same platform then both of these entries should be found together in Apache Sling Service User Mapper Service Amendment.

Version 6.3.0-1.3.3

File Extension

Introduced Apache Tika libraries to detect the file extensions based on the translation project mime type.

In order for this version of the connector to function properly the user should make sure that the appropriate configuration for the file extensions filters is configured in either TMS or WorldServer environment.

Apache Tika will detect the extension based on the mime type of the object and it should be able to detect more than 400+ file extensions.

Version 6.3.0-1.3.1

Routing language

Routing language path did not correspond anymore after refactoring the content package.Fixed the routing language path and moved all the configurations for TMS language mapping, WorldServer language mapping,routing language mechanism and basic authentication mechanism in JCR properties class

Version 6.3.0-1.3.0

Connectors Packages Configuration

The AEM 6.3 common connector solution builds have been split into two different artifacts,one artifact for WorldServer environment and another one for Mantra environment:

com.adobe.granite.translation.connector.sdlws.pkg-6.3.0-1.3.0.zip
com.adobe.granite.translation.connector.sdlmantra.pkg-6.3.0-1.3.0.zip

For customers who are using a patched version of the connector and for which the configurations in the user mapper services are not done automatically the following settings will be necessary:

Configuration	WorldServer com.adobe.granite.translation.connector.sdlws.pkg-6.3.0-1.3.0.zip	Mantra com.adobe.granite.translation.connector.sdlmantra.pkg-6.3.0-1.3.0.zip
Apache Sling Service User Mapper Service	com.adobe.granite.translation.connector.sdlws:writeService=translation-config-service com.adobe.granite.translation:writeService=translation-config-service com.adobe.granite.translation.connector.sdlws:readService=translation-config-service com.adobe.granite.translation:readService=translation-config-service	com.adobe.granite.translation.connector.sdlmantra:writeService=translation-config-service com.adobe.granite.translation:writeService=translation-config-service com.adobe.granite.translation.connector.sdlmantra:readService=translation-config-service com.adobe.granite.translation:readService=translation-config-service
Apache Sling Service User Mapper Service Amendment	com.adobe.granite.translation.:translation-config=translation-config-service com.adobe.granite.translation.connector.sdlws:translation-config=translation-config-service	com.adobe.granite.translation.:translation-config=translation-config-service com.adobe.granite.translation.connector.sdlmantra:translation-config=translation-config-service

Access http://localhost:4502/useradmin
Search after translation-config-service and make sure that translation-config-service user has reading/writing rights to everything under content:

Version 6.3.0-1.2.1

Language Mapping

The AEM 6.x connectors contained an xml language mapping that was being read and written in the JCR when installing the connector.

Initially the language mapping configurations where designed specifically for TMS environment.Therefore when using the AEM 6.x common connector solution these configurations were causing inconsistencies in the implementation breaking the target language detection on the WorldServer environment.

Couple of changes were necessary for fixing this issue:

the language mapping configuration was split between TMS environment and WorldServer environment
the Jenkins build was separated into two different builds: one build for WorldServer environment and another build for TMS environment
when building the artifact for TMS environment a Maven profile is being used to pack inside the connector only the language mapping settings specific to the TMS environment.
when building the artifact for WorldServer environment a Maven profile will be used to pack inside the connector only the language mapping settings specific to the WorldServer environment.

If after installing the connector the target language is still not being detected correctly the user should do the following:

access /apps/sdl/config/languageMapping
search after the language code from AEM
change the languageMapping property to the ISO code from either TMS environment or WorldServer environment.Please note:on the WorldServer environment the values returned by the WorldServer API are different than the values of the ISO code that the user is able to see on the Locales section.For example for EN-US locale the WorldServer API is returning EN_US as ISO code.For WorldServer environment in the languageMapping property the user needs to use the values returned by the APIs and he needs to make sure that these are correct.

Request Scope

Request project scope was not working properly on the common connector solution because it did not wait for all the translation files to reach either Authorization step in WorldServer or For Approval status in TMS. Therefore there was the risk that the project scope was always empty when the translation reached Scope Completed status in AEM. This aspect has been fixed and now the request scope should function properly.

Filename Truncation Removed

It has been made sure that the filename truncation is not anymore present in the connector implementation starting with this version.

Version 6.3.0-1.1.12

Reject Translation

Considering the following testing scenario:

A translation job with at least two files
The translation job was in a Ready For Review state
The user was first accepting a translation for a file and then rejecting the translation for another file on a WorldServer environment

The general translation job status should had remained in Translation in Progress and the status of the translation file that was already accepted should had remained in Approved.This was the result that was expected under normal circumstances but status of the translation file that was already approved was being changed back into Translation In Progress.This was fixed and the Reject/Accept translation should work as expected.

Translation API Update

The Translation API had to be updated in order to eliminate the WorldServer target language id detection based on the language code.Doing this caused issues and for languages with the same language code the wrong id was being detected.

This issue was fixed and now the target language id is being detected correctly.

Version 6.3.0-1.1.10

Basic Authentication

By default the option to use the basic authentication mechanism in AEM 6.3 connector is set to be disabled.

In order to activate the Basic Authentication mechanism a user needs to access CRX explorer or CRXDE Lite editor.

Under /apps/sdl/config a user will find a new node called basicAuthentication.

In order to activate Basic Authentication please change the property isBasicAuthenticationEnabled from the stated node to true.

Upon successfully changing this property to true in Cloud Service Configuration page two new fields will appear.These fields will have to be filled with the basic authentication username and basic authentication password in order to be able to authenticate a user and use the connector.

Cloud Service Configuration Page Updates

Cloud service configuration page has been updated to:

display only the fields specific to Mantra API configuration when TMS option is selected.
display only the fields specific to WorldServer API configuration when WorldServer option is selected.
display Basic Authentication Username and Basic Authentication Password only when Basic Authentication mechanism has been enabled.

Version 6.3.0-1.1.9

Basic Authentication

The connector has been updated in order to support basic authentication through a reverse proxy that sits behind a firewall and intercepts all the requests to either WorldServer environment or TMS environment.

In case that the Basic Authentication mechanism is enabled in AEM 6.3 Connector :

Translation API will take the basic authentication username and basic authentication password and will construct an authentication string encoded in Base64
Translation API will add this authentication string as a header parameter in all the requests performed to either WorldServer or TMS environment
In case that the basic authentication credentials are missing from cloud service configuration page the requests that are performed through Translation API will not add as a header parameter the basic authentication encoded string

Version 6.3.0-1.1.8

Translation API implementation Update

Translation API implementation has been altered in order to avoid the breaking of the project creating for the WorldServer environment in case that the WorldServer API from our customer environments is not updated.

Still this won't guarantee that the detection of the target language id will be successful in case that the customers will restrict the target locales in a project type.

Therefore it is recommended that starting with the previous the WorldServer API is being updated.

Version 6.3.0-1.1.5

Automatically Complete Task in World Server

After approving a task in AEM the task was not being automatically completed in World Server.

File and Project Naming Conventions

There was a request for the filename length to be smaller or equal with fifty characters. In case that the filename length was greater than fifty characters the name of the file is being truncated.

For Project Naming Convention the following requirements are currently implemented and released:

project name length is smaller or equal than fifty characters
the implementation will remove the square brackets from the folder name that is added automatically by the platform in project name
the project name will be separated from the folder name by using an underscore
the project name will not be anymore retrieved from the Cover URL property. Instead it will be retrieved from the jcr:title property

Routing language mechanism

In case that the translation target language in which the content should be translated is different than the translation target language from WorldServer the user has the possibility to route the content for translation in a different language.

More details about this functionality can be found at the following link AEM Routing Language Mechanism

Release Notes - January to April 2018: SDL Integration for AEM 6.4

Nigel Watson — Tue, 21 Aug 2018 12:38:26 GMT

Dear Community,

The below update covers release notes from January to April 2018 for the SDL Integration for AEM version 6.4. It is for information to those customers wanting to know what changes have been made this year as we develop the integration, and whether they shoudl upgrade to the latest versions.

Version 6.4.0-1.0.3

Translation API

This aspect has been fixed by setting up the encoding of the StringEntity to UTF-8.

Version 6.4.0-1.0.2

Package structure refactoring

The root package structure has been changed to com.sdl.connectors.
The package group that is inherited by all child poms in AEM 6.4 connector has been changed to com.sdl.connectors.reactor.
The paths from the cloud service configuration page have remained intact and no alteration has been performed on them.

Gson Dependency

Introduce Gson dependency to replace Json Writer which has been deprecated by Adobe.
The Gson object mapper can be used to transform data into JSON and send it to the front-end.

Translation API Update

Translation API has been updated to version 1.0.8. The connector should now support also the reject translation functionality through Mantra API.

Version 6.4.0-1.0.1

Apache Sling Service User Mapper Service

Eliminated the Apache Sling Service User Mapper Service configurations that the connector was writing during its installation.

These configurations are not needed anymore because the connector will make use only of the written configurations in Apache Sling User Mapper Service Amendment.

When installing the connector the following will happen:

a bootstrap-service user will be created that will get reading/writing rights under content.
in Apache Sling User Mapper Service Amendment a writeAccessResourceResolver service will be defined that will make use of the bootstrap-service user.The writeAccessResourceResolver will be used to instantiate the resource resolver in connector.Therefore according to the nature of the connector the user should find one of these entries in Apache Sling User Mapper Service:com.adobe.granite.translation.connector.sdlws:writeAccessResourceResolver=bootstrap-service,com.adobe.granite.translation.connector.sdlmantra:writeAccessResourceResolver=bootstrap-service or
com.sdl.connectors.machine.translation:writeAccessResourceResolver=bootstrap-service.If the connector for Mantra is installed together with the connector for WorldServer and machine translation then all these entries should be found together in Apache Sling Service User Mapper Service.

Version 6.4.0-1.0.0

Connector Migration

Updated the connector dependencies to the latest versions recommended by Adobe
Eliminated the support for org.apache.felix.scr.annotations and replaced them with org.osgi.service.component.annotations
Migrated the connector services from Apache Sling Services to OSGI Services
Migrated the connector configuration servlets from SlingServlet to HttpServlet
Introduced a bundle activator in order to correctly register and unregistered the configuration servlets.
Eliminated BootstrapTranslationAdapterFactory. Read the cloud services configurations directly from JCR.
Read the translation target language from the translation job.

Available features

Request Scope
Accept Translation
Reject Translation(only for WorldServer environment)
Cancel Translation
Complete Translation
Archive Translation Job.

Product Update: SDL Integration for AEM - July '18

Nigel Watson — Tue, 21 Aug 2018 12:31:59 GMT

Dear Community,

The July '18 update for the SDL Integration for AEM is now available from your given download location.

The following updates are included in the below connector versions:

AEM 6.2.0-1.5.4

New/Updated Features

Proxy Configurations

AEM 6.3.0-1.6.3

New/Updated Features

Proxy Configurations

Details of Feature Updates

Proxy Configurations

Please note: only one type of active proxy configuration should be enabled at the same time.

Please note: if the user enabled a basic authentication proxy configuration and wants to enable a simple proxy configuration, ensure that in the cloud service configuration page the value for the basic authentication proxy configuration are deleted and the cloud service configuration page is saved.

Simple Proxy Configuration

If the user has a forward proxy configured with no authentication mechanism, in order for the connector to be functional he needs to follow the next set of instructions:

Access localhost:4502/.../de and in sdlmantra/sdlws directory select noAuthProxyConfig and set it's value to true:

I the user successfully managed to enable the option, in the cloud services configuration page he should see a proxy host field and a proxy port field.Please input your details and save the configuration:

Save the configuration and start a translation project. All the requests should be successfully routed through the proxy configuration.

Basic Authentication Proxy Configuration

If the user has a forward proxy configured with a basic authentication mechanism,in order for the connector to be functional he needs to follow the next set of instructions:

Access localhost:4502/.../de and in sdlmantra/sdlws directory select basicAuthProxyConfig and set it's value to true:

I the user successfully managed to enable the option, in the cloud services configuration page he should see a proxy host field, a proxy port field, a proxy username field and a proxy password field.Please input your details and save the configuration:

Save the configuration and start a translation project.All the requests should be successfully authorized by the proxy configuration.

NT Credentials Proxy Configuration

If the user has a forward proxy configured with NTLM credentials,in order for the connector to be functional he needs to follow the next set of instructions:

Access localhost:4502/.../de and in sdlmantra/sdlws directory select ntlmAuthProxyConfig and set it's value to true:

I the user successfully managed to enable the option, in the cloud services configuration page he should see a proxy host field, a proxy port field, a proxy username field,a proxy password field and a proxy domain field.Please input your details and save the configuration:

Save the configuration and start a translation project.All the requests should be successfully authorized by the proxy configuration.

Translation API Update

Translation API has been updated to allow the connector to make request through a forward proxy configuration

The current version of the Translation API is 1.0.9.

Product Update: SDL Integration for AEM - May '18

Nigel Watson — Tue, 19 Jun 2018 13:14:47 GMT

Dear Community,

The May '18 update for the SDL Integration for AEM is now available from your given download location.

The following updates are included in the below connector versions:

AEM 6.4.0-1.2.0

New/Updated Features

Cloud Services Configuration Migration
Dynamic loading of TMS/Worldserver configurations based on the user's account
Configurable Preview Attribute for WorldServer environment

Fixed Isssues

Fixed the mapping of the Completed project status for WorldServer environment

AEM 6.3.0-1.6.0

New/Updated Features

Configurable Preview Attribute for WorldServer environment

Fixed Isssues

Fixed the mapping of the Completed project status for WorldServer environment
Fixed corrupted preview packages for WorldServer environment and TMS environment

AEM 6.2.0-1.5.0

New/Updated Features

Configurable Preview Attribute for WorldServer environment

Fixed Isssues

Fixed the mapping of the Completed project status for WorldServer environment
Fixed corrupted preview packages for WorldServer environment and TMS environment

Details of Feature Updates

1. WorldServer Configurable Preview Custom Attribute

The WorldServer custom attribute for uploading the preview packages with AEM WorldServer connector has been changed in order to be configurable.

If the project type in WorldServer contains multiple custom attributes of type attachment, in order to make sure that the preview package uploaded with the WorldServer connector will target the correct custom attribute in the project type:

Install the SDL WorldServer Connector
Go in JCR and access /apps/sdlws/config/configurations/
Fill in the value of the customPreviewAttributeId with the id of the WorldServer custom attribute that should be used for the preview functionality.

See below a print screen showing an example:

Note: this setting is needed only in case that the project type contains multiple custom attributes of Attachments type.

2. Load configurations dynamically (AEM 6.4 Only)

The cloud services configurations pages have been changed in order to partially load some of the configurations dynamically.

SDL TMS/Managed Translation

the user will have to enter the Mantra API URL, a username, a password, a client id and a client secret representing its account details.
when the user will click the project options drop down the connector will dynamically load all the project options to which the user account has access.
if the users' account details are incorrect and the connector won't be able to connect to the TMS environment through Mantra API a popup exception will appear on the screen indicating this aspect

SDL Worldserver

the user will have to enter the WorldServer API URL, a username and a password representing its WorldServer account details.
when the user will click the client drop down the connector will load dynamically all the WorldServer client details to which the user has access
when the user will click the project type, the connector will load dynamically the project types corresponding to the previously selected WorldServer client
if the users' account details are incorrect and the connector won't be able to connect to the WorldServer environment a popup exception will appear on the screen indicating this aspect

3. Cloud Services Configuration Migration (AEM 6.4 Only)

Migrated the connector configurations from legacy cloud services to cloud services configuration directory.

Note: with this migration the path under which the details of the translation configurations were being saved has been changed as well.

Until now, when the user was creating a new translation configuration the translation configuration was being saved under /etc directory.

Currently the configurations are saved, as recommended by Adobe, under the /conf directory like in the attached print screen:

The path for the other settings such as the language mappings, language encoding, routing languages, cache or custom preview attribute id have remained unchanged and they can be found under /apps/sdlws or under /apps/sdlmantra:

General Notes on SDL Integration for AEM

Nigel Watson — Mon, 18 Jun 2018 13:47:10 GMT

This forum will cover information and product releases for the SDL Integration for Adobe Experience Manager in general.

There will be product updates and release notes to support AEM 6.1, 6.2, 6.3 and 6.4 integrations for SDL Worldserver, SDL TMS and SDL Managed Translation.

There will be separate forum posts that discuss specific items for each of the SDL products as some features and functionality vary. Please be sure you are aware of the product specified in the forum discussion.

When posting a question, ensure to specify the version of AEM and the version of the SDL Language Technology you are connecting to as this will help identify the right solution.