2017 R1 Update Rollup 2

Configuration of the SAP SystemPermanent link for this heading

Fabasoft iArchiveLink can only be used with a well configured SAP system. The next chapters describe several configuration steps.

Output DevicePermanent link for this heading

First it has to be checked whether an output device for Fabasoft iArchiveLink is configured. If no output device is configured, a new one has to be created. Perform the following steps:

  1. Start the transaction “SPAD” and click “Display” next to Output Devices.
  2. If there is no entry with Dev. type “ARCHLINK”, create a new one.
  3. To switch into edit mode click “Change” or F8 and then click “Create” or Shift+F1.
  4. Configure the output device on the “DeviceAttributes” tab.

    Click the “Access Method” tab and define the Host Spool Access Method.
  5. Afterwards click “Save” to save the changes.

Content RepositoryPermanent link for this heading

In SAP the Fabasoft iArchiveLink HTTP content server has to be configured as content repository.

Perform the following steps:

  1. Start the transaction “OAC0”.
  2. To switch into edit mode click “Display/Change” .
  3. Create and configure a new entry for Fabasoft iArchiveLink ( or F5).
  4. Ensure that you are in “Full administration” mode by using the corresponding buttons.
  5. The following options must be configured at least:
    • HTTP server
      Type the IP address or server name of the Fabasoft iArchiveLink server.
    • Port Number
      Specify the port on which the Fabasoft iArchiveLink Service is listening (typically in a Microsoft Windows environment: 80 and in a Linux environment: 17050).
    • No Signature
      The checkbox needs to be unchecked.
    • HTTP Script
      Specify the HTTP script. Type “FSCArSap/fscarsap.dll”.

Note: For an optional HTTPS configuration type “%HTTPS” in the transaction field:

  1. Use “Test Connection” to test the connection between SAP and the Fabasoft iArchiveLink Service.
  2. Click “Send Certificate” to send the certificate to the Fabasoft iArchiveLink Service.
  3. Click “Exit” to save the configuration settings.

Note: If one Fabasoft iArchiveLink Service should connect to several SAP systems it is mandatory that each content repository ID is unique and each certificate has a unique common name.

Document TypePermanent link for this heading

For testing purpose create your own document types. The names of these document types have to start with “Z” (e.g. “ZZPRILIST”).

To create a new document type, perform the following steps:

  1. Start the transaction “OAC2”.
  2. Click “New Entries”.
  3. Specify the settings for the new document type (e.g. FAX, PDF or DOC in the “Document Class” field).
  4. Afterwards the document type has to be linked.

Link for Content RepositoryPermanent link for this heading

To link a document type, perform the following steps:

  1. Start the transaction “OAC3”.
  2. To switch into edit mode click “Display/Change” .
  3. Click “New Entries”.
  4. Create a new entry for the desired document type.

    Note: Only links with “L=X” will be active.
  5. Click “Save” to save the configuration.

Document Type Customizing WizardPermanent link for this heading

The document type customizing wizard can be used to specify workflow pre-settings for existing document types or new document types created using this wizard.

Perform the following steps:

  1. Start the transaction “OAD5”.
  2. Select the document type created before and click “Continue”.
  3. Select a document type template and click “Continue”.
    Note: If no template is selected the default value is incoming invoice.
  4. Select the checkbox “Workflow document type” to define workflow pre-settings and click “Continue”.
  5. Specify the object type. Select “CREATE” as entry method and specify the tasks. Afterwards click “Continue”.
  6. Specify the content server and the link table and click “Continue”
  7. Select available pre-settings if you want to maintain these. Otherwise click “Continue” without selecting.
  8. To create new pre-settings specify a unique ID and the name. Afterwards click “Continue”.
  9. Define the details of the pre-settings. Select an organizational unit for which these pre-settings will take effect and configure appropriate restrictions. Click “Continue”.
  10. Click “Complete” to finalize the configuration.

Note: Start the transaction “OAWD”. The pre-settings defined before should be available.

Configuration of the GUI IntegrationPermanent link for this heading

To configure the GUI integration, perform the following steps:

  1. Start the transaction “OAA3”.
  2. Double-click “SAPHTTP” to edit this protocol.
  3. Click “Application maintenance”.
  4. Click “Create” to create a new application.
  5. Double-click the new application.
  6. Double-click “Display Stored Document” and configure the settings of the stored documents. Afterwards click “Back”.
  7. Double-click “Archive from Frontend” and configure the settings. Afterwards click “Back”.
  8. Click “Save” to save the settings.
  9. Click “Back” twice to switch back to “ArchiveLink Protocols: Overview of Protocol”.
  10. Double-click “Archive from frontend”. Select a document class that should be maintained and double-click this document class or click “Change” .
  11. Select the communication type “OPEN (OLE)” and the application created before. Click “Continue” .
  12. Repeat the last two steps for all document classes that should be maintained. Afterwards click “Save” to save the configuration.
  13. Double-click “Display Stored Document”. To maintain the stored documents repeat the steps described before to maintain a document class.

Support of Two Archives Permanent link for this heading

In SAP a document type can only be active for one content repository, but archived contents are also available if the document type is inactive (“L!=X”, see chapter “Link for Content Repository”).

To configure a new archive edit the link of a document type, perform the following steps:

  1. Create a second content repository. See chapter “Content Repository”.
  2. Start the transaction “OAC3”.
  3. To switch into edit mode click “Display/Change” .
  4. Select the line of the link that should be configured to use the new content repository and click “Copy as” . A new line with a copy of the link configuration is created.
  5. In the new entry change the “L” property to something different than “X”. Click “Continue” to confirm.
  6. In the original entry change the “Cont.Rep.ID” and “Link” properties. Specify the newly created content repository.
  7. Click “Save” to save the configuration.

Enable HTTPS Communication Between SAP and the Fabasoft Folio Web ServicePermanent link for this heading

Optionally, the communication between SAP and the Fabasoft Folio Web Service can be configured as HTTPS communication.

To enable HTTPS communication the newest version of sapcrypto-library has to be installed. Download this library on the SAP marketplace (http://service.sap.com) for example. The following steps are also described in the SAP hints 510007 and 712330.

Installation of the SAPCRYPTO LibraryPermanent link for this heading

To install sapcrypto-library, perform the following steps:

  1. Copy the files sapcrypto.dll and sapgenpse.exe, compatible to your system, in the exe folder of the SAP installation (e.g. C:\usr\sap\TST\SYS\exe\nuc\NTAMD64\).
  2. Edit the file <SAPSYSTEMNAME>_<INSTANCE_NAME>_<SAPGLOBALHOST> (e.g.: TST_DVEBMGS00_sapsrv). Add the following lines in the profile directory:
    ssf/name= SAPSECULIB
    ssf/ssfapi_lib= <path to sapcrypto>\sapcrypto.dll
    libsapsecu= <path to sapcrypto>\sapcrypto.dll
    ssl/ssl_lib= <path to sapcrypto>\sapcrypto.dll
    icm/server_port_x = PROT=HTTPS,PORT=443


ssf/name = SAPSECULIB
ssf/ssfapi_lib = C:\usr\sap\TST\SYS\exe\nuc\NTAMD64\sapcrypto.dll
libsapsecu = C:\usr\sap\TST\SYS\exe\nuc\NTAMD64\sapcrypto.dll
ssl/ssl_lib = C:\usr\sap\TST\SYS\exe\nuc\NTAMD64\sapcrypto.dll
icm/server_port_2 = PROT=HTTPS,PORT=443

Configuration in SAPPermanent link for this heading

Perform the following configuration steps in SAP:

  1. Start the “Trust Manager” (transaction “STRUST”).
  2. Right-click “SSL Server” and click “Create“.
  3. Create PSEs for all instances.
  4. Double-click on the (first) new entry below “SSL Server“.
  5. A CA-certificate has to be imported. In the “Certificate” area, click “Import certificate“. Specify the path to the CA-certificate and choose the right encoding (e.g. Base64). Click “Continue” to save the changes.
  6. Click “Add to Certificate List” to add the certificate to the “Certificate List”.
  7. The CA-certificate has to be added to the SAP trust store. Click “Export certificate“ and switch to “Database”. Specify the name of your CA in the field “Trust Center”.
    Note: This identifier has to start with ZZ. Otherwise the error message “Choose the key from the allowed namespace” will occur.
    Click “Continue” to save the changes.
  8. The certificate has to be configured for an instance. In the area “Own Certificate” click “Create a Certificate Request” . This request has to be signed by a trusted CA. Click “Import Cert. Response” and “Load local file” to import the response of the trusted CA. Afterwards click “Continue” to save the changes.
  9. Repeat the last step for all instances.
  10. Right-click “SSL Client (Standard)” and click “Create”.
  11. Configure the client PSE like Name=<SID>.
    Note: This step is very important because otherwise the SSL agent will not start.
  12. For this PSE also import the CA-certificate and add the certificate to the “Certificate List”.
  13. Save the configuration settings and restart all ICM processes.

To restart the ICM processes start the transaction “SMICM”.

Click “Administration ICM Exit Hard Global”:

Confirm with “Yes”:

Check SSL ConfigurationPermanent link for this heading

To check the SSL configuration, perform the following steps:

  1. Start the transaction “SMICM”.
  2. Click “Services” and verify that the HTTPS service is running.
  3. If the service is not running navigate “Back” . Click “Display All” to check the log for errors.

Note: Be sure that the content repository is configured to use HTTPS. See chapter 4.2 Content Repository” to enable HTTPS.