Database Settings V10 - Revision history

Vmurrell at 12:59, 28 March 2024

2024-03-28T12:59:22Z

2024-03-27T14:38:53Z

‎Schemea

2024-03-23T12:09:47Z

2022-08-25T13:08:06Z

Vmurrell moved page Database Settings to Database Settings V10 without leaving a redirect

2021-05-05T08:04:32Z

‎Single Sign-On (SQL Server only)

2021-05-05T08:03:57Z

‎2. Oracle

2021-05-05T08:03:40Z

‎1. MySql

2021-03-18T09:52:33Z

‎Single Sign-On (SQL only)

2021-02-23T16:36:46Z

‎Database type

2021-02-23T16:35:52Z

‎Single Sign-On (SQL only)

← Older revision		Revision as of 12:59, 28 March 2024
Line 1:		Line 1:
−	[[Category:~~Draft_-_Installation_and_Configuration~~]]	+	[[Category:Installation_and_Configuration]]

	[[Category:FMR_Configuration_Reference]]		[[Category:FMR_Configuration_Reference]]

@@ Line 44: / Line 44: @@
 The default port used by Apache Tomcat is 3306.
-==Schemea==
+==Schema==
 Enter the name of the schema as it appears in your chosen application.

← Older revision		Revision as of 12:09, 23 March 2024
Line 1:		Line 1:
		+	[[Category:Draft_-_Installation_and_Configuration]]
		+
	[[Category:FMR_Configuration_Reference]]		[[Category:FMR_Configuration_Reference]]
	==Overview==		==Overview==

← Older revision		Revision as of 08:04, 5 May 2021
Line 55:		Line 55:
	Fusion Metadata Registry 10+ supports Single Sign-On (SSO) when connecting to a SQL Server database. This can be activated via the Registry User Interface if SQL Server is selected.		Fusion Metadata Registry 10+ supports Single Sign-On (SSO) when connecting to a SQL Server database. This can be activated via the Registry User Interface if SQL Server is selected.

−	[[File:Singleso1.PNG\|800px]]<br>	+	[[File:Singleso1.PNG\|Single Sign-On\|800px]]<br>

@@ Line 15: / Line 15: @@
 '''Example'''
-[[File:Sql2.png|800px]]
+[[File:Sql2.png|Example Oracle|800px]]
 ===3. SQL Server===

← Older revision	Revision as of 13:08, 25 August 2022
(No difference)

@@ Line 10: / Line 10: @@
 '''Example'''
-[[File:Sql1.png|800px]]
+[[File:Sql1.png|Example MySQL|800px]]
 ===2. Oracle===

@@ Line 51: / Line 51: @@
 This is the password for the database (NOT the password used in the Registry).
-==Single Sign-On (SQL only)==
+==Single Sign-On (SQL Server only)==
 Fusion Metadata Registry 10+ supports Single Sign-On (SSO) when connecting to a SQL Server database.  This can be activated via the Registry User Interface if SQL Server is selected.

@@ Line 7: / Line 7: @@
 Options available are:
-===MySql===
+===1. MySql===
 '''Example'''
 [[File:Sql1.png|800px]]
-===Oracle===
+===2. Oracle===
 '''Example'''
 [[File:Sql2.png|800px]]
-===SQL Server===
+===3. SQL Server===
 '''Example'''
 See example of a [https://fmrwiki.sdmxcloud.org/Database_Settings#Single_Sign-On_.28SQL_only.29 SQL connection below].
-===Custom===
+===4. Custom===
 The schema must already exist but can be empty in which case the Registry will create all of the necessary tables. If you specify an existing Registry schema here, the service will attempt to load the content and settings within.

@@ Line 65: / Line 65: @@
 # Copy the DLL file to the Java Runtime “bin” directory that is running your Web Application Server.  It is important to place the DLL in the correct directory (for example:  C:\Java\jdk1.8.0_92\jre\bin).  Note: that modifying a Java Runtime in this manner means that all applications that use this Java Runtime will be affected.
-# Pass the DLL location to the Web Application Server on server startup.  If you are running Apache Tomcat as a service, please refer to section 11 of this document.  Otherwise this can be achieved by modifying the “setenv.bat” file located in the Tomcat bin directory. Locate the directory with the DLL you wish to add (e.g. c:\temp) then add the following line to setenv.bat and the Java library path will be modified allowing Tomcat to access the DLL file:
+# Pass the DLL location to the Web Application Server on server startup.  If you are running Apache Tomcat as a service, please refer to [https://fmrwiki.sdmxcloud.org/Install_Apache_Tomcat this article].  Otherwise this can be achieved by modifying the “setenv.bat” file located in the Tomcat bin directory. Locate the directory with the DLL you wish to add (e.g. c:\temp) then add the following line to setenv.bat and the Java library path will be modified allowing Tomcat to access the DLL file:
 '''set CATALINA_OPTS=%CATALINA_OPTS% -Djava.library.path=C:\temp\SSO_DLL'''