Content Server

2 min

below is the configuration needed for a box content server please refer to the section follow up box team tasks for more information on required indexes under "connections" click "box" under "box" click modify on a previously created box connection click "add content server" hover over each input box to see example values click "add" click "save" restart service via windows services 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 cssaptype configured sap system utilized s4 tmpdir directory to temporary use for storage must contain double slashes c \\\\\<connector install directory>\\\config\\\tmp certdir directory where certificates are located must contain double slashes c \\\\\<connector install directory>\\\config\\\certificates repoid sap repository for content server zs location folder id where the data is stored for box 123455852 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 box, a separate return call is made via sap jco rfc to log in the docuflow 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