Install iceScrum on your own server.
We recommend the use of Ubuntu 16.04 LTS (Long Term Support). However, iceScrum can be used with other Linux distributions, Windows and Mac OS.
iceScrum v7 requires Java 7 or 8.
You can download the latest Java 8 version for your platform here.
Be sure that the Java executable, java, is accessible (e.g. on Windows you can add its path to your PATH environment variable if necessary) by typing this in the Command Line:
A very important step is the choice of your database management system. iceScrum comes with an embedded H2 database so you can try iceScrum without needing to install or configure a DBMS. However, it is NOT suitable for production environments in terms of reliability and performances.
Thus, we recommend the use of one of the external DBMS compatible with iceScrum: MySQL, PostgreSQL, MS SQL Server or Oracle. If you do so, create and empty database for iceScrum, usually named icescrum, with a proper charset/collation, we strongly recommend UTF-8.
Here is how to create the empty database on MYSQL:
CREATE DATABASE `icescrum` CHARACTER SET utf8 COLLATE utf8_general_ci;
With PostgresQL, be careful, you have to use the “public” schema otherwise iceScrum won’t restart.
Then, provide the JDBC connection URL (which is pre-filled according to the DBMS you chose) that includes your database name and iceScrum will take care of creating the database structure.
If the setup refuses to go to the next step then please check that the settings entered in the current step are correct.
Invitations, notifications when stories are updated and password retrieval all require iceScrum to send emails. Thus, to enable the features you need to provide iceScrum with an external SMTP server.
You will need to enter the email server host, port and your username/password if your server requires authentication.
Then, you may have to add a technical setting in the “Technical setting” field. Usually only of them is required but if you need to combine them, separate them by a comma.
Once iceScrum is configured, depending on the settings you have changed, you may have to restart it. To do so, just kill the command (or close the command line) and start it again. Then, you can start using it and follow the getting started guide.
The settings you have chosen can be updated later:
You may want to get help for your install and configuration. iceScrum developers can help you! We can install and configure your iceScrum server (contact us) and iceScrum Pro Standalone comes with dedicated support (email, skype, phone).
If you want to use iceScrum with the HTTPS protocol and if you use a reverse proxy to manage the SSL part of it, then you should rather install iceScrum the old fashioned way with a Tomcat server: install iceScrum on Tomcat.
Starting iceScrum at server startup
With icescrum.jar, starting iceScrum is a simple command. Thus, starting iceScrum automatically at your server startup is not specific to iceScrum at all, it is rather specific to your operating system. You should find plenty of resources on the internet that explain how to start a command automatically at your OS startup. There is just one thing that you should keep in mind: if iceScrum requires other services on the same server, e.g. a local MySQL or mail server, then they will need to be started at server startup as well.
If this did not help you find the cause of your problem, please read the following sections about logs.
You should find a logs directory in the directory where you started the command from.
You may want to enable more log information. If you are using iceScrum Pro, you have to enable verbose logging in the settings administration. Otherwise, enable the debug setting in your config.groovy file:
icescrum.debug.enable = true
Then, have a look at the icescrum.log file. If you have a license then please contact us, we will be happy to help! Otherwise, post your issue with the logs on our community forums in order to get help.