Localization Framework Hub and Spoke architecture

  • Release version: Australia
  • 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 ServiceNow customers to centralize translation request fulfillment across multiple instances. Instead of handling translations independently, a designatedhubinstance receives translation requests from otherspokeinstances, manages these requests—such as interfacing with a translation management system (TMS)—and returns the translated content to the requesting spokes. This model is especially useful when you want to restrict the translation fulfillment process to a single controlled instance.

    Show full answer Show less

    Key Features

    • Centralized Translation Fulfillment: The hub instance manages all translation requests, acting as a translation management system for spoke instances.
    • Two-step Translation Process: Spokes submit requests to the hub, which processes and returns translated content.
    • Plugin-based Setup: Requires installation of Localization Framework Hub plugin on the hub instance and Localization Framework Spoke plugin on each spoke instance.
    • Configurable Preferences: Hub instance allows configuration of translation workflow, project preferences, and integration with your organization’s TMS.
    • Spoke Configuration: Spoke instances are set to use the hub as their TMS, linking via connection and credential aliases with appropriate authentication.
    • Optional Project Preferences: Hub can split multi-language translation requests into separate tasks per language if no project is specified.
    • Machine Translation: Available only if Dynamic Translation is installed on the hub instance.

    Implementation Steps

    • Install Plugins: Admin role installs the Hub plugin on the central instance and Spoke plugins on other instances.
    • Configure Hub: Use admin or localizationadmin role to define unique spoke settings and specify TMS and workflow options.
    • Configure Spokes: Enable TMS pointing to the hub, specify the spokeSettingsName to match hub configuration, and set connection details including URL and authentication.

    Key Outcomes

    By implementing the Hub and Spoke architecture, ServiceNow customers can:

    • Streamline translation workflows by centralizing translation request fulfillment.
    • Limit translation fulfillers’ access to a single instance, enhancing security and control.
    • Maintain consistent translation management practices across multiple instances.
    • Integrate 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:
    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.