Base SAP docuflow Configuration

ecm ecm requires base configuration regardless of what integration patterns, use cases, or functionality you would like to utilize content server content server requires no more docuflow specific configuration unless you are going to use the below functionality with content server outbound document storage (gos/sfo or message output) with outbound metadata transfer url/web viewing (instead of archivelink standard viewing) docmover folder creation it is recommended to use ecm unless you must use content server if you must use content server, this must be a separate (set of) oac0 repository id(s) reasons you may need to use content server sap message output without ecm plug in adk data archiving fiori apps using document service (ie without sfo/gos functionality) outbound dms any other application or 3rd party that relies on archivelink directly if you are not implementing outbound metadata transfer you do not need to perform the below configuration you will most likely require standard sap archivelink oac2 and oac3 configuration overview the base configuration consists of the following components one or more cms profiles one or more cms use tags one or more api destinations environment variables (optional) one or more repository id’s all above configuration is navigated via the content api system dashboard (transaction /dflow/sys) utilizing the top left menu path “configure” configuration must be done in sequence, and requires the repository id(s) to be created as a prerequisite all configuration must be saved in a transport for migration to qual and production (among other) environments cms profiles setting description sample value(s) cms profile cms profiles equate to top level site collections in s3 typically, there is only one cms profile per repository type of an organization s3 1 repository type s3 type s3 description an english description given to the describe the cms profile main site acme cms use tags 100,472,171 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type api destinations api designations are a unique combination of cms use tags and cms profiles that determines the sap rfc to be leveraged, and thus load on that rfc and in turn a group of sap jco server threads, allowing you to manually control the load balance processing across multiple rfc/sap jco connections this is not relevant to content server integration note that for extreme load, you can also have multiple enterprise connectors configure for an sap system, allowing you to spread api destinations (i e rfc destination) across multiple connector instances and possibly physical/virtual servers important this rfc destination chosen must match the api destination configured in enterprise connector in step base enterprise connector configuration – enterprise ecm only 100,527,116 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type environment variables environment variables are used for two reasons the primary/most common reason is when a enterprise configuration element requires a value that might change depending on which sap environment (i e sap system id) you are in an example of this would be a development server vs a production server for saving auditlink bundles viewing url’s are often different for development vs production as well this is leveraged extensively for on prem content repositories when there are more server and host names involved this is not relevant to content server integration the second reason and less common, is if the enterprise configuration field is too small in length to hold a crazy long value you may have yes, we have seen it note when used in configuration, the environment variable must be specified within brackets, i e \<hostname>, or \<reallylongsubsitestring> 100,319,324 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type repository id’s 101,446,196 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type repository id’s are the final element to the base configuration and tie in the top level cms profile with the repository store name (bucket in s3) along with which viewing mechanism and elements to use and a few other options at this point if you are viewing the system dashboard ( make sure to hit refresh to show your new changes! ) you will see your entry(ies) the api status column will be red until the enterprise connector is configured for that api/rfc destination check with your middleware installation and once completed and the windows service is turn on, see section establishing sap < > enterprise connector connectivity configuration