Shulou(Shulou.com)05/31 Report--

This article analyzes "how to achieve a horizontal comparison between Hybris service layer and SAP CRM WebClient UI architectures". The content is detailed and easy to understand, and friends who are interested in "how to achieve the horizontal comparison of Hybris service layer and SAP CRM WebClient UI architecture" can follow the editor's train of thought to read it in depth. I hope it will be helpful to everyone after reading. Let's follow the editor to learn more about "how to compare Hybris service layer and SAP CRM WebClient UI architectures horizontally".

I understand the HYBRIS services layer as the API layer of CRM WebUI.

Hyberry ServiceLayer is an API used to develop services for SAP Hyberry Commerce.

It provides many common services while allowing you to extend these services or develop your own services.

The main features of ServiceLayer are:-I compare it with the CRM WebUI framework one by one.

(1) based on service-oriented architecture.

The soa architecture in hybra is different from BYD, which supports different deployment units to be deployed on different servers, and cross-unit applications communicate through Message.

Hybra is a monolithic application where all extensions physically run on one server, one Session (regardless of cluster mode).

(2) Business logic and persistence logic are completely separated.

CRM WebUI is also satisfied.

(3) to provide a number of services, each with clear responsibilities.

(4) this description is so generic that a Layer in most Framework should be satisfied.

(5) it provides a framework for developing your own services and extending existing services.

CRM WebUI's API and Genil Layer also support extensibility.

(6) based on the Spring framework to a large extent.

This is the feature and strength of HYBRY, holding the thighs in spring.

(7) based on common patterns such as interface-oriented design and dependency injection.

CRM WebUI is also satisfied.

(8) it is the layer at which partners should implement their business logic.

CRM WebUI is also satisfied.

(9) it provides hooks to model lifecycle events to perform custom logic.

There is no Build in ABAP, and there is no need to perform POST operations when the class is activated.

There are no such use cases.

(10) it provides hooks to system event life cycle events, such as initialization and update processes.

CRM WebUI is also satisfied.

(11) it provides a framework for publishing and receiving events.

Event Subscription and Issue, which are widely used in CRM WebUI, are CL_CRM_BOL_ENTITY_COL 's FOCUS_CHANGED events.

The client in the figure above is the general name of these four entity:

(1) Page Controllers of an MVC framework

(2) Web Service clients

(3) Scripts

(4) Other services

Three types of service:

(1) Business Services implement business use cases, such as cart handling or back order.

(2) Infrastructure Services provide the underlying technical foundation, such as internationalization, import, export, and so on.

(3) System services provide functionality required by the ServiceLayer, such as model handling and session handling.

On how to achieve the horizontal comparison of Hybris service layer and SAP CRM WebClient UI architecture to share here, I hope that the above content can make you improve. If you want to learn more knowledge, please pay more attention to the editor's updates. Thank you for following the website!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.