tia Viewer Core is only available as Container and can support the container deployment. It supportsthe standalone viewer scenario with kgs customizing in SAP or a so called CSV scenario that is based on ArchiveLink get Commands.
In both cases in addition to the viewer a tia® Content Server ArchiveLink (tC) is required. Each viewer Container supports one tia ContentServer as destination.
When creation of annotations and notes to documents viewed are activated, the tia Viewer
...
requires access to SAP via ABAP REST interface. The annotations will be stored with the document in the content server.
SAP-side customized tia Viewer
In this scenario, the KGS Viewer Pack communicate to the tia Viewer with using a token containing encoded query for to retrieve the document of the content server using ArchiveLink.
SAP-side configuration (transaction /KGS1/VIEWER_CUST) contains the instance information and other customizing: In the tia Viewer Core a repositoryinstancemapping configuration is not required and ignored.
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
tia Viewer
...
in CSV Scenario
In this scenario, the KGS Viewer Pack communicate to the tia Viewer with using ArchiveLink, which retrieves the document from content server.
In this scenario, the repositoryinstancemapping configuration in tia Viewer Core is applied. If it is not configured, the setting for the instance default are applied .
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...