Differences between the old and new ER rich client

Beginning with version 9.3, ER rich client now has a new version available. This is due to the changes with Oracle Java licensing and web start technologies.

Note that while the er.jnlp launcher itself is the same between both the legacy and new rich clients, there are certain features that are dependent on IcedTea, such as using a single client to connect to multiple ER servers.

ER "new rich client" available starting with ER 9.3 (recommended)

The new rich client is available as part of the product installation files. 

The new ER client includes the Amazon Corretto and IcedTea installations. This is recommended for long term support and ease of use, as we ship the certified JDK with ER client, ensuring the team is utilizing a certified combination of these technologies.

For additional details on the new ER client installation, please refer to Steps for New Infogix ER Rich Client Package.

ER "legacy rich client" accessed via the web-UI

The ER rich client which is traditionally accessed via the web-UI requires Oracle JDK 8 and Java Web Start technologies. This is the same rich client that ER 9.2 and older uses. While it may be possible to replace Oracle and Java Web Start technologies with related technologies, some functionality may be lost.

Another Web-Start launcher in part of IcedTea may work, though would be uncertified / unsupported if issues arise. Please note, the Web-Start alternative must support standard JNLP protocol and descriptor. If utilizing an alternative ( i.e. ICE descriptor ), the rich client may lose functionality. 

A future upgrade to Java 11 would also impact the legacy rich client. More information can be found within ER Rich Client's Future Java 11 Compatibility.