Escolar Documentos
Profissional Documentos
Cultura Documentos
servlet
container or a j2EE compliant application server. Ex. Apache Tomcat.
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.
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.
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.
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
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
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.
HYBRIS COMMERCE
I. Introduction
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.
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.
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.
Provides
1. Data cleansing
2. Reformatting.
3. Conversion
4. Data Fragments.
Long-term, asynchronous data integration.
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.
V. SMART EDIT
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.
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
METHODS OF INTEGRATIONS
1. Asynchronous Integration
2. Synchronous
3. Mixed.