---
sourceDocument: Yokohama Impact
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/impact

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Impact

ft:clusterId :

    - ipact

bundleId :

    - ipact


---

# Configure the Multi-Instance Framework for Proactive Code Check

# Configure the Multi-Instance Framework for Proactive Code Check {#ariaid-title1}

* Release version: Yokohama
* 
* Updated April 24, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Configuring the Multi-Instance Framework explains how to connect data movement from non-production instances to production instances. The mTLS must be installed and configured to connect non-production instances to production
instances to allow data movement and synchronization. Before creating trust profiles, managing instances must also be configured.

## About this task

The following tasks summarize the steps required to install and configure the Multi-Instance Framework for Proactive Code Check.

* Submit a   Now Support ticket to enable ADCv2 mTLS, if not enabled.
* Submit a  Now Support ticket to install the Multi-Instance Framework mTLS (com.glide.mif.mtls) plugin.
* Log in to non-production instances and add required fields.
* Edit and create required trust profiles in the production instance.
* Sync the trust profiles to non-production instances.
{#configure-multi-instance-framework-proactive-code-review__ul_tz1_q5d_cfc}

## Before you begin

ADCv2 mTLS is required alongside the Multi-instance Framework mTLS (com.glide.mif.mtls) plugin for data sync to function correctly. See [Cross-instance application trust configuration](https://www.servicenow.com/docs/access?context=grant-access-v2&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) for additional information on multi-instance management.  
Important:  
Identify the primary production instance and all secondary instances where Impact Proactive Code Check will be used. The primary instance displays a consolidated view of non-production instance scan results.

Role required: admin

## Procedure

1. Verify if the instance has ADCv2 mTLS enabled by accessing the URL: \<instance\>.service-now.com/adcv2/supports_tls  

   | Value | Action |
   | True | Proceed to the next step. |
   | If not True | Submit a ticket to enable ADCv2 mTLS. Verify that ADCv2 mTLS has been enabled and then proceed to the next step. |
   |-|-|

   {#configure-multi-instance-framework-proactive-code-review__choicetable_qkk_g5d_j2c} {#configure-multi-instance-framework-proactive-code-review__mTLS-enabled-verification-step}
{#configure-multi-instance-framework-proactive-code-review__mTLS-enabled-verification-step}
2. Submit a  Now Support ticket to install the com.glide.mif.mtls plugin.
3. Wait for 24 hours after the com.glide.mif.mtls plugin is installed.
4. Repeat steps 1 to 3 on all of the required production and non-production instances.
5. Log in to a non-production development instance with the role admin.  
   Note:  
   Steps 5 - 7 are required for each non-production instance.
6. Navigate to AllMulti-Instance ManagementManager Instances.  
7. Create a record with the following values:  
   {#configure-multi-instance-framework-proactive-code-review__table_cmy_vyd_j2c__entry__2}

   | Field | Value |
   |-|-|
   | Application | Impact Health |
   | Manager Instance | \<primary production instance\> |
   [ ]

   {#configure-multi-instance-framework-proactive-code-review__table_cmy_vyd_j2c}
8. Log in to the primary production instance as admin.
9. Navigate to AllMulti-Instance ManagementManaged Instances.
10. Verify that you see a record for each non-production instance for which Production instance is assigned as manager in the previous steps.
11. Navigate to AllMulti-Instance ManagementApplication Trust profiles.
12. Open the record Trust Profile for Impact Health.  
13. Under the Active MIF Trust Profile Items related list, select New.
14. Fill in the fields for the trust profile.  
    {#configure-multi-instance-framework-proactive-code-review__table_k4d_k33_j2c__entry__2}

    | Field | Field Value |
    |-|-|
    | Capability | Proactive Code Check Data Transfer |
    | Application | Impact Health |
    | Application Capability Version | 1.0.0 |
    | Active | true |
    | Trusting Instance | \<non-production instance1\> |
    | Trusted Instance | \<primary production instance\> |
    | Description | Optional |
    [ ]

    {#configure-multi-instance-framework-proactive-code-review__table_k4d_k33_j2c}  
    Note:  
    A trust profile must be completed for each non-production instance to be registered as a Trusting Instance.
15. Navigate to AllMulti-Instance ManagementApplication Trust profiles.
16. Select Sync Trust Profiles.  
17. Navigate to AllMulti-Instance ManagementTrusting Instances.
18. Verify that you see a record for each non-production instance that you added to your trust profile.  
    See [Basic trust configuration for data sync applications](https://www.servicenow.com/docs/access?context=grant-access-other-instances&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) for additional information.

*[\>]: and then