In Boomi’s continuous efforts to provide the highest quality of service to our customers, we would like to officially announce upcoming upgrades to support  Java 11 on our Boomi runtime clouds, installers, and upgraders.

For customers running executions against the Boomi runtime cloud, we are upgrading our Test runtime clouds starting May 5, 2021. You can reference the following table to view Boomi’s schedule for performing Java 11 upgrades on Test and Production Clouds, and plan accordingly.

   

Please ensure to schedule time for testing once your test cloud is upgraded according to the schedule above. Testing prior to the production upgrade is particularly important if you are using any custom scripting or private connectors, so that you can ensure that they will function properly on the new version of Java.



For customers running executions against private runtime clouds or local runtimes, the upgraders and installers for Java 11 will be available on April 30, 2021. We strongly recommend you apply Runtime Release to your local runtimes if you run the Java upgrader prior to the Boomi Enterprise Platform Release on May 15th. If necessary, please work with your account or runtime administrator to coordinate the rollout schedule for Java 11.

FAQ:

Items to verify when upgrading to Java 11
Considerations when upgrading from Java 7 to Java 8 or 11
When will the install and upgrade scripts be available for customers that are not running on the Boomi public runtime clouds?
Is it possible to rollback to Java 8 if necessary based on testing?
What JDK versions will we support?
If I am running a local basic runtime/runtime cluster or private runtime cloud, can I use a different distribution of Java than what Boomi offers?
What are the licensing implications associated with the use of Oracle JDK versus Open JDK?
Why are we supporting Java 11 and not Java 15?
What is the Corretto Distribution of Java?
What does it mean now that Boomi ships JDK instead of only the JRE?
Will Boomi support for Java 11 include 32-bit?
Will the Support of Java 11 include Support for TLS 1.3 ?
When will a new Docker image with Java 11 be made available?
Can I reset the default Garbage Collector to Java 8 settings?
Will my processes continue to run after the end of official support for Java 7?
 

Items to verify when upgrading to Java 11:

• If your organization is utilizing custom authentication type for web service authentication on an basic runtime or runtime cluster with LDAP server, the basic runtime operation may be affected after the basic runtime Java 11 upgrade due to jetty-plus-6.1.26.jar module incompatibility with Java 11. Please visit the following article for resolution steps: LDAP Authentication Issue with Java 11 
• If you are running a private runtime cloud environment and either your tenant or one of your sub-tenants is using a Kafka Connector in one of their processes, the following permission will need to be added to the "misc other permissions" section of your clouds high security policy files (procbrowser, procrunner, procworker):
  • permission java.lang.RuntimePermission "accessClassInPackage.com.sun.security.sasl.util";
• If you are managing a private runtime cloud environment that utilizes a custom procrunner, procworker and/or procbrowser script:
  • Prior to upgrading to Java 11, the cloud administrator should:
    • First remove references to 'Djava.endorsed.dirs=' from those files.
    • Second, add the following permissions to the customer policy files:
      • permission java.lang.RuntimePermission "accessClassInPackage.jdk.internal.reflect";
      • permission javax.xml.bind.JAXBPermission "setDatatypeConverter";
    •  After the 'Djava.endorsed.dirs=' have been removed and the policy files updated, we recommend stopping the cloud, applying the Java 11 update, then restart the cloud (instead of rolling restart). This will ensure that all nodes of the cloud are started with the most recent version of the procrunner/procworker/procbrowser scripts. If you do not stop the cloud, it is possible you will have to perform consecutive rolling restarts of the cloud to get the scripts to synch across all nodes.
• If you are managing a multi-node runtime cluster or multi-node Cloud installed on the windows operating system, you must ensure that all nodes of the runtime that you wish to upgrade are stopped prior to the upgrade:
  1. Download the upgrader available to you via the Runtime Management page as you normally would when upgrading to the latest version of Java.
  2. Ensure all nodes of the runtime you wish to upgrade are stopped.  Your Cloud/runtime cluster should appear as completely offline in the Runtime Management page.
  3. Run the upgrader script as you normally would to upgrade to the latest version of Java. 
     Note: If you manage your own JDK and update it without using Boomi’s upgrader, but still wish to upgrade to Java 11 from Java 8, you still must run the Boomi upgrader to apply the changes to the executable.  You only need to specify in the upgrade process that you are managing your own JDK, and provide the path to that JDK.
  4. Ensure your runtimes have properly restarted, and the correct version of Java is shown in the Runtime Management page.

Considerations when upgrading from Java 7 to Java 8 or 11:

• If you are currently using an ODBC connection to a database in Java 7, please be aware that the JDBC/ODBC bridge that was included in Java 7 was removed from Java 8 and subsequent versions. Oracle recommends using JDBC drivers provided by the vendor of your database. Alternatively, you can use a third-party JDBC/ODBC bridge and install it like any other custom JDBC driver. Make sure that the basic runtime is running as a service and has user rights to the ODBC connection. You can then define your Database connection in  Boomi Integration. Please visit the help documentation located here for further information.

When will the install and upgrade scripts be available for customers that are not running on the Boomi public runtime clouds?

Install and upgrade scripts will be available as of April 30, 2021. Testing prior to the production upgrade is particularly important If you are using any custom scripting or private connectors, so that you can ensure that they will function properly on the new version of Java.

 

Is it possible to rollback to Java 8 if necessary based on testing?

Please refer to the following article for instructions on rolling back to a version of Java: Roll Back Java Operation

 

What JDK versions will we support?

• Oracle JDK 8 - localise runtimes can continue to leverage Java 8, though we will not continue to release quarterly patches per Oracle’s quarterly release schedule for Java 8. We will only provide patches for OpenJDK 11 once it is available.
• Amazon Corretto OpenJDK 11

 

If I am running a local basic runtime/runtime cluster or private runtime cloud, can I use a different distribution of Java than what Boomi offers?

Boomi only officially supports the following Java versions and distributions:

• Amazon Corretto Open JDK 11.0.8
• Oracle Java 1.8.0_281 and previous versions of Oracle Java 8 

If you encounter an issue and are running on a different distribution or version, this issue would need to be recreated in the officially supported versions.
 

What are the licensing implications associated with the use of Oracle JDK versus Open JDK?

While our recommendation is to upgrade to Java 11, customer use of Oracle JDK 8 in support of the basic runtime will continue to be covered by Boomi distribution licensing until such time as an Open JDK 8 equivalent is made available.

 

Why are we supporting Java 11 and not Java 15?

Our current Java support protocol is to support only the two latest LTS (Long Term Support) versions of Java. This is currently 8 and 11. 
 

What is the Corretto Distribution of Java?

Amazon Corretto is a no-cost, multi-platform, production-ready distribution of the Open Java Development Kit (OpenJDK). Corretto comes with long-term support that includes performance enhancements and security fixes. Corretto is certified as compatible with the Java SE standard.

 

What does it mean now that Boomi ships JDK instead of only the JRE?

Java no longer contains a JRE starting with Java 11; this is not unique to Boomi. Utilizing a JDK for your runtime environment provides additional functionality/out of the box toolsets for troubleshooting purposes (examples include jstack for thread dump generation, jmap for heap dump generation, etc)
 

Will Boomi support for Java 11 include 32-bit?

Boomi will not be providing 32-bit install/upgrade support for Java 11.

Can I reset the default Garbage Collector to Java 8 settings?

Java changed it's default Garbage Collector from Parallel in Java 8 to G1 in Java 11. Parallel GC offers faster throughput at the expense of longer Garbage Collector pauses of the application. G1 focuses on a low latency/less pauses collection at the expense of some throughput. For most purposes, G1 will be a faster garbage collector, however depending on the type of processes you may be running, this may not always be the case. The garbage collector can be switched back to use Parallel GC by adding the following Custom System Property: -XX:+UseParallelGC

 

Will my processes continue to run after the end of official support for Java 7?

Boomi will end support for Java 7 with the September 2021 Platform release. At this time, all runtimes utilizing Java 7 will fail to communicate with the Boomi Enterprise Platform and will not function moving forward. We strongly encourage you to upgrade as soon as possible to prevent any disruption in the execution of your processes.

 

During this transition period, Boomi will continue to support Java 7 and Java 8 concurrently for your production processes. This will give you time to migrate to Java 11. In the meantime, if you have any questions, please contact the Customer Success team.

If you have further questions or concerns, please contact your Success Assurance Resource or customersuccess@boomi.com.