Hybris SAP

32

Click here to load reader

description

Hybris SAP

Transcript of Hybris SAP

  • 1

  • 2

  • 3

  • 4

  • View portfolio slides for details

    5

  • 6

  • 7

  • 8

  • 9

  • 10

  • 11

  • 12

  • 13

  • 14

  • 15

  • 16

  • 17

  • 18

  • 19

  • 20

  • 21

  • 22

  • Master data, i.e. products, prices and modeling data is sent from SAP system to hybris.

    Product Configuration Runtime is deployed to hybris server. The general process from catalog browsing until checkout with creation of the order

    is done according to the scenarios defined for Order Management.

    23

  • Master data, i.e. products, prices and modeling data is sent from SAP system to hybris. Product Configuration Runtime is deployed to hybris server.

    The general process from catalog browsing until checkout with creation of the order is done according to the scenarios defined for Order Management.

    24

  • Product Details Page is enhanced to show a Configure button for all products which are marked as configurable in hybris PCM.

    25

  • Configure Page is newly introduced with the ysapproductconfigb2baddon. The

    page enables customers to configure a product and add the configured

    product to the cart. Detailed explanation of the CMS Component will follow on

    next slide.

    26

  • 27

  • 28

  • 29

  • 30

  • Core+ platform

    most important features of Core+ architecture:

    Similar to Core platform, it has type system (item xml), Persistency layer.

    1. Module independence (each module owns its data and other modules cannot

    break it by modifying its data or services)

    2. New persistence layer with a NoSQL engine for MongoDB

    3. Extensibility and customization options

    Architecture Overview:

    REST WebApp: Exposes the public API as a REST interface

    Facade - Provides a well-defined use case relating the API to the presentation

    layer, decoupled from the Service layer. It will be structured through use cases.

    Usually, the facade is composed of a set of Service layer calls, translating input

    arguments from DTO's to ManagedObjects and the results from

    ManagedObjects to DTOs.

    Service layer: Contains service logic needed to realize business use cases.

    This is the biggest layer and usually is divided into the: Data layer: Defines the domain model as ManagedObjects and data access

    components (Queries, DAOs)

    Services layer: Operates on ManagedObjects

    Persistence: If the service application requires persistence capabilities, it

    should use Kernel components and its PersistenceManager (supports several

    persistency engines MongoDB, NoSQL DBs like Cassandra)

    31

  • 32