Step 1. Create a MySQL database

Set up a MySQL database as follows:

• Configure the database to use the InnoDB storage engine
• Create a database on MySQL for FishEye/Crucible to use
• Create a FishEye user on the database
• Configure the database to use utf8 character set encoding
• Configure the database to use 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

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

Step 2. Configure FishEye/Crucible to use MySQL, and migrate data

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 via a backup restoration process. This can be done from either the FishEye/Crucible administration console, which streamlines the process, or via the command line tool which FishEye/Crucible provides.

From FishEye/Crucible's administration area

1. Navigate to the Database page in FishEye/Crucible's Administration console
2. Click Test Connection to verify that FishEye/Crucible can log in to the database.
3. Select MySQL from the database type.
4. Fill in the appropriate fields, replacing the host, port, database name, username and password as required.
5. Click Test Connection to validate the values.
   
   Screenshot: Testing the connection
   
   
   
   If this fails, verify that you have the MySQL JDBC driver .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.
6. Click Save & Migrate to start the migration process.
   
   During the migration process (which will take several minutes, depending on the size of your database and network throughput), the product will be inaccessible to users and external API clients. Users will see a maintenance screen that informs them of the process. Should the migration fail for any reason, FishEye/Crucible will not switch to the new database and report on the encountered problems. Because the destination database may now contain some, but not yet all data, drop all tables, indexes and constraints before attempting a new migration.
   
   Screenshot: Migrating the database
   
   

From the command line

1. Create a backup of the 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.

2. Run the following command from the bin directory in FISHEYE_INST

   $ ./fisheyectl.sh restore --sql \ --file /path/to/backup.zip \ --dbtype mysql \ --jdbcurl jdbc:mysql://hostname/dbname \ --username crucible \ --password password

3. When the import is complete, FishEye/Crucible can be started and will use MySQL.