Modernized Runtime Extension for Java overview
Modernized Runtime Extension for Java (MoRE) enables WebSphere® Application Server Network Deployment 9.0.5.23 and later users to run and manage WebSphere Application Server Liberty workloads with the administrative console, wsadmin scripting, and JMX clients. The Liberty workload uses a managed application server type that is called a managed Liberty server.
Network Deployment 9.0.5.23 and later supports Java™ workloads, including Java EE 7 applications. MoRE is supported on Network Deployment 9.0.5.23 and later. MoRE supports Liberty applications that run on Java SE 17 and use a subset of Jakarta EE 10 technologies.
Beginning in Network Deployment
9.0.5.25, MoRE also supports Liberty applications that run on Java SE 21.
MoRE supports deploying these Liberty applications by using the administrative console and wsadmin scripting that Network Deployment 9.0.5 provides.
Network Deployment 9.0.5 administrators and DevOps engineers can continue to use Network Deployment 9.0.5 administrative interfaces. Existing administrative console pages and wsadmin scripts for managing Network Deployment 9.0.5 servers continue to work. Administrators can integrate administrative commands specific to MoRE into new or existing wsadmin scripts. Administrators can also use existing administrative console pages with settings specific to MoRE. For more information, see Reference.
Managed Liberty servers
MoRE provides a managed application server type that is called a managed Liberty server. You can create this server with the administrative console and wsadmin scripting just like you create and federate application servers in a Network Deployment 9.0.5 cell.
Applications that are deployed to a managed Liberty server can use a subset of the technology that Liberty supports, such as Java SE 17 and Jakarta EE 10 specifications.
Managed Liberty servers
also support Java SE 21.
For more information, see Creating managed Liberty servers.
Supported Java SE levels
- Java SE 8 for Network Deployment 9.0.5.
- Java SE 17 for the managed Liberty server.
- The managed Liberty server end of support date
for Java SE 17 is October 2027.
A removal notice signifies that the item can be removed, typically no sooner than two years from the time the notice was issued.
- The managed Liberty server end of support date
for Java SE 17 is October 2027.
Java SE 21 for the managed Liberty server.
A node can use multiple Java SE versions and is not limited to having only one Java installation. For example, one managed Liberty server on a node can use Java SE 17 while another managed Liberty server can use Java SE 21.
- The user-configured Java SDK for a specific server, which the user specifies in the administrative console or through the setServerSDK admin task
- The user-configured default Java SDK for a node, which the user specifies in the administrative console or through the setNodeDefaultSDK admin task
- An automatic default Java SDK for a node, which is chosen as the highest available version when the first managed Liberty server on the node is created
Relationship between Network Deployment 9.0.5 servers and managed Liberty servers
Network Deployment 9.0.5 applications can run alongside Liberty applications in the same Network Deployment cell. The Network Deployment 9.0.5 applications run on WebSphere Application Server traditional servers while the Liberty applications run on managed Liberty servers.
- The Network Deployment cell contains the following components.
- A deployment manager.
- A managed Liberty server.
- Two WebSphere Application Server traditional 9.0.5 servers in a cluster.
Two managed Liberty servers in a static cluster.
The managed Liberty servers can be at different versions, such as one at version 25.0.0.8 and another at version 25.0.0.9.
- The deployment manager interacts with the following node agents:
- The node agents in the cluster for WebSphere Application Server traditional servers
- The node agent for the stand-alone managed Liberty server
The node agents for the managed Liberty servers that are in a static cluster
- The application servers and node agents each require a Java virtual machine (JVM) to run.
- The application servers run on the following Java SE versions.
- The WebSphere Application Server traditional 9.0.5 servers in the cluster run on Java SE 8.
The managed Liberty servers, which are stand-alone or in a static cluster, run on the following Java SE versions.
- Java SE 17
Java SE 21
- An HTTP server communicates with the Network Deployment 9.0.5 servers and the managed Liberty servers.
- You manage the cell through the administrative console, wsadmin scripting, or JMX clients.
Supported Jakarta EE 10 specifications
MoRE supports the following Jakarta EE 10 specifications that WebSphere Liberty supports, but support for a specific specification might be incompletely implemented. For more information, see the topic on known issues and limitations.
- Jakarta Annotations 2.1
- Jakarta Contexts and Dependency Injection 4.0
- Jakarta Dependency Injection 2.0
- Jakarta Expression Language 5.0
- Jakarta Interceptors 2.1
- Jakarta JSON Binding 3.0
- Jakarta JSON Processing 2.1
- Jakarta RESTful Web Services 3.1
- Jakarta Security 3.0
- Jakarta Servlet 6.0
- Jakarta Transactions 2.0
- Jakarta Bean Validation 3.0
- Jakarta Connectors 2.1
- Jakarta Faces 4.0
- Jakarta Mail 2.1
- Jakarta Managed Beans 2.0
- Jakarta Server Pages 3.1
- Jakarta Persistence 3.1
- Jakarta WebSocket 2.1
- Jakarta XML Binding 4.0
Supported Liberty features
MoRE supports the following WebSphere Liberty features, but support for a specific feature might be incompletely implemented. For more information, see the topic on known issues and limitations.
- servlet-6.0
- cdi-4.0
- jsonb-3.0
- jsonp-2.1
- restfulWS-3.1
- restfulWSClient-3.1
- appSecurity-5.0
- expressionLanguage-5.0
- distributedMap-1.0
- jndi-1.0
- jdbc-4.3
- transactions-2.0
- ssl-1.0
- transportSecurity-1.0
- ldapRegistry-3.0
- federatedRegistry-1.0
- beanValidation-3.0
- connectors-2.1
- faces-4.0
- mail-2.1
- managedBeans-2.0
- messagingClient-3.0
- pages-3.1
- persistence-3.1
- websocket-2.1
- wmqMessagingClient-3.0
- xmlBinding-4.0
- elasticCacheClient-1.0
- wmqMessagingClient-3.0
- openidConnectClient-1.0
Supported operating systems
- Windows
- Linux®
AIX®
Display of both MoRE and 9.0.5 icons in the documentation, when and where
To use a particular version of MoRE, you must install it with some specified minimum of a WebSphere Application Server Network Deployment 9.0.5 fix pack.
- This MoRE collection.
- The WebSphere Application Server Network Deployment 9.0.5 collection.
Updates to the WebSphere Application Server Network Deployment 9.0.5 collection for MoRE typically are on help pages.
- The MoRE collection doesn't have any icons in it
for the 1.0.0.0 release except for the What's new topic, which
has the
icon.
- The MoRE 1.0.0.0 documentation in the WebSphere Application Server Network Deployment 9.0.5 collection has both the
icon and the
icon on it.
Other capabilities for MoRE
are included in fix packs beyond WebSphere Application Server Network Deployment 9.0.5.23.
Multiple WebSphere Application Server Network Deployment 9.0.5 fix packs can apply to a
particular version of MoRE.