Integration requirements for Content Manager and WorldServer
The following will help you better understand the integration of Content Manager and 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 a 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 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 and for user roles, that defines a workflow for the integration:
- There is an initial status to indicate that the object is ready for translation: To be translated.
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: In translation.
Status transition: 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: Translation in review.
Status transition: In translation to Translation in review.
- With a status transition from the Translation in review, there is a status indicating that a user approved the translation: Translation approved.
Status transition: Translation in review to Translation approved.
- With a status transition from the Translation in review, there is a status indicating that a user rejected the translation and the object needs to be re-translated: Translation rejected.
Status transition: Translation in review to Translation rejected.
- Status transitions allow for objects to be re-translated from several positions in the flow, thus making the process cancelled or rolled back to the status To be translated.
Status transitions:
- In translation to To be translated.
- Translation in review to To be translated.
- Translation rejected to To be translated.
- There is an initial status to indicate that the object is ready for translation: To be translated.
The TRANSLATORSERVICE role and the status transitions are configured accordingly out-of-the-box.
WorldServer
- A dedicated user in WorldServer.
This is the user that is used by Translation Organizer to logon to WorldServer. This is the parameter
userNamewithin theworldServersection in the configuration file. - Content Manager mount configured to use UTF-16. It is also possible to work with UTF-8 projects. This requires adding UTF-8 locales for all users in Management > Business Rule Linkage > Locales in WorldServer. Refer to WorldServer documentation for more details.
- Locales, Workflow, Project Types, whatever is required by WorldServer to go through the translation process.
- A first step named Translate.
- After the Translate step there should be an automatic Save step.
After the Save step there should be Translated Content Retrieval step which is used by Content Manager to start getting the translation.
- After the Translated Content Retrieval step, a transition named Ready for review leads to the Translated Content In Review step.
- After the Translated Content In Review step, there must be two possible transitions:
- The Approved transition that leads to the end of the flow.
- The Rejected transition that leads back to the Translate step.
- The Asset path normalizer. This optional custom component can be implemented separately and installed in WorldServer to force WorldServer TM to consider the file name when doing the match.
- Compatibility
-
- For backward compatibility, it is still possible to configure a simplified flow made of Translated Content Retrieval immediately followed by a transition called Retrieved.
- The translation review flow with the possibility to approve or reject the translation, introduced in Content Manager 13.0.0, is incompatible with the SOAP API protocol. Therefore when WorldServer uses that protocol, only the legacy flow can be used (Translated Content Retrieval immediately followed by Retrieved).
- Any given job must be using only one type of flow: Either the current flow with an approval step, or the legacy flow. The system can not manage mixed flows.