Configuring the plugin

In order to configure the plugin you require the web location of a Beebox server, a project key and credentials. Please see the Prerequisites page.

Once your bundle is up and running, make following configurations to start your translation workflows.

Connection to Beebox

Once you have all connection details, proceed as follows:

• In the AEM administration, select Beebox Translation Console  (i.e. http://localhost:4502/etc/beeboxTranslation.html).
  
  
  
  
• On the right side on the page, press Settings then Beebox Connections.
  
  

• In the configuration window, complete the Beebox Server Configuration according to those you received.
  
  

1. Select the source language as configured in Beebox project.

2. Fill all Beebox connection details as shown below.

   Field	Description
   Source language	The source language that is configured in your AEM site and Beebox project.
   Server Url	A URL pointing to the Beebox server. Supplied by the Beebox manager.
   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.

3. Optionally, configure the proxy settings by providing :
   - Host: IP address of the proxy server.
   - Port: Port on which the proxy server needs to run.
   The proxy server can be authenticated by providing the authentication details as the username and its password.

4. Press Test, to check AEM site connection with Beebox should you have entered correct details Success message would be shown.
   
   
5. Finally, press Submit.

Language mapping

It can happen that the AEM langages codes differs from the Beebox language codes.

As an example, if your content is written as English (en) in AEM but the Beebox project use the complete locale name as English (United States), then it needs to be configured for correct translation to happen.

For language codes that do not have locale, like  and are simply “en” and “fr” like, you can start without configuring this.

To configure a mapping :

• In the AEM administration, select Beebox Translation Console. 
  
  
  
  

• On the right side on the page, press Settings then Languages Mappings.
  
  
  
  

• Then, configure the AEM languages to map the Beebox locales.
  
  
  
  The Path indicator is an optional user defined input.
  If the user specifies path indicator, then the target path will be changed accordingly.

  E.g, for a site language as French (fr),

  - Source path: /content/geometrixx-outdoors-4/en/men

  - Target path: /content/geometrixx-outdoors-4/fr/men

  If path indicator is specified as fr_FR, the target path would be as follows:

  - Source path: /content/geometrixx-outdoors-4/en/men

  - Target path: /content/geometrixx-outdoors-4/fr/fr_FR/men

   

Language configuration

IMPORTANT This part is mostly useful to add languages for translation in your AEM instance. Please refer to the language mappings if you need to map your current AEM languages to Beebox locales !

Before configuring the languages, you need to know:

• The source language i.e you require translation from. Corresponding to each source language, there must be a Beebox project configured. 
• The target languages i.e. you require translation into.

There is also a default asset language that will be used as a source language for the asset(doc, text files). 

To configure languages:

• In the AEM administration, select Web Console (i.e. http://localhost:4502/system/console/configMgr)
• Search for a configuration named Beebox Language Configuration and edit it.
  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 “=”. Then, “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.

Whitelist admin login

IMPORTANT For AEM > 6.2 there is need to the whitelist admin login

• In the AEM administration, select Web Console (i.e. http://localhost:4502/system/console/configMgr)
• Search for a configuration named Apache Sling Login Admin Whitelist and add beebox.beebox-bundle-Connector

Components configuration

By default, the connector is configured to translate the AEM default components only. If you use custom components in your AEM instance, you need to configure them in order to Beebox to know that components should be translated as well.

To configure the components:

• In the AEM administration, select Web Console (i.e. http://localhost:4502/system/console/configMgr)
• Search for a configuration named Beebox Components Configuration and edit it.
  
  
  
  To configure a new component for translation, add a row as following :
  path/to/component=fieldtoTranslation1;fieldToTranslate2

Meta-data/Preview configuration

It is possible to include the direct link of the page in the generated XML which are sent to Beebox.

This can be useful for your translators to know which page they are translating, or simply to use Beebox Live Preview.

To configure the base/public URL of your website,

• In the AEM administration, select Beebox Translation Console  (i.e. http://localhost:4502/etc/beeboxTranslation.html).
  
  
  
  
• On the right side on the page, press Settings then Translation Preview.