Base SAP ArchiveLink Configuration
Both ECM and Content Server require basic ArchiveLink configuration for connectivity. This involves creating one (or more) Content Repository ID via transaction OAC0.
Please review the functionality referenced in the "Introduction and Overview" section of this document for a matrix of ECM vs. Content Server functionality.
NOTE:
- For ECM usage - Each repository ID will equate to a Box flocation. If you have multiple Box domains, a repository ID for each will need to be created. If you have multiple locations, this is further dictated at the document type level.
- For Content Server usage - Each repository ID will equate to a SharePoint top-level site collection PLUS a final content sub-site / library / location. If you have multiple various of this final location, a repository ID for each will need to be created.
Additional ArchiveLink configuration may be required depending on the integration pattern implemented such as creation of doctypes (OAC2), assigning link tables (OAC3).
This configuration is not outlined in this guide – refer to the Solutions Guide for further information.
Optionally if you have big-bucket organization of content across sites within you site collections, you may choose to create a repository id for each, such as: Human Resources, Finance, Supply Chain, Health and Safety, etc. Please work with your VersaFile team to determine the best setup to meet your requirements. Regardless, a minimum of one repository is required (and for the purpose of basic setup and configuration).