3.2. Configuration¶
3.2.1. Various Replicator services¶
Both services run in the same server.
3.2.1.1. Local Replicator¶
It’s role is to be contacted by local services to interact with remote services. - Through API for remote access, it proxies the request from Accessor Services (Accessor Public Service or Accessor Replicator Service) to the remote Replicator (remote site). - Through topic for Replication Requests, which are sent to remote replicator service through API.
So its role is to handle outgoing requests.
3.2.1.2. Remote Replicator¶
It’s role is to handle remote requests: - Remote access through API goes to Accessor Internal Local service - Remote Replication Request are pushed into topic for Replication Actions. Those are handle then by the Accessor Replicator Local service.
So its role is to handle incoming requests.
3.2.2. application.yaml configuration¶
Property/Yaml property or Environment variable |
Possible Values |
Default Value |
---|---|---|
|
Http(s) url of the service |
|
Redefining |
Name of the outgoing topic for Replication Requests |
|
Property/Yaml property or Environment variable |
Possible Values |
Default Value |
---|---|---|
|
Name of the site |
|
|
|
|
Redefining |
Name of the outgoing topic for Action Requests |
|
Redefining |
Name of the incoming and outgoing topic for Replication Requests (if more than 1 instance, add broadcast=true to the incoming configuration) |
|
|
Http(s) url of the service |
|
|
Http(s) url of the service |
|
|
Http(s) url of the remote service |
|
|
Http(s) url of the service |