News in NetPhantom 7.0

In accordance with the long term commitment of Nexum International in providing a product attuned to today's computing environment, the new NetPhantom version 7 focuses on server-side functions and client enhancements that support the developing innovations in Java, with support for all Java Long Term Support releases (currently Java 8 and Java 11).

The advanced development environment in NetPhantom 7 is fully compatible with NetPhantom version 6.x. This means that you can use NetPhantom 7 for development and still have NetPhantom 6 on servers in production.

NetPhantom Editor 7 requires a 64-bit Windows operating system, version 7, 8, 8.1 or 10. It also supports Windows Server 2008 R2, 2012, 2016 and 2019. It comes with Java 14 by default in the NetPhantom Quick Start setup.

All other NetPhantom components requires Java 8 or better to run, the operating systems are not limited to Windows: you can use any operating system that supports the Java Runtime Environment SE 8 or better (such as Linux and macOS).

Below are news implemented in NetPhantom since version 6.90 Build 6900.

Also see news in the previous versions.

News in Version 7.0 RC3 Build 7105

  • NetPhantom support for Java 11 and 14
    The NetPhantom Client, Editor, Server, Cluster Controller and License Manager now supports running Java versions 11 or 14. The NetPhantom Client will handle screen DPI scaling on System Level, not on a Monitor/Display Level. NetPhantom Editor requires a 32-bit JDK (bundled with NetPhantom Quick Start).
  • Eclipse 4.16 (2020-06) 64-bit
    NetPhantom Quick Start is now bundled with Eclipse 4.16 (2020-06) 64-bit for Java Developers. This means that the address space is considerably larger and the memory can be increased well over 1 GB for very large applications or many projects are used at the same time.
  • NetPhantom is now bundled with OpenJDK
    The installation of NetPhantom Quick Start is bundled with the following OpenJDK versions and architectures:
    • Java Development Kit version 14, update 1, 32-bit
    • Java Runtime Environment version 14 update 1, 64-bit
    • Java Runtime Environment version 11 update 7, 64-bit
    • Java Runtime Environment version 8 update 252, 64-bit
    The 64-bit architecture is used for Eclipse, whereas 32-bit is only used by NetPhantom Editor.
  • NetPhantom Editor high resolution screen support
    Support for HiRes DPI screens is now available in the Editor. By default the edited panels are using scaling of 100%, but this can easily be changed in the Editor to the request scaling level. The NetPhantom Editor will handle screen DPI scaling on System Level, not on a Monitor/Display Level.
  • NetPhantom Client using Java 8 and high resolution screen support
    Support for HiRes DPI screens is now available in the Client, but it must be turned on specifically with Java 8. Follow this link for more information. The NetPhantom Client will handle screen DPI scaling on System Level, not on a Monitor/Display Level. NetPhantom Quick Start will automatically set DPI-awareness to the included 64-bit JRE and 32-bit JDK of Java version 8 during its installation.
  • NetPhantom Client reconnection support
    This setting enables a Client to lose connection due to a network problem or typically a laptop computer that is disconnected from its docking station that has an Ethernet connection. When undocking this laptop, it often switches over to a WiFi connection, and this can take some time, perhaps 20 seconds or longer. During this switch period, the NetPhantom Client will normally lose the network connection to NetPhantom Server. The reconnect timeout is set in server.ini using the reconnectTimeout setting in the [Base] section. This value is specified in seconds.
  • New settings for the NetPhantom Server Administration
    The settings for pingClientTimeout (default to 2 minutes) and reconnectTimeout (default to 20 seconds) are now configurable through the Server Administation program, using the menu item Server - Configure - Base. On the first page, these settings are available to be changed. The setting pingClientTimeout requires a server restart, and the setting reconnectTimeout only requires the client to shut down normally and then restart. If you have an earlier version of NetPhantom, these values might be zero (thus disabling the functionality). If the is the case, enter new values to your liking.
  • News in short
    More news in short for NetPhantom 7:
    • Faster listbox implementation.
    • Support for server-side ordering of SSL cipher suites.
    • Enhanced SSL cipher suites dialog box.
    • Option to disallow TLSv1.0 and TLSv1.1 (default disallowed).
    • Option to disallow TLSv1.3 in case of problems (default allowed and enabled if JVM supports it).
    • Added new weak cipher suites, aligning with TLS 1.2 and 1.3.
    • ALPN support (http/1.1).
    • Updated NetRexx and its documentation to version 3.08 GA.
    • Updated BouncyCastle libraries to 1.65(.01).
    • Tweaker for Look-and-Feels (Windows looks great), corrected as much as possible for Metal and Nimbus.
    • Added JavaDoc references to Eclipse Platform's JavaDoc.
    • Updated installation of JRE's and configured Java SE-NN runtime environments.
    • Added "Metal" as Look-and-Feel as well as "Windows" on command line as LAF:Name parameter.
  • Virus Scanning Software such as Windows Defender slows down NetPhantom Editor and Eclipse
    When you have a virus scanning software such as Windows Defender, Avast, Norton, Kapersky, etc, you might experience a slow-down in the Editor or typically in the Eclipse part, but also affecting start-up of NetPhantom Client. To remedy this situation, you may add an Exclusion filter to where NetPhantom (Quick Start or Eclipe is located).
    To perform this operation, open your virus scanning software, locate the Folder or Directory Filtering of virus scanning (generally in some Advanced menu option). Enter the path to NetPhantom Quickstart, e.g. C:\NetPhantom 7 QS or if you have installed NetPhantom and Eclipse separately, add those two root directories. You may see a difference in start-up time of up to 20 seconds, and about 5 seconds when starting the NetPhantom Client.
    Please note that this problem is not related to NetPhantom or Eclipse in general, it has to do with most of the virus scanning software checking compressed Jar (and mostly signed) files installed for both NetPhantom and Eclipse as Java products.
  • Dropped support for Java versions 1.6 and 1.7
    NetPhantom no longer support Java versions 1.6 and 1.7. Applications compiled with Java 1.6 or 1.7 can still be used. We strongly recommend to upgrade to using Java 11.
  • Dropped support for Compile Distribution for NetPhantom 5
    NetPhantom 5 applications can no longer be created from NetPhantom 7.
  • Updated NetPhantom System Certificates
    The NetPhantom certificate has been updated (SHA-256 from Symantec/DigiCert) and is valid until February 2022. The Quick-Start SSL self signed certificate has also been updated.
  • Java unlimited cryptography automatically set
    The unlimited Java cryptography for Java version 1.8 update 151 and better (including Java 9 and better) is now automatically turned on by the NetPhantom Server, NetPhantom Editor and the NetPhantom Client (when running directly as a Java program or from NetPhantom Starter). NetPhantom Client running with Java Web Start must configure this on the client side by changing the Java cryptography policy settings, see Oracle's Java documentation on this issue for more information.
  • 5250 host session now defaults to sendFieldsForPageKeys
    The setting sendFieldsForPageKeys in the [host] section of server.ini now has the value 1 or true for 5250 sessions. If you wish to turn off this setting, set sendFieldsForPageKeys=0 in the [host] section.

Previous versions

The links below indicates news implemented in the respective version: