Deployment options
System Requirements S/4 System
SAP S/4 Release 1709
Web Services on SAP are active and accessible
SAP technical User for Web Service
SAP Workflow user or Workflow is running
SAP User with Development - & Transport Authorization
For User-Defined Fields & Enhancements: SAP User with Developer Key
Remote access to SAP
Remote access to Message Broker Server
Package conditions
Component Category | Alternative Set | Software Component | Release | Package Category | Package |
Required Component Version | Alternatives for S4CORE | S4CORE | 102 |
|
|
| S4CORE | 103 |
|
| |
| S4CORE | 104 |
|
| |
| S4CORE | 105 |
|
| |
| Alternatives for SAP_BASIS | SAP_BASIS | 752 |
|
|
| SAP_BASIS | 753 |
|
| |
| SAP_BASIS | 754 |
|
| |
| SAP_BASIS | 755 |
|
| |
Component Version to Be Deleted |
| PACG | * |
|
|
System Requirements – Cloud Manager
An instance of Windows with .NET 4.7.2 Framework. Windows Server is not needed.
Network connectivity
The following firewall ports have to be opened in order to make E4C work:
SAP -> Message Broker host: one port has to be opened, the port number is arbitrary and it depends on configuration of Message Broker web service. Default 9990
Message Broker -> SAP host: one port has to be opened, the port number depends on SAP Internet Communication Manager Configuration. Default is (8000 + SAP system number).
Message Broker -> Coresuite Cloud host (intranet -> internet): currently one port need to be opened: 443 for HTTPS communication.
Note that although E4C handles bidirectional communication, from the point of view of the network connectivity, all connections between E4C and Coresystems Cloud are outgoing connections. I.e. no inbound connections/ports (from internet to intranet) on firewall need to be opened to enable receiving of inbound messages.