WebChart has it's own connection pool manager. There were several Java Servlet container such as Tomcat and Resin, both of them were very popular, but they have differnet database connection pool implementaion. In order to tranparently running on them, I wrote a dedicate database connection pool manager.
Since WebChart is just for intranet usage only, don't care too much about the performance, all the database connection configuration information is stored in the following file.
It's a pure text file, you can open and edit it with any text editor. It contains the following three sections.
# Datasource name list, separator by vertical line
DBLIST=datasource [|datasource [| datasourceâ€¦ ]]
# connection parameter for each datasource
datasource.DBHOST=JDBC DB URL (without the prefix)
datasource.MAXCONNS=Max Connections Limit
datasource.INITCONNS=Min Connections Limit
# WebChart Metadata datasource for Authorization
You can specify multiple data source name in the DBLIST line, and specify the data source name for each SQL query in the WebChart defination file (WCML), if you omit the data source name for each SQL, it will connect to the data source named "DEFAULT". If you want to use WebChart intergreted authorization features, you must specify a metadata data source in the "ADMINDB" line, and create some tables holding the users data and sessions data.
To be attention, there is no connection timeout exception for existing connection pool, you will never open the page if it cannot connect to the database, browser will always show you opening the page.
The database password is still stored in unencrypted format, but I am planing to improve the security features of WebChart.