How ARCHPATH and BASEPATH are utilized by CommonStore for SAP

Answer

If you are using RFC, the ARCHPATH and BASEPATH parameters in the CSSAP file archint.ini should point to the locations specified by the "Archive Path" and "Basic Path" parameters in the R/3 transaction OAC0, respectively. These locations must be accessible (for example, can be written to and read from) by both the SAP R/3 and CSSAP servers when using RFC. ARCHPATH and BASEPATH are the share names as visible from the CommonStore machine.

When archiving via RFC, R/3 will place documents to be archived in the location specified by the "Basic Path" parameter, and CSSAP reads the documents from there and archives them. When a document is retrieved, CSSAP will take it out of the back-end archive and place it in the ARCHPATH, where SAP will read it.

When you are using HTTP, specifying ARCHPATH and BASEPATH in the archint.ini file is optional. It is recommended to not to specify these keywords. If you specify ARCHPATH and BASEPATH, then the location of the ARCHPATH and BASEPATH should not be shared between the R/3 and CSSAP servers. If you do not specify an ARCHPATH and BASEPATH in the archint.ini when using HTTP communication, then CSSAP will default to the TEMPPATH keyword. In either case, no files will be written to the specified directories.