The article highlights improvements such as:
- API Usage: How JetBrains’s latest batch of deprecated APIs impacts the plugin.
- SAP Commerce in the Public Cloud (CCv2): Dive into the new features simplifying developers’ lives, including the addition of code contributions based on JSON schema.
- SAP Data Hub on CCv2: Explore the complexities and solutions offered for projects utilizing SAP Data Hub.
- JavaScript Storefront: The essential tools and updates for developers working in the SAP Public Cloud.
- Type System: Discover the new usability improvements in preview mode and items.xml.
- ImpEx & FlexibleSearch: Understand the nuances and tweaks in action group displays and custom icons.
- Cockpit NG System: From commons to the business process, take a look at the new references added.
- Extension Info: Dive deep into the added extras for extensioninfo.xml.
…and a plethora of other essential updates, adjustments, and fixes to ensure smoother, more efficient operations for SAP Commerce developers.
Read More »In the previous part, we discussed the importance of redundancy and failover in a cluster setup and introduced JGroups as a crucial component of SAP Commerce Cloud for distributed messaging and eventing. In this part, we will delve deeper into troubleshooting common issues that arise with JGroups in SAP Commerce.
In this article, we will explore troubleshooting tips for common issues related to JGroups in SAP Commerce. We will discuss how to address data inconsistencies, handle dynamic IPs and membership discovery, and effectively monitor the cluster.
It is important to highlight that these recommendations were formulated and tested for the on-premise, self-hosted SAP Commerce. This setup is now rare, as many SAP Commerce projects have already been migrated to the cloud. In the cloud setup, such challenges may never be your concern, as they fall under the responsibility of SAP CCV2 support engineers. However, understanding the limitations and constraints will still help you build the solution correctly.
Read More »
This article focuses on how SAP Commerce stores models in memory, which is a vast topic. To begin with, we will explore a relatively simple aspect, such as the unusual structure that appears in the debugger when trying to view the contents of any SAP Commerce model. We will also discuss how to access all the object properties contained within it.
This article contains an overview of the latest updates in SAP Commerce Cloud, version 2211. The update is only available for SAP Commerce Cloud in the Public Cloud and cannot be used for On-Prem or other non-SAP managed infrastructures/servers. The update includes deprecating the accelerator storefront and related addon extensions and introducing the SAP Commerce Cloud, Composable Storefront based on the Spartacus open-source project.
The article goes on to detail the improvements made in Backoffice and SmartEdit, CMS, B2B Commerce as well as other features such as audit logging and HTTP session failover in the platform module, improvements in the yForms module, and new product recommendations in Intelligent Selling Services for SAP Commerce Cloud. Read More »
For those who have been following the development progress of Spartacus, the Angular/Node.js front-end to Commerce Cloud, you may have followed the roadmap information on the SAP GitHub Spartacus repository documentation pages. For many months during 2022 the roadmap statements indicated that release 5 would be towards the end of 2022 comprising a number of user experience and feature improvements, architecture improvements including the need to upgrade the underlying technologies such as the Angular framework.
However, I was a bit surprised (and I suspect other readers also) when SAP announced:
- stopping support on the previous Spartcus versions (4.x);
- that Version 5 would be only available within an authenticated policy to SAP partners / customers; and
- Spartacus is renamed to Composable Commerce.
Read More »
I have been discussing where the merchants have multiple instances of SAP-Commerce (hybris) and they want their non-production environments to be “more representative” of the production environment in terms of the data. In the previous part of this article, I looked at the rationale of why data migration is important and a number of various initiatives that have supported this over the years. In this part, I look at the areas of data for migration and the necessary concerns to consider when data is migrated. Read More »
I want to focus on a requirement I have met on several projects over the years where the merchant has multiple instances of SAP-Commerce (hybris) and they want their non-production environments to be “more representative” of the production environment in terms of the data.Many merchants have 3 such environments typically defined as development, staging and production and as time passes by, the production environment receives multiple BAU changes to core data areas such as web content, products/categories/classifications undertaken by merchandising teams or product management and of course a lot of data is generated through customer registrations and orders placed.
However, the non-production environments are frequently not kept in line in terms of web content, product data or representation in terms of quantities of customers or orders. I’m not referring here to the code and core configuration related data that is included in builds.
Read More »
Taking advantage of back-in-stock notifications, customers are informed that a product they were interested in recently has become available again. Alternatively, a customer may want to get subscribed to the product price updates and get notified when the price drops on a product.
As a result, customers are more likely to return to make a purchase. These two features are often considered as must-have for almost any marketplace solution.
Their implementation and design are also considered to be quick and easy. In fact, it is not so — there are many points for consideration easy to miss in the design phase. In this article, I focus on the potential pitfalls and best practices in implementing “Back-in-stock notifications” and “Price drop alerts”. Read More »
