MySQL Database Transfer Guide for Release 3.1

Documentation Home | Desktop Client User Guide | Web Client User Guide | Support and Training
Organizations with large databases and/or user bases may wish to use MySQL instead of the default Hypersonic database. This guide is intended to describe the necessary steps for moving the data between the databases.
Quick Links
Transferring to MySQL Post-transfer configuration

Documentation Home

Transferring to MySQL

General Precautions
This is a one-way process. Once the data has been moved to MySQL, there is no process for switching back to the default Hypersonic database. You should only perform the transfer if you are willing to abandon the default database.

Before getting started with the transfer from Hypersonic to MySQL, please follow the ScrumWorks Pro backup procedure.

» top

Requirements
ScrumWorks Pro with MySQL requires:
  • ScrumWorks Pro release 3.0.0+

  • MySQL 5.0.x Community Edition or Enterprise Edition


  • An empty database created in your MySQL installation. The user you want to use for the migration must be able to drop and create tables inside that database.



» top

MySQL Support
Your ScrumWorks Pro license 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.


» top

Transfer on Windows
The Windows MySQL transfer tool is distributed in a file called mysql-transfer.exe. You can download the mysql-transfer.exe package from the ScrumWorks Upgrade website.
  1. Stop your ScrumWorks Pro Server.

  2. Launch mysql-transfer.exe. Note that the transfer tool takes some time to start up since it has to extract the files necessary for it to run.

  3. Fill in the required data about your ScrumWorks Pro Server root directory and MySQL database information.

  4. The mysql-transfer.exe program will perform the transfer, create the necessary files, and configure the ScrumWorks Pro Server to run with MySQL.

    Note: The transfer process may run for several hours depending on the size of your database.

    To abort the transfer process, use CTRL-C

    If anything goes wrong with the data transfer, the process will abort and you will have a scrumworks-transfer.log file. Your existing data has not been modified and it is safe to restart the ScrumWorks Pro Server with the old database. The scrumworks-transfer.log file may contain relevant information about the reason your transfer failed.

  5. Start your ScrumWorks Pro Server. Your ScrumWorks Pro Server is now using a MySQL database.



» top

Transfer on Linux and Mac OS X
The Unix transfer tool is distributed in a package called scrumworks-{version}-mysql-transfer.tar.bz2. You can download the package from the ScrumWorks Upgrade website.
  1. Stop your ScrumWorks Pro Server.

  2. Extract the package:
    tar jxvf scrumworks-{version}-mysql-transfer.tar.bz2

  3. Change to the scrumworks-transfer directory:
    cd scrumworks-transfer

  4. Run the transfer tool:
    ./mysql-transfer.sh

  5. Answer the questions about your ScrumWorks Pro Server root directory and MySQL database information.

  6. The installation will perform the transfer, create the necessary files, and configure the ScrumWorks Pro Server to run with MySQL.

    Note: The transfer process may run for several hours depending on the size of your database.

    To abort the transfer process, use CTRL-C

    If anything goes wrong with the data transfer, the process will abort and you will have a scrumworks-transfer.log file. Your existing data has not been modified and it is safe to restart the ScrumWorks Pro Server with the old database. The scrumworks-transfer.log file may contain relevant information about the reason your transfer failed.

  7. Start your ScrumWorks Pro Server. Your ScrumWorks Pro Server is now using a MySQL database.



» top



Post-transfer configuration

Connection Pool Sizes
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 fine for medium use, but larger companies with more concurrent users will need to increase this value. The error you will see on the client is a message that says "No ManagedConnections available".

Contact your MySQL administrator to find out what you can safely change this parameter to. You can increase the connection pool size:
  1. Shut down your ScrumWorks Pro server

  2. Edit the file INSTALL_DIR/server/scrumworks/deploy/scrumworks-mysql-ds.xml

  3. Find the option <max-pool-size>20</max-pool-size>

  4. Change "20" to the value supplied by your MySQL database administrator

  5. Save your changes

  6. Restart your ScrumWorks Pro server

» top



Documentation Home | Desktop Client User Guide | Web Client User Guide | Support and Training

© 2008 Scrumworks, LLC. All rights reserved.