Fusion Registry Wiki - User contributions [en]

What's new

2026-09-28T11:47:49Z

Vmurrell: /* Compatibility */

=September 2026 H2.0.0.01=
== Key Features ==

'''Fusion Data Browser''' - filters now follow the Dimension order as defined by the DSD.

'''Fusion Registry''' - behavioural change with Aggregations. [[Auto_Aggregate_items_using_hierarchies#Parameter_detail.3DforceAggregates | click here to read more]]. This can also be set when the Registry starts up [[Aggregations-_Series_Threshold| read more]].

Please refer to the change logs and Release Notes for more information.

== Compatibility ==
[[File:Compatibility-sept2026.png|800px]]

== Upgrade Instructions ==
No major upgrades are needed since R2.0.0.00_RFS_28.08.26. The upgrade process for this release consists only of updating the relevant components.

If you are moving to this hotfix from a P1 release or from a Version 11 release, complete the R2.0.0.00_RFS_28.08.26 upgrade first and refer to the R2.0.0.00_RFS_28.08.26 upgrade instructions that were supplied in the R2.0.0.00_RFS_28.08.26 release notes.

'''Optional configuration introduced by this hotfix''' - aggregation.query.limit — system property setting the matched series count above which hierarchy aggregates are no longer computed by default. Defaults to 10000 when not set.

=August 2026 R2.0.0.00=

==Migrating Regnology Fusion Statistics from Version 1.3 to Version 2.0 ==
Version 2.0 introduces significant changes.

This is a short guide for technical teams preparing to install or upgrade to the '''Spring Framework 7'''– based Fusion Registry.

For '''dependency detail''' and '''migration notes''', please open the attached PDF Document. [[File:Client-facing README.pdf]]

'''Fusion Registry — Client installation readiness (Spring 7)'''

== 1. What you must provide ==

{| class="wikitable"
|-
! Area !! Requirement
|-
| '''Java''' || '''JDK 17 or newer''' (LTS such as '''21''' recommended). JDK '''8''' and '''11''' are not sufficient for this release line.
|-
| '''Application server''' || A servlet container that implements '''Jakarta Servlet 6.1'''. '''Apache Tomcat 10+''' is the typical choice. '''Tomcat 9.x''' (and other servers stuck on <code>javax.*</code> / older Servlet APIs) must be upgraded or replaced before deployment.
|-
| '''JDBC drivers''' || Vendor JDBC drivers '''compatible with Java 17+''', matching your database major version. Align driver versions with your DBA — older drivers packaged for JDK 8 often cause runtime issues on newer JDKs.
|}

== 2. Tomcat upgrade (high level) ==

The Spring 7 stack uses the '''Jakarta EE 11/Servlet 6.1''' APIs (<code>jakarta.servlet.*</code>), rather than the legacy Java EE <code>javax.servlet.*</code>.

# Plan migration from '''Tomcat 9''' → '''Tomcat 10+''' (or another '''Servlet 6.1'''–certified server).
# Verify '''JVM options''' (<code>JAVA_HOME</code>, memory, encoding, timezone) on the new instance.
# Deploy only the '''new''' Registry WAR; do not mix '''old''' Spring 5 libraries on the shared Tomcat classpath.
# Re-test '''TLS''', '''reverse proxy''' (paths, headers, WebSockets if used), and '''JNDI''' datasource configuration if applicable.

== 3. Database connectors (JDBC) ==

Supported database platforms are those your contract and release notes specify (commonly '''MariaDB''', '''Oracle''', '''Microsoft SQL Server'''). For installation:

# '''Use a current JDBC driver''' from the database vendor, certified for '''JDK 17+''' and your '''supported''' database server version.
# Install the driver where your deployment model requires it ('''<code>$CATALINA_BASE/lib</code>''' for Tomcat-wide use, or follow your vendor runbook).
# '''Do not''' downgrade the driver to an old “JRE 8” artefact unless your support team explicitly approves it — classpath and TLS/cipher requirements often break on modern JDKs.
# Confirm '''connection URLs''', '''schemas''', '''collation/charset''', and '''pool sizing''' after the upgrade; Hibernate '''7.x''' / JPA '''3.2''' ride the same datasource configuration as in the technical brief.

== 4. Checklist — environment ready before installing the new Registry ==

Use this before first start in each environment (dev → test → prod).

=== Java and server ===

* ☐ '''JDK 17+''' installed; <code>java -version</code> matches the planned production JDK.
* ☐ '''Tomcat 10+''' (or equivalent '''Servlet 6.1''' server) installed and hardened (user, file permissions, logging).
* ☐ '''Tomcat service''' configured with sufficient '''heap''' and '''metaspace'''; garbage collector settings reviewed if you had custom tuning on JDK 8/11.
* ☐ '''File system''' paths for logs, temp, and Registry properties exist and are writable by the Tomcat user.

=== Database and JDBC ===

* ☐ '''Database version''' supported for this Registry release (confirm with release notes / your vendor).
* ☐ '''JDBC driver''' upgraded and tested against '''JDK 17+'''.
* ☐ '''Backup and restore''' procedure verified; a '''rollback''' snapshot exists before migration.
* ☐ '''Dedicated schema/user''' permissions unchanged or re-applied after any DBA maintenance.
* ☐ '''Character set / encoding''' aligned (e.g. UTF-8) end-to-end.

=== Security and networking ===

* ☐ '''TLS certificates''' valid on proxies and connectors; cipher suites acceptable to your security policy.
* ☐ '''Firewall''' rules allow app → DB, and clients → Registry as today.
* ☐ '''LDAP / SSO / OAuth''' (if used) endpoints and trust stores updated if URLs or certs changed during infra moves.

=== Application configuration ===

* ☐ '''<code>RegistryProperties</code>''' (or equivalent) points to the correct DB, LDAP, and paths for this environment.
* ☐ '''Secrets''' not embedded in old formats incompatible with the new image or systemd/tomcat layout.
* ☐ '''Smoke test plan''' agreed (login, structure browse, critical data/API flows).

=== Regression ===

* ☐ '''Staging''' run completed on JDK 17+ and Tomcat 10+ with production-like data volume where possible.
* ☐ '''Integration partners''' notified of cutover window if URLs or TLS fingerprints change.

== 5. After installation ==

* Monitor startup logs for '''<code>NoClassDefFoundError</code>''', '''<code>javax/</code>''' packages, or '''duplicate Spring/Hibernate''' JAR warnings (usually means classpath contamination).
* Keep the '''Spring 7 client brief''' (<code>docs/client-facing/README.md</code>) bookmarked for dependency versions (Spring '''7.0.x''', Spring Security '''7.0.x''', Hibernate '''7.2''', Jakarta Servlet '''6.1''', JPA '''3.2''').

== Compatibility ==
Below is a summary of the component compatibility for each Fusion Registry version. The recommended version is R2.0.0.00.

[[File:R2 Compatability.png|400px]]

==Key Features==
===Fusion Registry ===
* Upgrade from Spring 5 to Spring 7
* Support pop up box introduced [[Support_Tab| read more]]
* Database consistency checker web service [[Database_Consistency_Web_Service| read more]]
* Semantic and Non-Semantic structure versions - ability to co-exist
* Bulk Actions to include Hierarchy Associations
* Loading structures - ability to skip invalid structures [[Load_Structures#Submitting_Invalid_Structures| read more]]

More information can be found in the [[Change_Log_FR_-_V11_and_subsequent_releases#Release_R2.0.0.00_RFS_28.08.26_Released_August_28.2C_2026|Change Log.]]

===Fusion Data Browser ===
* Implementation of loading indicator
* Ability to implement a cookie policy [[Data_Browser_Configuration#Cookie_Notice|read more]]
* Language selection button placement
* <Enter> to work as Apply
* Loading wheel to display for very large datafiles'''

More information can be found in the [[Change_Log_Fusion_Data_Browser#Release_R2.0.0.00_RFS_28.08.26_Released_August_28.2C_2026|Change Log.]]

=== FXLData Enhancements ===
* Introduction of login functionality [[Security_and_Authentication_in_FXLData#Fusion_Registry_Authentication| read more.]]
* Introduction of System Properties reporter [[https://wiki.sdmxcloud.org/FXLData_System_Info| read more.]]
* Support for hierarchical structures in the query builder
* Improved medium verbosity logging: limited to API request URLs and response codes
* Alignment of result grid data order with selected codes in the query builder

More information can be found in the [[FXLData_Change_Log#Release_R2.0.0.00_RFS_28.08.26_Released_August_28.2C_2026|Change Log.]]

===Fusion Security Manager ===
* Data Point Rule changes.

More information can be found in the [[Change_Log_Fusion_Security_Manager#Release_R2.0.0.00_RFS_28.08.26_Released_August_28.2C_2026|Change Logs.]]

==Plus Miscellaneous bug fixes and minor enhancements, full details of which will be available in the Release Notes and Change Logs==

=July 2026 H1.3.1.01=
Hot fix to resolve alignment issue with the search bar in Fusion Data Browser.

=May 2026 P1.3.1.00=
=== Compatibility ===
Below is a summary of the component compatibility for each Fusion Registry version. The recommended version is P1.3.1.00.

[[File:Compatability- May26-Patch.png|400px]]

===Upgrade Instructions===
The upgrade process for this release consists only of updating the relevant components.

No new installations or additional configurations are required since H1.3.0.03_RFS_30.01.26.

=March 2026 H1.3.0.04 =

=== Compatibility ===

[[File:H1.04 - compatability.png|800px]]

=March 2026 H1.3.0.03=
[[FXLData - New Functions |Please refer to this article which details the new functions introduced in FXLData version H1.3.0.03.]]

=== Compatibility ===

The components that have changed since H1.3.0.02 are
* FXL Data
* and Fusion Data Browser.
Below is the complete list of Fusion Registry versions compatible with each other component for H1.3.0.03
{| class="wikitable"
|-
! Module !! Version (s)
|-
| FXL Data || H1.3.0.02, H1.3.0.03
|-
| Fusion Data Browser|| H1.3.0.02, H1.3.0.03
|-
| Fusion Security Manager|| H1.3.0.02, H1.3.0.03
|-
| Fusion Portal|| H1.3.0.02, H1.3.0.03
|-
| Fusion FAME Mapper|| H1.3.0.02, H1.3.0.03
|}

=August 2025 - R1.3.00=
[[FXLData_what%27s_new_in_R1.3%3F |Please refer to this article which summarises all the changes since the last main Release in January 2025 and the product specific change logs.]]

=July 4, 2025 - H1.2.04=
[[FXLData_Change_Log#H1.2.0.04_RFS_04.07.2025_.28Released_July_4.2C_2025.29 | Please see the change log for FXLData]]

=March 12, 2025 - H1.2.03=
[[Change_Log_FR_-_V11_and_subsequent_releases#H1.2.0.03_RFS_12.03.25_.28Released_March_12.2C_2025.29 | Please see the change log for Fusion Registry]]

[[File:RFS-ReleaseNotes-H1.2.0.03 RFS 12.03.25.pdf |Release Notes]]

==March 7, 2025 - H1.2.02==
[[FXLData_Change_Log| Please see the change log for FXLData]]

[[File:PDD - Enhanced Dataflow Selection Fusion Excel Data Wizard – English.pdf |Enhanced Dataflow selection in FXLData]]

==February 20, 2025 - H1.2.01==
[[Change_Log_FR_-_V11_and_subsequent_releases#H1.2.0.01_RFS_20.02.25_.28Released_February_20.2C_2025.29 | Please see the change log for Fusion Registry]]

[[FXLData_Change_Log| Please see the change log for FXLData]]

[[File:RFS-ReleaseNotes-H1.2.0.01 RFS 20.02.25 (1).pdf |Release Notes]]

=January 30, 2025 - R1.2.0=

[[Support for Multiple Measures| Support for Multiple Measures]] 

[[Web Services - GUI - Data| Web Services - GUI-Data - change to default SDMX version and ability to set a query period.]]

[[File:RFS-ReleaseNotes-R1.2.0.00 RFS 30.01.25.pdf |Release Notes]]

2026-08-19T11:23:42Z

Vmurrell: /* Example */