Running SAP Hybris Using SAP HANA

This article describes a series of architectures for deploying SAP Hybris using SAP HANA on Google Cloud. SAP Hybris is a commerce platform designed for scalability, high traffic, and high order volumes. The SAP Hybris platform supports business-to-business (B2B) and business-to-consumer (B2C) workloads. This article describes the SAP Hybris architectural components for B2B and B2C deployments using SAP HANA and explains how to deploy them using Google Cloud.

Component architecture

SAP Hybris using SAP HANA on Google Cloud consists of the following components:

  • A web server for serving static content, such as Apache.
  • A Java application server for running the SAP Hybris core application. By default, SAP Hybris uses Apache Tomcat.
  • A SAP HANA database for storing customer, purchase, and product data.
  • An optional search mechanism for product search, such as Apache Solr.
  • An optional caching mechanism for page and session caching, such as Redis.

The following diagram shows a sample high-level component architecture for an SAP Hybris deployment using SAP HANA, including the optional search and cache components.

high-level component architecture for an SAP Hybris deployment using SAP HANA

Licensing and prerequisites

To run SAP HANA on Google Cloud, you can use your existing or new SAP HANA licenses, following the bring-your-own-license (BYOL) model. Google Cloud supports SAP HANA BYOL for both production and non-production use cases.

Before implementing SAP Hybris using SAP HANA on Google Cloud, review the following technical notes from SAP on Google Cloud for recent deployment information.

ID Technical note
2456432 SAP Applications on Google Cloud: Supported Products and Google VM types
2446441 Linux on Google Cloud (IaaS): Adaption of your SAP License
2456953 Windows on Google Cloud (IaaS): Adaption of your SAP License
1380654 SAP support in public cloud environments

Compute instance sizing

Google Cloud offers various VM types that are SAP certified and supported, and that match the sizing requirements for SAP Hybris and SAP HANA. SAP Hybris is a user-based application, and sizing is computed based on the number of active users who are using the application. For more detailed information on how to size, refer to the Sizing SAP Hybris Billing, Pricing Simulation guide.

The SAP Hybris application can be deployed on machine types and operating systems that comply with software requirements from SAP.

If SAP HANA is used as the database, the machine type must be certified by SAP for use with SAP HANA. For a list of the machine types that are certified for SAP HANA, see Certifications for SAP HANA on Google Cloud.

Configuring storage for SAP HANA

Compute Engine persistent disks, which are designed for high durability, stores data redundantly to ensure data integrity. Each persistent disk can be up to 64 TB in size, so you don't need to manage arrays of disks to create large logical volumes. One of the key features of persistent disks is that they are automatically encrypted to protect data. Persistent disk SSDs are designed to offer high IOPS and low latency. The recommended approach is to use persistent disk SSDs for storing operational data with SAP Hybris and SAP HANA. For backup data, the recommended approach is to use a persistent disk with standard hard drives.

Database configuration for SAP Hybris

When you deploy SAP Hybris for development or evaluation purposes, you can use the built-in HSQLDB database, which is typically sufficient for these use cases. High-scale production deployments of SAP Hybris use SAP HANA. When using SAP HANA, you must install the HANA client on the same instances that contain the SAP Hybris application.

To properly support SAP HANA, configure the following Hybris application properties:

Properties Detail
db.url The path at which to access the database, such as db.url=jdbc:sap://[HOST_NAME]:[PORT_NAME]?reconnect=true.
db.driver The fully qualified name of the JDBC driver class that is used to access the database. The default value in the project.properties file is com.sap.db.jdbc.Driver.
db.username The name of the user account that is used to access the database.
db.password The password that matches the database user account specified in db.username.

Deployment architectures

You can deploy SAP Hybris in a number of configurations, ranging from development, to small-scale production, to multi-zone distributed deployments, depending on your use case.

Development and evaluation deployments

In a development or evaluation deployment of SAP Hybris, you deploy the core components, including web server, Hybris platform core, search, and the HANA database, on a single Compute Engine instance. In this configuration, the Hybris platform core, search, and HANA database all use the same JVM. Additionally, in this configuration you can optionally deploy an HTTP load balancer to terminate external connections and mask the Hybris deployment from the user.

Production deployments

Production deployment configurations of SAP Hybris can range in size and complexity, depending on the problem you're trying to solve. In most scenarios, the size and complexity are determined by high availability (HA) needs.

Many SAP Hybris production deployment configurations share common patterns. Specifically, you deploy the components of the SAP Hybris stack (web server, application server, search, and database) across multiple Compute Engine instances to balance the system load. Depending on the HA needs, you deploy those instances either in a single zone or across multiple zones in a single region. For more information, refer to the Designing Robust Systems tutorial.

The following architecture is an example single-zone production deployment for SAP Hybris using SAP HANA:

single-zone production deployment for SAP Hybris using SAP HANA

The following architecture is an example multi-zone production deployment for SAP Hybris using SAP HANA:

multi-zone production deployment for SAP Hybris using SAP HANA

Small-scale production deployments (or scaled development deployments) use similar approaches to the preceding production architectures, but with smaller Compute Engine instances.

Backup and restore

For a subset of the components in the SAP Hybris stack (web server, application server, search), use persistent disk snapshots to back up the entire disk. The snapshot should include items such as data, configuration, and log files. The advantage of persistent disk snapshots is that they are incremental, where each subsequent snapshot stores only incremental block-level changes. To back up individual files or folders, copy the files or folders to Cloud Storage buckets by using the Cloud Console or gsutil.

In normal operating scenarios, SAP HANA automatically saves in-memory data to persistent storage at regular five-minute intervals. For more information, refer to the Persistent Data Storage in SAP HANA documentation. SAP HANA provides support for storing backups and restoring data using Cloud Storage buckets, configurable through the SAP HANA Cockpit.

What's next

  • For more information about deploying and operating SAP HANA, refer to the Google Cloud SAP HANA guides.
  • Try out other Google Cloud features for yourself. Have a look at our tutorials.