Hide Forgot
++ This bug is a clone of bug 779527 ++ project_key: SOA Currently the directory jboss-soa-p.5.0.0\jbpm-jpdl\config there are a bunch of configuration files to help customers customize the jBPM configuration for a different DB. The jbpm.cfg.xml in there is the wrong one, I belive. Customers should not customize the jbpm.cfg.xml. So that file should not be in the config directory. There should be one base hibernate.cfg.xml that serves for most DBs. It should point to the datasource called java:/JbpmDS. Only for some dbs, it's necessary to have a differrent database-specific ${database}.hibernate.cfg.xml file. E.g. for DB2, maybe for others as well. The ${database}-ds.xml configuration files are good. Updates to these configuration files should be done in the productization build script. Care has to be taken with changing the source files in the jBPM source branch as that might lead to breaking the build. In the documentation, Chapter 3 should be completly replaced with an explanation of how these configuration files should be used to customize jBPM for a given database. It should also be added that all jbpm configuration changes not described in the product documentation is not supported. The documentation should also include the libraries: where the customer can find them and where to put them.