Description of problem: Version-Release number of selected component (if applicable): SOA 6.0.0.ER1 How reproducible: Steps to Reproduce: 1. Install SOA 6.0.0.ER1 using installer 2. In post-installation configuration of the installer create a new datasource (e.g. with connection to Mysql database) with appropriate jdbc driver. 3. Finish installer Actual results: * New datasource along with appropriate driver is created in standalone.xml, however the existing datasources (jbpmDS, OverlordRTgov ds, ...) still use the default H2 database. Expected results: * After explicitly configuring a new database driver in the installer, this database driver should be used for existing datasources as well. Additional info: * We can consider creating a checkbox in the installer GUI so users can decide.
The scripts now exist, and the chosen JDBC driver will be put into the existing datasources through the corresponding *.properties file.
Verified in FSW 6.0.0.ER3. However, datasources are updated to use the new database driver, credentials remains the same which won't be correct until someone creates new users in its DB with exact the same credentials as the installer script specified. Moreover, URL of the jBPM DS is not updated: https://bugzilla.redhat.com/show_bug.cgi?id=1011494