Use this information to configure the SAP Connector. Check the following SAP access privileges in order to continue with the configuration.
To configure the SAP Connector properly on the SAP side, an SAP dialog user is required who has access to the following SAP transactions:
||Define and maintain SAP Content Repositories which includes the storage system (Alfresco) for the documents.|
||Define global document types and assign document classes. Required for end-user testing.|
||Link SAP Content Repositories, document types and SAP object types. Assign retention periods. Required for end-user testing.|
||Run and edit SAP function modules (
In this section, you’ll create and configure a new SAP Content Repository where the (Content Server) is Content Services. In addition, the connection between the SAP Content Repository and Content Services is secured by a certificate and tested.
1. Create SAP Content Repository
Create a new SAP Content Repository which points to Content Services.
The maintenance screen for creating new SAP Content Repositories can be accessed with transaction
In the SAP Content Repository overview, click Display/change (CTRL+F4).
Another icon appears: Create (F5). Click on it to create a new SAP Content Repository.
Enter mandatory values for the new repository.
See the following table to choose the correct settings.
- Values in bold must match the values given in the table exactly.
- Values in italics are customer specific and need to be adapted according to your environment.
Field Description Content Rep. The name of the new repository. Remember the SAP naming conventions (only 2 characters allowed for Archivelink).
Description A brief description for the repository (max 50 characters).
Value: Alfresco Content Services via SAP Connector
Document Area The document area for the documents.
Storage Type The storage type of the repository
Value: HTTP content server
Version no. Number of the current SAP content server version. For content server version 4.7 enter 0047.
HTTP Server The IP address of the Content Services server - or the Load Balancer.
Port Number The port number where the Content Services is listening - usually 8080.
SSL Port Number The port number for secure layer. Only required for Communication via HTTPS.
Value: For now, leave empty.
HTTP Script The Web Script location in Content Services where all requests from SAP are processed.
Transfer drctry For some ArchiveLink scenarios, files have to be created in a transfer directory (on SAP side) before sending it to the content server. Maintain it, if the default value does not match your company standard.
Click either on icon Test connection or on icon Status information.
In both cases, a message appears saying the content repository does not exist.
Note: Any other message than Content repository XX does not exist indicates an issue with the network connection between the SAP server and the Alfresco server. In such a case, double-check the login credentials for Alfresco (
alfresco-global.properties) and make sure Alfresco is available.
Save the current repository configuration (click Save on the bottom line) before proceeding with the next steps.
To create the repository on the content server click on icon CS Admin (Content Server Administration) in the middle of the screen, besides the Test connection icon.
In the administration area, the repository has to be created by the Create repository icon on the left. It is available in section Create.
If the repository has been created successfully, you’ll be redirected to the Details section. At the bottom of this screen, you’ll see already some basic repository information coming “live” from Content Services.
Click the Save (CTRL + S) button in the bottom bar to save the changes again.
After saving, the screen can be closed by clicking on Exit button in the top right toolbar.
2. Secure connection using a certificate
Create a certificate in SAP that will be stored in Content Services to allow only authorized requests from the SAP Content Repository.
By default, all HTTP(S)-requests coming from the SAP Content Repository and arriving via the SAP Connector in Content Services are dropped until a certificate is available and active (you can disable the certificate check in the
Important: We strongly recommend securing the connection between SAP and Alfresco at all times.
Open the newly created SAP Content Repository for editing in transaction
Navigate to the Content Server Administration by clicking the CS Admin button.
Switch to section Certificates and refer to the Certificates Properties table at the bottom (which is still empty).
Click the button Send certificate (mail icon) to send a certificate to the SAP Content Repository.
The certificate was sent to Content Services. Therefore, it appears in the table Certificates Properties - but it is not yet activated. Checkbox in column Active is not selected.
Note: From the SAP HTTP-Content Server protocol specification, the certificate can only be activated from the content repository side. This is an additional security step. Therefore, no additional action is necessary on the SAP side. Switch to Content Services and proceed with the activation in the next step.
3. Enable security by activating the certificate
Activate the certificate in Content Services to process authorized requests only.
There are two options for activating the recently sent certificate. Either activate it in the SAP Connector - Administration Console (recommended and preferred way) or manually edit the related property at the certificate document in the Alfresco repository.
Activation via SAP Connector - Administration Console:
Login to Alfresco Share and navigate to the SAP Connector - Administration Console (via menu Admin Tools > SAP Integration).
Scroll down to the related SAP System Configuration where the recently created SAP Content Repository belongs to.
Click the Enable certificate for content repository XX button.
The connection is now secured by the certificate.
Activation by manually editing the certificate properties:
Login to Alfresco Share and navigate to the following (new) folder structure in the Alfresco repository to find the recently created certificate document: Repository > Data Dictionary > SAP Content Connector > SAP Repositories > XX.
Within the XX folder two files are available. The repository file (with name
XX Repository) and the certificate document (contains the common name of the SAP system in the document name).
Edit the properties of the certificate document and select checkbox Certificate Active and save the document.
The connection is now secured by the certificate.
4. Check certificate in SAP
Control step to confirm that the certificate activation in Content Services reflects in the SAP system for the SAP Content Repository.
To proof that the activation of the certificate from the previous step reflects immediately for the SAP Content Repository, check the certificate section of the SAP Content Repository.
In the SAP system, open the created SAP Content Repository in transaction
Click button CS Admin.
Switch to Certificates section and refer to table Certificate Properties.
In column Active the checkbox is now selected.
5. Functional test
This page describes how the SAP Connector and therefore the ArchiveLink interface can be tested. The testing requires some additional SAP fundamentals, and is based on the same procedure used by SAP to certify the SAP Connector content ArchiveLink interface.
Note: In order to successfully complete these tests, all mandatory steps described in the Basic configuration section should have been completed.
In SAP, open the ABAP editor with transaction
RSCMSTas report name in the Program field and execute it (click Execute in the toolbar or press F8).
In the Repository field enter the name of the recently created SAP Content Repository and click Execute in the toolbar or press F8.
In the next screen, all sub-reports are listed that could be executed against the repository.
The most important report is
RSCMSTH0. This will test the basic communication like
deletecommands via HTTP against the repository. Click the Execute icon for the report.
The report return with success if the SAP Content Repository was properly configured and hence, the SAP Connector is working.
(Option 1): If you’re interested in more technical details of the test, then click the Details icon near the green result.
In this screen, each function call with its parameter is logged that was sent [to Alfresco]. Scroll down to the end of the detail page and find a summary of the functions which was tested including times.
(Option 2): You can execute some further test reports against the repository.
This will test additional functionality of the HTTP interface. The additional available test reports are:
Note: For SAP BASIS component 740 up to (at least) 752 there is a known bug in the
RSCMSTH2report. If the report returns with a lot of issues regarding document protection like
DOC_P[rc], refer to the following SAP
OSSnotes: 2371386, 2198970. Skip this report unless the notes are implemented.