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 repoid will equate to a s3 bucket for content server usage each repoid will equate to a s3 bucket 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 buckets within your bucket collections, you may choose to create a oaco repository id for each, such as human resources, finance, supply chain, health and safety, etc please work with your gimmal link enterprise 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)