...
| Code Block | ||
|---|---|---|
| ||
<remoteInstance url="https://host:port/registry">
<id>instanceId</id>
<dbConfig>h2-db</dbConfig>
<readOnly>false</readOnly>
<registryRoot>/</registryRoot>
</remoteInstance> |
Elements of the configuration are explained below.
url | The URL of the remote instance. |
|---|---|
id | Remote instance id. |
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. |
| Info | |
|---|---|
|
...
| |
For specific configuration details on mounting a remote WSO2 Governance Registry (G-Reg) instance using the JDBC-based configuration model, refer to Sharing Registry Space Among Multiple Products. |
Atom-Based Remote Instance Configuration
| Info | ||
|---|---|---|
| ||
The Atom-based remote instance configuration is not recommended for use in a production deployment as it does not support transactions. |
Following is an example configuration of a remote instance.
| Code Block | ||
|---|---|---|
|
...
<remoteInstance url="https://host:port/registry">
<id>instanceId</id>
<username>username</username>
<password>password</password>
</remoteInstance> |
Elements of the configuration are explained below.
url | The URL of the remote instance. |
|---|---|
id |
...
| Remote instance id. | |
username |
...
| Username of the remote registry login. | |
password |
...
| Password of the remote registry login. | |
cacheId |
...
| The identifier used in computing cache keys. |
Below is an example configuration of a remote instance.
<remoteInstance url="https://host:port/registry"> <id>instanceId</id> <username>username</username> <password>password</password> </remoteInstance>
More You can attach more than one remote instance can be attached to a given WSO2 product by adding the relevant configuration details as seen above. Each Provide each remote instance must be given an identifier along with valid credentials that have sufficient privileges to perform the desired registry operations (requires at least read-privileges to the registry along with permission to log-in to the server). The URL of the remote instance can be deduced as follows:
- 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.
The cache id is an optional parameter and should be used . Use it only if multi-node replicated caching is enabled. The cache id should be in the format of databaseUser@databaseURL. For example, the cache id for a remote instance running with the default embedded H2 database will should be wso2carbon@jdbc:h2:repository/database/WSO2CARBON_DB.
| Info | ||
|---|---|---|
| ||
| You cannot mount the same server as a remote instance to itself. |
WebService-Based Remote Instance Configuration
| Info | ||
|---|---|---|
| ||
| The WebService-based configuration is not recommended for use in a production deployment as it does not support transactions. |
Following is an example configuration of a remote instance.
| Code Block | ||
|---|---|---|
| ||
<remoteInstance url="https://host:port/registry"> <id>instanceId</id> <username>username</username> <password>password</password> <type>ws</type> </remoteInstance> |
url - The URL of the remote instance.
...
cacheId - The identifier used in computing cache keys.
Below is an example configuration of a remote instance.
<remoteInstance url="https://host:port/registry"> <id>instanceId</id> <username>username</username> <password>password</password> <type>ws</type> </remoteInstance>
More than one remote instance can be attached to a given WSO2 product by adding the relevant configuration details as seen above. Each remote instance must be given an identifier along with valid credentials that have sufficient privileges to perform the desired registry operations (requires at least read-privileges to the registry along with permission to log-in to the server). The URL of the remote instance can be deduced as follows:
...