Within this documentation, you may find helpful information and steps that are necessary in order to connect your own storage with the help of KGS SAPALink SDKs.
...
The downloaded ZIP container follows a certain structure:
Docu
Within this folder, you may find the manual for the SAPALink SDK as well as two KGS specific manuals.SAPALINK Add-On 2_10A.pdf
Refers to extended functionalities like componentCreateCOLD as well as DocumentKeysSet
Please note: componentCreateCOLD is deprecated and will not be supported by the OSGi-ContentServer4Storage-Version!SAPALINK Query.pdf
SAPALINK SDK ImpRevGuide
Runtime
The runtime directory contains the compiled SAPALINKTEST.exe, which you may use in order to test your implementations. It’s still recommended to use the KGS API Tester application in order to test your implementations.SAPALINKTEST.DAT
The SAPALINKTEST.DAT-file is being used as a Settings-file by the SAPALINKTEST.exeSAPALINKTEST.EXE
Storage-profile.txt
The storage-profile.txt-file has to point to a valid KGS Storage-configuration
CPlusPlus
JavaDMSlink.dll
Within this directory you may find libraries and precompiled Java-classes necessary in order to load your C++ SAPALink-implementation into the KGS ContentServer4Storage.DMSException.class
SAPALinkDLL.class
32 Bit
JavaDMSlink.dll
x64
JavaDMSlink.dll
SAPALINK
Visual C++ Project for creating a C++-based implementation of SAPALink SDK
Java
SAPALINK.JAVA
DMSException.java
SAPALink.java
If you’re implementing your classes in Java you’ll have to implement the DMSException.java (for error handling) as well as the SAPALink.java for each required method and compile it.
SAPALINKTEST
Sources (C++) for SAPALINKTEST.exe
In order to understand how the SAPALINKTEST.exe-application works and which methods are being provided by KGS we decided to provide you with our source-code for this testing application.
TestDocuments
...
Some test documents (tif,pdf)