I am working on a project in which the requirement is to build custom iflows using SAP cloud platform integration and to decommission on-premise SAP Process Integration (SAP- PI). As of today, client landscape has SAP PI as a middleware which is used to perform business data transformation with multiple vendors and customers. The current landscape has an industry standard 3 tier architecture as shown below.
All SAP PI system is using local System Landscape Directory(SLD) and all the development objects are moved to respective environments using Central Transport System (CTS+). This is a traditional taught process which most clients are comfortable but when there is a cloud solution introduced in the landscape there are many changes which need to be adapted with respect to Architecture, Development, and Transports of development objects.
In this blog, I will explain the architecture which is recommended when moving to a cloud solution and also the use of cloud connector in the landscape. When cloud solutions are provided as services means that it is based on a subscription fee. This subscription fee will be per system and depends on the number of cores and memory. In general, SAP production tenant will have 8 core CPU and 16 GB RAM and it is a high availability system which means that customers need not worry about upgrading the patches or version and also downtime for maintenance as they need to do with the on-premise system. SAP will roll out the new functionality to all respective tenant which is available for no extra cost and it is all real time with no downtime.
Note: As of today there are a couple of things which SAP is working to address, First is the disaster recovery for data center and second is an increase in a number of the data centers. They are working with different partners and vendors to address these topics and the update will be available soon.
When moving to cloud solution a 2 tier system architecture is recommended. In which 2 tenants need to be procured one for development which is called NON-PRD tenant and second will be PRD tenant which will be used to run business transactions and one SAP cloud connector (SCC) which can be installed on the separate virtual machine (VM) hosted on premise or can be installed on-premise DMZ.
When procuring PRD and NON-PRD tenant customer have multiple options like choosing less core and memory for NON- PRD tenant which will involve less cost compared to PRD tenant which will have more memory and cores. The project which I am working on, We have mimicked NON- PRD and PRD tenant as the customer was willing to invest some extra cost upfront so that they would have robust cloud systems as they have an intention to move more business to the cloud. Please find below high-level SAP Cloud Connector (SCC) architecture in first screenshot and 2 tier architectural diagram in the second screenshot recommended for HCI-IS cloud solution.
In the above mentioned 2 screenshots, the former is a recommended design for installing the SAP Cloud Connector (SCC) and latter is the one which I have designed for our client's landscape. I will briefly explain regarding the latter which has some uniqueness. If you observe the design it has only one SCC which has been connected to multiple SAP ERP systems. The idea was that client did not want to have a separate installation of SCC as they have to build and maintain multiple virtual machines (VM) for connecting DEV and QA ERP systems for 2 tier architecture for using cloud integration solution. We have used only one SCC and connected multiple ERP systems under destinations so that client will have the flexibility to develop and perform unit testing in the Non-PRD system which is connected to DEV ERP and then perform complete integrated testing using the same tenant and QA ERP system or to receive the data to QA ERP systems.
Note: The cloud connector is recommended when compared to SAP web dispatcher for following reasons. https://blogs.sap.com/2015/07/13/cloud-connector-a-brief-guide-for-beginners/. This blog also provides steps to install and configure SCC which is very well explained.
Some of the highlights of SAP Cloud Connectors (SCC). Below points are referenced from SAP.
Hope this information provides a high-level idea about SCC and also recommended 2 tier architecture when migrating to cloud solutions!
See you next blog!
All SAP PI system is using local System Landscape Directory(SLD) and all the development objects are moved to respective environments using Central Transport System (CTS+). This is a traditional taught process which most clients are comfortable but when there is a cloud solution introduced in the landscape there are many changes which need to be adapted with respect to Architecture, Development, and Transports of development objects.
In this blog, I will explain the architecture which is recommended when moving to a cloud solution and also the use of cloud connector in the landscape. When cloud solutions are provided as services means that it is based on a subscription fee. This subscription fee will be per system and depends on the number of cores and memory. In general, SAP production tenant will have 8 core CPU and 16 GB RAM and it is a high availability system which means that customers need not worry about upgrading the patches or version and also downtime for maintenance as they need to do with the on-premise system. SAP will roll out the new functionality to all respective tenant which is available for no extra cost and it is all real time with no downtime.
Note: As of today there are a couple of things which SAP is working to address, First is the disaster recovery for data center and second is an increase in a number of the data centers. They are working with different partners and vendors to address these topics and the update will be available soon.
When moving to cloud solution a 2 tier system architecture is recommended. In which 2 tenants need to be procured one for development which is called NON-PRD tenant and second will be PRD tenant which will be used to run business transactions and one SAP cloud connector (SCC) which can be installed on the separate virtual machine (VM) hosted on premise or can be installed on-premise DMZ.
When procuring PRD and NON-PRD tenant customer have multiple options like choosing less core and memory for NON- PRD tenant which will involve less cost compared to PRD tenant which will have more memory and cores. The project which I am working on, We have mimicked NON- PRD and PRD tenant as the customer was willing to invest some extra cost upfront so that they would have robust cloud systems as they have an intention to move more business to the cloud. Please find below high-level SAP Cloud Connector (SCC) architecture in first screenshot and 2 tier architectural diagram in the second screenshot recommended for HCI-IS cloud solution.
In the above mentioned 2 screenshots, the former is a recommended design for installing the SAP Cloud Connector (SCC) and latter is the one which I have designed for our client's landscape. I will briefly explain regarding the latter which has some uniqueness. If you observe the design it has only one SCC which has been connected to multiple SAP ERP systems. The idea was that client did not want to have a separate installation of SCC as they have to build and maintain multiple virtual machines (VM) for connecting DEV and QA ERP systems for 2 tier architecture for using cloud integration solution. We have used only one SCC and connected multiple ERP systems under destinations so that client will have the flexibility to develop and perform unit testing in the Non-PRD system which is connected to DEV ERP and then perform complete integrated testing using the same tenant and QA ERP system or to receive the data to QA ERP systems.
Note: The cloud connector is recommended when compared to SAP web dispatcher for following reasons. https://blogs.sap.com/2015/07/13/cloud-connector-a-brief-guide-for-beginners/. This blog also provides steps to install and configure SCC which is very well explained.
Some of the highlights of SAP Cloud Connectors (SCC). Below points are referenced from SAP.
- Establishes a secure SSL tunnel between SAP Cloud Platform and on-premise systems.
- Creates connectivity through an on-premise agent by the reverse-invoke process.
- Safeguards against forgeries by supporting a preconfigured destination API and certificate inspection.
- Is appropriate for both on-premise and cloud landscapes.
Hope this information provides a high-level idea about SCC and also recommended 2 tier architecture when migrating to cloud solutions!
See you next blog!
- SAP Managed Tags:
