1. Integrating and Extending Oracle Content Management
  2. Developing Oracle Content Management Extensions
  3. Develop Translation Connectors for Language Service Providers
  4. Register Multiple Lingotek Connectors

Register Multiple Lingotek Connectors

You can register and enable multiple Lingotek language service provider (LSP) translation connectors in an Oracle Content Management instance.

Configuration of a Lingotek translation connector requires values for three additional fields:

  • Bearer Token: The sign-in for your Lingotek account. You can use the same bearer token for all of your Lingotek connectors or specify a different one for a connector.
  • Community: The community to use for your translation projects. The default is Oracle.
  • Workflow: The workflow profile to use for your Lingotek translation projects. The default is Machine Translation.

You can change any of these values. Use the Additional Data fields to define optional attributes of the connector.


This image shows the additional fields for configuring a Lingotek translation connector.

To create a translation job for an asset, you can select the asset in a repository and then choose Translate from the drop-down menu to open the Create Translation Job dialog.


This image shows the Create Translation Job dialog with the Lingotek Post-Edit translation connector selected.

The Workflow field shows workflows that you can use for your translation jobs. You can specify a workflow for a connector on the Additional Fields page when you create the connector.


This image shows the workflow options that you choose for a translation job.

The Translation Jobs page, under Assets, shows the status of jobs you have running on your Lingotek translation connectors.


This image shows the translation jobs running on your Lingotek connectors.

If the workflow is different than Machine Translation, a translator edits or finishes the job, and you will need to approve each of the translator's changes before the job is 100% complete.