This the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Setting Up the Translation Database

You set up the database so that the Connector can use it to store translation-related data.

1 - Translation Database Size Requirements

The required size of the database depends on the volume of translation you anticipate. When the database is used only for translation-related data, 100MB is usually adequate. However, by default, the Lionbridge Connector backs up translation data, which it uses to support the Translation Correction and Update Remote TM features. For descriptions of these features, refer to the Lionbridge Connector for Sitecore User Guide.

  • If you keep the default setting of backing up data so that you can use these features, you may need to increase the size of the database by 50 to 100 percent to support the backup.
  • If you do not want to back up data, you do not need to increase the size of the database.

Note: To prevent the Connector from backing up translation-related data, you modify the ClayTablet.BackupTranslationData setting, described in Configuring Database Settings.

You can use the Connector to delete the translation-backup database at any time from the Sitecore Content Editor, however the relevant Connector features will not work properly. For instructions on deleting the backup, refer to the Lionbridge Connector for Sitecore User Guide.

2 - Setting Up a Microsoft SQL Server-Based Translation Database

This section describes how to set up a Microsoft SQL Server database to use with the Connector. For information on database size requirements, see Translation Database Size Requirements.

  1. Use Microsoft SQL Server Management Studio to create an empty database. For detailed instructions, refer to the Microsoft SQL Server documentation.

Recommendation: Name the new database CT3Translation.

Note: Set your default database collation to SQL_Latin1_General_CP1_CI_AS.

  1. Configure the Connector database connection string. The Website_root/App_Config/ConnectionStrings.config file defines the database connections.

Important: The database part of the connection string must match the database name you created in the previous step.

Typically, it should be:

<?xml version=“1.0” encoding=“utf-8”?>

<connectionStrings>

<add name=“core” connectionString=“user id=xxx;password=xxxt;Data Source=xxx;Database=XXX_Core”/>

<add name=“master” connectionString=“user id=xxx;password=xxxt;Data Source=xxxx;Database=XXX_Master”/>

<add name=“web” connectionString=“user id=xx;password=xxx;Data Source=xxx;Database=XXX_Web”/>

</connectionStrings>

You must add one more connection string called CT3Translation for the Connector database. This is the name of the database from above:

<add name=“CT3Translation” connectionString=“user id=xxx;password=xxx;Data Source=xxx;Database= CT3Translation “/>

Note: Do not use any name other than CT3Translation for the connection string.

The User ID, password, and Data Source values are usually the same as those used for the other connection strings.

Note: The user specified in the connection string must have permission to modify the table structure in the database. This user must have permission to run ALTER TABLE statements.

3 - Setting Up an Oracle-Based Translation Database

This section describes how to set up an Oracle database to use with the Connector. For information on database size requirements, see Translation Database Size Requirements.

Recommendation: Create a separate Oracle database user for Content API data. Alternatively, you can use an existing Oracle database user for Content API data.

  1. Optional. Create a Oracle database user for Content API data, using SQL statements similar to the following:

CREATE USER ctttrans IDENTIFIED BY xxxxxxxx 

DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp; 

GRANT UNLIMITED TABLESPACE TO ctttrans;

GRANT CONNECT, CREATE TABLE TO ctttrans;

  1. Add a CT3Translation.Oracle connection to the Sitecore connection string configuration. Add the following to the Sitecore connection string configuration:

<add name=“CT3Translation.Oracle” connectionString=“user id=ctttrans;password=xxxxxxxx;Data Source=XE”/>

Depending on the active configuration in the user’s setup, this is one of the following:

  • Website/App_Config/ConnectionStrings.config
  • Website/App_Config/ConnectionStringsOracle.config

Note: The user specified in the connection string must have permission to modify the table structure in the database. This user must have permission to run ALTER TABLE statements.

  1. Ensure that the right version of Oracle.DataAccess.dll is in the Website/bin directory or in the right path. The DLL should match the Oracle database that the user is using. If the user is already using Oracle as the database for the Sitecore content, this should already be set up correctly.

4 - Setting Up a Microsoft Azure SQL-Based Translation Database

This section describes how to set up a Microsoft Azure SQL database to use with the Connector. For information on database size requirements, see Translation Database Size Requirements.

  1. Create an empty Azure database. For detailed instructions, refer to the Microsoft Azure documentation.

Recommendation: Name the new database CT3Translation.

Note: Set your default database collation to SQL_Latin1_General_CP1_CI_AS.

  1. Configure the Connector database connection string. The Website_root/App_Config/ConnectionStrings.config file defines the database connections.

Important: The database part of the connection string must match the database name you created in the previous step.

Typically, it should be:

<?xml version=“1.0” encoding=“utf-8”?>

<connectionStrings>

<add name=“core” connectionString=“user id=xxx;password=xxxt;Data Source=xxx;Database=XXX_Core”/>

<add name=“master” connectionString=“user id=xxx;password=xxxt;Data Source=xxxx;Database=XXX_Master”/>

<add name=“web” connectionString=“user id=xx;password=xxx;Data Source=xxx;Database=XXX_Web”/>

</connectionStrings>

You must add one more connection string called CT3Translation for the Connector database. This is the name of the database from above:

<add name=“CT3Translation” connectionString=“Data Source=tcp:SERVER.database.windows.net;Initial Catalog=DB_NAME;Integrated Security=False;User ID=USER_NAME@SERVER;Password=PASSWORD;Encrypt=True”/>

For example:

<add name=“CT3Translation” connectionString=“Data Source=tcp:mpr0fb9mzh.database.windows.net;Initial Catalog=CTT;Integrated Security=False;User ID=CTT@mpr0fb9mzh;Password=csct@blet99;Encrypt=True”/>

Note: Do not use any name other than CT3Translation for the connection string.

The User ID, Password, and Data Source values are usually the same as those used for the other connection strings.

Note: The user specified in the connection string must have permission to modify the table structure in the database. This user must have permission to run ALTER TABLE statements.

5 - Configuring Database Settings

You configure the Connector’s database settings by modifying the following configuration file: Website_root/Website/App_Config/Include/CT3Translation.config. You can specify the following settings:

Setting Name Description Supported Values Default Value
ClayTablet.
Translation
Database
The location of your Sitecore content. If your Sitecore content is not in the master database, then you must change this value to match the name of your content database. a database name master
ClayTablet.
Backup
TranslationData
Determines whether or not the Connector stores backup translation data on the Content Editor server to support the Translation Correction and Update Remote TM features. For descriptions of these features, refer to the Lionbridge Connector for Sitecore User Guide. If you do not want to use these features, you can change this setting to False. This prevents substantial amounts of data from being stored on your Sitecore server, but it also prevents your company from accessing these useful features.

Recommendation: Initially keep the default setting of True in case you want to use any of the features that rely on this data.
* True
* False
True