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.
Key interactions in the architecture diagram:
In the SDL Tridion Content Explorer, 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 to SDL Tridion Core Services APIs to retrieve details of content folders/items for which translation has been requested. After reading the data the connector forwards content and meta-data to the Wordbee Beebox software by means of the Beebox web API.
The Wordbee Beebox software then sends items to Wordbee Translator TMS. 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 Translator, translated content is retrieved by Wordbee Beebox. Beebox periodically polls Wordbee Translator for completed work.
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.
Key characteristics of this architecture:
The Beebox components can be hosted on the same server as SDL Tridion or be released to a dedicated VM or machine.
Each Beebox installation provides localization support to a single SDL Tridion 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 setup.
Apart from the Translation request form, the GUI extension will also include two options that list all queued translation requests and all completed requests, respectively.
Beebox 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 (e.g. type of content, urgency, type of translators, or vendors…).
Any metadata 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 platform of the client (the TMS).