Connect SAP Business One using Service Layer (HANA)


Published on

We recently had a webinar on “Connect SAP Business One with third party apps using Service Layer (HANA)” on 28th of September. The webinar was a great success. The points which were covered in the webinar includes the following:
• Service Layer Architecture: The protocols and Usages.
• How service layer communicates with SAP B1.
• Creating a 3rd Party communication channel to send / receive data using .NET
• Why and when to use Service Layer?
• Architectural differences between DI Server and Service Layer

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Connect SAP Business One using Service Layer (HANA)

  1. 1. Connect SAP Business One with Third Party Apps WEBINAR BY: using Service Layer (HANA)
  2. 2. PRESENTED BY Abhishek Sur Software Architect, InSync Tech-Fin Solutions Ltd. Microsoft MVP
  3. 3. Agenda • Overview • Why Service Layer? • Architectural differences between communication channels • When do we use Service Layer • Connecting SAP Business One and retrieving objects using basic HTTP tools • Demonstration using .NET Client • References
  4. 4. Overview
  5. 5. • Service Layer is an extension to SAP Business One to expose data and objects of SAP to external world. • Service Layer is built as a Web Component following HTTP protocol, more specifically Odata. • Open data standard enables SAP Business One objects to be consumed using basic HTTP methods and also opens wide range of tools to consume data. • Service Layer runs on SUSE Linux Enterprise Release 11 SP2, 64-bit edition. It is an application server built on the Apache HTTP Web server. The required database backend is SAP HANA Platform Edition 1.0 SPS 07 Rev74 Service Layer
  6. 6. Why Service Layer?
  7. 7. • Service layer is the code component to communicate with SAP Business One. • It is built using standard ODATA formats. • It directly communicates with SAP Business One Core, and hence best when throughput is concern. • Service Layer is built keeping data integration in mind. • Service Layer supports WCF Restful services and hence can be consumed with WCF tools • Many 3rd party libraries are built on top of SL to build communication channel with SAP Business One. Features
  8. 8. • Service Layer has a 3-tier architecture: the clients communicate with the Web server using HTTP/OData, and the Web server relies on the database for data persistence. • Service Layer API and DI API have identical definitions for objects and object properties, smoothing the learning curve for developers who have already acquired DI API development experience. • The OData Parser looks at the requested URL and HTTP methods (GET/POST/PATCH/DELETE), translates them into the business objects, and calls each object's respective method create(Add) /retrieve(GetByKey) /update (Update) /delete(Delete) (CRUD) operations. In reverse, the OData Parser also receives the returned data from business objects, translates them into HTTP return code and JSON data representatives, and responds to the original client. • The session manager implements session stickiness, working with the Service Layer load balancer, so that requests from the same client will be handled by the same Service Layer node. Insights
  9. 9. Architectural Comparison
  10. 10. Architectural Comparison
  11. 11. Architectural Comparison
  12. 12. Scalability and High Availability Source : Business-One-Service-Layer_Trinidad_Martinez.pdf
  13. 13. • When you cannot use COM interfaces of DI Server component. • When your application need to have scalability and portability. • Outside your home network. • Require HTTP standards while communication • Need to use your existing toolsets for communication • Less learning curve • Uniform way of representing structured data : ATOM, JSON • Enhanced documentation When do you use Service Layer?
  14. 14. Source : Business-One-Service-Layer_Trinidad_Martinez.pdf OData Key points Any Odata client can access data provided by any data source
  15. 15. Connecting SAP Business One and retrieving objects using basic HTTP tools DEMO
  16. 16. Creating .NET Application DEMO
  17. 17. For more info, visit: Smart Integration Solution for your business APPSeCONNECT is a robust platform which connects ERP (Like SAP Business One, SAP ECC, etc.) with various Ecommerce, Marketplace and CRM Applications.
  18. 18. • Documentation at https://<servername>:<loadbalancerPort>/ • Service Layer and Integration for 3rd party applications • Accessing SAP B1 Service Layer via WCF • Accessing SAP B1 Service Layer via Typescript • Script Engine for SAP B1 Service Layer • Developing extension using Javascript and SAP B1 Service Layer • B1 Sample payloads for CRUD • SAP B1 Service Layer implementation using Javascript (Youtube) References:
  19. 19. Time for Q&A
  20. 20. Thank you For more such webinars, visit: /appseconnect /company/insync