Versions Compared

Old Version 3

changes.mady.by.user Maik Wodarz

Saved on

compared with

New Version 4

changes.mady.by.user Maik Wodarz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following sub chapters are describing the possibilities.

In document router SAP tab defined SAP connector connection is used.

While archiving document router requests an Archive URL via RFC connection from connected SAP-System. This URL may signed as well.

The advantage is, that the content server has not to be configured second time in document router. In addition no certificate for archiving needs to be installed.

The disadvantage is that annother round trip time to SAP-Archive is required. Is the SAP-System off site this will cause perfomance drwa backs.

Another disadvantage is early locking. It is not possible to suppress locking while archiving because Document Router does not know which content server is configured in SAP. Further it is not possible to realize late locking because we don’t git feedback if early locking was done and if it was successfully.

For archiving the connection configured in tab SAP in document router instance is irrelevant.

In order to configure SAPA-Link the web.xml file needs to be configured inside Tomcat webapps folder.

Code Block
C:\Program Files\Tomcat 9.0\webapps\KGSAdmin-DR-4\WEB-INF\web.xml

In order to use it, please consult: FAQ: SAPALink Implementation

This possibility is much more flexible. So for example it is possible to archive to an S3 archive. Document router behaves like an inbuilt KGS Content Server and can archive so to a brad variety of storage systems.

KGS External API

Like in case of ArchiveLink the communication is using the ArchiveLink protocol. In comparison to option ArchiveLink the required URLs for archiving/locking are not created by SAP. Instead an own implentation is used for creating ArchiveLink URLs. According ArchiveLink Spezifikation it is possible to sign the URL. Using security level 2 the inbuild certificate needs to be placed into content server. The document router does not offer such an possibility. Instead you can use KGS-Migration.

KGS External API is respecting AL Connection Mapping File which can be configured in document router instance configuation in tab Archiving. This offers and index file dependent archive mapping.

SAP Connections for Linking

...