Advanced configuration - Advanced configuration - Alfresco - Alfresco Content Connector for SAP Applications - Alfresco/Alfresco-Content-Connector-for-SAP-Applications/5.0/Alfresco-Content-Connector-for-SAP-Applications/Alfresco-Content-Connector-for-SAP-Applications/Configure/Advanced-configuration - 5.0

Alfresco Content Connector for SAP Applications

Platform
Alfresco
Product
Alfresco Content Connector for SAP Applications
Release
5.0
ft:lastPublication
2026-05-06T14:51:00.094000
ft:locale
en-US
ArchiveStatus
Archived

This section basically describes all additional configuration options for the SAP Connector to replicate metadata from the SAP Business Object to the document in Content Services.

If a document is stored in SAP via the SAP Content-Server HTTP-Interface on a content server, SAP submits only three additional properties in the HTTP-request (besides the content itself). These are the SAP Content Repository (name of the SAP Content Repository), the SAP Document Id (unique number created from SAP to identify the object) and the SAP Component Id (hidden in the Alfresco Share UI because of non-human readable values). The additional parameters will show up in an aspect with name SAP Connection Details at the document.

sap_conf_aspect_sap-connection-details

However, there may be a lot of additional reasons to have more information from the SAP Business Object in Content Services available than just these few, which are also not very meaningful to a user, by the way.

The SAP Connector offers the capability to make additional metadata available outside SAP already by default. To get additional metadata out of SAP and store it at the document in Content Services, the connection to SAP is done through the SAP JavaConnector (JCo). Furthermore, the SAP Connector takes advantage of different ways to trigger an action which results in the metadata replication.

These are mainly Jobs and Behaviors, but also event-based action is possible. The replicated information will be provided in connexas related aspects at the documents in Content Services.