System Requirements SAP System
SAP ECC Release 6.0 SP 19 or higher
SAP Netweaver 7.0 SP 14 or higher
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
System Requirements – Message Broker
Any Windows Server with .NET 4.7.2 Framework
RAM: minimum 1 GB allocatable
HDD: the program itself has minimal disk space requirements. What can grow big and quickly take several gigabytes are the log files. Therefore 50GB above the system requirements are recommended. Log files retention policy should be considered and implemented to keep the HDD requirements lower
remote access: installation and administration of Message Broker requires a (remote or physical) access to the machine, with administrative rights (necessary to install/update program binaries and start/stop windows service)
Network encryption and the (lack of) maintenance of certificates and algorithms to do those can cause connectivity issues. Note that especially root certification authorities should be updated regularly. In case of connection issues to FSM Cloud due to untrusted TLS certificate please refer to the following SAP note: https://launchpad.support.sap.com/#/notes/2943007.
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 ECC -> Message Broker host: one port has to be opened, the port number is arbitrary and it depends on configuration of Message Broker web service.
Message Broker -> SAP ECC host: one port has to be opened, the port number depends on SAP Internet Communication Manager configuration. Default for HTTP is (8000 + SAP system instance 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 Coresuite 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.