Install Fusion Metadata Registry MySQL

From Metadata Technology Wiki
Jump to navigation Jump to search


To successfully install FMR using MySql you need ensure that the previous steps have been followed:

  • Install a Java Runtime Environment More
  • Install and configure an Apache Tomcat web application server More
  • Install and configure a MySQL database More
  • Deploy the Fusion Metadata Registry software to the web application server More


There are two further steps to complete a fresh Fusion Metadata Registry installation:

  • Connect to the database
  • Configure some basic server settings

Database Connection

This is where you need to provide the details of how to connect to your MySQL database service, the schema to use, and the database account credentials.

Database Page
  • Choose MySQL as the Database Type
  • The Server should be localhost if you installed MySQL on the same machine as the Registy, or the hostname of the machine running your database service
  • The default MySQL port is 3306
  • The Schema should be the name of the dedicated schema you created when configuring the database, for instance fusion_registry
  • The UserId and Password should be those of an account on your database service that has sufficient privileges to read and write to the schema

Clicking Apply Settings will test the connection to the database and automatically build all of the tables.

Database Connection Troubleshooting

Any problems Fusion Registry encounters connecting to the database service will result in an error message. The example below indicates that the user credentials are wrong.

Installation Error

Server Settings

Some basic settings are now required.

Server Settings Page
  • Server URL is the URL on which Fusion Registry is operating. When running on a private machine, this can be set to

If running on a server and will be used by multiple people, then the Server URL will be

  • Choose a username and password for the primary administration account. This is typically named
root or admin 

You can also set a limit on the maximum of unsuccessful log in attempts before the account is locked