Versions Compared

Version Old Version 3 New Version Current
Changes made by

Former user

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Key Wordbee components in the architecture diagram: 

  • The Wordbee Beebox SDL Tridion Connector software, which is installed on a dedicated Windows server. But in the case of constraint, it can be on the same server as SDL Tridion. 

  • The Wordbee Beebox software, which typically is installed on the same server as the Beebox SDL Tridion Connector. 

  • An SDL Tridion Beebox GUI Extension which is installed to SDL Tridion using the SDL Tridion Content Explorer configuration. 

  1. Key interactions in the architecture diagram: 

  • In the SDL Tridion Content ExplorerIn the SDL Tridion CME, the business user selects the content folder/item and opens Beebox GUI Extension. 

  • The user fill-in necessary details like Translation request name, Translation deadline, Instructions, etc., and submits the translation request. 

  • The Beebox GUI Extension makes a web API call to Wordbee Beebox SDL Tridion Connector and submits a translation request. 

  • Then the Beebox SDL Tridion Connector connects item and clicks on Wordbee Translate, which launches Wordbee Translation Manager (short read: ‘WTM’) GUI extension. The translation option is limited to the following content types only: 

  • Component 

  • Page 

  • Category 

  • Keyword 

  • Folder 

  • Virtual Folder 

  • Structure Group 

  • WTM GUI extension, create jobs out of selected content items and allow the user to fill-in necessary details like translation job title, target languages, required date, priority, and other metadata. 

  • The WTM GUI extension consists of WCF services (supported by Tridion as an OOTB feature), which stores translation job detail into Wordbee Translation Manager DB. 

  • Wordbee Beebox SDL Tridion Connector windows service pings WTM DB at regular intervals and reads new translation job details. Upon the arrival of a new translation job, the connector windows service connects to SDL Tridion Core Services APIs to retrieve details of content folders/items for of content items, for which translation has been requested. After reading the data the connector forwards , the connector windows service forwards content and meta-data to the Wordbee BeeboxWordbee Beebox software by means of the the Beebox web  web API. 

  • The Wordbee Beebox software then sends items to Wordbee Translator Wordbee Beebox software then sends items to Wordbee Translator TMS.  This This triggers the creation of translation jobs (or other pre-configured single or multi-stage translation workflows).  

  • Once a translation workflow for content is completed in Wordbee TranslatorWordbee Translator,  translated translated content is retrieved by Wordbee BeeboxWordbee Beebox. Beebox periodically polls Wordbee Translator polls Wordbee Translator for completed work. 

  • Wordbee Beebox Wordbee Beebox SDL Tridion Connector itself polls Beebox in periodic intervals. Once translated content is received, the connector uses the Core Services APIs to push translated content to SDL Tridion and updates translation job status into WTM DB. 

 

  1. Key characteristics of this architecture: 

...

  1.  

  • Wordbee Translation Manager GUI extension consists of editor extension and WCF services. Editor extension posts the data to WCF services as and when key events occurred (like the creation of translation jobs, sending jobs to translation, etc.). And then the WCF service pushes translation jobs into Wordbee Translation Manager DB. 

  • The WTM GUI extension and WCF services are hosted on the same server as SDL Tridion. 

  • WTM DB is hosted on the same DB server as SDL Tridion or be released to a dedicated VM or machine.  

  • Wordbee Beebox will be hosted in Wordbee Data Center. 

  • Each Beebox installation Each connector installation provides localization support to a single single SDL Tridion instance instance. 

  • The solution seamlessly integrates with the blueprinting and localization capabilities of SDL Tridion. Translation workflows are implemented using the specifically developed SDL Tridion Beebox GUI extension. This extension permits to select content for translation and to receive back translations from the Beebox setupof SDL Tridion. 

  • Apart from the Translation request form, the GUI extension will also include two options that will also include two options that list all queued translation requests and all completed requests, respectively. 

  • Beebox can  can handle any amount of translation volume of transactions per day. 

  • Translation requests can include any custom metadata attached to content. 

  • Through the configuration of the Beebox setup, translation requests can be routed into different translation workflows. In practice, this is done by first configuring one “Beebox project” per workflow per workflow (e.g. type of content, urgency, type of translators , or vendors…). Then, again through configuration, we specify which metadata content routes content to which Beebox project (aka workflow). 

  • Any metadata can be selected can be selected to be visible to the translator of the content (to give additional context). 

  • Each Beebox project (workflow) can then be connected to a project in the Wordbee Translator the Wordbee Translator platform of the client KLM (the TMS).