The MySQL distribution of ScrumWorks Pro allows use of the MySQL database. Before installing the MySQL distribution of ScrumWorks Pro, please read the MySQL requirements and configuration guide.
MySQL is recommended for large production ScrumWorks Pro instances, but requires systems administration knowledge to set up. The Hypersonic distribution is intended for quick and easy set up. If you wish to transfer from a Hypersonic to a MySQL database, please read the Hypersonic-to-MySQL transfer documentation.
Caution: once transferred to MySQL, ScrumWorks Pro data cannot be transferred back to Hypersonic.
Please request a trial license. You will receive an email with instructions on how to obtain ScrumWorks Pro. For all support related questions during your Scrumworks Pro Trial please contact us at: http://community.danube.com/danube
Existing customers can obtain the latest stable version of ScrumWorks Pro Mac OS X distribution from the ScrumWorks Pro download web site. Note, the same binaries are used for both upgrades and fresh installations.
scrumworks-pro-[version]-mac_linux.tar.bz2
tar -jxvf scrumworks-pro-[version]-mac_linux.tar.bz2
Run with root privileges:
# ./setup.sh
Follow the prompts to download the required third-party files. These files are necessary for a successful installation of ScrumWorks Pro (your server has no internet access).
After the installation is complete, ScrumWorks will be started automatically. The ScrumWorks Pro setup.sh program has registered ScrumWorks Pro server as a "launchdaemon" meaning that ScrumWorks Pro server will start automatically on reboot. Use launchctl to manually start/stop the ScrumWorks Pro service:
# launchctl start scrumworks
# launchctl stop scrumworks
setup.sh again. During the setup.sh script, indicate whether ScrumWorks Pro starts as a daemon or not. tar -jxvf scrumworks-pro-[version]-mac_linux.tar.bz2
As an unprivileged user, run:
./setup.sh
Follow the prompts to download the required third-party files. These files are necessary for a successful installation of ScrumWorks Pro (your server has no internet access).
After the upgrade is complete, ScrumWorks can be started as a foreground process with:
cd /path/to/scrumworks-version/bin
./scrumworks.sh
setup.sh again. During the setup.sh script, indicate whether ScrumWorks Pro starts as a daemon or not. Your installation can be accessed via a web browser once the ScrumWorks Pro starts. It may take a few minutes for the service to start, so please be patient. Once the server is up, open a web browser on the local machine and point to:
If a web page loads with login options, your installation is successful, congratulations!
Continue on to the documentation on using the ScrumWorks Pro Desktop Client.
INSTALLDIR/server/scrumworks/log/server.log
Log files are rotated once daily.
Please see our Support Resources with any questions or issues.
# launchctl stop scrumworks
# launchctl unload /Library/LaunchDaemons/scrumworks.plist
The ports ScrumWorks Pro server listens to by default should be fine for most users. If you have pre-existing software installed on your machine, such as IIS or another copy of JBoss, you may need to change the ports ScrumWorks uses. Also, you may wish to add SSL security to your installation. Please refer to the port and SSL configuration guide.
By default, ScrumWorks Pro is permitted to use up to 1024MB of memory. Please read the Performance Tuning Guide for instructions on changing the amount of memory used by the ScrumWorks Pro server.
You will need to restart the server for the changes to take effect.
Note that if the allocated memory is too large, the service will fail to start. In this case, the amount of allocated memory needs to be lowered. Please check with your Windows administrator for advice on adjusting ScrumWorks Pro server's memory allocation. For more information, please read Memory Management in ScrumWorks Pro.