Upgrading to Version 11.4 - Revision history

Plazarou: /* Important Information for Registries using MySQL Database */

2022-10-14T07:34:27Z

‎Important Information for Registries using MySQL Database

2022-10-10T12:48:03Z

‎Troubleshooting

2022-10-10T12:44:34Z

‎Important Information for Registries using MySQL Database

2022-10-10T12:42:33Z

‎Troubleshooting

2022-10-10T12:39:50Z

‎Troubleshooting

2022-10-10T12:34:19Z

‎Supplying the JAR file to your Java Web Server

2022-10-10T12:34:01Z

‎Supplying the JAR file to your Java Web Server

2022-10-10T12:29:31Z

‎Change setenv.bat

2022-10-10T12:28:52Z

‎Adding the MySQL Connector Dependency

2022-10-10T12:26:26Z

‎Obtaining the MySql Connector Dependency

@@ Line 1: / Line 1: @@
 [[Category:How_To V11]]
 =Important Information for Registries using MySQL Database=
-From version 11.4.0 onwards, the Fusion Metadata Registry will no longer ship with a MySQL connector (due to licensing issues).  FMR can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of FMR, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.4 or later.  If you do not supply this dependency then you will receive a "ClassNotFoundException: com.mysql.cj.jdbc.Driver" error when attempting to start FMR and communicate with a MySQL database.
+From version 11.4.0 onwards, the Fusion Metadata Registry will '''no longer''' ship with a MySQL connector due to licensing issues.  FMR can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of FMR, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.4 or later.  If you do not supply this dependency then you will receive a "ClassNotFoundException: com.mysql.cj.jdbc.Driver" error when attempting to start FMR and communicate with a MySQL database.
 ==Upgrading from Version 10 or earlier==

← Older revision		Revision as of 12:48, 10 October 2022
Line 73:		Line 73:
	</pre>		</pre>

−	This means that the JAR file has not been supplied correctly to your	+	This means that the JAR file has not been supplied correctly to your Web Server. Please review the steps you took in supplying the jar file to your Web Server and ensure that all locations and file names have been correctly specified.

@@ Line 1: / Line 1: @@
 [[Category:How_To V11]]
 =Important Information for Registries using MySQL Database=
-From version 11.4.0 onwards, the Fusion Metadata Registry will no longer ship with a MySQL connector (due to licensing issues).  FMR can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of FMR, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.4 or later.
+From version 11.4.0 onwards, the Fusion Metadata Registry will no longer ship with a MySQL connector (due to licensing issues).  FMR can still be used with a MySQL database, but you will need to manually supply the MySQL dependency JAR file. If you were using MySQL with an earlier version of FMR, then you will need to make this change in order to successfully start your Tomcat after installing Version 11.4 or later.  If you do not supply this dependency then you will receive a "ClassNotFoundException: com.mysql.cj.jdbc.Driver" error when attempting to start FMR and communicate with a MySQL database.
 ==Upgrading from Version 10 or earlier==

@@ Line 59: / Line 59: @@
 ==Troubleshooting==
-If FMR fails to start and looking at the logs you see the following error:
+If FMR fails to start, inspect the Web Server logs.  If you encounter the following error:
 <pre>
@@ Line 72: / Line 72: @@
          ...
 </pre>

← Older revision		Revision as of 12:39, 10 October 2022
Line 59:		Line 59:

	==Troubleshooting==		==Troubleshooting==
		+	If FMR fails to start and looking at the logs you see the following error:
		+
		+	<pre>
		+	2022-09-30 23:59:59.999 WARN main org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator - HHH000342: Could not obtain connection to query metadata
		+	java.sql.SQLException: Cannot load JDBC driver class 'com.mysql.cj.jdbc.Driver'
		+	at org.apache.commons.dbcp2.DriverFactory.createDriver(DriverFactory.java:54)
		+	at org.apache.commons.dbcp2.BasicDataSource.createConnectionFactory(BasicDataSource.java:459)
		+	at org.apache.commons.dbcp2.BasicDataSource.createDataSource(BasicDataSource.java:525)
		+	...
		+	Caused by: java.lang.ClassNotFoundException: com.mysql.cj.jdbc.Driver
		+	at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1407)
		+	...
		+	</pre>

@@ Line 46: / Line 46: @@
 [[File:Jar file location.PNG|600px]]<br>
-==Supplying the JAR file to your Java Web Server==
+==Providing the JAR file to your Java Web Server==
 There are a number of ways that the JAR file can be supplied to your Web Server and these ways will depend on the Web Server you are using.  We recommend the use of Apache Tomcat since it is quick and easy to configure.
 For Apache Tomcat, the jar file can be added to the "lib" folder of the Tomcat instance.  The jar could also be added to the WEB-INF\lib folder of FMR once FMR has been expanded under the "webapps" directory (this method is not recommended as the file is lost when the Registry is upgraded). Another method is to specify the jar via the "setenv" file which allows the setting of environment variables at Tomcat launch-time.
 ===Specifying via setenv===
@@ Line 58: / Line 57: @@
   set CLASSPATH=C:\SQL_Connector\mysql-connector-java-8.0.30\mysql-connector-java-8.0.30.jar

@@ Line 48: / Line 48: @@
 ==Supplying the JAR file to your Java Web Server==
-===Change setenv.bat===
+===Via setenv===
 setenv.bat (or setenv.sh for UNIX) is located in the Tomcat's bin folder.  If it doesn't exist simply create it.

@@ Line 12: / Line 12: @@
 # Obtain the correct dependency file
 # Supply this to your Java Web Server (e.g. Tomcat) that you are using to run the Registry.
 ==Obtaining the MySql Connector Dependency==
@@ Line 47: / Line 46: @@
 [[File:Jar file location.PNG|600px]]<br>
-==Change setenv.bat==
+==Supplying the JAR file to your Java Web Server==
-Setenv.bat is located in the Tomcat's bin folder and it can easily be edited using Notepad.
+===Change setenv.bat===
-A line need to be added, in the example above it would be this:
+In this file, add the location of the mysql-connector jar file to the CLASSPATH.  This can be achieved by use of the following line (which uses a location from the example above):
   set CLASSPATH=C:\SQL_Connector\mysql-connector-java-8.0.30\mysql-connector-java-8.0.30.jar
 To the command set CLASSPATH =, the location of the jar file AND the name of the file is included.
 You can now start the Tomcat and once started, can use FMR.

@@ Line 31: / Line 31: @@
 [[File:Download Connector Confirm.PNG|600px]]<br>
 Once the zip file has been downloaded you need to unzip it in the usual way to a folder which will always be available to the application.
@@ Line 48: / Line 46: @@
 [[File:Jar file location.PNG|600px]]<br>
 ==Change setenv.bat==