/
Historical Documents (WS)
Historical Documents (WS)
The Webservice contains the proxy logic for re-routing “read” and “get” requests to a historical repository or to a historical content server. Below are few Sample Configurations.
Scenario A: The historical and new repositories are located on the same Content Server, but have different content repository Ids.
| Configuration for scenario A |
|
---|---|---|
|
|
Scenario B: The historical and new repositories are located on different Content Servers, but have the same content repository Id.
| Configuration for scenario B |
|
---|---|---|
|
|
Scenario C: The historical and new repositories are located on different Content Servers and have different content repository Ids.
| Configuration for scenario B |
|
---|---|---|
|
|
Related content
Common (WS)
Common (WS)
More like this
Content Service
Content Service
More like this
WebService API (WS)
WebService API (WS)
More like this
Repository-Connection (MIG)
Repository-Connection (MIG)
More like this
REST examples (Browser Binding)
REST examples (Browser Binding)
More like this
kgsstore
kgsstore
More like this