...
The connection setting page shows these fields:
Field | Description |
---|---|
Server Url | A URL pointing to the Beebox server. Supplied by the Beebox manager: Prerequisites |
Project Key | A key identifying a Beebox project. Supplied by the Beebox manager. |
Login | A login to access the Beebox. Supplied by the Beebox manager. |
Password | A password to access the Beebox. Supplied by the Beebox manager. |
Source language | The source language that is configured in your AEM site and Beebox project. |
Configuring language
Once your bundle is up and running, make following configurations to start your translation workflows.
- You need to know source language i.e you require translation from. Corresponding to each source language, there must be a Beebox project configured.
- You need to target languages i.e. you require translation into.
- Then there is default asset language that will be used as source language for asset(doc, text files).
To finally configure languages;
- Go to AEM instance i.e. http://localhost:4502/system/console/configMgr
- Search for “Language Info”, you will find a configuration with name “Beebox Language Configuration”. Select it.
- Press on Edit, the following screen would come up.
Only these source and target languages will be available for translation. Each source and target language are separated by “=”. For example, “English” with AEM language code as “en” would be represented as en=English
Other languages can be configured in a similar way, with AEM language code on left of “=“ and nice name on right hand side.
Configuring Component Properties
On same URL(http://localhost:4502/system/console/configMgr), search for following three configurations. Although it is needed if you will be using “Rolloutfeature”, still it is recommended that you make this configurations otherwise alsoin the first place.
Add following to “Exclude page properties”:
beebox_translationStatus
beebox_translatedFrom
beebox_translatedTo
beebox_lastTranslationDate
WCM Rollout Manager
CQ MSM Content update action