E_C4HYCP_12 SAP Certified Product Support Specialist - SAP Commerce Cloud Questions and Answers

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

You can investigate a connection pool issue by checking the physical connections, requesting console log files and thread dumps, and checking the configuration parameters related to connection pool. The physical connections can help you monitor the number and status of connections to the database. The console log files and thread dumps can help you identify any errors or exceptions related to connection pool. The configuration parameters can help you adjust the connection pool size, timeout, or validation settings. You do not need to request heap dumps or database dumps, as they are not relevant for connection pool issues.

When you set the impex.legacy.mode property to True, you enable the legacy mode of ImpEx, which means that the ServiceLayer interceptors and validators are not triggered during the import/export process and that the INSERT, UPDATE, and REMOVE operations are not performed by the ModelService during the import. The legacy mode is a quick and crude way of importing data that bypasses the ServiceLayer of SAP Commerce. It may improve performance but also increase the risk of data inconsistency or errors. Reference: 2