...
In contrast to the OSGi plugin tia Proxy, which is a real archive link proxy, the described functionality just acting like a proxy while it is embedded inside the tia core and configures to content store backends.
The proxy plugin is used , when a customer had in a past a kgs classic content server in the past or is using uses a classic content server in parallel.
tia core is able to interact with storages former configured for kgs classic content server.
| Inc drawio | ||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The picture abobe depicts the situation.
let us give you an example:
Before, the customer had a classic CS 5 connected with e.g. an FS filesystem storage.
Then he could replace the classic CS using tia core with the backend kgsstore and the specific shape SAPHTTPtia core archivelink (saphttp). It act like an archive link CS but using the tia core. (AD)
The config of SAPHttp prox config for archivelink (saphttp) can be used with the shape CMISApp tia core CMIS interface as well. Then he could access via CMIS the old AL data.
A typical proxy sceenario it depicted is shown in the picture on topabove. The customer uses the tia CMIS interface, the proxy configuration uses e.g azure blob storage as primary and kgsstore as secondary. Now he can archive via CMIS zu into a new storage like SFS or Azure for example azure blob storage (primary) and access legacy data (read only) via secondary and kgs store.
...
The content server type is now proxy, now.
Please respect, that the meta services are effected, as well.
...