Recently, I had the opportunity to install, configure and integrate Sitecore Claytablet Translation Connector (as known as CT3) for implementing a multilingual solution to one of our Sitecore CMS integrated client projects. In this article, I am going to refer to CT3 as opposed to using its long usual name. I realised that there aren’t many blogs out there which provide basic installation steps to get the CT3 Connector going along. I decided to put together a short blog of a step by step guide of preinstallation requirements. But before I dive into it, a quick nutshell of the CT3 Connector. This is the connector which Claytablet has developed to connect the Sitecore CMS to provide connectivity to the Claytablet Platform which is used to receive and route content from the cms to Translation providers and back. We can think of the connector as the bridge sitting between Sitecore cms and Claytablet.
Firstly, you will need the list of things below.
1. Obtain the CT3 Translation account license keys from Clay Tablet. This is usually one license key per translation provider. The license key comes in a .xml file such as source.xml. A target.xml file is supplied from Clay Tablet to indicate Clay Tablet platform as the destination where content will be sent to. You need not modify any of the source and target.xml.
Note: You cannot duplicate the license keys on two ore more difference environments. Doing so will cause unexpected behaviour with the CT3 connector resulting in lost translated content from the translator providers, orphaned projects etc.
2. Obtain the CT3 Installer package from Clay Tablet. This will be a Sitecore installation package (.zip file) which you will need to install via the Installation Wizard. Don’t do this step yet as we have not reached the installation stage.
3. Obtain the CT3 Database zip file from Clay Tabelt which includes the “CT3Translation.mdf” and “CT3Translation_log.mdf”. You will need to attach the CT3 databases on the same database server where your Sitecore (web, master and core) database are located. Make sure the CT3 database is online.
4. Configure the CT3 Database connection string:
You need to add one more connection string called “CT3Translation” (don’t use any
other name) for the CT3 Database:
The “User ID”, “password” and “Data Source” are usually same as used for the
other connection strings.
“Database= CT3Translation” where “CT3Translation” is the name of CT3 database from
5. Prepare the required folders and setup permissions. You will need to create a folder called “CT3” (recommend you use case sensitive) and then create two sub folders called “Accounts” and “data” in that newly created “CT3” folder. You will need to then setup security permissions on “CT3/Accounts” with Windows Account and IIS read permissions, and Full permissions on “CT3/Data” folders. Place the two Account License Keys from Clay Tablet into “CT3/Accounts”.
Note: The CT3 folder must be placed under the Sitecore Data Folder (not the Sitecore website root folder). You can check your web.config file and search this line.
<sc.variable name=”dataFolder” value=”/App_Data” />
6. Install the pckage using the “Installation Wizard” under “Development Tools” on the Sitecore Desktop. You will need to have Administrator privileges to perform the installation. Wait the installation to complete. I recommend using Internet Explorer to perform package installations. According to the Sitecore Claytable installation document, the package will install one important file called CT3_LanguagesCodes.txt. If you do not see this file (which I experienced before), do not be alarmed. You can simply open up the package.zip file and then copy out that .txt file.
For info, the CT3_LanguagesCodes.txt file shows all valid region language code that are only valid for Sitecore ClayTablet to work. This may be used as reference in the configuration step.
7. Once installed, you will see the following new tab “CT3Translation” in the ribbon bar in Sitecore Content Editor.
But hold your horses, we are not done yet with 20 percent more to go. We will need to further perform a few parameter configurations.
In my next upcoming part 2 article, I will talk about parameter configurations and CT3 workflows.