Jedox Production Cloud uses third-party “public” cloud infrastructure providers such as Amazon Web Services (AWS), Microsoft Azure, and ProfitBricks.
When using AWS, the recommended setup for connecting the Production Cloud environment with an on-premise SAP system would look similar to Figure 1 – Single VPN Connection, as described in this AWS document: http://docs.aws.amazon.com/
Your cloud environment will be connected via Virtual Private Gateway on the Jedox Cloud side to a VPN gateway on your corporate side. The list of protocols needed to be supported by gateway on your side can be found here: http://docs.aws.amazon.com/
AmazonVPC/latest/ NetworkAdminGuide/vpc-nag.pdf# CGRequirements
Some of the devices officially tested by AWS can be seen here: http://docs.aws.amazon.com/
AmazonVPC/latest/ NetworkAdminGuide/vpc-nag.pdf# DevicesTested This is the recommended way of doing things when using AWS. AWS also supports AWS Direct Connect, i.e. “stretching cable from your office to AWS”.
Once a VPN connection between Jedox Production Cloud and an on-premise data center is established, one has to make sure the internal SAP system is reachable for the outside system. The following SAP document lists ports that are required to be open/accessible on the SAP side from an external—in this case Jedox—system: http://wiki.scn.sap.com/wiki/
display/TCPIP/Application+ Server+ABAP In our case, “External Ports” and the first 3 entries are relevant.
Was this post helpful?