Fusion Registry Wiki - Recent changes [en]

Upgrading from Fusion Registry R1 series to Fusion Registry 2.0FR1.2

Vmurrell — Wed, 29 Jul 2026 15:12:03 GMT

Vmurrell moved page Upgrading from Fusion Registry R1 series to Fusion Registry 2.0FR1.2 to Upgrading from Fusion Registry R1 series to Fusion Registry 2.0 without leaving a redirect

New page

[[Category:Updating_Fusion_Registry]]

Please refer to this article [[What%27s_new#August_2026_R2.0.0.00.]]

Upgrading from FR R1 to FR1.2

Vmurrell — Wed, 29 Jul 2026 15:11:37 GMT

Vmurrell moved page Upgrading from FR R1 to FR1.2 to Upgrading from Fusion Registry R1 series to Fusion Registry 2.0FR1.2

New page

[[Category:Updating_Fusion_Registry]]

Please refer to this article [[What%27s_new#August_2026_R2.0.0.00.]]

Upgrading from FR R1 to FR1.2

Vmurrell — Wed, 29 Jul 2026 15:10:44 GMT

Created page with "Category:Updating_Fusion_Registry Please refer to this article What's_new#August_2026_R2.0.0.00."

New page

[[Category:Updating_Fusion_Registry]]

Please refer to this article [[What%27s_new#August_2026_R2.0.0.00.]]

What's new

Vmurrell — Wed, 29 Jul 2026 15:03:39 GMT

‎August 2026 R2.0.0.00

File:Client-facing README.pdf

Vmurrell — Wed, 29 Jul 2026 15:00:47 GMT

Vmurrell uploaded File:Client-facing README.pdf

New page

What's new

Vmurrell — Wed, 29 Jul 2026 12:26:18 GMT

‎Migrating Regnology Fusion Statistics from Version 1.3 to Version 2.0

File:RELEASE ENVIRONMENT UPGRADE.pdf

Vmurrell — Wed, 29 Jul 2026 12:23:09 GMT

Vmurrell uploaded File:RELEASE ENVIRONMENT UPGRADE.pdf

New page

What's new

Vmurrell — Wed, 29 Jul 2026 12:10:26 GMT

‎Migrating Regnology Fusion Statistics from Version 1.3 to Version 2.0

File:R2 Compatability.png

Vmurrell — Wed, 29 Jul 2026 09:53:04 GMT

Vmurrell uploaded File:R2 Compatability.png

New page

What's new

Vmurrell — Wed, 29 Jul 2026 09:47:30 GMT

@@ Line 4: / Line 4: @@
 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, see '''<code>docs/client-facing/README.md</code>''' (Spring 7 client technical brief). Click here to access a PDF version.[[File:RELEASE ENVIRONMENT UPGRADE.pdf| upgrade instructions to access a PDF version.]]
+This is a short guide for technical teams preparing to install or upgrade to the '''Spring Framework 7'''– based Fusion Registry.
 '''Fusion Registry — Client installation readiness (Spring 7)'''

@@ Line 4: / Line 4: @@
 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, see '''<code>docs/client-facing/README.md</code>''' (Spring 7 client technical brief).
+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, see '''<code>docs/client-facing/README.md</code>''' (Spring 7 client technical brief). Click here to access a PDF version.[[File:RELEASE ENVIRONMENT UPGRADE.pdf| upgrade instructions to access a PDF version.]]
 '''Fusion Registry — Client installation readiness (Spring 7)'''

← Older revision		Revision as of 12:10, 29 July 2026
(12 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	=August 2026 R2.0.0.00=		=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, see '''<code>docs/client-facing/README.md</code>''' (Spring 7 client technical brief).
		+
		+	'''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]]

	==May 2026 P1.3.1.00==		==May 2026 P1.3.1.00==

← Older revision		Revision as of 09:47, 29 July 2026
Line 1:		Line 1:
		+	=August 2026 R2.0.0.00=
		+
		+
		+
	==May 2026 P1.3.1.00==		==May 2026 P1.3.1.00==