You are on page 1of 6

Hybris is a java based system, runs within the Java Virtual machine system on a

servlet
container or a j2EE compliant application server. Ex. Apache Tomcat.

Hybris comes pre-bundled with an optimized version of Apache Tomcat including


relevant caching and persistence mechanism.

B. Platform

The core platfom is the basis of SAP Hybris, offering the services and
functionality needed to run
and operate the suite. The platform layer abstracts the various data and
functionalities streams
into discrete units and exposes them to higher layers of the suite. An example of
this is the
Persistence layer that handles database access and caching.

Important: Core or platform should never be altered, instead extensions and


customizations
should be made in line with Hybris best practices. Example /custom

C. Extensions

Bundles of functionality that are ready to use and leverage by the developers in
the
SAP Hybris eco system.

Can be used singularly but often have interdependence, being strongly leveraged in
accelerator offerings.

Allow for extensive customization and abstraction with the Hybris Suite.

D. APIS

The APIS are subject to continuous update but some commonly used APIS are
ServiceLayer API,
WebServiceLaye API, WebService API, and Virtual JDBC API.

The Hybris Web service framework is based on the ReSTful architecture, thereby
providing
secure CRUD access to all models in the ServiceLayer over a widely adopted
protocol.
An example of this is the mobile app.

E. ACCELERATORS - Signficant selling point.

A company can develop within less than a day and astorefront in less than a week.

Out of the box, ready to use collection of extensions and functionality that create
a basic
building block for use in a project. Eg. A B2C Storefront.

Allow for extremely fast development cycles and adhesion to the best practices.

Use is not Mandatory and Flexibility allows a project to pick and choose from
examples shipped with SAP Hybris.

F. FrontEnd
At the very top level is the look and feel exposed to end users either via
storefronts
or cockpits.

The Spring MVC is the core technology in use here, but Hybris allows for easy
integration to all
modern web design frameworks. Eg. Angular JS, Infact, SAP Hybris can be abstracted
to an entirely
different framework and service, only using webservices to SAP Hybris for content
retrieval.

Hybris uses the Model, View and Controller design paradigm of Spring to present the
frontend to
the end user.

a. Model - Manages data, logic and rules of the application.


b. View - The output representation of the information from the Model. eg. Display
a grid of
products to the end user from the data returned.
c. Controller - Accepts input and converts to commands fro both the Model and or
the View to
leverage.

G. SAP Hybris Layers

1. Presentation Layer
- Composed of: Servlet Components, Spring MVC and View
- Object Form: Represented as a user would interact with them.

2. Service Layer
- Composed Of: The Java Application Programmer's interface (API) for objects in
SAP Hybris Commerce, the Hybris API via POJOs.

Object Form: Java Classes and Code using the Hybris API.

3. Type Layer

Composed of: Definitions of business objects(Types) and their fields (Attributes)


made
via the items.xml and associated XML files.

Object Form: Items and Associated Data in XML representation.

4. Persistence Layer
Composed of: Creates an abstraction from the database for data persistency and
caching.
This layer is largely transparent but should never be circumvented. Ie. Direct SQL
access via Java
Code.

Object Form: Data is represented and passed in an SQL compliant manner to the
underlying suite
datbase.

F. SPRING FRAMEWORK

The Spring Framework is an application framework and inversion of control container


for
the Java Platform.
An open source and widely supported framework, maintained by Spring Source.
Hybris makes use of the majority of Springs Paradigms and effective development in
Hybris
is dependent on the understanding the framework.
The most important topics for review if developing are:

1. Dependency Injection - used heavily, provides better decoupling and improves


testability (also known as Inversion of Control ).
2. Aspect Oriented Programming - not used by default, but usable for extending
areas that aren't
customizable by default or when implementing cross cutting concerns.
3. Spring MVC - request based framework used n the accelerators and end user
display operations.
4. Spring Security - used for authenthication and basic authorization.

G. CONFIGURING SAP HYBRIS

local.properties is the center of configurations for SAP Hybris.

Editable in any text editor, parameters are stored on each line with do and equals
notation:

solrserver.instances.master.autostart=true
solrserver.instances.master.mode=standalone
solrserver.instances.master.hostname=localhost
solrserver.instances.master.port=8983
solrserver.instances.master.memory=512m

Parameters are read at startup only, changes made during runtime will not be
reflected but
most can be changed in hAC temporaily.

Located in the hybris/config folder and supercedes project.properties in the core


files.

HYBRIS COMMERCE

I. Introduction

Functionality is packaged as modules


1. Leverage the platform
2. Enrich the platform capabilities

WCMS module is packaged designed for web content management


a. Business user interface
b. Content libraries with templates and components

II. ACCELERATORS
Accelators are ready to use commerce solution tailored for
B2C and B2B.

Industry Specific
a. Finance b. Telco c. Travel
Specific Accelator for China.

Whats great about Accelerators?

These accelarators can be used such that they can match 80% of the
requirements of the customer. They come with storefronts that can be
easily rebranded to suit your needs.

The stroefront has already business logic and functionality already


implemented such as search, cart, checkout and more.

With every accelator it offers you the synergy of


1. Platform
2. Product Content Management.
3. Web Content Management.
4. Customer Service Capabilities
5. Order Management
6. Store Locator.
7. Search and Navigation.
8. Payment and Reporting.

You can use the logic as is or customize them to your needs!


B2C Accelarators come with two sample storefronts

1. Apparel and Electronics each implementing B2C functionality.


The checkout functionality is already built in in the functionality
of the b2c site.

B2B
Includes all the B2C Functionality
Added capabilities specific to a B2B Environment
1. Spend Control
2. Order Approval
3. Replenishment
4. Organization Management.
5. Customer Account Management.
6. Quote Negotiation
7. Volume Pricing Control
8. Future Stock Availability Service
9. Punch Out Functionality, integrated with Ariba.

III. DATA IMPORT

Data Hub is not part of any accelerator but must be licensed


seperately.

Data HUB - allows you to integrate with any other system.


Full control over your data.

Provides
1. Data cleansing
2. Reformatting.
3. Conversion
4. Data Fragments.
Long-term, asynchronous data integration.

Cockpits and BackOffice

Product Cockpit is used to administer product related information.


Offers two perspective

a. Product Perspective
b. Catalog Perspective

There are two versions staged version and the online version where the changes
are published and made available.

IV. WCMS

WCMS is build for web content managers. The hybris wcms cockpit is built for
webcontent managers. It can publish content across different channels and devices.
This where we can manage all of my website pages. This is how ew can change
the content on stores.

The padlock components are used by multiple pages simulteneously. It is a sign


changes here would affect all pages.

The admin can do everything.

Go to WCMS Component which holds the navigation components.

V. SMART EDIT

Introduced in Commerce 6.0 based on cockpit and G that allows editing


website content. Users can do tasks like drag and drop. Select from a variety of
components. You can also edit components directly in context.

VI. BackOffice

Allows access to functions depending on the user role. A user can have access
to one or more based on the account permissions. The Admin perspective is for more
technical users.

a. Support Module
b. Admin Module

SYSTEM INTEGRATIONS

THe SAP ERP and ERP CRM backend integration provides integration to ERP to hybris
commerce front end. It allows customers to extend sales channels.

IT uses master data available on ERP backend.

It takes advantage of standar order fulfillment process from ERP/CRM


it enables you to safeguard existing investment in ERP and CRM solutions and
reduces
implementation cost for Commerce
Accelerates time to value.

CPQ
Allows customer to sell configurable to setup and manages those configurations.
It enables cars and accesories and engines
Using WCMS to setup manager configurations
CPQ used in B2B

WHEN SAP MARKING is used

Extend your sales cannels by using Commerce


Reuse Marketing segmentation target groups and product recommendations.
C4C
Provides best in class sales support and service.
Synchronize customer dat aand ticket information.
Connect customers with support agents.
Use assisted service module in Commerce directly from C4C.

Customer Activity Repository


- Provides B2C Customers with complet view of purchase history.
- Collects data from various channels
- When inegrated with ERP and COmmerce allows to see additional purchases in the
online store order history.

METHODS OF INTEGRATIONS

1. Asynchronous Integration
2. Synchronous
3. Mixed.