Actions

Landscape components of SAP Cloud Platform Integration

January 13, 2015 | 2,543 Views |
Follow

Hello Colleagues !

 

In this blog, we shall look into the components of an SAP Cloud Platform Integration(f.k.a HCI) landscape. This blog is part of the architectural overview of SAP Cloud Platform Integration. You can find all the blogs over here.

 

SAP Cloud Platform Integration Nodes

 

At the core of SAP Cloud Platform Integration are integration nodes that run on the SAP Cloud Platform . Each node is a virtual machine instance. We have two types of nodes and each node performs a different function.

 

A worker node performs all the message processing while a tenant management node functions as a supervisor for the worker nodes. Tenant Management Nodes can bring up worker nodes, ensure it is up and running all the time, and keeps a repository of all your integration artifacts. You can picture the node architecture like the one below:

 

Node_Architecture.png

 

The simplified diagram maps to the following view that you shall see in the Node explorer:

 

Node_Architecture_Mapping.png

SAP Cloud Platform Integration Components

 

All components that make up the SAP Cloud Platform Integration is given below –

 

  1. An Eclipse based tool-set allows integration developers to create and model integration flows. The Eclipse-based tool-set also provides integration administrators tools to administer and monitor the integration flows. (Integration flows are visual-based artifacts that an integration developer models)
  2. A Web-based IDE provides you the tool-set quickly configure and deploy integration flows.SAP Cloud Platform Integration comes with a host of pre-packaged integration flows that you can discover using the Web-based IDE. Discover the integration flows for your requirement, configure them for your requirements, and deploy them to the runtime.
  3. Integration Nodes that house a powerful, secure and scalable runtime – and a repository to store the cloud artifacts.

Technical_Overview.JPG

Best Regards,

Sujit

To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  4. Thierry CRIFASI

    What is the recommended number of HCI tenants when integrating SAP C4C and ECC with a 3 tier landscape (DEV/QA/PRD)?

    How many HCI tenants are included in the HCI license? C4C provides 2 tenants (TEST/PROD).

    Regards

    (0) 
    1. Sujit Hemachandran Post author

      Hi Thierry,

      For HCI that is bundled along with the C4C application, two tenants are provided. Customers use Dev & QA with one HCI test tenant, and the other for connecting to PROD. You have the option to buy a single HCI tenant, too – so customer insisting on a 3-tier landscape can do so.

      Thanks and Regards,
      Sujit

      (0) 
      1. Thierry CRIFASI

        Thanks for your reply. For what reasons would a customer require a 3rd HCI tenant? My understanding is that you can have several copies of the same iFlow within the same HCI tenant.

        (0) 
        1. Sujit Hemachandran Post author

          Yes, you can have several copies of the iflow in a tenant. And that is how many customers use it. The reasons for using a 3rd HCI tenant exist where in some customer sites they have different teams for Dev and QA – and they enforce stricter access controls. Dev teams do not have access to the QA tenant.

          (0) 
  7. SRI RAM

    Hi Sujit,

    Hope you are doing good.

    Above screenshot is from HCI overview documentation.

    Is there any limitations on number of Iflows that can be deployed in each versions of HCI?

    What is the Connection row refers? E.g., For the professional edition it is mentioned like Connections 25 and Unlimited connectivity: Any to Any.

    Is that mean we can only deploy 25 iflows in the tenant? If yes, if we deploy more than that what will be the cost for additional iflows.

    Any links/ pricing documents will be really helpful.

     

    Thanks and Regards,

    Sriram

     

    (0) 

Leave a Reply