This documentation is for WSO2 Enterprise Integrator version 6.5.0 . View documentation for the latest release in the 6.x.x family and the latest release in the 7.x.x family.

All docs This doc

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



Note the following when adding these configurations:

  • The existing dbConfig called wso2registry must not be removed.
  • The datasource you specify in the <dbConfig name="sharedregistry"> tag must match the JNDI Config name you specify in the <EI_HOME>/conf/datasources/master-datasources.xml file.
  • The registry mount path denotes the type of registry. For example, ”/_system/config” refers to configuration Registry, and "/_system/governance" refers to the governance registry.

  • The <dbconfig> entry enables you to identify the datasource you configured in the <EI_HOME>/conf/datasources/master-datasources.xml file. The unique name "sharedregistry" refers to that datasource entry.

  • The <remoteInstance> section refers to an external registry mount. Specify the read-only/read-write nature of this instance, caching configurations and the registry root location in this section.
  • Also, specify the cache ID in the <remoteInstance> section. This enables caching to function properly in the clustered environment.


    Cache ID is the same as the JDBC connection URL of the registry database. This value is the Cache ID of the remote instance. It should be in the format of [email protected]$database_url, where $database_username is the username of the remote instance database and $database_url is the remote instance database URL. This cacheID denotes the enabled cache. In this case, the database it should connect to is REGISTRY_DB, which is the database shared across all the nodes. You can find that in the mounting configurations of the same datasource that is being used.

  • Define a unique name in the <id> tag instance ID for each remote instance . This is then referred to from mount configurations. In the above (using the <id> tag). Be sure to refer to the same instance ID from the corresponding mount configurations (using the <instanceId> tag). In this example, the unique ID for the remote instance is "instanceId". This same ID as used as the instance ID for the config mount as well as the governance mount.


    Note that registry mounting will not be successful if the registry mount configuration (specified using the <mount> section) does not have a corresponding remote registry instance (specified using the <remoteInstance> section) with the same instance ID. If you have used mismatching instance IDs under the <remoteInstance> and <mount> configurations by mistake, you need to follow the steps given below to rectify the error:

    1. Delete the existing local registry.
      If you are using a database other than the embedded H2, you need to perform the addition step of setting up a new database.

    2. Apply the configurations in the registry.xml file.

    3. Restart the server.
  • Specify the actual mount path and target mount path in each of the mounting configurations. The target path can be any meaningful name. In this instance, it is "/_system/eiconfig".