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.

The ImpEx headers that you can use to update an SAP Commerce Cloud item are INSERT_UPDATE UserGroup;UID[unique=true];locname[lang=en];locname[lang=de];groups(uid)[mode=append] and UPDATE UserGroup;UID[unique=true];locname;groups(uid)[mode=append]. These headers can modify existing items or create new items if they do not exist. The INSERT_UPDATE header can also specify the language for localized attributes using the lang modifier. The other headers are not valid because they either use an incorrect syntax for the lang modifier (B) or do not specify the unique attribute (D).

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

The scripting languages that are supported by the Backoffice application in SAP Commerce are Groovy, BeanShell, and JavaScript. These languages can be used to create scripts for various purposes such as data manipulation, testing, debugging, or automation. Python and Bash are not supported by the Backoffice application