Localization Framework Hub and Spoke architecture

  • Release version: Australia
  • Updated March 12, 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 allows a central instance (hub) to handle translation requests from other instances (spokes). This model streamlines the translation process by enabling spoke instances to submit requests to a designated hub, which then manages and fulfills those requests, including interfacing with a translation management system (TMS). This is particularly useful when you want to restrict access to translation fulfillers to a single instance.

    Show full answer Show less

    Key Features

    • Hub and Spoke Model: Enables centralized management of translation requests.
    • Two-Step Process: Spoke instances send requests to the hub, which fulfills them and returns the translated content.
    • Plugin Installation: Requires installation of the Localization Framework Hub and Spoke plugins to set up the architecture.
    • Configuration Options: Administrators can configure connection settings, TMS preferences, and workflow requirements on both hub and spoke instances.

    Key Outcomes

    By implementing the Hub and Spoke architecture, ServiceNow customers can expect improved efficiency in managing translation requests, enhanced control over translation workflows, and the ability to centralize translation processes while maintaining security by limiting access to a single instance. Proper setup and configuration will enable seamless integration with existing translation management systems.

    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. However, in the Australia release, 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.