System Requirements

the middleware component (enterprise connector) can be deployed on premise, in a private cloud or as a fully managed service from gimmal when deploying on premise or in a private cloud environment, physical or virtual hardware is supported the following server resources are the minimum requirements operating systems cpu disk space ram java runtime environment sapjco windows server 2016, windows server 2019, windows server 2022 (x64) minimum 2 cores or 2 physical cpus with at least 2 0ghz 40 gb 8 gb jdk 1 8 (x64) 3 1 and above (jco 3 1 requires the microsoft visual studio 2015 2022 c/c++ runtime libraries ) see https //me sap com/notes/2786882 https //me sap com/notes/2786882 when deploying on premise or in a private cloud environment, physical or virtual hardware is supported the following server resources are the recommended requirements operating systems cpu disk space ram java runtime environment sapjco windows server 2016, windows server 2019, windows server 2022 (x64) minimum 4 cores or 2 physical cpus with at least 2 0ghz 128 gb 64 gb jdk 1 8 (x64) 3 1 and above (jco 3 1 requires the microsoft visual studio 2015 2022 c/c++ runtime libraries ) see https //me sap com/notes/2786882 https //me sap com/notes/2786882 production/non production environments sap typically follows a 3 tier landscape development (dev) quality assurance (qual) production (prod) albeit link enterprise supports a 1 middleware to \<n> sap connection, it is recommended to have 1 middleware environment (separate windows machine/vm) for each sap system ie most common is 3 separate windows machines/vm's a development can be minimum server requirement specs if desired b we recomend qual be identical to production (recomended requirement specs) reasons why you may choose to share the dev and qual sap connections to a single non production midldeware server instance low volume and load no migration testing little or no concurrent "inbound to sap" processing where you might want some event to go up to both dev and qual sap at the same time enterprise connector middleware service the gimmal link enterprise middleware service requires read/write permission to the gimmal link enterprise installation root directory and sub directories this can be accomplished via two methods based on your server configuration running as local host a specified service account where local host does not have read/write permissions sap firewall access the gimmal link enterprise content server application communicates via http/https and can be configured to use any port number the gimmal link enterprise content server application communicates via http/https and can be configured to use any port number (ex 8085) (inbound to middleware and outbound from sap refer to organizations internal it security and project team on which ip address to allow) note that each sap repository (z1, z2, etc) requires its own set of ports, for example z1 1 unique port for http eg 8085 1 unique port for https eg 8086 z2 1 unique port for http eg 8087 1 unique prt for https eg 8088 the gimmal link enterprise ecm application communicates via sap jco over the following ports gateway port the port number used to communicate with the gateway typically 33## with the ##’s being the system number (ex 3300) (inbound to sap) message server host (if applicable) the port number used to communicate with the gateway typically 36## with the ##’s being the system number (ex 3600) (inbound to sap refer to organizations internal it security and project team on which ip address to allow) confirm with your sap basis team for the values specific to your sap installation url and firewall configuration for m365 api access access to the following urls is required from the server base url \<your sharepoint site(s)> source the ip of the gimmal link enterprise server port https is 443 protocol https this provides the basic functionality that link enterprise requires for its processing