Multi-DC Sync  for Custom Connections

Early Access
This feature is not enabled for all users. If you’d like to try it out, please email our support team for early access.

1. This feature is supported only for Zoho Projects service extensions.                                                
   
2. Once access is enabled, you can follow the steps outlined in this guide.

To support Multi-DC sync for extensions with custom connections, the dcConnectors key is introduced in the plugin-manifest.json. This configuration ensures that extensions created in the Primary Data Center (DC) are synced to the DCs specified in dcConnectors while publishing extension with connections.

How to Configure  

1. Create Connections in the Primary DC   

• Create all the required custom connections in the Primary DC from the Connections page.

• Refer to Sigma Connections documentation for detailed steps on creating connections.  

2. Get the Connection Details   

• After publishing the connection, a connection JSON will be available under the Sample Code section.

• This JSON contains the required details (such as connection link name) needed for configuration.

3. Update the Plugin Manifest   

Format:

{
  "dcConnectors":{
      "{DCType}":{
         "{sharedBy}":[
            "{connectionLinkName1}",
            "{connectionLinkName2}",
            "etc"
         ] 
      },
      "{DCtype}":{
        "{sharedBy}":[
          {
            "actualConnectionName":"aliasConnectionName"
          },
          "etc"
        ]
      }
  }
}

Sample plugin-manifest.json format for Dc connector

Alias Connection Name Mapping   

Configuration Steps  

1. Create the required custom connection for each DC using the DC-specific configurations (e.g., auth URL).

2. Assign a DC-specific connection name for each DC.

3. Map the DC-specific connection to a common alias in dcConnectors

{
  "dcConnectors":{
      "US":{
         "57294746":[
            "google_drive",
            "projects_conn"
         ]
      },
      "EU":{
         "57294746":[
          {
            "projects_eu_conn":"projects_conn"
          },
          "google_drive"
        ]
      }
  }
}

In this example:

• projects_conn is the common alias
  

• projects_eu_conn is the EU-specific connection

• The extension continues to use projects_conn across all DCs
  

4. Add All Required DC Keys   

Before publishing, manually add all required DC keys in the dcConnectors object.

Supported DC Keys  

US, EU, AU, IN, JP, UAE, CN, CA, SA, UK

If a DC key is not included in the dcConnectors object:

• A notification will be displayed during publishing                                                                                            

• Skipped DCs will be listed

• The extension will not be synced to those DCs.
  

Adding a New DC   

When a new DC is introduced:

1. Add the new DC key under dcConnectors.

2. Provide the connection mappings in the same format.

3. Republish the extension.

Migrating from Existing Connectors to DC Connectors   

• In a DC Connector-enabled workspace: When an extension is run or published, existing entries under the connectors key are automatically converted into dcConnectors for the current DC

• For Multi-DC Sync  : Developers must manually add all required DC keys in dcConnectors before publishing to ensure proper synchronization