RFC Destination (Outbound Rule) - ECM Only
At least 1 RFC destination is required for ECM integration. This must match the RFC created in SAP (refer to Configure SAP RFC destination). This is a 1 to 1 relationship with RFC's configured in SAP for Link Enterprise integration.
- Navigate to Mappings->RFC Destinations tab in the Enterprise Connector.
- Choose Add Row
- Configure the below fields:
Setting | Description | Sample Value(s) |
|---|---|---|
Enabled | Turns RFC destination on or off | true |
IncludeSubFolders | Not applicable to M365 | false |
ErrorifDuplicate (Box) | For Box only: if same filename being created, error (enabled) or overwrite/version (false) | true |
Rename On-Duplicate (SP Online) | For M365 only: if same filename being created, rename automatically (_1, _2, etc) (enabled) or overwrite/version (false) true | true |
Enable GUID ON Filenames (SP Online) | For M365 only: append unique GUID onto filename every time (no duplicate check) | false |
CMS name | The CMS system to connect to | M365_DEV |
SAP name | The SAP system to connect to | SAPDEV |
RFCDestination | The RFC configuration in SAP (must match) | Z_CMSAPI_01 |
Server Count | How many connections per RFC destination *increase this number if the number of simultaneous RFC calls is being approached / throttled | 30 |
MaxResults | An optional setting to limit the number of entries returned when searching for documents.
A setting of 0 has no limit (limit set by Graph API). | 0 |
Working Directory | temporary directory ** must contain double slashes | c:\\<middleware installation directory>//tmp |
*the Windows service must be restarted for changed to take effect