FMR 11.0 release notes - Revision history

Vmurrell: /* Environment Synchronisation temporarily removed */

2022-07-22T11:11:59Z

‎Environment Synchronisation temporarily removed

2022-04-12T18:30:43Z

‎FMR 11 incompatible with FMR 10 databases

2022-01-19T14:45:19Z

‎Fusion Security support deprecated=

2022-01-19T14:45:10Z

‎Breaking changes

2022-01-14T15:41:36Z

‎Complete list of features and changes in FMR 11.0

2022-01-14T15:40:24Z

‎Strengthen security by externalising the password used to encrypt database and other passwords

2022-01-14T15:36:46Z

‎Strengthen security by externalising the password used to encrypt database and other passwords

2022-01-14T15:35:16Z

‎Other new features in FMR 11

2022-01-07T17:06:44Z

‎Overview

2022-01-07T17:05:36Z

@@ Line 74: / Line 74: @@
 =Environment Synchronisation temporarily removed=
 FMR 11.0 does not provide an [[Synchronise structural metadata between FMR environments|Environment Synchronisation]] tool for moving structures between two Registry installations. The tool is being redesigned to improve usability and performance, and support the SDMX 3.0 information model.
 =Complete list of features and changes in FMR 11.0=

@@ Line 55: / Line 55: @@
 =Breaking changes=
 ====FMR 11 incompatible with FMR 10 databases====
-FMR 11.0 is not compatible with FMR 10 operating databases. Upgrading from FMR 11 therefore requires the software to be installed on a new database schema and existing structural metadata migrated by hand. [[Upgrading to Version 11]] explains how.
+FMR 11.0 is not compatible with FMR 10 operating databases. Upgrading from FMR 11 therefore requires the software to be installed on a new database schema and existing structural metadata migrated by hand. [[Upgrading_from_Version_10_to_Version_11]] explains how.
 ====Upper case enforced for Maintainable Structure IDs====

@@ Line 67: / Line 67: @@
 Structure IDs will automatically be converted to upper case on import. An error will result should attempts be made to import two structures with IDs that differ only in case.
-====Fusion Security support deprecated=====
+====Fusion Security support deprecated====
 Fusion Security is no longer supported for user authentication. FMR 11 supports two options:
 * Microsoft Active Directory

← Older revision		Revision as of 14:45, 19 January 2022
Line 66:		Line 66:

	Structure IDs will automatically be converted to upper case on import. An error will result should attempts be made to import two structures with IDs that differ only in case.		Structure IDs will automatically be converted to upper case on import. An error will result should attempts be made to import two structures with IDs that differ only in case.
		+
		+	====Fusion Security support deprecated=====
		+	Fusion Security is no longer supported for user authentication. FMR 11 supports two options:
		+	* Microsoft Active Directory
		+	* OpenLDAP

	=Environment Synchronisation temporarily removed=		=Environment Synchronisation temporarily removed=

← Older revision		Revision as of 15:41, 14 January 2022
Line 551:		Line 551:

	IDs are converted to upper case on structure import. Attempting to import structures with IDs that differ only in case will result in an error.		IDs are converted to upper case on structure import. Attempting to import structures with IDs that differ only in case will result in an error.
		+
		+	\|-
		+	\|
		+	FMR11-79
		+	\|
		+	Change
		+	\|
		+	Strengthen security by externalising the password used to encrypt database and other passwords
		+	\|
		+	Passwords for database access and other purposes are encrypted using AES-256. In FMR 11, the password for that encryption is randomly generated at install time and stored in the properties file which defaults to fmr.properties. Access to the properties file must therefore be strictly controlled using filesystem access controls. The change makes the password unique to each installation and reduces the risk of security being compromised.

	\|}		\|}

@@ Line 46: / Line 46: @@
 ====Strengthen security by externalising the password used to encrypt database and other passwords====
-Passwords for database access and other purposes are encrypted using AES-256. In FMR 11, the password for that encryption is randomly generated at install time and stored in the properties file which defaults to <code>fmr.properies</code>. Access to the properties file must therefore be strictly controlled using filesystem access controls. The change makes the password unique to each installation and reduces the risk of security being compromised.
+Passwords for database access and other purposes are encrypted using AES-256. In FMR 11, the password for that encryption is randomly generated at install time and stored in the properties file which defaults to <code>fmr.properties</code>. Access to the properties file must therefore be strictly controlled using filesystem access controls. The change makes the password unique to each installation and reduces the risk of security being compromised.
 =Backward compatibility=

@@ Line 44: / Line 44: @@
 JNDI data sources can now be used for FMR's operating database connection when deployed on Tomcat or JBoss web application servers.<br>
 Support for Oracle Weblogic is planned for a future FMR 11 release.
 =Backward compatibility=

@@ Line 2: / Line 2: @@
 FMR 11.0 implements the SDMX 3.0 information model and differs from FMR 10 which uses SDMX 2.1.
-Backward compatibility with SDMX 2.1 and FMR 10 has been preserved where possible allowing upgrade to FMR 11 with few changes to operating procedures and intergated systems / processes. However, FMR 11 is not compatible with existing FMR 10 databases requiring a fresh install and export / import of the structural metadata content.
+However, backward compatibility with SDMX 2.1 and FMR 10 has been preserved where possible allowing upgrade to FMR 11 with few changes to operating procedures and intergated systems / processes.
 =Key new SDMX 3.0 features supported by FMR 11=

← Older revision		Revision as of 17:05, 7 January 2022
Line 1:		Line 1:
−	FMR 11.0 implements the SDMX 3.0 information model and differs ~~fundamentally in that respect~~ from FMR 10 which ~~is designed around~~ SDMX 2.1.	+	=Overview=
		+	FMR 11.0 implements the SDMX 3.0 information model and differs from FMR 10 which uses SDMX 2.1.

	Backward compatibility with SDMX 2.1 and FMR 10 has been preserved where possible allowing upgrade to FMR 11 with few changes to operating procedures and intergated systems / processes. However, FMR 11 is not compatible with existing FMR 10 databases requiring a fresh install and export / import of the structural metadata content.		Backward compatibility with SDMX 2.1 and FMR 10 has been preserved where possible allowing upgrade to FMR 11 with few changes to operating procedures and intergated systems / processes. However, FMR 11 is not compatible with existing FMR 10 databases requiring a fresh install and export / import of the structural metadata content.