Localization Framework Hub and Spoke architecture
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
Summary of Localization Framework Hub and Spoke architecture
The Localization Framework Hub and Spoke architecture enables ServiceNow customers to centralize translation request fulfillment by designating one instance as a hub and others as spokes. This model supports a two-step translation process where spoke instances submit requests to the hub, which then handles translation fulfillment and returns the translated content. This approach is ideal for organizations wanting to restrict translation fulfillers’ access to a single instance.
Show less
Key Features
- Hub and Spoke Model: Separates translation request submission (spokes) from fulfillment (hub).
- Centralized Translation Management: The hub interacts with translation management systems (TMS) to fulfill requests.
- Plugin-Based Configuration: Requires installation of Localization Framework Hub plugin on the hub instance and Localization Framework Spoke plugin on spoke instances.
- Configurable Translation Preferences: Includes settings for TMS integration, workflow preferences, and optional project preferences to manage translation tasks per language.
- Security and Access Control: Limits fulfillers’ access to a single hub instance while spokes act as clients.
- Hub Appears as TMS to Spokes: From the spoke’s perspective, the hub functions as their translation management system.
Configuration and Setup
- Install Localization Framework Hub [com.sn.localizationframework.hub] plugin on the designated hub instance.
- Install Localization Framework Spoke [com.sn.localizationframework.spoke] plugin on the designated spoke instances.
- On the hub instance, configure spoke connections via Localization Framework > Hub > Spoke Settings:
- Assign unique names to spoke entries.
- Set the organization’s TMS service in Translation Preferences.
- Configure workflow and optional project preferences as needed.
- On each spoke instance:
- Enable TMS and set it to Localization Framework Hub in Translation Preferences.
- Reference the hub connection by name in TMS Additional Info.
- Configure connection credentials to the hub in the Connection & Credential Aliases table.
Practical Benefits for ServiceNow Customers
- Streamlines translation workflows by centralizing fulfillment processes.
- Reduces administrative overhead by maintaining one hub for translation management.
- Improves security by limiting translation fulfillment access to a single controlled instance.
- Supports multi-language translation by optionally breaking requests into language-specific tasks.
- Integrates seamlessly with existing translation management systems through the hub.
Enable one central instance to fulfill translation requests submitted from other instances using the Localization Framework Hub and Spoke architecture. Install optional Localization Framework plugins to configure one of your instances as a hub and other instances as spokes.
By default, translations are requested and fulfilled on the same instance. Alternatively, there is an available hub-spoke model for translation requests and fulfillment. With this architecture translation requests are a two-step process:
- The spoke instance submits a translation request to the hub instance.
- The hub instance manages the fulfillment of the request, such as by sending the content to a translation management system (TMS). The hub returns the translated contents to the spoke instance.
To set up this architecture, use the admin role to install the following plugins:
- Localization Framework Hub [com.sn.localization_framework.hub]. Install this plugin on the instance you designate as a hub.
- Localization Framework Spoke [com.sn.localization_framework.spoke]. Install this plugin on the instances you designate as spokes.
For more information on installation, see Activate Localization Framework.
When both plugins are installed, use the admin or localization_admin role to configure the connection between hub and spoke instances. On the hub instance:
- Navigate to
- In the Name field, enter a unique name for each entry.
- In the tab for Translation Preferences, find the Translation Management System (TMS) section. Enter the TMS service your organization uses.
- In the tab Workflow Preferences, configure according to your requirements. Depending on the workflow you choose, different subfields are populated.
- The tab Project Preferences is optional. If no project is entered, any request for translations into more than one target language is broken into separate tasks, one for each language.
Note:
If Dynamic Translation is not installed, the option for machine translation is not available.
On a spoke instance:
- Navigate to the Settings All Artifacts table [sn_lf_setting].
- In the tab Translation Preferences, find the Translation Management System (TMS) section.
- Enable TMS: select.
- TMS: Set to Localization Framework Hub.
- TMS Additional Info: for spokeSettingsName, enter the name of the connection setting that has been configured on the hub.
- Navigate to the Connection & Credential Aliases table. Find and open the record named Localization Framework Hub TMS.
- Add the connection to the hub in the Connections tab. You can enter the URL to your hub in the Connection URL field. Set authentication and other attributes appropriate to your environment.