In the SAP Commerce cache, invalidation works on a product type by invalidating cached Product items updated during the import in all connected SAP Commerce cluster nodes and by invalidating all cached FlexibleSearch results where Product type is included. This ensures that the cache only holds valid data and that the queries return consistent results. The invalidation is not limited to the node where the import is running, nor does it affect all cached FlexibleSearch results from the query results region. Reference: 1

The steps that you must do when configuring OAuth2 for SAP Cloud Integration are assigning ROLE_CLIENT or ROLE_TRUSTED_CLIENT in the SAP Commerce Backoffice, running an ImpEx to import the OAuthClientDetails and ExposedOAuthCredential type data in the SAP Commerce Backoffice, and creating the secret client credentials in the SAP Commerce Backoffice. These steps are necessary to enable role-based authentication between SAP Commerce Cloud and SAP Cloud Integration using OAuth2 tokens.

The thread dump entry indicates that the thread is waiting for an incoming connection. The thread is part of the AJP connector, which communicates with a web connector via the AJP protocol. The thread is in a WAITING state, which means that it is waiting for another thread to perform an action. The thread is waiting on an object of type org.apache.tomcat.util.net.JIoEndpoint$Worker, which represents a worker thread that processes incoming requests. The thread dump entry does not imply that the Tomcat AJP parameter maxThreads is too small, that the JVM option maxAJPThreads is too small, or that the system is about to crash. Reference: 1

SAP Commerce Cloud, context-driven services capture click events, order events, and address book event updates, quantity updates in the shopping cart, and all customer interactions and behaviors. These data points are used to provide personalized and relevant experiences for customers based on their context and preferences.

The tool that you use to persist changes to enable and disable JDBC logging is configuration properties file. You can use this file to set various configuration parameters related to JDBC logging, such as jdbc.log.enable, jdbc.log.level, jdbc.log.file.path, or jdbc.log.trace. These parameters are persisted across server restarts and can be changed without modifying the source code. You do not use SAP Commerce Administration Console, Java code, or Backoffice Administration Cockpit to persist changes to enable and disable JDBC logging. Reference: 2