Base SAP Link Enterprise Configuration
ECM requires base configuration regardless of what integration patterns, use cases, or functionality you would like to utilize.
Content Server requires no more SAP Link Enterprise 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.
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.
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 |
Setting | Description | Sample Value(s) |
|---|---|---|
CMS Use Tag
| CMS Use Tags, in combination with CMS Profiles, will together determine an API Destination (below) to be utilized. API Destinations in turn determine the SAP RFC to be leveraged, and thus load on that RFC and in turn a group of SAP JCo server threads. In short, this combination allows you to load balance processing across multiple RFC/SAP JCo connections. A very common approach to at a minimum to break out viewing from the rest of your processing. As let’s face it, end users hate when they can’t view their documents and if you are hammering an RFC with other processing, well, insert hourglass icon. Also, have one or more use tags for custom usage. This way if you mess up you don’t affect everyone else ;-) The load balancing features of Use Tags is not relevant to Content Server usage. | Doc_Storage_FI Doc_Storage_SCM Doc_Storage_HR Custom_API_Usage_1 Migration_1 Migration_2 AuditLink_1 Etc.…
|
Description | An English description given to the describe the CMS Tag | Outbound document storage for FI |
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.
Setting | Description | Sample Value(s) |
|---|---|---|
CMS Profile | CMS Profile that will use this API/RFC Destination | S3_1 |
CMS Tag
| CMS Use Tag that will use this API/RFC Destination | • Outbound document storage for FI or • Viewing |
Disable | Used to temporary disable processing on this API Destination | ON/OFF |
CMS RFC Destination
| SAP RFC to be used to communicate with a specific instance of a Enterprise Connector. This RFC destination chosen must match the API Destination configured in Enterprise Connector in step Base Enterprise Connector Configuration – ECM Only. | Z_CMSAPI_01
|
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>
Setting | Description | Sample Value(s) |
|---|---|---|
SAP System ID | SAP system id that should use the value specified | DEV QA1 PRD |
Variable Name | Variable name that will be specified in any relevant Enterprise ECM configuration. | • SPOnPremHost or • reallylongsubsitestring |
Variable Value 1 | The value to be substituted in the ECM configuration per SAP environment/system ID. | http://devsp2013srv1/ http://qualsp2013srv1/ http://prodsp2013srv1/ or mycompany.sharepoint.com/sites/sapdemo |
Setting | Description | Sample Value(s) |
|---|---|---|
Cont.Rep.ID | The content repository ID matching OAC0 | Z1 |
Disable | The ability to temporarily turn off all usage of the repository ID for ECM usage. | OFF |
Use CMSID | Relevant to ECM only: this uses CMSID (instead of SAPDocID) for all ArchiveLink entries. For all implementations it is highly recommended this be KEPT OFF and shoud only be turned on in Link Enterprise legacy installations if dictated by your Link Enterprise SME. | OFF |
Is ArchiveLink | If this repository ID is a Content Server (ie: not ECM), this must be enabled. *** You cannot share an “Is ArchiveLink” repository ID with an ECM repository ID *** | ON/OFF |
Use Direct API | Future use | n/a |
Req. Location | Determines whether the repository requires location as part of the ECM Processing. Currently all S3 versions require a location. | ON/OFF |
CMS Profile | CMS profile that is relevant to this repository ID. | S3_1 |
CMS Rep/Store | For S3, this is your top-level construct that uniquely determines your online repository. This is a bucket id. | 4123123123 |
Viewer Medium | The method of viewing you would like to utilized. | |
CMS Portal URL | Typically used for specifying viewing URL and future use. Not needed for S3 as the enterprise connector compiles the viewing URL at request time. | N/A |
En. Embedded URL | Use this to prevent user logon to the repository when viewing by using short lived expiring unauthenticated URLs. Currently not available in M365 but expected soon from Microsoft. | OFF |
CMS Use Tag V. | The use tag to be utilized for viewing requests as API calls are required to compile information in order to view content. This is typically a separate Use Tag so that either from the start or in the future you can split viewing off to its own API/RFC destination. | Viewing |
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.