Recent updates by Oracle have introduced two different versions of Java and there is also a major version upgrade to Java 8 in the queue. As SEEBURGER Business Integration Suite (BIS 6) and the SEEBURGER B2B Portal depend on the Java platform to run on different enterprise platforms, here is some information about what is happening in development at SEEBURGER.

The following Java runtimes are supported for SEEBURGER BIS:

Windows x64 – Oracle Server Runtime 7
Linux (SLES, RHEL, OEL) x64 – Oracle Server Runtime 7
Solaris x64, SPARC64 – Oracle Server Runtime 7
HPUX ia64 – HP Java JDK 7

OpenJDK is not supported on any of those platforms, in order to reduce the number of combinations to be tested and supported by SEEBURGER, which enables us to deliver patches to our customers faster. For Windows and Linux, we ship an unmodified Server Runtime with the installer. We follow the public Oracle updates and make them available as BIS patches and hotfixes, so this should be your preferred method for updates.

For Solaris, HPUX and IBM AIX the installer requires you to make a working and supported JDK available (in BIS_HOME/runtime/jvm64 for each instance). This is typically with Java 7 and above, as the current security baseline.

Best practice architecture for easy Java Updates
By using a copy (instead of pointing to a system-provided JRE), we can better manage the lifecycle of an installation. However, it is possible (and typically used on IBM AIX) to make this directory a symbolic link to the system-maintained JDK installation (BIS_HOME/runtime/jvm64 -> /usr/java71_64/). In this case, the operating team should be aware that updates to the Java file sets need to be tested and coordinated with the application team.

Release of Java Patch for BIS
Currently, we are preparing the BIS 6.5.2 Q4/P4 patch bundle. This will include Oracle Server Runtime 7U72 (PSU). Oracle has started to issue two different public updates: Critical Patch Updates (CPU), which are strictly security related and Patch Set Updates (PSU), which also contain non-critical fixes. The difference is further explained in this article by Oracle. We will ensure a version of Java runtime is available which fulfills the security baseline. In this case, we decided to use the PSU (as the additional non-critical bugfixes seem to be low-risk and we prefer the newer version). This will be re-evaluated for each following update.

Java 8 Roadmap
We have been planning on a Java 8 runtime version compatibility update for BIS since Oracle announced the end of public updates for Java 7 (in April 2015). We are on schedule as planned. Before Oracle stops providing critical updates for Java 7, we will have Java 8 with BIS patches available. This is the case for Windows, Linux and Solaris operating environments. Oracle has published a blog post on upgrading major versions, which we think is helpful in this process.

Both IBM and HP have not yet announced end-of-life for Java 7, and in fact there is no Java 8 generally available yet. So we will continue to support Java 7 from HP and IBM after Oracle has switched to Java 8. Our main focus for all products under active service is to maintain a compatible Java runtime for all officially supported platforms.

On the desktop (Java Webstart and Java Plugin), Java 8 is already supported with the BIS Front-End and the SEE FX applet.

As always, don’t hesitate to contact our support team for more information about how SEEBURGER will help you transition through the changes.