Hi Fellas, Very Good morning. Here is a short article on properties (configurations) which could help you to improve development velocity.
Hybris provides many of the OOB application configurations using project.properties and local.properties which you can choose to enable/disable as per your project needs in different environment. These properties gives you a control of some OOB functions which can make your development cycle easier and faster.
Without wasting anymore time, find below list and choose to enable/disable as per your project needs… 🙂
Activate JDBC logs by setting following property to true
To get full logs, that is logs consisting of both your prepared statement and your actual statement with values, set db.log.sql.parameters to true
To get stack trace info, set db.log.appendStackTrace to true.
It can be set to true only in the development mode (i.e., when development.mode=true).
The purpose of the property is to speed up development by omitting some caches, or resource loading (for example, labels are reloaded after a user logs out from Backoffice)
This property enables the Deploy button on backoffice. You can build and redeploy a specific backoffice extension by doing following steps :
ant buildin your particular extension
- Click on
Deploybutton in backoffice to do a run-time redeployment
Comma-separated list of triggers that should start the reset. During the development, it might be useful to reset the Backoffice Framework configuration automatically, for example on every application startup, to remove any test changes done in the Orchestrator. The reset restores the configuration to the default state defined in the *-backoffice-widgets.xml and *-backoffice-config.xml files in your extensions.
comma-separated list of configurations that should be reset, no matter which event triggered the reset. Possible values are widgets, cockpitConfig.
Task Engine Properties
In order to disable cronjobs to start automatically on the server startup you need to add
To enables task processing, ‘true’ by default, setting it to ‘false’ disables it (tasks and cronjobs will not be executed on the current node)
Platform may process tasks very fast and poll the database to retrieve new tasks immediately. Since the task engine queues only a small portion of retrieved tasks, the number of processed tasks per poll is small too. As a result, the task engine performance may drop drastically because it spends most of the time on retrieving another batch of tasks.
You can remedy this by setting the task.polling.interval.min property to an appropriate value. This value defines the minimum time interval (in seconds) between subsequent polls.
Storing Processing Logs in the Database
With the processengine.process.log.dbstore.enabled property set to true, the task engine task logger persists a log file in the database. The file contains logs gathered as a result of task engine processing tasks.