Integration requirements for Content Manager and SDL TMS
The following are items that will help you better understand the integration of Content Manager and SDL TMS and considerations when configuring translation and workflow.
Content Manager
Required for Content Manager integration:
- Languages are defined as described for source and pivot languages (see related topic). For example:
The following example defines a source language of English with target languages for German, Spanish, French, Italian and Chinese. The last group indicates that Chinese can be used as source language (pivot) for translating to Japanese and Korean.
<languagepaths> <languagepath from="nl" to="fr"/> <languagepath from="en" to="de"/> <languagepath from="en" to="es"/> <languagepath from="en" to="fr"/> <languagepath from="en" to="it"/> <languagepath from="en" to="zh"/> <languagepath from="zh" to="ja"/> <languagepath from="zh" to="ko"/> </languagepaths> - Translation templates come from SDL TMS and are automatically pushed to Content Manager by TranslationOrganizer.
- Content Manager uses UTF-16 for the content.
- The dedicated user (typically 'ServiceUser') having the role TRANSLATORSERVICE.
- Statuses and status transitions, configured for the TRANSLATORSERVICE role, that define a workflow for the integration:
- There is an initial status to indicate that the object is ready for translation.
This is typically the
To be translatedstatus.This status is used by TranslationBuilder to create new target language objects and by TranslationOrganizer to identify and include objects to send.
- With the status transition from the initial status, there is a status to indicate that the object is no longer under control of the CMS.
This is typically the
In translationstatus.The status transition is:
To be translated to In translation.TranslationJob option
Include 'In translation' itemsforces the re-sending of objects in this status. - With the status transition from the status above, there is a status to indicate that the object is back in CMS control.
This is typically the
Translatedstatus.The status transition is:
In translation to Translated. - The last status indicates that the translation was rejected and object should be re-translated.
This is typically the
Translation rejectedstatus.The status transition is:
Translated to Translation rejected. - The status transition from
Translation rejected to In translationallows items to be re-translated.
- There is an initial status to indicate that the object is ready for translation.
to status as a result, so it can deterministically push your object from one status to the next one.
Defining and configuring the TRANSLATORSERIVCE role and the status transition are described in Configuring the translation builder.
SDL TMS
Required for SDL TMS integration:
- Configurations specifying the workflow and all necessary language pairs.
- The workflow should contain minimally the following 2 steps:
- The 'Content retrieval' step which is used by Content Manager to start getting the translation.
- The 'Completed' step which is used by Content Manager to indicate that the translation was downloaded successfully.
Refer to the SDL TMS manuals for the further details about how to configure the workflow in SDL TMS.