Name: Integrating Data in Backoffice Framework in SAP Commerce Cloud
Uploaded: 2021-4-20
Duration: 219 s
Description: In this video, you will learn how to integrate the Backoffice Framework with third-party data layers by implementing Cockpit Data Integration abstraction layer.For more information, visit Cockpit Data Integration Layer of the Backoffice Framework documentation.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><p>In this video, you will learn how to integrate the Backoffice Framework with third-party data layers by implementing Cockpit Data Integration abstraction layer.</p>For more information, visit Cockpit Data Integration Layer of the Backoffice Framework <a href="https://help.sap.com/viewer/5c9ea0c629214e42b727bf08800d8dfa/2011/en-US/8b7e07aa866910149f57b60f4fece66c.html" rel="nofollow noopener noreferrer" target="_blank">documentation</a>. </div></div></div>

Integrating Data in Backoffice Framework in SAP Commerce Cloud

Hi, my name is Lily. In this video, we're going to see how to integrate the back office framework with third party data layers by implementing a cockpit data integration abstraction layer. The back office framework provides generic widgets for working with data, including the ability to perform Crud, create, read, update, and delete operations, modify permissions, and run searches. Examples of such widgets include editor, area, list view, and text search. These widgets are independent from the underlying platform through their use of the cockpit data Integration abstraction layer. While projects may have different subsystem capabilities and may define custom rules in terms of data access. The back office framework provides a layer of abstraction that allows for seamless integration. This is the cockpit data integration abstraction layer. In this video, you'll get some highlights on its capabilities and out-of-the-box provided implementation. The back office framework is designed to be generic and does not depend on any data coming from a particular persistence system. For example, the persistence system within SAP Commerce Platform, one of the key measures of cockpit data integration is its extensibility. You can plug in various strategies to add support for your custom domain model, which is important when integrating with third party systems. Also, in your project's cockpit, data integration can hide the underlying data model's complexity, for example by introducing data transfer objects dittos to hide unnecessary details that are not needed in this layer, as shown in the diagram. The cockpit data integration abstraction layer can be a connection point between generic components or the back office framework, and any data related layer. All standard widgets, like the editor area or the list view, use this mechanism when a new set of strategies is registered. All of the widgets seamlessly integrate and cooperate with the new data layer. Cockpit data integration exposes five complimentary interfaces to the widget layer. They are type facade, which provides type mirror information such as the types, name and attributes with their types and cardinalities. Object facade is responsible for the crowd logic in the picture on the right hand side. You have some of the methods defined by this interface. Fields for each facade allows for execution of searches based on field conditions. Permission facade provides type and instance space. Permission information. Permission management facade allows management of permissions for principals. Cockpit data integration needs all five interfaces to be implemented in order for it to work with the underlying data layer. In this video, you have learned how to integrate back office framework with third party sources of data. You also learned about the strategies provided out of the box to work this data, coming from the SAP Commerce Platform service layer. In addition to that, you gain knowledge to implementing and registering additional strategies, which is a back office specific mechanism and how to make them visible in all of the back office modules within the application. You can get further information, complete diagrams, and a sample of how to effectively declare your custom data access strategy. In the documentation of the cockpit data integration. Thanks for watching.