Currently all SolarNet applications rely on a single JDBC DataSource for their database connectivity. The SolarQuery application is mostly read-only, with just a single task that needs write access in the database, to update audit query counts. It would be useful to be able to deploy SolarQuery so that queries are directed against read-only database replicas. For that, a second DataSource must be used with different connection properties for that write task.

 

Update the SolarQuery application to look for and use a second "write access" DataSource. It should continue to work with only a single DataSource as well, which would be assumed as write-capable.