WSO2 Carbon-based products support The WSO2 Governance Registry supports the concept of federating the directory structure of the repository across multiple servers. ThereforeThus, the structure of collections does need not necessarily need to exist in be existent on a single instance of the server. You can mount/un-mount each remote registry instance using a configuration, which defines Each remote instance can be mounted and un-mounted by the simple addition of a configuration describing how to connect to it. The WSO2 Governance Registry's Remote Registry API is used to communicate between such remote instances.
The configurations in this page are all found in the registry.xml file which is located in the <PRODUCT_HOME>/repository/conf folder.
In order to mount an external registry, you have to define the remote registry instance. This can could use either the JDBC-based configuration model, the Atom-based configuration model or the WebService-based configuration model.
...
| Code Block | ||
|---|---|---|
| ||
<remoteInstance url="https://host:port/registry">
<id>instanceId</id>
<dbConfig>h2-db</dbConfig>
<readOnly>false</readOnly>
<registryRoot>/</registryRoot>
<enableCache>true</enableCache>
<cacheId>wso2carbon@jdbc:h2:repository/database/WSO2CARBON_DB</cacheId>
</remoteInstance> |
Elements of the configuration are explained below.
url | The URL of the remote instance. |
id | Remote instance idID. |
dbConfig | The database configuration to use, which should not be the currentDBConfig. |
readOnly | Whether the instance is read-only. |
enableCache | Whether caching is enabled for this instance. |
registryRoot | The root of the registry instance. |
cacheID | This is the cache id of the remote instance. Here the cache id should be in the format of $database_username@$database_url, where $database_username is the username of the remote instance database and $database_url is the remote instance database URL. |
| Info | ||
|---|---|---|
| ||
For specific configuration details on mounting a remote WSO2 Governance Registry (G-Reg) instance using the JDBC-based configuration model, refer to see Sharing Registry Space Among Multiple Products. |
Atom-Based Remote Instance Configuration
...
| Code Block | ||
|---|---|---|
| ||
<remoteInstance url="https://host:port/registry"> <id>instanceId< <id>instanceId</id> <username>username<<username>username</username> <password>password<<password>password</password> </remoteInstance> |
Elements of the configuration are explained below.
url | The URL of the remote instance. |
id | Remote instance idiID. |
username | Username of the remote registry login. |
password | Password of the remote registry login. |
cacheId | The identifier used in computing cache keys. |
...
- Let the URL of the destination server be be
https://localhost:9443/services. Then the URL of the remote instance will be behttps://localhost:9443/registry. - Let the URL of the destination server be be
https://10.20.30.40:9445/webcontext/services. Then the URL of the remote instance will be behttps://10.20.30.40:9445/webcontext/registry.
The cache id is an optional parameter. Use it only if multi-node replicated caching is enabled. The cache id should be in the format of of databaseUser@databaseURL. For example, the cache id for a remote instance running with the default embedded H2 database should be be wso2carbon@jdbc:h2:repository/database/WSO2CARBON_DB.
...
Elements of the configuration are explained below.
url | The URL of the remote instance. |
id | Remote instance idID. |
username | Username of the remote registry login. |
password | Password of the remote registry login. |
type | Set the type to ws. |
cacheId | The identifier used in computing cache keys. |
...
- Let the URL of the destination server be
https://localhost:9443/services. Then the URL of the remote instance will behttps://localhost:9443/registry. - Let the URL of the destination server be
https://10.20.30.40:9445/webcontext/services. Then the URL of the remote instance will behttps://10.20.30.40:9445/webcontext/registry.
...
| Code Block | ||
|---|---|---|
| ||
<mount path="/_system/config" overwrite="true|false|virtual"> <instanceId>instanceId< <instanceId>instanceId</instanceId> <targetPath> <targetPath>/_system/nodes</targetPath> </mount> |
Elements of the configuration are explained below.
path | The path to which the mount will be added | to. |
overwrite | Optional. Defines whether an existing collection at the given path will be overwritten or not. This is an optional field. | |
instanceId | Remote instance idID. | |
targetPath | The path on the remote registry. |
...
| Info | |||||
|---|---|---|---|---|---|
| |||||
It is recommended to refrain from mounting a target path under "/_system/governance" of a remote registry to path "/_system/config". Similarly, refrain refrain from mounting a target path under "/_system/config" of a remote registry to path "/_system/governance". Such configurations can produce unpredictable results. For example, with the following mounting configurations, "/_system/governance" will be mounted to the correct path, which is "/_system/governance/mounting/governance" but "/_system/config" will be mounted to " /_system/governance/mounting/governance/ mounting/config".
|
...
To enable clustering for a node, the the enable attribute attribute of the configuration in $GREG_HOMEin <ESB_HOME>/repository/conf/axis2/axis2.xml file file should be set to to true as as follows:
| Code Block | ||
|---|---|---|
| ||
<clustering class="org.wso2.apachecarbon.axis2core.clustering.tribeshazelcast.TribesClusteringAgentHazelcastClusteringAgent" enable="true"> |
This configuration is responsible for the initialization of a node in the cluster and getting it to join the cluster.