Hybris Architecture

Basic Architecture
From a business point of view, the hybris Commerce Suite is divided into individual packages, such as
Commerce, Content, Channel, and Orders. These packages are bundles of functionality assembled
for a certain range of business functionality. All of these packages rely on more basic functionality
provided by the hybris Platform. While the hybris Platform can run without any package, no package
can run without the hybris Platform.
Figure: The hybris Commerce Suite diagram

From a more technical point of view, packages consist of individual modules (also referred to
as extensions). For example, the hybris Print technically consists of two extensions: Print (the
technical foundation) and Print Cockpit (the graphical user interface).
Extensions are written by hybris or the implementation partner of your project. Extensions written by
hybris provide standardized functionality and are supported and maintained by hybris. If you write an
extension, you need to maintain them by yourself, but you are free to implement any business
functionality you need. A full hybris Commerce Suite installation therefore consists of the hybris
Platform plus any hybris packages plus any additional extensions that you have implemented.
Extensions that are part of hybris Platform proper are also referred to as the core extensions. On top
of these core extensions, hybris Platform contains several pieces of hybris software, such as the Build
Framework, and third-party software, such as the pre-bundled Apache Tomcat.
hybris Commerce Suite is run in a Java Virtual Machine on a Servlet Container or a J2EE-compliant
application server (such as IBM Websphere or Oracle WebLogic) and connects to an external
database (MySQL, Oracle DB, Microsoft SQL Server). Internal caching and persistence mechanisms
allow the hybris Commerce Suite to run on a Servlet Container. A full-fledged J2EE-compliant
application server can be used but is not necessary.
Figure: A technical view on the basic architecture of a hybris Commerce Suite installation.
The hybris Platform layer abstracts data from the storage structure on the database using the
persistence framework and provides functionality such as Clustering and the hybris Platform Cache.
Relying on the persistence framework, the other functional components of the Platform Layer provide
basic business functionality: Transactions, CronJobs, Personalization, Internationalization, and more.
The packages on the Functional Layer (hybris Commerce, hybris PIM, hybris Print) use the hybris
Platform to implement the functions they deliver. Actually, hybris Platform is part of any hybris
Package.
Layer Architecture
The hybris Commerce Suite contains several layers, each of which has a different function and data
abstraction level.
Figure: Overview of the architectural layers of the hybris Commerce Suite.
Layer
Name
Description
Cockpits,
hmc,
WebServi
ces
This is where objects

are represented in a
way that an end-user
can interact with
them: add products
to a cart, edit a
product description,
or set a password for
a user account, for
example. On this
layer it is possible to
let a user do
something with an
object in the hybris
Platform via a
graphical user
interface.
What would a Product look like on this Layer?
Functionality on this
level (such as the
JSF-based hybris
StoreFoundation or
the ZK-based hybris
Print Cockpit) uses
the ServiceLayer for
functionality and the
Type Layer for
storage of objects.
Depending on the
complexity of your
implementation, this
layer can itself
consist of several
individual layers and
even use an
individual data
model
ServiceLa
yer
Framewor
k
(including
the actual
ServiceLa
yer, the
Provides the Java

Application
Programmer's
Interface (API) for
objects in the hybris
Commerce Suite, the
hybris API. The
hybris ServiceLayer
Klicken Sie hier, um zu erweitern...
Layer
Name
Description
What would a Product look like on this Layer?
Infrastruc
ture
Services,
and the
Business
Services)
relies on so-called
models, which
are POJO objects.
Attributes on models
have automatically
generated getter and
setter methods.
Models are generated
based on types.
Type
Layer
Describes business
object models. It is
on this layer that
definitions of
business objects
(types) and their
fields (attributes) are
made via
the items.xml items.
xmlfile. Models are
generated based on
types.
items.xml
Persistenc
e Layer
Deals with
abstraction from the
database, caching,
and clustering. You
are not likely to get
into contact with the
Persistence Layer at
all as it is completely
transparent and does
not require any
explicit interaction
from your side.
SQL-compliant representation of numbers and

strings in a database table, such
as VARCHAR, CLOB
Database
Although not a layer

of the hybris
Commerce Suite, the
database is also an
important component
in this overview: the
database makes the
data held in the
hybris Commerce
Suite persistent.
Database-specific representation of numbers and

strings.
<itemtype code="Product" extends="LocalizableItem">

<attributes>
<attribute qualifier="code" type="java.lang.Strin
g"/>
</attributes>
</itemtype>
Modes of Operation
You can run the hybris Commerce Suite in three different modes of operation:
Operation
Mode
Schema
Graphics
Description
Operation
Mode
Schema
Graphics
Description
Single Node
The most basic mode of operation. A single machine

running one instance of a hybris Commerce Suite
installation. Does not have several nodes (unlike in Cluster
Mode) and only has one set of data (unlike Multi-Tenant
mode).
Cluster
Mode
The hybris Cluster consists of several individual nodes.

These nodes access a common database and communicate
among each other via the TCP or UDP protocol. Summing
up, this is a multi-node, cross-linked version of Single
Node.
Multi-Tenant
Mode
A hybris Commerce Suite in Multi-Tenant Mode allows

using several individual, distinguished sets of data
separated by database table prefixes. Multi-Tenant Mode
can be used for Single Node and for Cluster Mode
operation.

Hybris Architecture

Uploaded by

Copyright:

Available Formats

Hybris Architecture

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hybris Architecture

Uploaded by

Copyright:

Available Formats

Basic Architecture

Figure: The hybris Commerce Suite diagram

Figure: Overview of the architectural layers of the hybris Commerce Suite.

This is where objects

What would a Product look like on this Layer?

Provides the Java

Klicken Sie hier, um zu erweitern...

What would a Product look like on this Layer?

SQL-compliant representation of numbers and

Although not a layer

Database-specific representation of numbers and

<itemtype code="Product" extends="LocalizableItem">

The most basic mode of operation. A single machine

The hybris Cluster consists of several individual nodes.

A hybris Commerce Suite in Multi-Tenant Mode allows

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.