This page provides useful references for the SAP Connector.

Abbreviations

Here are all the abbreviations that are used in the SAP Connector documentation.

The SAP Connector release includes the following third-party software. These are used either at runtime or while packaging the delivery:

Additional repository settings

The following table lists additional settings that can be provided in the alfresco-global.properties file to override the standard behavior of the SAP Connector. These settings are not related to a particular SAP System Configuration, but they will affect the basic functionality and should be used with caution.

Important: The recommendation is to always consult Alfresco Support before overriding SAP Connector standard behavior with any of the settings below.

Example configurations

This section gives examples of different types of system configurations.

Example 1: One SAP system configuration with Archivelink only

This is an example for one SAP System Configuration with one connected SAP Content Repository, using pure Archivelink (metadata replication is off).

Copy and paste the SAP System Configuration code snippet below to your alfresco-global.properties and replace the values indicated according to your specification.

Note: Do not remove unused property keys.

Code copied to clipboard.
integrations.sap.system.1.al.alfrescoUser=**admin**
integrations.sap.system.1.al.alfrescoPassword=**t0ps3cR3t**
integrations.sap.system.1.al.archiveIds=**M1**
integrations.sap.system.1.al.documentRoot=**/app:company_home/st:sites/cm:sap/cm:documentLibrary/cm:SAP_Documents**
integrations.sap.system.1.al.checkSignature=**true**
integrations.sap.system.1.al.checkExpiration=**true**

integrations.sap.system.1.enabled=**false**
integrations.sap.system.1.name=${sap.system.1.name}
integrations.sap.system.1.host= ${sap.system.1.host}
integrations.sap.system.1.client= ${sap.system.1.client}
integrations.sap.system.1.systemNumber= ${sap.system.1.systemNumber}
integrations.sap.system.1.user= ${sap.system.1.user}
integrations.sap.system.1.password= ${sap.system.1.password}
integrations.sap.system.1.language= ${sap.system.1.language}
integrations.sap.system.1.webClient.enabled=false
integrations.sap.system.1.webClient.url=https://sapserver:port/sap/bc/gui/sap/its/webgui

integrations.sap.system.1.jobs.sapContentConnectorReplicate.enabled = false
integrations.sap.system.1.jobs.sapContentConnectorReplicate.cronExpression = 0 0/1 * 1/1 * ? *
integrations.sap.system.1.jobs.sapContentConnectorPlus.enabled = false
integrations.sap.system.1.jobs.sapContentConnectorPlus.cronExpression = 0 0/1 * 1/1 * ? *
integrations.sap.system.1.jobs.sapContentConnectorBarcode.enabled = false
integrations.sap.system.1.jobs.sapContentConnectorBarcode.cronExpression = 0 0/1 * 1/1 * ? *
integrations.sap.system.1.jobs.sapContentConnectorDirReplicate.enabled = false
integrations.sap.system.1.jobs.sapContentConnectorDirReplicate.cronExpression = 0 0/1 * 1/1 * ? *

Example 2: One SAP system configuration with metadata replication

This is an example for one SAP System Configuration with one connected SAP Content Repository, using default and additional metadata replication. It also enables the Open corresponding business object in SAP feature in Alfresco Share.

Copy and paste the SAP System Configuration code snippet below to your alfresco-global.properties and replace the values indicated according to your specification.

Note: Do not remove unused property keys.

Code copied to clipboard.
integrations.sap.system.1.al.alfrescoUser=**admin**
integrations.sap.system.1.al.alfrescoPassword=**t0ps3cR3t**
integrations.sap.system.1.al.archiveIds=**M1**
integrations.sap.system.1.al.documentRoot=**/app:company_home/st:sites/cm:sap/cm:documentLibrary/cm:SAP_Documents**
integrations.sap.system.1.al.checkSignature=**true**
integrations.sap.system.1.al.checkExpiration=**true**

integrations.sap.system.1.enabled=**true**
integrations.sap.system.1.name=**SAP Finance (NSP)**
integrations.sap.system.1.host=**192.168.112.112**
integrations.sap.system.1.client=**800**
integrations.sap.system.1.systemNumber=**01**
integrations.sap.system.1.user=**ALFRESCO**
integrations.sap.system.1.password=**t0ps3cR3tP@Ssw0rD**
integrations.sap.system.1.language=**EN**
integrations.sap.system.1.webClient.enabled=**true**
integrations.sap.system.1.webClient.url=**https://192.168.112.112:8021/sap/bc/gui/sap/its/webgui**

integrations.sap.system.1.jobs.sapContentConnectorReplicate.enabled=**true**
integrations.sap.system.1.jobs.sapContentConnectorReplicate.cronExpression=**0 0/1 \* 1/1 \* ? \***
integrations.sap.system.1.jobs.sapContentConnectorPlus.enabled=**true**
integrations.sap.system.1.jobs.sapContentConnectorPlus.cronExpression=**0 0/1 \* 1/1 \* ? \***
integrations.sap.system.1.jobs.sapContentConnectorBarcode.enabled=false
integrations.sap.system.1.jobs.sapContentConnectorBarcode.cronExpression=0 0/1 * 1/1 * ? *
integrations.sap.system.1.jobs.sapContentConnectorDirReplicate.enabled=false
integrations.sap.system.1.jobs.sapContentConnectorDirReplicate.cronExpression=0 0/1 * 1/1 * ? *

Example 3: Two SAP system configurations with metadata replication

This is a more complex example with two SAP System Configurations, different SAP Content Repositories having a mix of properties enabled and disabled.

Copy and paste the SAP System Configuration code snippet below to your alfresco-global.properties and replace the values indicated according to your specification.

Note: Do not remove unused property keys.

In this example, the first SAP System Configuration uses plain-text passwords while the second SAP System Configuration uses encrypted passwords (see Encrypting passwords for more). It also has two connected SAP Content Repositories and uses a different site to store the documents. It doesn’t have the SAP Web-GUI enabled, and the metadata replication jobs are invoked every 5 minutes instead running each minute like in the first SAP System Configuration.

Code copied to clipboard.
// SAP System Configuration 1
integrations.sap.system.1.al.alfrescoUser=**admin**
integrations.sap.system.1.al.alfrescoPassword=**t0ps3cR3t**
integrations.sap.system.1.al.archiveIds=**M1**
integrations.sap.system.1.al.documentRoot=**/app:company_home/st:sites/cm:sap/cm:documentLibrary/cm:SAP_Documents**
integrations.sap.system.1.al.checkSignature=**true**
integrations.sap.system.1.al.checkExpiration=**true**

integrations.sap.system.1.enabled=**true**
integrations.sap.system.1.name=**SAP Finance (NSP)**
integrations.sap.system.1.host=**192.168.112.112**
integrations.sap.system.1.client=**800**
integrations.sap.system.1.systemNumber=**01**
integrations.sap.system.1.user=**ALFRESCO**
integrations.sap.system.1.password=**t0ps3cR3tP@Ssw0rD**
integrations.sap.system.1.language=**EN**
integrations.sap.system.1.webClient.enabled=**true**
integrations.sap.system.1.webClient.url=**https://192.168.112.112:8021/sap/bc/gui/sap/its/webgui**

integrations.sap.system.1.jobs.sapContentConnectorReplicate.enabled=**true**
integrations.sap.system.1.jobs.sapContentConnectorReplicate.cronExpression=**0 0/1 \* 1/1 \* ? \***
integrations.sap.system.1.jobs.sapContentConnectorPlus.enabled=**true**
integrations.sap.system.1.jobs.sapContentConnectorPlus.cronExpression=**0 0/1 \* 1/1 \* ? \***
integrations.sap.system.1.jobs.sapContentConnectorBarcode.enabled=false
integrations.sap.system.1.jobs.sapContentConnectorBarcode.cronExpression=0 0/1 * 1/1 * ? *
integrations.sap.system.1.jobs.sapContentConnectorDirReplicate.enabled=false
integrations.sap.system.1.jobs.sapContentConnectorDirReplicate.cronExpression=0 0/1 * 1/1 * ? *
  
// SAP System Configuration 2
integrations.sap.system.2.al.alfrescoUser=**sapinteg**
integrations.sap.system.2.al.alfrescoPassword=**ENC(XbfE4Z112==)**
integrations.sap.system.2.al.archiveIds=**K2,Z1**
integrations.sap.system.2.al.documentRoot=**/app:company_home/st:sites/cm:sap_hr/cm:documentLibrary/cm:SAP_Documents**
integrations.sap.system.2.al.checkSignature=**true**
integrations.sap.system.2.al.checkExpiration=**true**

integrations.sap.system.2.enabled=**true**
integrations.sap.system.2.name=**SAP HR (S4H)**
integrations.sap.system.2.host=**192.168.1.110**
integrations.sap.system.2.client=**100**
integrations.sap.system.2.systemNumber=**00**
integrations.sap.system.2.user=**ALF_HR**
integrations.sap.system.2.password=**ENC(RET45324GFDSFfsf43ZEr4rfer45)**
integrations.sap.system.2.language=**EN**
integrations.sap.system.2.webClient.enabled=**false**
integrations.sap.system.2.webClient.url=https://sapserver:port/sap/bc/gui/sap/its/webgui

integrations.sap.system.2.jobs.sapContentConnectorReplicate.enabled=**true**
integrations.sap.system.2.jobs.sapContentConnectorReplicate.cronExpression=**0 0/5 \* 1/1 \* ? \***
integrations.sap.system.2.jobs.sapContentConnectorPlus.enabled=**true**
integrations.sap.system.2.jobs.sapContentConnectorPlus.cronExpression=**0 0/5 \* 1/1 \* ? \***
integrations.sap.system.2.jobs.sapContentConnectorBarcode.enabled=false
integrations.sap.system.2.jobs.sapContentConnectorBarcode.cronExpression=0 0/1 * 1/1 * ? *
integrations.sap.system.2.jobs.sapContentConnectorDirReplicate.enabled=false
integrations.sap.system.2.jobs.sapContentConnectorDirReplicate.cronExpression=0 0/1 * 1/1 * ? *

Reference for SAP Object Type Mapping

This is the reference for all supported SAP Object Types that are available by default in Alfresco Share to open the associated SAP Business Object along with their related transaction within the SAP Web-GUI.

See the Opening associated Business Object in SAP feature to learn how to enable and how to customize it.

Note: Because the SAP Object Types BKPF and BUS2081 requires a split of the replicated SAP Object Id into at least 2 separate parameters, the URL of both SAP Object Types should never be changed (not even the order).

Additional SAP JavaConnector properties

This reference lists the additional properties (such using Logon Groups) for the SAP JavaConnector that are supported for each available SAP System Configuration.

See Configure repository properties and the example configurations. The properties in the table below use SAP system configuration with Archivelink only as an example.

Note: See the SAP JavaConnector documentation to learn more about the available properties and their behaviors in detail.

Communication via HTTPS

Set up a secure communication between Content Services and SAP.

The SAP Connector works well over HTTPS. In general, there is no need to configure the SAP Connector. The main part is to prepare the SAP system and Content Services with the related certificates to use a secure connection.

Important: This chapter only describes the necessary steps to implement the certificate from the Content Services web server in SAP and prepare SAP Content Repositories to use HTTPS over HTTP for the communication.

CAUTION: The creation and installation of the certificate on the Content Services web server is not part of this section.

Get current certificate from Alfresco

Get the current certificate from Alfresco.

The current certificate used by the Content Services webserver must be known (and imported) in SAP. Therefore, export the certificate by following the steps below:

Important: The Content Services webserver must be up and running on a secure connection. This documentation does not cover the installation and configuration of the SSL connection on Content Services side. It only covers how to get the existing certificate.

1. Open Content Services (either the Alfresco Share or Alfresco Digital Workspace login page) in a web-browser and view the details of the current certificate.

   

2. Export the certificate to the local machine (depending on the browser manufacturer).

   

3. Make sure you use DER encoded binary X.509 (.CER) as the export format.

   

4. Once successfully saved, the file will be required in step Import Alfresco Certificate in SAP PSE.

Prepare the SAP Content Repository to use a secure connection.

Prepare SAP Content Repository for HTTPS

Set up SAP Content Repository connection to use a secure connection.

To prepare the SAP Content Repository to use a secure connection, follow these steps:

1. Open transaction OAC0.

2. Select the desired SAP Content Repository.

3. Enter %https in the transaction code field to show required HTTPS related settings:

   1. Remove the value for Port Number.

   2. Add the SSL Port Number.

   3. Select HTTPS required as a value for HTTPS on frontend.

   4. Select HTTPS required as a value for HTTPs on backend.

4. Save the settings for the SAP Content Repository.

Note: Make sure you remove the non-SSL Port Number, otherwise the connection will fail.

Import the certificate from Content Services to the Personal Security Environment (PSE) in SAP.

Import Alfresco Certificate in SAP PSE

Import the certificate to the SAP Personal Security Environment.

Make sure you have the certificate from Content Services webserver available.

To import the certificate to the SAP

1. Open transaction STRUST.

2. Check whether a SSL Client (Standard)

   PSE
   Personal Security Environment (SAP)
   exists.

   Note: If there is no SSL Client (Standard) PSE available yet, select SSL Client (Standard) entry and use the context menu to create a new PSE. Use default settings, if applicable.

3. Select the PSE (double-click) for SSL Client (Standard) and scroll down on the settings screen. At the bottom there is a button for uploading the certificate.

   

4. Upload the certificate previously downloaded from the Content Services webserver (Get current certificate from Alfresco).

5. Once imported, enter the Edit mode (menu Display ↔ Change) and click on Add to Certificate List.

   

6. The certificate should now appear in the Certificates List of the screen.

   

7. Save the changes.

Restart SAP Internet Communication Manager

You can restart the Internet Communication Server (ICM) to apply the certificate to the SAP system. Make sure the certificate from the Content Services webserver was successfully imported in SAP

1. Open transaction SMICM.

2. Restart the SAP ICM in menu More > Administration > ICM.

   

Next, test the communication via a secured connection.

(Optional) Test secured connection

To test the secure connection from the SAP side:

1. Open transaction SM59.

2. Review the current HTTP connections to external servers by expanding the HTTP Connections to External Server section. In this section a new entry must be created pointing to Content Services.

3. Create a new RFC Destination via the Create icon with connection type G HTTP connection to external server and a name, then click Continue.

   

4. Now, in the Technical Settings section, enter the Content Services Host along with the SSL Port and use /alfresco as the Path Prefix.

   

5. Switch to section Logon & Security and scroll down to Security Options > Status of Secure Protocol. Select Active for SSL and choose DEFAULT SSL Client (Standard) as SSL Certificate.

   

6. Save the settings.

7. Click Connection Test in the toolbar.

   

8. Review the test result. The connection should work and return with HTTP status code 200 .

   

9. The newly created RFC Destination is now available in section HTTP Connections to External Servers for transaction SM59 and can be tested at any time.

The communication via HTTPS should work fine between the SAP system and Content Services.

Using encrypted passwords

Encrypt all passwords used in the alfresco-global.properties by the SAP Connector instead of storing it as plain-text. Make sure the SAP Connector is configured properly and working as expected.

1. Go to Hyland Community.

2. Download the related JAR file:

   Code copied to clipboard.
    sap-content-connector-encryptor-2.0.jar
   

3. Create a public key and private key:

   Navigate to the folder of the downloaded JAR and run the following command to create the key pair in the current path:

   Code copied to clipboard.
    java –jar sap-content-connector-encryptor-2.0.jar init -path .
   

   Two files are created:

   • sapContentConnectorPrivateKey.pri (private key)
   • sapContentConnectorPublicKey.pub (public key)

4. Create an encrypted password:

   Code copied to clipboard.
    java -jar sap-content-connector-encryptor-2.0.jar encrypt -password H3ll0W0rlD112! -publicKey ./sapContentConnectorPublicKey.pub
   

   The encrypted password will be printed to the console, for example:

   Code copied to clipboard.
    ENC(XbfE4Z112==)
   

   Since it’s already surrounded by the required ENC() function, it can be copied and used as-is.

5. Upload the private key file to Content Services.

   To be able to resolve the password, the previously created private key (sapContentConnectorPrivateKey.pri) must be uploaded to the application server root directory (such as /usr/local/tomcat/sapContentConnectorPrivateKey.pri).

6. Provide encrypted password.

   To use the encrypted password, paste it as a value for the required properties in the alfresco-global.properties file.

   For example:

   Code copied to clipboard.
    integrations.sap.system.1.al.alfrescoPassword = **ENC(XbfE4Z112==)**
   

7. Restart the application server since alfresco-global.properties has changed.

The passwords are now encrypted and not plain-text.