Documentation Center

Integration requirements for Content Manager and SDL WorldServer

The following are items that will help you better understand the integration of Content Manager and SDL WorldServer 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 WorldServer 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 defines 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 translated status.

      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 translation status.

      The status transition is: To be translated to In translation.

      TranslationJob option Include 'In translation' items forces 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 Translated status.

      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 rejected status.

      The status transition is: Translated to Translation rejected.

    • The status transition from Translation rejected to In translation allows items to be re-translated.
The system finds your configured initial and next status by executing a GetPossibleTransitionStatus on your object having the user role 'TRANSLATORSERVICE'. For every call, the system expects exactly one 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 WorldServer

Required for SDL WorldServer integration:

  • A dedicated user in SDL WorldServer.

    This is the user that is used by Translation Organizer to logon to SDL WorldServer. This is the parameter userName within the worldServer section in the configuration file.

  • Content Manager mount configured to use UTF-16.

    Refer to the SDL WorldServer manuals for the further details.

  • Locales, Workflow, Project Types, whatever is required by WorldServer to go through the translation process.

    Refer to the SDL WorldServer manuals for the further details.

  • After Translate step in a workflow should be an automatic Save step.

    Refer to the SDL WorldServer manuals for the further details about how to configure the workflow in SDL WorldServer.

  • After Save step in a workflow should be Translated Content Retrieval step which is used by Content Manager to start getting the translation. From Translated Content Retrieval step there should be a transition called Retrieved.

    Refer to the SDL WorldServer manuals for the further details about how to configure the workflow in SDL WorldServer.

  • Asset path normalizer. This is optional custom component that can be implemented separately and installed in SDL WorldServer to force SDL WorldServer TM to consider the file name when doing match.

    Refer to the SDL WorldServer manuals for the further details.