...
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. |
type |
-
- Set the type to ws.
cacheId
...
- The identifier used in computing cache keys.
You can attach more
More than one remote instance can be attached to a given WSO2 product by adding the relevant configuration details as seen above. Provide each 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
...
be https://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
...
be https://10.20.30.40:9445/webcontext/registry .
The cache id is an optional parameter and should be used 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 would be, wso2carbon@jdbc:h2:repository/database/WSO2CARBON_DB .
...
| title | Note |
|---|
You cannot mount the same server as a remote instance to itself.
Mount Configurations
Following is an example configuration of a mount.
| Code Block | ||
|---|---|---|
| ||
<mount path="/_system/config" overwrite="true|false|virtual">
<instanceId>instanceId</instanceId>
<targetPath>/_system/nodes</targetPath>
</mount> |
Elements of the configuration are explained below.
...
Once a remote instance has been defined a collection on the remote registry can be mounted to the local instance.
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.
instanceId
...
- Remote instance id.
targetPath
...
- The path on the remote registry.
Once you have defined a remote instance, a collection on the remote registry can be mounted to the local instance.
...
| title | Note |
|---|
Here is an example configuration of a mount.
<mount path="/_system/config" overwrite="true|false|virtual"> <instanceId>instanceId</instanceId> <targetPath>/_system/nodes</targetPath> </mount>
It is recommended to refrain from mounting a target path under "/_system/governance" of a remote registry to path "/_system/config". Similarly, 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".
...
| language | html/xml |
|---|
...
<mount path="/_system/config"
...
overwrite="true">
...
<instanceId>instanceId</instanceId>
...
<targetPath>/_system/governance/mounting/config</targetPath>
...
</mount>
...
<mount
...
path="/_system/config"
...
overwrite="true">
...
<instanceId>instanceId</instanceId>
...
<targetPath>/_system/governance/mounting/governance</targetPath>
...
</mount>
Enable Clustering
To enable clustering for a node, the enable attribute of the configuration in $GREG_HOME/repository/conf/axis2/axis2.xml file should should be set to true as follows:
...
<clustering
...
class="org.apache.axis2.clustering.tribes.TribesClusteringAgent"
...
enable="true">
This configuration is responsible for the initialization of a node in the cluster and getting it this node to join the cluster.
Description of remote instance and mount configuration details.