KantanMT v2.1 Connector

From Okapi Framework
Jump to: navigation, search

Overview

Starting in M36, the commercial KantanMT v2.1 service can be accessed via API, which is documented at http://docs.kantanmt.apiary.io. This connector replaces the now deprecated previous connector: KantanMT Connector.

The connector assumes that the specified KantanMT engine is running, which is not always the case. Users must start the the appropriate engine prior to using the connector, either via the KantanMT dashboard or using the API (for example, with curl.)

Note that the connector provides extra methods that allow you to list, query, start and stop engines:

  • getEngines
  • getEngineStatus
  • startEngine
  • stopEngineEngine


Using the Connector

In Rainbow, the connector can be accessed through the Leveraging Step. It can also be called programmatically.

Parameters

KantanMT Authorization Token (internal name: apiToken) — the authorization token. (Sample value: "ABCdef123467")

Engine name (internal name: engine) — the identifier of the engine to use. (Sample value: "Test-EN-DE")

Alias name (internal name: alias) — the identifier of the alias to use. (Sample value: "myMT")

Either the engine or the alias parameter must be set. If both are set, the engine parameter takes precedence and the alias parameter is ignored.

Limitations

  • The connector assumes that the specified KantanMT engine is running, which is not always the case. Users must start the the appropriate engine prior to using the connector, either via the KantanMT dashboard or using the API (for example, with curl.)