|
Set up a MySQL database as follows:
utf8 character set encoding utf8_bin collation (to ensure case sensitivity).Here is an example of how to do that. When FishEye/Crucible and MySQL run on the same machine (accessible through localhost), issue the following commands (replacing fisheyeuser and password with you own values):
mysql> SET GLOBAL storage_engine = 'InnoDB'; mysql> CREATE DATABASE fisheye CHARACTER SET utf8 COLLATE utf8_bin; mysql> GRANT ALL PRIVILEGES ON fisheye.* TO 'fisheyeuser'@'localhost' IDENTIFIED BY 'password'; mysql> FLUSH PRIVILEGES; mysql> QUIT |
For MySQL 5.6 and later, replace the first statement (SET GLOBAL storage_engine = 'InnoDB') with the following:
|
This creates an empty MySQL database with the name fisheye, and a user that can log in from the host that FIshEye is running on who has full access to the newly created database. In particular, the user should be allowed to create and drop tables, indexes and other constraints.
You will also need to set the Server Characterset to utf8. This can be done by adding the following in my.ini for Windows or my.cnf for other operating systems (create the file at /etc/my.cnf if it doesn't already exist). It has to be declared in the Server section, which is the section after [mysqld]:
[mysqld] character-set-server=utf8 |
You'll need to restart MySQL for that change to take effect. Now use the status command to verify database character encoding information:
mysql> use fisheye; mysql> status; |
Screenshot: Using the MySQL status command

Both the server and database character set must be UTF-8. You may not initially notice a problem because of the characterset overlap but this is indeed a requirement. We've verified that when using a charset such as Swedish 7 bit as the server charset and UTF-8 as the database charset data corruption is easy to reproduce and obvious. This proves that the server character set is as important and that data corruption is possible when there is a charset mismatch. We absolutely cannot suggest a configuration where the server charset and database charset are anything other than UTF-8. |
In order to migrate to a different database backend, you must create a backup of sql data, configure the database and finally import the data using a backup restoration process. This can be done from either the FishEye/Crucible administration console, which streamlines the process, or using the command line tool which FishEye/Crucible provides.
Database page in FishEye/Crucible's Administration console.To log in to the Admin area, you can either:
HOSTNAME is the name of the server on which you installed Fisheye.Once logged in as an administrator you can also get to the Admin area by clicking the 'cog' menu in the FishEye/Crucible header, and choosing Administration.

.jar file in the classpath (see Prerequisites section above for instructions on how to install the driver). Also, ensure that the database user can log in to the database from the machine that FishEye/Crucible is running on and that all the required privileges are present.
sql data from the FishEye/Crucible instance. Read Backing up and restoring FishEye data and Backing up and restoring Crucible data for information on how to create a backup.Run the following command from the <FishEye installation directory>/bin directory:
$ ./fisheyectl.sh restore --sql \
--file /path/to/backup.zip \
--dbtype mysql \
--jdbcurl jdbc:mysql://hostname/dbname \
--username crucible \
--password password
|