Using SAPALink SDK with C++ - Configuration of KGS Generic Store Provider & usage of your SAPALink-implementation

A standard installation of KGS ContentServer4Storage is being assumed.

First, please copy the following files to your <Tomcat installation directory>\bin folder:

• SAPALINK.dll
  The result of your compilation process of the implementation of the SAPALink-SDK.

• JavaDMSlink.dll
  You may find this in <Unpacked ZIP archive>\SAPALink_SDK_v210H-2\CPlusPlus\
  Please choose either the 32-bit or 64-bit version depending on your implementation and compilation.

• DMSException.class and SAPALinkDLL.class
  You may find both here <Unpacked ZIP archive>\SAPALink_SDK_v210H-2\CPlusPlus\

After copying those files please make sure that your <Tomcat installation directory>\bin is part of the System variables → Path.

In order to add your bin-directory to the path please open the “Environment Variables”-menu by pressing the Windows-key + R and entering “rundll32.exe sysdm.cpl,EditEnvironmentVariables”.

This will open the Environment Variables window.

In the “System variables”-section click the Edit…-button. This will open the “Edit environment variable”-menu.

Highlighted “System variables-Edit…”-button
Open

Within the opened menu click the New-button in order to add a new line and either type in the path or browser via the Browse…-button to the location of your Tomcat-bin-folder.

“Edit environment variable”-menu with highlighted and “New”-button and new line.
Open

After making sure that the bin-directory is part of the System variable Path, please open the WebGUI of KGS ContentServer4Storage.

Within the WebGUI please click on the Configuration-submenu within OSGi.

Highlighted Configuration-submenu within OSGi-menu.
Open

Within the Configuration-menu please click on the pencil-menu on the right-hand side of the Generic Store Service in order to open the configuration of the Generic Store Service.

Highlighted pencil-menu of the “Generic Store Service”
Open

Within the configuration menu please follow these steps:

• Make sure that the “Archive Link Implementation Class” is set to SAPALinkDLL

• Let the “Implementation Folder” point to the Tomcat-bin-folder

• Set the “Use internal Implementation” to False

“Generic Store Service”-configuration with highlighted sections and parameters
Open

After configuring these, please restart the webserver.

Within the WebGUI please open the Main → ContentServer4ArchiveLink-menu. Here you should see the name of your company, the version number you entered as well as the name of the dms you chose.

Highlighted vendor, product name as well as version within ContentServer4ArchiveLink
Open

Please note also the changes in the SAPALink Info (Main → SAPALink Info):

“SAPALink Info”-menu with highlighted vendor, product and class
Open

The ArchiveLink command serverInfo should also return the assumed results:

http://localhost:8080/KGSAdmin-CS/contentserver?serverInfo&pVersion=0047&resultAs=ascii

Highlighted output of the “serverInfo”-request.
Open