What's new in IBM Modernized Runtime Extension for Java
Learn about new features, improvements, limitations, and other changes in IBM® Modernized Runtime Extension for Java™ (MoRE). New capabilities for MoRE are delivered through IBM WebSphere® Application Server Network Deployment 9.0.5 fix packs.
1.0.3.0
All the capabilities that are available in 1.0.0.0, 1.0.1.0, and 1.0.2.0 are available in 1.0.3.0.
You can add Liberty installations that the node does not automatically pick up. For more information, see Adding a Liberty installation for a node by using the console and Adding a Liberty installation for a node by using scripting.
MoRE on distributed operating systems can now use the Process execution page to set process execution settings. For more information, see Process execution.
You can use managed Liberty servers in a dynamic cluster. Select the Managed Liberty server dynamic cluster server type. For more information, see Configuring dynamic clusters for managed Liberty servers.
You can install Jakarta Enterprise Beans (EJB) 4.0 applications on a managed Liberty server if they use Lite, 2.x, or Remote API groups. For more information, see Deploying EJB applications to managed Liberty targets.
You can configure the Object Request Broker (ORB) to manage Internet Inter-ORB Protocol (IIOP) communication for Jakarta Enterprise Beans (EJB) 4.0 applications that use remote interfaces. For more information, see Object Request Broker (ORB) settings and custom properties.
You can install, update, and delete Jakarta EE10 resource adapters for managed Liberty servers. You can also create, configure, delete, and manage the state of Jakarta EE10 connection factories for managed Liberty servers. You can do these tasks with existing AdminTask commands.
1.0.2.0
All the capabilities that are available in 1.0.0.0 and 1.0.1.0 are available in 1.0.2.0.
The minimum Liberty version is 25.0.0.12.
The minimum WebSphere Application Server Network Deployment fix pack that is supported for 1.0.2.0 is 9.0.5.27.
AES-256 password encryption is supported for managed Liberty servers.
You can customize the application installation path. For more information, see Preparing for application installation and Select installation options.
For nodes that run managed Liberty servers and have multiple Liberty installations, you can select the Liberty installation to use for a node on the Liberty installations console page.
For application deployment, the values for target runtime change in 9.0.5.27 for MoRE 1.0.2.0 or later installations.
- To deploy an application to a WebSphere Application Server traditional
application server or cluster, choose
Java EE 7. By choosingJava EE 7, you can install an application or module that runs on Java SE 8, including Java EE 7 applications or older technologies. Before 9.0.5.27, the value isWebSphere Application Server traditional. - To deploy an application to a managed Liberty
server or cluster, choose
Jakarta EE 10. Before 9.0.5.27, the value isWebSphere Liberty.
- To deploy an application to a WebSphere Application Server traditional
application server or cluster, choose
1.0.1.0
All the capabilities that are available in 1.0.0.0 and 1.0.0.1 are available in 1.0.1.0.
The minimum Liberty version is 25.0.0.6.
The minimum WebSphere Application Server Network Deployment fix pack that is supported for 1.0.1.0 is 9.0.5.26.
Nodes that run managed Liberty servers can now have multiple Liberty installations. Nodes initially use the highest installed version of Liberty. You can change the configured Liberty version by using the setConfiguredManagedLibertyInstallation admin task command. All managed Liberty servers in a node use the configured Liberty installation of a node.
You can enable WebSphere eXtreme Scale support for managed Liberty servers in IBM Modernized Runtime Extension for Java (MoRE). For more information, see WebSphere eXtreme Scale support for managed Liberty servers
You can migrate relatively simple OIDC Relying party TAI configurations to managed Liberty servers. You can alternatively configure an OpenID Connect (OIDC) Relying Party (RP or client) to manage Liberty servers in your cell. For more information, see Migrating or configuring an OpenID Connect Relying Party.
Applications can access message queues that are hosted on IBM MQ. For more information, see Queue collection and AdminTask.installJakartaMQResourceAdapter.
1.0.0.1
MoRE is available
on the AIX operating system beginning with WebSphere Application Server Network Deployment
9.0.5.24.
All the capabilities that are available in 1.0.0.0 are available in 1.0.0.1.
Only the WebSphere Application Server Network Deployment 9.0.5.24, and 9.0.5.25 fix packs are supported in 1.0.0.1.
1.0.0.0
You get MoRE capabilities based on the WebSphere Application Server Network Deployment fix pack that you install.
Only the WebSphere Application Server Network Deployment 9.0.5.23, 9.0.5.24, and 9.0.5.25 fix packs are supported in 1.0.0.0.
Beginning with WebSphere Application Server Network Deployment
9.0.5.25, managed Liberty servers, which are
stand-alone or in a static cluster, can run on Java SE 21 in addition to Java SE 17.
You can create and administer static clusters for managed Liberty servers in MoRE beginning with WebSphere Application Server Network Deployment 9.0.5.24.
MoRE enables WebSphere Application Server Network Deployment 9.0.5.23 and later users to run and manage WebSphere Application Server Liberty workloads that begin with Liberty 25.0.0.3. MoRE provides a managed application server type that is
called a managed Liberty server. This server can
be used to deploy Java workloads that run on Java SE 17 and Jakarta EE Core Profile 10. WebSphere Application Server Network Deployment 9.0.5 administrators and DevOps engineers can use
WebSphere Application Server Network Deployment 9.0.5 administrative interfaces to administer
a managed Liberty server.