IBM Watson Language Translator Service spoke
Summarize
Summary of IBM Watson Language Translator Service Spoke
The IBM Watson Language Translator Service Spoke has been deprecated, with IBM announcing that the service will be withdrawn entirely by December 10, 2024. Existing users can continue to use the service until its end of support on June 10, 2024. New customers will no longer have access as of June 10, 2023.
Show less
Key Features
- Activation: To use the service, activate the Dynamic Translation plugin (com.glide.dynamictranslation) or the IBM Watson Language Translator Service Spoke plugin (com.glide.ibmtranslationspoke).
- Subscription: Requires a Professional or higher ServiceNow subscription that includes Dynamic Translation.
- Supported API Version: API version v3.
- Spoke Subflows: Provides subflows like Detect Language and Translate Text to facilitate language detection and translation tasks.
- Connection and Credential Management: Uses aliases for managing connection and credential information, simplifying configuration across multiple environments.
Key Outcomes
By following the outlined activation and configuration steps, customers can continue utilizing the IBM Watson Language Translator services until the service is fully withdrawn. It is essential for customers to prepare for this transition and explore alternative translation solutions as the end of support date approaches.
The IBM Watson Language Translator Service Spoke has been deprecated by IBM. This information is provided for legacy context. Customers with existing spoke installations can continue to use the translator service until it is withdrawn by IBM.
Activation
Activate the Dynamic Translation plugin (com.glide.dynamic_translation) or the IBM Watson Language Translator Service Spoke plugin (com.glide.ibm_translation_spoke).
Subscription
This spoke requires any ServiceNow subscription that is Professional or above, and includes Dynamic Translation.
Supported versions
API version v3.
Spoke subflows
The spoke provides subflows in the Published state to integrate with the IBM Watson Language translation services. These subflows can be used as part of other subflows and flows.
| Subflow | Description |
|---|---|
| Detect Language [detect_language_v3] | Contains a set of inputs, actions, and output to detect the language of the input text. |
| Translate Text [translate_text_v3] | Contains a set of inputs, actions, and outputs to translate the input text to multiple languages. |
Spoke actions
The spoke provides actions to integrate with IBM translation services.
| Action | Description |
|---|---|
| Detect Language [detect_language_v3] | Detects the language of the input text. |
| Translate Text [translate_text_v3] | Translates the input text to multiple languages. |
IBM account requirements
For information on the IBM Language Translator API and the notice of deprecation, see the IBM documentation.
Connection and credential alias requirements
IntegrationHub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you do not need to update any actions that use the connection. For more information, see Credentials and connection information.
To use the spoke connection aliases, create an associated connection record and a credential record for each alias.
This spoke uses the IBMTranslation alias (sn_ibm_trans_spoke.IBMTranslation) to authorize actions.
- Connection type: HTTP
- Connection URL: Base URL provided by IBM to connect to the language translator service. Users can have a different URL based on their geographical preference.
Perform the following tasks to connect to the IBM Watson Language translation services and use them to translate the dynamically generated text.