This document provides information about an upcoming webinar series on SAP Hybris architecture. It discusses the topics and agenda for Part II of the series on Architecture & Building Blocks, which will cover SAP Hybris architecture models, synchronous and asynchronous integration with SAP systems, and the architecture building blocks. The presentation is by Ravi Pal from Kellton Tech and will provide an overview of SAP Hybris architecture and its key components.

1. 0
SAP HYBRIS
ARCHITECTURE

2. 1
Upcoming Webinar Information
Keep an eye out for the invite to Parts III of our webinar series
Part I – Project Plan & Governance
Part II: Architecture & Building Blocks – Nov 1, 2018 at 10am CST
▪ Views of Architecture Models supporting information, application, integration & data
▪ Synchronous calls to SAP CRM / ECC
▪ Asynchronous calls through Datahub
Part III: Development & Operations – December 13 at 10am CST
▪ How to manage SAP Hybris Cloud
▪ Best practices
▪ Hybris system landscape and tools for automation
A Successful C/4HANA (SAP Hybris) B2B
Implementation
Part II: Architecture & Building Blocks

3. Agenda
Kellton Tech Corporate Overview
SAP Hybris Architecture
Architecture Perspectives
Architecture Building Blocks
Presenter
Ravi Pal
ravinder.pal@kelltontech.com
2
A Successful C/4HANA (SAP Hybris) B2B
Implementation
Part II: Architecture & Building Blocks

4. 3
Foundation
2009
Footprint
USA, UK, Ireland,
Singapore and India
Clients
Startups to Fortune 500
Core Strength
People and Technology
ISO 9001:2015 &
CMMi Level 5
Ownership
Public Limited
BSE, NSE:
KELLTONTEC
Team
1500+
Employees
McLean | Princeton| Jersey City | Chicago | Houston | Cupertino | Dublin | London
Singapore |Delhi | Hyderabad | Kandla |Pune
Kellton Tech, A Pioneer of Digital Transformation

5. 4
What We Do?

6. SAP Hybris Architecture
5
Today, we will explore the components or building blocks that make up
the overall information system of SAP Hybris platform.
A good understanding of its architecture provides a plan for procurement,
and a successful adoption.
It thus enables you to manage your IT investment in a way that meets the
needs of your business.

7. Why is it important and why do I need it?
6
Critical to business survival and success
An architecture understanding provides a strategic context for the evolution of
the technology in response to the constantly changing needs of the business
environment.
Enables managed innovation within the enterprise
It enables you to achieve the right balance between technology efficiency and
business innovation. It enables managed innovation within the
enterprise. Individual business units can innovate safely in their pursuit of
competitive advantage.
A more efficient IT operation
Better defined structure and modularity in the IT infrastructure lead to a much
more efficient overall IT operation.
Better return on existing investment, reduced risk for future investment
Faster time-to-market
In short, it can make the difference between business success and failure.

8. Architecture Perspectives
7
Logical Architecture
Business Architecture
Technology Architecture
Business Architecture
Service/
Integration
Information Application
Data
Models
App
Models
Development
Models
Execution
Models
Operations
Models
Network
Models
Security
Models
Infrastructure

9. Supply Chain Integration
Web Analytics
Reviews and
Rating
Search & Browse Cart & Checkout
Search Engine
Optimization Web Portal, Personalization and Content Mgmt
Call /Contact
Center
Product & Pricing
Order Mgmt
In Store Apps
Inventory Mgmt
Returns Mgmt
Warehouse Mgmt
Transportation
Mgmt
Delivery Network
Direct Delivery Customer Fraud
Social Apps
Payment Systems
Campaign Mgmt
Security &
Compliance
Reporting
User Experience
Infrastructure
Performance
Engineering
Loyalty Mgmt
Digital Marketing
Merchandizing
Partner Apps
Online Marketing Online Shopping
Channel Integration
Product Management
Capacity Mgmt
Compliance Mgmt
Business Capability Model

10. Hybris Logical Architecture
PresentationApplicationServices
Information Integration
Adapters
CompositionServices
Business MonitoringProcess Management & Execution
Sales Rep
CSR
Customer
Vendors
Partner App
Protocol
Conversion
Queuing Event Handling
Message
Transformation
Service
Orchestration
Process
Choreography
Thick Client Thin ClientPortal B2B Mobile Devices
Process ProgramData Access REST / WS
Instrument-
ation
Workflow
Automation
Rules Engine
Processing
Process Business Intelligence Reporting
Real-time Analysis
Business / Instrumentation
Translation Engine
Automated Business Response
JBDC / Native
Third PartyWeb Services
Custom API
Legacy
Legacy Data
Abstraction
Data Modeling
Indexing
SequencingCorrelationAggregationProcessing
Hybris
Lifecycle
Storage : RAID, SAN, NAS,
Optical Tape
Network: Routers, Firewalls,
Mobility Svc
Servers : App, Content,
Database, Edge
Peripherals : Printers,
Scanners, Telephony
Integration
Transformation
Translation
Messaging
Interaction
Personalization
Customization
Transcoding
Navigation
Resource
Deployment
Scheduling
Rules & Flow
Persistence
Caching
Security
LB / Failover
Document
Web Content
Metadata
Directory
Management
Instrumentation
Analyze, Deploy & Execute
AssembleDesignDeployMonitor
Business Services Content Management
ETL

11. Servlet Engine
Systems & Data Sources
SAP
Business
Partners
Component Communication Architecture
10
ApplicationB2B / B2C Other Application
Business Services
c
c c
Spring Container
c
Hybris Persistence Service Model Services
B B B B I I
Spring Integration
I
IIII
c
B
I
Composite
Business
Interface
End Point
Hybris
Initiate
MDM
other
I
BusinessActivityMonitoring
Governance
10
Hybris Implementation
▪ Tiered architecture, mainly
façade, service, information,
integration and resource tiers
▪ Façade tier is a composite
pattern calling downstream
services
▪ Services compose information
fetching data from DAOs
through model based services
▪ Spring injection
▪ Java / Spring based events
▪ Transformation – converters
and populators
▪ Spring MVC and JSP
templating

12. Hybris Technology Architecture
11
Hybris Implementation
▪ Tiered architecture, mainly
façade, service, information,
integration and resource tiers
▪ Façade tier is a composite
pattern calling downstream
services
▪ Services compose information
fetching data from DAOs
through model based services
▪ Spring injection
▪ Java / Spring based events
▪ Transformation – converters
and populators
▪ Spring MVC and JSP
templating

13. Marketing Sales SettlementProduct Supplier Complianc
e
I II III IV V VIIIVIIVI IX
Customer
Service
Returns &
Exchanges
Order &
Fulfilment
Shared Digital Commerce Capabilities
Product
Module
Catalog
Module
Search
Module
Payment
Module
Promotion
Module
Workflow
Module
OMS Returns
Cockpits
Hybris
Module
A Hybris Component

14. 13
Component Based Architecture
Data Access Objects
Design Pattern Component Based Architecture
Benefits Limitations
▪ Discrete treatment of business
objects allows editing of
components without affecting
others
▪ Distributed data access enables
integration at all levels without
geographical constraints
▪ New components are easy to
plug in
▪ Relies on a proprietary design
and runtime framework which
makes interoperability difficult
▪ Object interaction rule setting
becomes complicated with
increase in number of
components
▪ Access permissions need to be
meticulously planned
Recommended Usage
▪ Integration of diverse business objects to single user environment is
required
▪ Multiple business rules governing diverse data and business
applications exist
Inputs Outputs
▪ API▪ API
▪ Architecture paradigm encompassing Object oriented
approaches to software development
▪ Creates software abstractions of business objects treating
them as separate entities with interaction rules
▪ Abstracts business objects to single interface
▪ Plugs in to front-end enterprise solutions
Description
Presentation/
Transaction
components
Native
Process/
Workflow
Components
Business
Logic/Rules
Components
API API API
API APIAPIAPI
API
API
Hybris Implementation
▪ In Hybris, a self contained
autonomous component is
packaged into an extension.
▪ Examples of those extensions
are core, commons, catalog,
impex, media, processing,
workflow etc.
▪ Extensions have dependencies
on each other. The build
framework take those
dependencies into
consideration during
compilation.
▪ Extensions refers to each other
by means of Spring framework
dependency injection.

15. 14
Data Hub
Database
Source
Application 2
Design Pattern
Data Management
Benefits Limitations
▪ Keeps reference data across
business applications and data
warehouses /marts in sync
▪ Provides mapping rules to
translate application specific
reference data to enterprise
definitions
▪ Reference data mapping is
cumbersome and changes can
compromise data integrity of
historical data
Recommended Usage
▪ Management of reference data across disparate applications and data
warehouses/marts is a challenge
▪ A centralized, automated mechanism for syncing reference data
across systems is required
Inputs Outputs
▪ Flat File
▪ XML
▪ SQL
▪ Flat File
▪ XML
▪ SQL
▪ Data Management is a technique to manage standard and
organization specific value lists used by various applications
▪ Consolidate enterprise reference data in a single “golden
copy” repository to be used by all firm-wide applications
▪ Automate data distribution and synchronization across the
whole enterprise, standardize and track data across disparate
systems
Description
Hybris Data Management
Source
Application 1
Data Integration (
Data Hub)
Industry Ref Data –
Flat File, XML (I)
Ref Data Change
Mgmt – Flat File,
SQL, XML (I/O)
Mapping Rules – Flat
File, SQL, XML (O) Publish to Target
Systems
Industry
Ref Data
Vendor
Industry Ref
Data Sets
App Specific Ref
Data
Relationships
Rules
Enumeration
Data Management
Hybris Implementation
▪ Hybris type system for data
management resembles with
EJB implementation.
▪ Hybris uses its own persistence
engine, transaction manager
and access management.
▪ Entities (types such as
products, categories, catalog)
are created by following entity
schema model (*items.xml)
▪ During compilation time,
schemas are converted to
models (beans)
▪ Type system also maintains a
dictionary

16. 15
▪ JMS/MQ
▪ SOAP
▪ Custom & File Adapters
▪ SQL
▪ IMAP/SMTP
▪ JMS/MQ
▪ SOAP
▪ Custom & File Adapters
▪ SQL
▪ IMAP/SMTPJMS/MO (I/O) SOAP (I/O) Custom Adapter (I/O) REST (I/O)
Design Pattern Services Based Integration
Benefits Limitations
▪ Platform neutrality allows a
variety of applications built on
multiple platforms to exchange
security information seamlessly
▪ Security directories need not be
synchronized and can be loosely
coupled with SAML
▪ Improved end-user experience
with one time authentication
▪ Authentication is delegated to
another provider and hence not
in the SAML server’s control
Recommended Usage
▪ Where multiple cooperating services/ applications are provided
through a single portal/ website, needing a single sign-on for all
▪ When authentication authority can be delegated to a provider and only
retain only handling validation of consumer
Inputs Outputs
▪ Represents an environment designed to foster sophisticated
interconnectivity between services, establishing an
intermediate layer of processing, helping in reliability and
scalability of communications
▪ Comprised of co-existent applications of Asynchronous
Queuing, Intermediate Routing, and Service Broker, be further
extended via Reliable Messaging, Policy Mgmt. and Rules
Centralization
Description
Queue
Manager
Process
Manager
Message
Handler
Message
Transformer
Data Hub / SAP Cloud Platform Integration
Process
Persistence
REST I/O File Adapters (I/O)
Services Based Integration
Hybris Implementation
▪ Hybris uses spring based
services architecture where
services are Spring managed
runtime components.
▪ The association between
services is facilitated through
dependency injection.
▪ During invocation / initialization,
the services go through a
validation and state
management.
▪ Once initialized, the Spring
engine maintain the life cycle.
▪ Across applications,
synchronous and asynchronous
means are in place for message
communication.

17. 16
Design Pattern Federated Content Search
Benefits Limitations
▪ Provides content search as a
shared service and avoids need
for redundant investments
▪ Provides users and applications
with a standard set of services
they can leverage
▪ Analytics will also help in
identifying high usage sources
and improve performance
▪ Indexing large repositories
across the enterprise may result
in slow performance
▪ May be difficult to restrict search
results to only authorized
content
Recommended Usage
▪ An organization has multiple content repositories of searchable
content that must be accessible through standard services
Inputs Outputs
▪ HTML
▪ Search API
▪ Web Services
▪ Content API
▪ A federated search engine supports indexing of content across
content stores
▪ Provides various methods of search to integrated with other
applications
Description
Query Management
Index Engine
Index Repository
Content
Unification
Services
Search Service
Store
Front
Search
API (O)
Web
Service (O)
Content
API (I)
Search
Content Search
Hybris Implementation
▪ Hybris use Apache SOLR that
helps to maintain documents
and indexes.
▪ Out-of-the-box extensions with
the prefix solr* (solrfacetsearch,
solrserver, solrfacetsearchhmc)
provide configured functionality
hiding complexity of schema
generation, indexing, and
faceting
▪ Apache Solr comes with Hybris
but need to be configured
separately for production ready
environments

18. Doc ID
17
Design Pattern Metadata Management
Benefits Limitations
▪ Provides a business oriented
reference for IT to implement
data stores / warehouses / marts
(data at rest) and enterprise
level integration services (data in
transit)
▪ Facilitates a centralized impact
analysis mechanism for changes
that require modification of
information definitions
▪ Integrating data definitions may
become challenging in a rapidly
changing environment
▪ Bad design may lead to meta-
data silos which alienate data
sources
Recommended Usage
▪ Multiple meta-data dictionaries need to be integrated to provide single
point of access and management of meta-data
▪ Business applications and users need to pull meta-data references
from organization wide databases
Inputs Outputs
▪ XSD
▪ DTD
▪ XSD
▪ DTD
▪ Is a technique for data assurance whereby standard
enterprise-wide logical definitions of information and their
sources is captured in a centralized directory
▪ It support searchable business catalogs where analysts can
understand data structures without having to understand the
physical implementation details
Description
Application Specific
Data Structures
Enterprise Data
Dictionary
Data Hub
Source
Application 1
(SAP ERP)
Source
Application 2
(SAP CRM)
Data Hub Engine
Metadata Management
Metadata XSD, DTD (I)
Metadata - XSD, DTD (O)
Metadata -
XSD, DTD (O)
Metadata Management
Hybris Implementation
▪ Hybris type system supports
metadata management of the
entities managed by Hybris.
▪ All entities and the associations
among them are stored and
used for rights and access
management.

19. 18
▪ SOAP
▪ JMS / MQ
▪ HTML
▪ WSRP
Business
Application 1
Business
Application 2
Design Pattern Business Process Engine
Benefits Limitations
▪ Promotes visibility and
performance of end-to-end
business processes
▪ Promotes reuse of standard
back-office processes and the
service-oriented integration of
applications
▪ Difficult to define a logical
granularity of processes
Recommended Usage
▪ Standard processes require efficiency of execution
▪ Processes need to be managed, monitored and optimized using a
centralized control mechanism
Inputs Outputs
▪ SOAP
▪ JMS / MQ
▪ Pattern involves using an overarching engine to orchestrate
end-to-end business processes
▪ Processes are defined using standards such as BPMN
▪ Provides standard UI components for a task inbox and task
execution
▪ Delegates to a BPEL engine / ESB for application integration
needs as part of executing end-to-end processes
Description
Monitoring &
Logging
BAM
Process
Composer
BPMN/UI/Rules
Repository
Process
Persistence
Rules
Engine
Process
Manager
BPEL Engine (ESB)
SOAP (I/O)
JMS/MQ (I/O)
Task Management
Portlet (O)
BPM Engine
Business Process Engine
Hybris Implementation
▪ Hybris uses Activiti for BPMN
▪ In earlier versions (prior to 6), a
spring based workflow process
was in place that got replaced
with standard engine.

20. 19
Design Pattern Composite Application Framework
Benefits Limitations
▪ Allows definition of reusable
assets as framework
components or services
▪ Allows model-driven
development of assets that
improves design governance
▪ Adds agility by facilitating visual
design, reconfiguration of
existing assets and faster, non-
intrusive deployment of solutions
▪ Composite frameworks are often
proprietary. Strong design
governance needs to ensure
adherence to open standards
▪ Defining a meaningful level of
granularity of assets is a
challenge and should be defined
by a governance board
▪ Reusing existing web interfaces
is not possible, requiring a more
comprehensive service
orientation effort of existing
legacy applications
Recommended Usage
▪ An organization decides to adopt a SOA approach to application
design in order to improve agility
▪ Need to promote reuse of assets in order to reduce implementation
and maintenance costs
Inputs Outputs
▪ HTML/ XML
▪ HTTP Request / Response
▪ JSP Templating with Spring
MVC
▪ HTTP Request / Response
▪ Integration Adapters
▪ Component Configuration
▪ The pattern represents delivery of a new service or application
built by combining multiple existing services or components
▪ A Composite Application Framework (CAF) is a framework
that manages the composition, deployment and execution of
reusable assets (components and services)
Description
Composite Application Framework
Hybris Implementation
▪ Tier architecture support with
core Spring and Spring MVC is
the central design was
application framework.
▪ Composite behavior provides
omni channel orchestration.

21. Doc ID
Business Activity Monitoring
20
Design Pattern Business Activity Monitoring
Benefits Limitations
▪ Capable of capturing business
activity events to a customizable
level of granularity
▪ High flexibility in reporting
formats and analysis
▪ Does not integrate controls as a
part of activity monitoring
▪ Cannot capture non-IT events
Recommended Usage
▪ Business analysts require frequent information about business
activities in the organization, continuously monitor and improve
processes under tight SLAs
▪ Most of the business processes are automated and the activities are
directly routed through the IT infrastructure
Inputs Outputs
▪ JMS / MQ
▪ HTML / XML
▪ Email
▪ JMS / MQ
▪ The pattern enables aggregation, analysis and presentation of
real-time information about activities inside organizations
involving customers and partners
▪ It provides an enterprise solution that collects and reports
business activities from all levels to managers and decision-
stakeholders
Description
Enterprise Integration
Services
Rules Engine
Complex Event
Processing
Business Activity Monitoring (BAM)
Business App Business App Business App
JMS/MQ Event DB Trigger
JMS/MQ (O) HTML/XML (O) Email (O)
JMS/MQ Event

22. Integrated Rights Management
21
Design Pattern Integrated Rights Management
Benefits Limitations
▪ Allows centralized control of
content based on its profile
▪ Separates the access control
policy making from the identity,
authentication services
▪ Policy server can be replicated
across locations to ensure
consistency
▪ May add to process and
maintenance overheads
reducing adoption
Recommended Usage
▪ Content is available on different platforms across the organization,
requiring multiple levels of authentication
Inputs Outputs
▪ Policy enforced content▪ User Login
▪ Centralized policy server manages the configuration of
content, content access, applications and users' settings
controlling what users can and cannot access
▪ Based on the rules set in the server, the content may or may
not be available to the user
Description
Policy Server
Identity and Access
Management
Secure Content
Viewer (E.g. Adobe
Acrobat Reader)
Login Principle Principle
Policy enforced Content
End User
Content
Management
System
Policy

23. Role Based Access
22
Design Pattern Role Based Access
Benefits Limitations
▪ Easier to manage access rights
at UI level as compared to other
forms of access control
▪ Provides a policy based access
control, aligned to the information
security policies of the
organization
▪ Supports the concepts of least-
privilege, separation of duties and
centralized administration of roles
and their respective access rights
▪ Administration of a large
organization and its associated
roles may become cumbersome
▪ In case of non generalized
custom role definitions, role
based access may not be
suitable and more complex
application logic and backend
privileges need to be relied upon
Recommended Usage
▪ Navigation framework should display pages and links based on
user role
▪ Organization has non conflicting roles defined
Inputs Outputs
▪ Personalized Navigation Layout▪ User Profile Principle
▪ A generalized access control mechanism based on user roles
▪ Permissions are assigned to roles/groups and users are then
made members of the groups
▪ Navigation framework only displays links accessible by the
user
Description
Navigation
Framework
Content
Management
Session
Management
User / Role
Management
Shopfront
Configuration
Portal Configuration
Framework API (I)
Session Content
Framework API (I)
User management
Framework API (I)
Filtered Content
Navigation Framework
HTML (O)

24. Business Rules Engine
23
Design Pattern Business Rules Engine
Benefits Limitations
▪ Has the ability to develop data
abstraction to represent business
entities and their relationships
▪ Maintains a separation between
the logic of the rules and the
data, allowing changes to made
due to policies, regulations, etc
▪ Creates a central repository of all
business rules and logic
▪ Immense flexibility in choice of
language to write the rules
▪ Careful design of rules engine is
imperative to maintain data
consistency
Recommended Usage
▪ Business rules and logic are dynamic, changing often
▪ Business rules need to govern a large amount of data
▪ Business experts are non technical people offering the business logic
rather than programming logic
Inputs Outputs
▪ XML
▪ API
▪ XML
▪ API
▪ The execution of business rules created in the system during
run time in the application
▪ It provides the ability to register, define, classify and manage
all rules, verify consistency of rules definition and define the
relationship between different rules
▪ Relates business rules to IT specific applications
Description
Rules Repository
Rules Editor
Business
Rules Engine
BAEIS
SOAP (I) API (I)
API
(O)
SOAP (O)

25. Batch File Transfer – Hot Folders
24
Design Pattern Batch File Transfer
Benefits Limitations
▪ It allows the integration of
multiple, diverse applications
while minimizing the impact to
existing applications
▪ Helps dependence on specific
vendors for application
enhancement, etc
▪ Improve information delivery
efficiency
▪ Limited ability to manipulate any
of the messages
▪ May not be possible to include
any human interaction during the
transmission
Recommended Usage
▪ There is high dependency among the systems
▪ The systems need to continuously communicate with one another
Inputs Outputs
▪ Hybris Impex▪ File
▪ This is a batch driven periodical data transfer mechanism,
usually performed overnight
▪ It propagates the prevalent data from the source i.e. latest
changes are also included
▪ The target database’s data is usually refreshed completely
Description
Source
database
Extract
module
(+ transform)
Flat files
(Transform)
+ Load
module
Target
database
Shared repository
SQL (O)
CSV flat
file (O)
CSV flat
file (I)
SQL (I)

26. Browser
Mobile
Kiosk
App
Tablet
Apache
Siteminder
Accelerators
System
Services
Business
Services
Persistence
Models
DataSources
XML & ORM
Spring
Container
Integration
App Container
ANT & Maven Build
Windows
Staging
Production
Linux, Windows, Tomcat, WebLogic, Websphere,
JBoss
Deployment Architecture

27. Summary Slide
Takeaways
Critical to business survival and success
An architecture understanding provides a strategic context for the evolution of the technology in response to the constantly changing
needs of the business environment.
Enables managed innovation within the enterprise
It enables you to achieve the right balance between technology efficiency and business innovation. It enables managed innovation
within the enterprise. Individual business units can innovate safely in their pursuit of competitive advantage.
A more efficient IT operation
Better defined structure and modularity in the IT infrastructure lead to a much more efficient overall IT operation.
Better return on existing investment, reduced risk for future investment
Faster time-to-market for changing business processes
26

28. Upcoming Webinar Information
Keep an eye out for the invite to Part III of our webinar series
Part III: Development & Operations – December 13 at 10am CST
▪ How to manage SAP Hybris Cloud
▪ Best practices
▪ Hybris system landscape and tools for automation
Q&A
27

29. www.kelltontech.com
28
Presenter
Ravi Pal
ravinder.pal@kelltontech.com

30. Process
Integration
WAS
WAS
29
Plan Buy Distribute Market Sell Customer
Financial
Planning
Merchandise
Planning
Buying
Price
Management
Supply Chain
Management
Inventory
Management
Brand / Product
Management
Customer
Management
Sales &
Analytics
Quote
Management
Analytics
Loyalty &
Customer
Trends
SAP ECC
SAP Hybris
APR, PMR
CRM
SCM
F&R
MM SD PP FICO PM HCM
NetWeaverGateway
oData
Datahub /
SCPI
Customer, Product,
Orders
SAP
BW/P4R
CAR
Master Data, Sales,
Inventory
Intelligence – Promotion, Customer, Assortment
POS
Sales
BW
Message Platform System Module Legends
Store