--- title: Content Server slug: content-server docTags: createdAt: 2020-02-21T00:53:38.000Z --- Below is the configuration needed for a SharePoint Content Server. \*\*\* please refer to the section Follow Up SharePoint Team Tasks for more information on required indexes \*\*\* 1. Under "Connections" click "SharePoint Online" 2. Under "SharePoint Online" click modify on a previously created box connection. 3. Click "Add Content Server" 4. Hover over each input box to see example values. 5. Click "Add" 6. Click "Save". 7. Restart service via Windows services.   ::Image[]{src="https://api.archbee.com/api/optimize/1hH4CNQG9tP4YS-TB-TC6/sXK8kJEqLKdTfPxiiBo2f_screenshot-624.png" size="58" width="536" height="720" position="center" showCaption="false"} Image CaptionImage alt text The below table is a description of each configuration entry above, along with possible value.  | Setting | Description | Sample Value(s) | | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | | enabled | YES/NO | Yes to enable, No to not but still configure. | | signature required | YES | Used for verify authentic origin requests.  | | csHost | Binds to local IP address  | 127.0.01 | | port | Port we want content server to be deployed on. | 8089 | | threads | Max Number of threads to allocate for parallel processing.  | 50 | | contentType | CMS Custom metadata needs to specify the name of template | invoices | | SAPType | Configured SAP System utilized  | S4 | | tmpDir | Directory to temporary use for storage | C:\\\\\\\\config\\\tmp | | certDir | Directory where certificates are located | C:\\\\\\\\config\\\certificates | | RepoId | SAP repository for content Server | ZS | | Location | subsite and or document library value where the data is stored

i.e /insertsubsitename/insertdocumentlibraryname | For SharePoint: /fi/ap | | repository | For SharePoint, Provide site Information | tenantname.sharepoint.com/sites/test | | callBackEnabled(for version 6.6.8) | Enable callbackHandler to link and monitor content server activities from SAP and to allow for ECM/SAPDocID mapping. ie: for each content server call from SAP to M365, a separate return call is made via SAP Jco RFC to log in the Link Enterprise SAP Gateway as well for a CREATE, it will map SAPDocID to the ECM M365 object id.

The recommended setting is YES as this will support:
- ECM based viewing
- ECM API support for documents stored via Content Server
In extremely high volume content server scenarios where no ECM will be in play, this setting should be set to NO | YES | \*the Windows service must be restarted for changed to take effect ### Mapping SharePoint Fields to docuflow Metadata SharePoint stores columns with internal names that may differ from those expected by docuflow. To synchronize document metadata correctly, the field names must be mapped in the defaultConfig.ini file. Add the following line: :::BlockQuote contentServer.contentType.columns = \{"DOCID":"docID","COMPID":"compId","PVERSION":"pVersion","CONTREP":"contRep","DOCPROT":"docProt"} ::: - The keys on the left (e.g., DOCID) represent standard metadata fields used by docuflow. - The values on the right (e.g., docID) correspond exactly to the internal SharePoint field names. This mapping enables docuflow to correctly interpret SharePoint metadata fields for indexing and synchronization. ### Multi-Library Support for SharePoint The **Multi-Library Support** feature enables Link Enterprise to search documents across multiple repositories and document libraries within the same SharePoint tenant, providing a unified and seamless search experience. To enable this feature, update the defaultConfig.ini configuration file with the following settings: :::BlockQuote contentServer.searchAll = YES contentServer.AdditionalSearchRepositoryWithLocation = xxxx.sharepoint.com/sites/repository/library ::: - contentServer.searchAll = YES activates Multi-Library Support. - contentServer.AdditionalSearchRepositoryWithLocation lists additional SharePoint document libraries (comma-separated) to include in the search. Once configured, Link Enterprise will search across the main repository and all specified SharePoint document libraries within the tenant.