This document sets forth the requirements and configuration suggestions for using MySQL with ScrumWorks Pro. Hypersonic database is not recommended for production use. Users are encouraged to use the MySQL database for production use.
Your ScrumWorks Pro license or support contract does not include technical support related to MySQL installation, configuration, or troubleshooting of any kind. Please refer to the MySQL web site for documentation and support related to MySQL.
MySQL components are not bundled with ScrumWorks Pro, and all MySQL components must be downloaded from the MySQL web site directly for licensing reasons. Using MySQL with ScrumWorks Pro requires:
ScrumWorks Pro release 3+
MySQL 5.0.x or 5.1.x Community Edition or Enterprise Edition
MySQL Connector/J version 5.1
MySQL Connector/J version 5.1 is required for the ScrumWorks Pro Server to communicate with the MySQL server.
Specifically, minor update 5.1.7 or higher is required. The ScrumWorks MySQL installer or transfer tool will prompt you to manually download this component.
You can get the latest version from the
MySQL Connector/J web site.
Empty MySQL database
ScrumWorks Pro needs an empty database created in your MySQL installation. A MySQL user must also be supplied with permissions to drop and create tables inside that database. Note that general MySQL security practices recommend creating users with special permissions rather than using the "root" user directly.
The InnoDB storage engine is required due to the way ScrumWorks Pro handles transactions. Failure to use InnoDB tables will result in an unstable system and upgrade issues. To enable InnoDB on a MySQL server:
Locat the MySQL configuration file. On Unix systems this typically called "my.cnf", while on Windows "my.ini"
Edit the configuration file and remove or comment-out the line "skip-innodb", if it exists in the file.
Uncomment or add a line "innodb"
ther InnoDB related configuration options can be uncommented or added; please read MySQL's documentation on InnoDB related configuration options (external link).
ScrumWorks Pro 3.0 (MySQL) shipped with a maximum connection pool size of 20. ScrumWorks Pro 3.1+ (MySQL)
ships with a maximum connection pool size of 50. This is often sufficient for moderate use,
but organizations experiencing connection pool issues will need to increase this value. Users will see an error
"No ManagedConnections available" when the connection pool is insufficient.
Contact your MySQL administrator to find out what you can safely change this parameter to.
You can increase the connection pool size:
Shut down your ScrumWorks Pro server
Edit the file INSTALL_DIR/server/scrumworks/deploy/scrumworks-mysql-ds.xml
Find the option <max-pool-size>20</max-pool-size>
Change "20" to the value supplied by your MySQL database administrator