About
This article gives an overview how and when SAP connections are used in KGS Document Router.
Content
Introduction
SAP-Connection may required in two occasions:
Archiving
Linking
The following sections will explain the work and usage of sap connections in KGS Document Router.
SAP Connector Plugin
KGS Document Router is delivered with KGS SAP Connector plugin. It can be reached by OSGI UI: Main → KGS SAP Connector.
There SAP-Connections can be configured.
These connections are primarily used for SAP-Linking.
In document router instance configuration in tab common an SAPALinkInterface can be defined. Only if this setting is set to ArchiveLink, then also the SAP Connector plugin is used in order to generate Archive URLs in order to communicate with an Archive Link archive system. In other setting of the parameter SAPALinkInterface the SAP connection configured in SAP Connector plugin is not used for archiving.
SAP Connections for archiving
In document router instance configuration in tab common, the SAPALinkInterface can be chosen.
ArchiveLink
SAPALink
KGS External API
The following sub chapters are describing the possibilities.
ArchiveLink
SAPALink
KGS External API
SAP Connections for Linking
In SAP connector plugin are SAP connections configured.
In document router instance config in tab SAP via configuration item SAPConnection, a default SAP connection is chosen. (Can be overwritten by index file → https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2311028919/DR4+-+Defining+DataInterfaces+SIDMappings+and+Archive+Link+Mappings#SIDMapping-definition )
In schema file (as constant) or in index file an content repository is set.
With these information in addition to SAP-Object-Id and document ID are enough information for linking an document archive to content server to an SAP-Object.
Please respect that you need to set BCSAPLinkObject to Link to business object.