8

Cloud Integration suite to connect external custom... - SAP Community

 7 months ago
source link: https://community.sap.com/t5/technology-q-a/cloud-integration-suite-to-connect-external-custom-website-and-hana-on/qaq-p/13603400
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Cloud Integration suite to connect external custom website and HANA on Cloud

Dear experts,

  We have cloud integration suite (CPI) + HANA on cloud licenses on public BTP cloud and external custom website with Django backend with APIs. 

We would like to know what will be the right approach to consume data from website and save it to HANA DB (Cloud) and vice-a-versa using Cloud Integration suite. Any tips, help, reading material references would be appreciated for further understanding.

Regards,

Accepted Solutions (0)

Answers (1)

Ivan-Mirisola

Product and Topic Expert

Wednesday

Hi @prasad_dix,

An iFlow (integration flow) will often have a message sender system and a message receiver system.

In your case, the receiving system will be your HANA Cloud instance. For that you may integrate it with an JDBC Adapter or by using a specialized HTTP Adapter for OData or REST protocol. If you opt to use the later you could implemented an API using CAP on BTP which will perform all the actions required on your Database - instead of having stored procedures or any complex SQL statements. 

On the other hand, the message sender system can be the system where the need for integrations gets raised. Thus, your originating system will be calling the Cloud Integration iFlow's End-Point with the message payload. For that you can use whatever adapter fits your requirements best. Just remember to create an instance of Cloud Integration Runtime with plan = 'integration-flow' so you are able to call this end-point using OAuth2 Client Credentials authentication flow. 

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/creating-service-instance-and-serv...

You could also use the trigger based integration. So, instead of having a sender system, the iFlow will always kick-start based on a Timer Start Event. Please check the following:

https://help.sap.com/docs/cloud-integration/sap-cloud-integration/define-timer-start-event

There is also the option to develop your integration to use event-based architecture. That will imply that your sender will be a message which should be fetched from a queue. So, every time your integration needs to kick-start, all you have to do is send an event-message to this queue for which your iFlow will be listening to.

Usually this event-message doesn't contain any payload other the the event type and an object reference. This information will then be used throughout the integration flow to perform call-backs to the originating system in order to fetch any additional data for processing and storing it at the Hana Cloud system.

BTP has the Event Mesh service that you can use to implement message queues just for this type of scenario.

Hope this helps clarify a bit.

Best regards,
Ivan 


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK