Name: Cloud Portal Overview - SAP Commerce Cloud
Uploaded: 2019-3-7
Duration: 512 s
Description: This video provides an overview of SAP Commerce Cloud Portal and includes:Creation of EnvironmentsCreation and Deployment of BuildsRepository, Security and Storefront Availability Features

Share feedback

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

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div>This video provides an overview of SAP Commerce Cloud Portal and includes:<br><ul><li>Creation of Environments</li><li>Creation and Deployment of Builds<br></li><li>Repository, Security and Storefront Availability Features</li></ul><div><br></div></div></div>

Cloud Portal Overview - SAP Commerce Cloud

Hello, my name is Adam. >> And as part of our regular series of videos on SAP Commerce Cloud. >> This video will provide a brief overview of the creation and deployment of application builds, endpoint configurations, environment specifications, and provisioning and extensibility options. >> Commerce Cloud is coordinated and deployed through the Cloud Portal. A secure browser-based interface running on the SAP Cloud Platform. >> The Portal enables you to connect your code repository for downloading your source code, compile your application, create and provision environments, configure and secure endpoints, and deploy. customized builds for your store into the cloud and on-demand. >> It's also used to access monitoring and logging solutions, add other Commerce Cloud users and manage their permissions and extend functionality in various ways. >> Application builds are initiated through the cloud Portal. To specify how applications and their extensions are built, a manifest JSON file is used to define specific properties, add-ons, aspects, and tests. The manifest sits at the root layer of your Git repository, which is connected and secured using public and private access keys. >> Once the manifest is in your repository, you can go ahead and initiate a build. A build progress bar and event log provides an indication of the steps completed in the process. >> During that process, the source code from your repository and the application itself are downloaded. >> The code base is built, custom hardened Docker images are created based on your code and the images are uploaded to the container registry ready for deployment. >> The builds overview lists all application builds and their unique ID together with their status. >> Click on any build name to view more information about it and click the link to download a build log. >> Once you've created and provisioned a suitable environment, you can go ahead and deploy a build to it. >> First, select the target environment, then the database action. >> There are three options here: for a new build and a new environment, >> select Initialize database. >> When redeploying a build with a few system changes, the update database option deactivates background processing while the update runs. >> If no downtime is required, select no action to deploy the application with a rolling update. >> Now click Deploy. >> A progress bar provides a visual indication of the deployment process and an event log lists the key steps as they complete. >> Once that deployment has finished, your shop is up and running in a dedicated optimized infrastructure. To provide suitable infrastructure and resources for the application, to function, you create and provision environments in the Cloud Portal. Commerce Cloud subscriptions provide three different types of environment which correspond to predefined resource allocations and so define their minimum size. Development environments have a lower capacity. >> They're used to create, configure and test application builds. Staging environments are designed to simulate production activity and achieve business validation. >> And the production environment is used to run live Commerce Cloud applications. >> The resources and hence the size of a production environment can be increased and decreased to reflect demand, providing consistently fast response times for growing traffic and more cost effective service. >> To create a new environment, enter a name and select the required environment type. There are two mandatory regional settings, environment locale and environment time zone. >> These are used for virtual machine configuration. >> For example, when using custom extensions that rely on JVM defaults. Setting the time zone also enables the application to run in local time, ensuring that processes and logs are correctly timestamped. >> Now click Save. >> When the environment has successfully provisioned, it appears as available in the Cloud Portal. Select any available environment to display more information about it. This includes endpoints that define Web routing and access, cloud storage that enables files to be uploaded to hot folders, snapshots that create a backup of your data at any time and let you restore it if something goes wrong, and deployment configuration, which lets you add trusted certificates for Java virtual machines, host aliases and other properties. >> Endpoints control web access to running applications in an environment. >> Each new environment includes endpoints for storefront, backoffice, SOLR, logging, background processing, and API. >> These are all configurable and other endpoints can be added as required, but each must be tied to an aspect configured in your manifest JSON file in order to work. By clicking the name of an endpoint or the pencil icon. You can check how the endpoint is currently configured and edit its name, web proxy, and service. >> You can also edit the domain being used to access the service and the SSL certificate used to confirm the integrity and privacy of web requests. >> Further down the endpoint screen, you can setup IP filters. Endpoints use an allow all or deny all filtering rule. And by uploading your own filter set, you can define exceptions to the chosen rule. This is useful, for example, when limiting backoffice access to employees in your own offices. Using redirect sets, you can determine the landing page of incoming requests. This is ideal for directing visitors to seasonal marketing campaigns and time limited promotions. Static files such as robot files, sitemaps, and custom error pages can be bundled into a zip archive and attached to the endpoint of a specific environment. Commerce Cloud delivers business value through its principal functionality and extensibility. >> You can integrate with other ERP systems, for example, by using custom code in the build manifest or dedicated endpoints, You can monitor storefront availability data from external monitoring tools within the Cloud Portal. >> And leverage the power of SAP Commerce Data Hub to integrate and stage large amounts of data from various sources. >> Data hub also prepares that data for delivery to any number of target systems. >> Adding host alias sets enables commerce environments to communicate with third-party services using domain names that are not recorded in DNS. And trusted certificates can be added to establish secure connections between applications deployed into Commerce Cloud environments and external services and systems. >> Rather than writing commerce extensions, creating new builds, and deploying and managing upgrades later, you can write lambda functions in the SAP Cloud Platform extension factory. These consumes such events sent from the application, implement logic, and call back rest services to retrieve additional data. SAP Commerce Cloud enables you to build, configure, and manage your applications, provision the right environment for those applications, and deploy them into the cloud on demand. When combined with centralized monitoring and logging and a host of customization tools, it accelerates, simplifies, and de-risks commerce projects. >> That concludes our brief overview of Commerce Cloud. >> Thank you for watching.