tia Viewer Core is only available as 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 and kgs Viewer Pack for SAP are required to display documents archived in a content server from within SAP.
The communication with the content server is ArchiveLink. For more information to tia Content Server Core ArchiveLink see tia® Content Server ArchiveLink (tC) is required. Each viewer Container supports one tia ContentServer as destinationtia Viewer Core container started works with one content server.
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.
Following configurations are supported:
SAP-side customized tia Viewer Core
In this scenarioconfiguration, 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 repository-instance-mapping is not required and respective ignored.
| Drawio | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Content Server Viewer
...
(CSV
...
)
In this scenario, the KGS Viewer Pack communicate to the tia Viewer with using ArchiveLink, which retrieves the document from content server via ArchiveLink get-commands..
In this scenario, the repositoryinstancemapping configuration repository-instance-mapping in tia Viewer Core configuration is applied. If it is not explicitly configured, the setting for the instance default are applied .
...