Building enterprise digital application using SAP Integration Suite
SAP Integration Suite is a versatile, dynamic and enterprise-grade iPaaS (integration platform-as-a-service) from SAP that simplifies and accelerates enterprise integration and helps organizations to quickly transition to becoming intelligent enterprises. It is an open and modular iPaaS supporting a comprehensive set of end-to-end integration scenarios. Integration scenarios represent the customer-jobs-to-done, the modular set of integration services work together in cohesion to support these customer scenarios. More details on SAP Integration Suite is covered in this blog from Harshavardhan Jegadeesan .
In SAP Integration Suite we have services like Open Connectors which provides feature rich pre-built connectors to 160+ non-SAP cloud applications and API Management which enables our customers to manage the end to end API life cycle with secure access to the data and process using API Security best practices. Click here to view all the integration scenarios and services supported by SAP Integration Suite.
In this blog series we focus on a specific customer integration job to be done, which is of building an enterprise grade digital applications combining data from SAP and non-SAP applications.
For building this scenario, we would using Open Connectors to access data from non-SAP application using harmonized APIs from CRM Hubs. This harmonized APIs would be managed by API Management where all the security best practices and governance policies would be applied. Finally we will be building a Fiori application to display this harmonized data from any of the non-SAP CRM applications of your choice. A high level solution blue-print of this sample application is captured in the below figure.
Part 1: Use Common Resource templates for Harmonized APIs to non-SAP CRM Hubs
Common Resources provide a canonical data model view of your data objects eliminating the need for point-to-point mapping of data to each and every new application. This enables you to keep the application code clean and simple. Since the Common Resources are exposed as APIs you could use the common resources in an application of your choice whether it is a Fiori based Web application or your mobile application enabling you to re-use your mapping across multiple application and integration scenarios.
Refer this blog to use a common resource template named basic-companies to connect to a non-SAP CRM Hub of your choice.
Part 2: Manage APIs from non-SAP CRM Hubs using SAP Cloud Platform API Management
API Management drastically reduce the time to build application and integration in addition to guaranteeing the benefits of security, traffic management and deep-analytics. It reduces complexity by leveraging a single provisioning platform (API Platform) to provide unified access and governance of APIs across a heterogeneous landscape. SAP Cloud Platform API Management also enables you to share digital assets and engage with developer, partner communities to consume these assets in new channels, devices and user interfaces.
The Open Connectors API Provider in API Management enables you to discover and manage the APIs from non-SAP ecosystem maintained in your Open Connectors tenant.
Refer this blog to use Open Connectors provider to seamlessly manage any non-SAP APIs from the CRM Hubs.
Part 3: Build Fiori application connecting to non-SAP applications
Application developers can quickly build extensions application (such as for Line of Business applications), mobile applications or web applications by consuming the SAP Cloud Platform API Management managed APIs directly from SAP Cloud Platform Web IDE or iOS SDK Assistant.
Refer this blog to build a Fiori application connecting to any non-SAP APIs from the CRM Hubs via the harmonized APIs.
Finally, SAP Integration Suite is a cohesive Integration Suite on the cloud to simplify integration for our customers by combing together the right set of services. To learn more about SAP Cloud Platform Integration Suite, visit us at SAP Community.
On the Cloud Platform I have the subscription for SAP Cloud Platform Open Connectors - However when I click on go to application I get the following error
I''am following the Open SAP course but using the current hana cloud version. Another question I have is in the process integration runtime or in Process Integration- I dont find sap cloud process integration advisory
in Process Integration I have tenant details and Enterprise messaging
For Open Connectors trial environment we are facing issue with new users on-boarding and our product engineering team is working with priority to fix the issue.
We expect this issue to be resolved soon.
Thanks and Best Regards,
thanks for the Inio - I was trying out timer example from this open sap course
I find that it is missing records in the output - For example, I was expecting 5 records I was getting
3 - This appears to be a bug - if this is the case can you forward it to the appropriate team.
Another issue with the following
Simplify Integration with SAP Cloud Platform Integration Suite
Week 2 Unit 7: Expose Back-End Services as
When I deploy I get the following error is this a system issue that is currently being worked on?
ProcessWorkerDeployResponses >> 15:03:08.884 [itcoMEDIUM62] ERROR - (deployPostProcess) Failed DeployTask: d53d1476-1bed-4d51-9efd-61b0b4cdf738 java.util.concurrent.CompletionException: com.sap.it.co.api.types.CoException: Did not receive response from Generation and build service for deploy contextId: d53d1476-1bed-4d51-9efd-61b0b4cdf738, tenant: testprocess, artifacts:[f4935e3b-31bb-444b-ab02-c2e3b46ed16e] at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273) at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280) at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:618) at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:591) at java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:456) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:836) Caused by: com.sap.it.co.api.types.CoException: Did not receive response from Generation and build service for deploy contextId: d53d1476-1bed-4d51-9efd-61b0b4cdf738, tenant: testprocess, artifacts:[f4935e3b-31bb-444b-ab02-c2e3b46ed16e] at com.sap.it.co.core.task.DeployTaskMaker.handleGbResponseEvent(DeployTaskMaker.java:353) at com.sap.it.co.core.task.DeployTaskMaker.lambda$addGbStage$15(DeployTaskMaker.java:208) at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:616) ... 9 common frames omitted ProcessWorkerDeployResponses >> 15:03:08.904 [itcoMEDIUM62] INFO - (deployPostProcess)(task d53d1476-1bed-4d51-9efd-61b0b4cdf738) Completed in time 20
It is great to see that you are trying out the Simplify Integration with SAP Cloud Platform Integration Suite openSAP course.
For the issue faced while trying out the openSAP course, it would be great if you could post it as an question in this SAP Cloud Platform Integration Suite community page.
Thanks and Best Regards,