Name: Commerce Cloud Architecture- SAP Commerce Cloud
Uploaded: 2020-7-29
Duration: 485 s
Description: Watch this video to learn more about SAP Commerce architecture in the Public Cloud. We will take a look at key benefits, architectural features, types of environments as well as the deployment process.If you would like to find out more, please check our Help documentation:Commerce Cloud in the Public Cloud

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>Watch this video to learn more about SAP Commerce architecture in the Public Cloud. We will take a look at key benefits, architectural features, types of environments as well as the deployment process.<br><br>If you would like to find out more, please check our Help documentation:<br><a href="https://help.sap.com/viewer/20125f0eca6340dba918bda360e3cdfa/SHIP/en-US" rel="nofollow noopener noreferrer" target="_blank">Commerce Cloud in the Public Cloud</a></div></div>

Commerce Cloud Architecture- SAP Commerce Cloud

Hi! In this session, I'm going to talk about the Commerce Cloud architecture. SAP Commerce Cloud, currently the CCV2 version, drives digital transformation and enables you to function as an omni-channel business, delivering contextual customer experiences and unifying customer processes. It provides numerous benefits that are hard to beat. First, the Public Cloud Infrastructure, which is quick and easy to set up. Your IT team can configure and manage all necessary tools using a browser without needing to SSH into servers. The CCV2 Public Cloud Infrastructure offers massive economies of scale, which really comes into its own for larger enterprises. The self-service environment management ensures "no maintenance required”. SAP, using Microsoft Azure under the hood, is responsible for the maintenance of the hardware, software, and cloud-based networks, which significantly reduces overall costs. One of the main benefits of running SAP Commerce in the Public Cloud is the resilience it brings. You get maximum uptime and almost zero risk of failure. And finally, the agility that comes with flexible deployments. With CCV2, businesses experience simplified internal operations, better delivery, better collaboration, faster rollouts of new business initiatives, and improved data gathering and analysis. The Commerce Cloud architecture can be best understood from two aspects: its Conceptual Architecture; and its Runtime Architecture. In terms of its Conceptual Architecture, SAP Commerce Cloud comprises three different layers. The lowest, the Infrastrature layer is used to provision the environment in Azure, to generate builds from customer code, to deploy those builds to the environments, and to provide self-service capabilities. The Environment layer is responsible for the allocation of the platform resources and services that enable SAP Commerce applications to run, for example, the database server, Azure Blob Storage, Kubernetes clusters and Solr. And finally, the Commerce Application layer defines the vendor-specific business solution. This is the layer where customization is added. Turning now to the Runtime Architecture, at the top we have the customer Cloud Portal. This is how you interact with the Commerce Cloud environment. The Cloud Portal is a web UI that enables you to set up and deploy SAP Commerce in the Public Cloud and perform other common operational tasks. Just under Cloud Portal, is the Cloud Automation Engine, which is the core of the SAP Commerce Cloud infrastructure. The Automation Engine is the basis of the automatic Dev Ops pipeline. Currently, the Automation Engine is initially deployed on Azure, but it should support other 'Infrastructure as a Service' architectures, such as AWS and Google Cloud in the future. All environments, and all Commerce applications within a specific environment, are managed by the Automation Engine. Let's take a closer look at the main tasks of the infrastructure core, the Automation Engine. These include: Environment provisioning; The Build and deployment of SAP Commerce solutions; and scaling. Other features, such as the Cloud Portal, monitoring, disaster recovery and snapshots will be introduced in other videos. Environments define allocations of a cloud provider's resources and services; provisioned in a way that enables the client's application to function. Each Customer Zone in CCv2 may comprise three different environment types: Development, Staging and Production. The Development environment is used as a sandbox. It is not intended to be used as a fully functional test environment, especially if you intend to test with large datasets. It has one node for each service. The Staging environment has a larger Blob storage and a faster database server. It is not equivalent to production but is fairly close. It has multiple nodes for many of your services, like Storefront, Backoffice and Solr. Because it provides load balancing to service multiple nodes, you don’t have to wait for production to detect clustering problems. The Production environment provides more capability in terms of storage and calculation, which can be scaled according to the specific needs of the customer. All environment provisioning is based on an automated workflow, providing all necessary resources, including SQL Server, Virtual Machine Scale Set, Virtual Machine, Disks, and Network entities. All in a consistent, efficient and reproducible way. Once the environment is provisioned, the next step is to build and deploy the SAP Commerce application. The development team first needs to link their Git repository to the Cloud Portal. All custom changes are committed to the Git repository. A builder then fetches the custom code from the Git repository; the Commerce platform from SAP code repository, and builds a set of immutable docker images. There will be one for each of the Storefront, Backoffice, Solr, Apache, and so on. In order to enable the build process, you need to provide the necessary build metadata: You use the Cloud Portal to provide basic build information, such as the Git repository URL for custom code and licenses. You then define a manifest.json to configure Commerce Cloud to your exact specifications. The manifest.json is stored at the root of your Git repository. An operator is finally responsible for creating corresponding docker containers in your environment using the defined images. Once a deployment starts, there are no manual steps. The process is entirely automated. Each of the docker container images is deployed into a Kubernetes cluster. Each cluster contains all the services you need. The Kubernetes cluster sits on top of VMs. There are static VMs which provides some of the services; and scaling-set VMs, which are used for the environments we want to scale, most notably the storefront. And as you see from the diagram, all clusters run on top of the Azure public cloud infrastructure. A word about infrastructure scaling. The platform supports horizontal scaling only. Services can be scaled up using virtual machine scaling sets. Scaling requirements are determined by application alerts. The key point here is that no customer intervention is required. And more importantly, there is no additional charge. Of course, you can notify SAP in advance if you are expecting peak periods. The scaling services are split according to the various aspects. These include the Storefront, web services, Background processing, such as IMPEX inbound and outbound services, Backoffice, Solr and Zookeeper. These sliders give an idea of what adjustments can be made in the host environment. Services can easily be scaled based on the load that the customer site is receiving. Of course, it takes some time for the new nodes to warm up and become active. That's all for now. Thank you for watching!