...
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 protocol proxy. It is embeeded in tia embedded in tia core, proxies the archive link request and connects to content store backends.
...
tia core is able to interact with storages former formerly configured for kgs classic content server.
...
By switching to the latest kgs architecture "tia Core - saphttp", the new integrated proxy service has a decisive advantage.
The historical storage configuration of the former “kgsstore” “kgsstore” is still used, which means that no data migration has to take place. At the same time, you address your new storage device (S3, Azure etc.) via tia Core.
It is also possible to access historical ArchiveLink documents via the new proxy service using the newly propagated CMIS interface.
A typical proxy sceenario scenario is designed in the picture above. The customer uses the tia Core CMIS interface, the proxy configuration uses e.g azure blob storage as primary and kgsstore kgs store as secondary storage type.
That means you´re you archive your data via the CMIS Interface in your new storage as your primary device and access legacy data (read only) via secondary and kgs store.
...
For performance reasons you van try to set usefallback = false, but then it can lead to documents that are no longer found. Examples are documents that are decoded only once (on storage like data%37), documents that contains a plus (a+b.pdf is stored as a b.pdf) or documents with wrong encoding (stored like � � �+�.pdf)
Configuration example
...
Excerpt of repository.cfg for proxy configuration of example repository T1.
| Code Block |
|---|
# the repository list for the default repositoryfactory.class repositoryfactory.repositorylist = T1 #---------------------- T1 sample configuration (proxy) ---------------------------------- #===== T1 repository configuration T1.contentservice.type = proxy T1.accessmode = rucd T1.description = T1 Proxy-Repository T1.saphttp.security = 1 T1.authentication.cmis.type = basic T1.authentication.cmis.idprovider = config T1.authentication.cmis.config.login1.user = admin:admin T1.authentication.cmis.config.login1.role = admin T1.configdata.filesystem.root = /temp/meta/ #===== T1 content service configuration (filesystem|azureblobstore|s3blobstore|kgsstore) T1.contentservice.proxy.primary.splitfilesystemv2.root = /temp/tiacore_data/ T1.contentservice.proxy.primary.splitfilesystemv2.contrepinpath = true T1.contentservice.proxy.primary.type = splitfilesystemv2 T1.contentservice.proxy.primary.accessmode = rwrcud T1.contentservice.proxy.secondary.type = kgsstore T1.contentservice.proxy.secondary.accessmode = r T1.contentservice.proxy.secondary.kgsstore.configfile = /temp/proxy/legacy-storage.cfg T1.contentservice.proxy.secondary.kgsstore.context = default T1.metaservice.proxy.secondary.type = kgsstore #===== T1 keystore service configuration (none|pkcs12) T1.keystoreservice.type = pkcs12 T1.keystoreservice.pkcs12.name = tiacore T1.keystoreservice.pkcs12.path = /temp/ #===== T1 meta service configuration (none|elastic|database|kafka) T1.metaservice.type = proxyelastic T1.metaservice.elastic.host = http://elasticsearch:9200 T1.metaservice.elastic.index.write = tiacore-meta T1.metaservice.elastic.index.search = tiacore-meta T1.metaservice.elastic.index.update = tiacore-meta T1.metaservice.elastic.index.delete = tiacore-meta T1.metaservice.elastic.authentication.type = none #===== T1 meta service configuration (none|elastic|database|kafka) T1.protocolservice.type = none |
...