Additional repository settings - Additional repository settings - 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/Administer/SAP-Connector-reference/Additional-repository-settings - 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

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.

Note

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

Property Description
integrations.sap.configuration.attributeService.enabled Use the SAP Connector internal AttributeService to find documents from SAP, across multiple nodes in high availability systems. Only required if the Alfresco Full Text Search within the Transactional Query Options was set to Never use Database in the Alfresco Admin Console. Default value: false
integrations.sap.configuration.defaultDocProtection Override the default setting for the SAP DocProtection (property connexasArchivelink:docprot). If no docProt parameter is transferred or an SAP Archivelink Document is created, this value will be used to override the default. Default value: rcdu
integrations.sap.configuration.chunkSize Chunk size that is used to read the payload of the HTTP request. Usually there is no need to change this setting. Default value: 65536 (byte)
integrations.sap.configuration.postFilter.enabled If true, the SAP Connector queries the database only for docId instead of docId, compId and archiveId.In this case, compId and archiveId will be filtered in a second step. Recommended if the database execution plan prioritizes compId and archiveId (both not unique) over the docId (unique) and therefore get an huge result set. Default value: false
integrations.sap.configuration.doubleSearch.enabled If true, the query used for finding documents requested by SAP is first executed against Solr. If we don't find the desired document, we search again, but against the database using transactional metadata queries (TMQ). In some situations, especially large databases, this can improve speed. Default value: false