...
| Code Block | ||
|---|---|---|
| ||
<remoteInstance url="https://host:port/registry"> <id>instanceId< <id>instanceId</id> <username>username< <username>username</username> <password>password< <password>password</password> <type>ws< <type>ws</type> </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. | |
type |
...
| Set the type to ws. | |
cacheId |
...
| The identifier used in computing cache keys. |
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
...
- 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
...
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 would will be, wso2carbon@jdbc:h2:repository/database/WSO2CARBON_DB.
| 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.
...