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.

Connection to Beebox

Once you have all connection details, proceed as follows:

• In the AEM administration, select Beebox Translation Console. 
  
  
  
  
• 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 doesn't match with the Beebox, especially when the content is written in a specific locale like en-US.

As an example, if you need to configure a mapping between English (en) in AEM and English (United States) in Beebox.

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.
  
  

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

• Next is target language configuration. This needs to be done in case beebox language code differs from AEM language code. For example, in AEM if some language code is en_ab whereas in Beebox its en-LA, then it needs to be configured for correct translation to happen. For language codes that do not have locale and are simply “en” and “fr” like, you can start without configuring this.

            Go to Settings -> Language Mappings

• Path indicator is a user defined input and it is optional. 
• If the user specifies path indicator, then the target path will be changed accordingly.

           E.g. For site language French(fr),

                 1. If path indicator is not specified, the target path would be as follows:

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

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

                 2. If path indicator is specified as fr_FF, the target path would be as follows:

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

                  target path: /content/geometrixx-outdoors-4/fr/fr_FF/men

 NOTE : Path indicator is optional and one time configurable. It is advised not to change it as we will be consdering source lang through path.  Once it is configured, translated pages will be created in the path configured.