Localization Framework Hub and Spoke architecture

  • Release version: Zurich
  • Updated June 10, 2026
  • 2 minutes to read
    • 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 a centralized translation fulfillment model within ServiceNow instances. Instead of each instance handling its own translation requests, one designatedhubinstance manages all translation requests submitted by multiplespokeinstances. This setup is ideal when you want to restrict translation fulfillers' access to a single instance, improving control and security.

    Show full answer Show less

    Key Features

    • Hub instance: Receives translation requests from spoke instances, manages fulfillment (including integration with Translation Management Systems - TMS), and returns translated content to spokes.
    • Spoke instances: Submit translation requests to the hub and receive completed translations without direct TMS interaction.
    • Two-step translation process: 1) Spoke submits request to hub; 2) Hub manages fulfillment and returns translated content.
    • Plugin-based setup: Install the Localization Framework Hub plugin on the hub instance and the Localization Framework Spoke plugin on each spoke instance.
    • Configurable translation preferences: Hub and spoke instances offer settings to specify TMS details, workflow preferences, and optional project preferences to control translation tasks.
    • TMS integration: The hub interfaces with your organization’s chosen TMS, while spokes treat the hub as their TMS endpoint.
    • Security and authentication: Connection and credential aliases allow configuring secure communication between spoke and hub instances.

    How to Set Up

    1. Install plugins: Use the admin role to install Localization Framework Hub [com.sn.localizationframework.hub] on the hub instance and Localization Framework Spoke [com.sn.localizationframework.spoke] on spoke instances.

    2. Configure the hub: Using the admin or localizationadmin role, define spoke settings (unique names), specify the TMS service, and set workflow and optional project preferences under Localization Framework > Hub > Spoke Settings.

    3. Configure each spoke: Enable TMS and select “Localization Framework Hub” as the TMS. Reference the hub’s spoke settings name and configure connection credentials pointing to the hub instance URL.

    Practical Benefits for ServiceNow Customers

    • Centralized translation management: Simplifies administration by centralizing translation tasks and TMS integration on one hub instance.
    • Improved security: Limits access for translation fulfillers to a single, controlled hub instance.
    • Scalability: Supports multiple spoke instances submitting translation requests concurrently to a single hub.
    • Flexible workflows and project management: Customize workflow preferences and project task breakdowns per your organizational translation needs.

    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:
    1. The spoke instance submits a translation request to the hub instance.
    2. 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.
    Consider the Localization Framework Hub and Spoke architecture when you want to limit fulfillers' access to one instance only.
    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:
    1. Navigate to Localization Framework > Hub > Spoke Settings.
    2. In the Name field, enter a unique name for each entry.
    3. In the tab for Translation Preferences, find the Translation Management System (TMS) section. Enter the TMS service your organization uses.
    4. In the tab Workflow Preferences, configure according to your requirements. Depending on the workflow you choose, different subfields are populated.
    5. 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:
    1. Navigate to the Settings All Artifacts table [sn_lf_setting].
    2. 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.
    3. Navigate to the Connection & Credential Aliases table. Find and open the record named Localization Framework Hub TMS.
    4. 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.
    From the perspective of the spoke instance, the hub acts as a TMS. The application scope for the Hub and Spoke architecture is Localization Framework Hub.