You are here: Installation and Configuration Guides > Connector for Sitecore > Configuring the Lionbridge Connector for Sitecore

Configuring the Lionbridge Connector for Sitecore

You perform the following steps to configure your Connector installation:

  1. Configuring Your License ID and New Translation Providers. In a new Connector installation, you must enter your license ID and configure one or more translation providers.
  2. Upgrading Account Keys for Current Translation Providers. Required if you are upgrading the Connector from version 3.x to version 4.x.
  3. Configuring Content Encryption. Optional.
  4. Importing Content into a Local Translation Memory (TM). Required if you have a new Connector installation and you want to leverage previously translated content from your website.
  5. Configuring the Connector to Run in a Clustered Environment of Multiple Load-Balanced Sitecore Servers. Required only if you are using the Connector in a clustered environment of multiple load-balanced Sitecore servers.
  6. Configuring Network Settings for a Firewall. Optional.
  7. Configuring Global Translation Settings.
  8. Configuring fields in items that need translation. You do this in the Bulk Translation section of /sitecore/system/Settings/Lionbridge Settings/Lionbridge Connector Settings/ in the content tree, in the Content Editor. For detailed instructions, see Configuring Bulk Translation Settings in Sitecore.
  9. Configuring the Upload and Download Scheduled Tasks. Optional.
  10. Configuring the Sitecore Languages in the Sitecore Content Editor.
  11. Configuring the Translation Workflow.
  12. Filtering Fields in Items that Do Not Need Translation.
  13. Adding Purchase Order Numbers and Descriptions. Optional.
  14. Configuring Connector Roles and Adding Users.
  15. Configuring Team Profiles. Optional.
  16. Configuring How the Connector Handles Special Characters. Optional.
  17. Configuring the Behavior of the Send Dependent Items Check Box. Optional.
  18. Configuring the In-Context Preview Feature.

Important: This feature is currently in alpha testing. It is not currently generally available for production usage.