...
Atom-Based Remote Instance Configuration
| Infowarning | ||
|---|---|---|
| ||
The Atom-based remote instance configuration is not recommended for use in a production deployment as it does not support transactions. |
...
| Info | ||
|---|---|---|
| ||
| You cannot mount the same server as a remote instance to itself. |
Mount Configurations
Once a remote instance has been defined a collection on the remote registry can be mounted to the local instance.
path - 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.
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. |
Here is an example configuration of a mount.
<mount path="/_system/config" overwrite="true|false|virtual"> <instanceId>instanceId</instanceId> <targetPath>/_system/nodes</targetPath> </mount>
Once you have defined a remote instance, a collection on the remote registry can be mounted to the local instance.
| Info | ||
|---|---|---|
| ||
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". |
...
|
...
...
Enable Clustering
To enable clustering for a node, the enable attribute of the configuration in $GREG_HOME/repository/conf/axis2/axis2.xml should file should be set to true as follows:
| Code Block | ||
|---|---|---|
| ||
<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 this node it to join the cluster.
...
.
...