Settings in MoRE

Add a server

The Create new server instance option on the Add a server page has the Managed Liberty server type in the list of available middleware server types.

Application binary files

The default value for the Use configuration information in binary setting on the Application binary files console page is true (selected) for applications that are installed on a managed Liberty server target.

The default value is false (deselected) for applications that are installed on a WebSphere Application Server traditional target. For more information, see the Liberty servers and clusters known issues and limitations documentation.

All applications collection

On the All applications page, the Submit action button and the Actions field are not available for managed Liberty servers.

The Application details view does not correctly display information for Liberty applications in the All Applications page. For more information, see the Liberty administrative console known issues and limitations.

When the MoRE feature pack is installed and enabled on the deployment manager, an application becomes orphaned if the managed Liberty server it was deployed to is deleted. If managed Liberty servers are still available in the environment, you can reassign the orphaned application to a different managed Liberty server.

Application servers

Buttons on the Application servers page have several changes.

• The New menu has two choices, Application server and Managed Liberty server.
• Restart, ImmediateStop, and Terminate are unavailable for managed Liberty servers.

For managed Liberty servers, the Version value shows the WebSphere Liberty and MoRE versions.

Application server settings

The Type field on the application server settings page is new in MoRE. A managed Liberty server has the ManagedLibertyServer type. A WebSphere Application Server traditional server has the ApplicationServer type.

For managed Liberty servers, only the Type, Name, and Node name fields are in the server details. Also, fewer configuration links are available for managed Liberty servers than for WebSphere Application Server traditional servers.

CDI settings

On the Java virtual machine settings page for the managed Liberty server, you can specify the following options to control the behavior of the CDI:

• com.ibm.ws.cdi.enableImplicitBeanArchives

  When enabled, implicit bean archives are scanned for any bean discoveries. The default value is true.

• com.ibm.ws.cdi.emptyBeansXmlCDI3Compatibility

  In Jakarta EE 10 and later, an archive with an empty beans.xml file is considered an implicit bean archive (bean-discovery-mode=ANNOTATED). This property allows an empty beans.xml file to be treated as it was in Jakarta EE 9 and earlier (bean-discovery-mode=ALL). The default value is false.

• com.ibm.ws.cdi.enableCDI

  The property is ignored for managed Liberty servers because CDI is always enabled by default.

Change log detail levels

The Change log detail levels page has the following changes.

• The Runtime tab is not available.
• You can set the trace specification for a managed Liberty server.

To apply changes to these settings to managed Liberty servers, you must synchronize the node after you change the settings.

Class loading and update detection settings

On the Class loading and update detection settings page, the Class loader order setting is configurable for applications that are targeted to managed Liberty servers or clusters. For managed Liberty servers, the Class loader order setting is known as Class loader delegation.

Connection factory collection

On the Connection factory collection page, the Scope setting is available for managed Liberty servers. Unless otherwise specified, none of the other settings are available for managed Liberty servers.

Context root for web modules

The Map context roots for web modules page in the application installation wizard has changes for a managed Liberty server target.

In MoRE, if your application sets the web module context-root in the application.xml file, then the product uses that value for the module context-root. If the web module context-root is not set in the application.xml file, but the default-context-root is set in the web archive's web.xml file, then the context-root for the web module is set to the default-context-root. A context-root set in the application.xml file takes precedence over a default-context-root set in the web.xml file. You can change the context root on this wizard page.

After deployment, the settings are on the Context root for web modules page, but you cannot change the context root after deployment.

Creating a cluster: Basic cluster settings

The Prefer local and Configure HTTP session memory-to-memory replication fields on the Creating a cluster: Basic cluster settings page do not apply to managed Liberty servers.

Creating a cluster: Create first cluster member

On the Creating a cluster: Create first cluster member page, you can select the default managed Liberty server template or an existing managed Liberty server as a template for the first cluster member.

Diagnostic trace service

The Diagnostic trace service page has the following changes.

• The Runtime tab is not available.

• The following information applies to Trace Output settings.

  • Only the File option is available.

  • You can update the Maximum File Size, Maximum Number of Historical Files, File name, and Trace Output Format settings.

  • When you set the Maximum File Size or Maximum Number of Historical Files, the settings apply for all Liberty logs, which include the message.log, trace.log, and FFDCs.

  • For the File name setting, the default value is ${SERVER_LOG_ROOT}/trace.log. The binary scanner uses only the file name (for example, trace.log) to update the traceFileName logging attribute in the server.xml file. When you update this value, even if the absolute file path is shown, only the file name is parsed and applied to the managed Liberty server. The directory path is ignored.

  • For the Trace Output Format setting, only Basic and Advanced trace formats are shown. When Basic is set, the managed Liberty server trace format is set to Enhanced, which is the default. When Advanced is set, the managed Liberty server trace format is set to Advanced.

To apply changes to these settings to managed Liberty servers, you must synchronize the node after you change the settings.

Web container custom properties

On the Web container custom properties page, only some properties are applicable to managed Liberty servers. Also, certain properties are available exclusively for managed Liberty servers and do not apply to the traditional WebSphere Application Server.

JavaServer Pages specific web container custom properties

On the JavaServer Pages specific web container custom properties page, only certain Web container custom properties are applicable for managed Liberty servers. Also, certain Web container custom properties are available exclusively for managed Liberty servers and do not apply to the traditional WebSphere Application Server.

For a complete list of JavaServer Pages Web container custom properties available for managed Liberty servers, see JSP Engine (jspEngine) in the Liberty documentation. Each jspEngine configuration attribute can be specified as a Web Container custom property, as follows:

• If a jspEngine configuration attribute corresponds to a WebSphere traditional custom property, the traditional property name should be used when configuring a managed Liberty server. For example, the jspEngine attribute recomplieJspOnRestart is configured by using the com.ibm.wsspi.jsp.recompilejsponrestart Web container custom property name.

• If a jspEngine configuration attribute does not identify an equivalent WebSphere traditional custom property name, then the name of the attribute should be used as the custom property name. For example, the jspEngine attribute prepareJSPs is configured with the prepareJSPs Web container custom property name.

Important: Different properties are used for setting the Java source level for WebSphere traditional and Liberty servers. WebSphere traditional uses com.ibm.wsspi.jsp.jdkSourceLevel, whereas javaSourceLevel must be used for Liberty servers. The values for each of these properties are different as well. For example, the value 17 for WebSphere traditional means Java 7, whereas the value 17 for Liberty means Java 17.

Enterprise applications

After application deployment on a managed Liberty server, the Enterprise applications page shows the deployed application in the list of installed applications. The status of the application is unknown, even when the application is running.

The application starts when it's deployed. If the application is not running, start or restart the managed Liberty server. Applications start when the managed Liberty server starts and remain running until the managed Liberty server stops. For more information, see the Liberty servers and clusters known issues and limitations.

The Start and Stop buttons might not work for applications that are installed on a managed Liberty server. If you try to start or stop the application on the console page, you might get an error message regardless of the application's actual status.

The Start, Stop, and Analyze buttons are disabled when a managed Liberty server is selected.

Applications deployed to a managed Liberty server remain in the list of applications even after the managed Liberty server is deleted. You can deploy the orphaned applications to another managed Liberty server. Also, if MoRE is uninstalled from the deployment manager, applications deployed to a managed Liberty server remain in the list of applications but only the Uninstall button is available to those applications.

Install new middleware application

On the Install new middleware application page, the Java 2 Platform, Enterprise Edition application type changed to Enterprise Java Application in the Select application type list.

Java SDK collection

Beginning with V9.0.5.25, the Java SDK collection is available for managed Liberty servers.

For nodes with MoRE installed this administrative console page contains only the available SDKs for managed Liberty servers.

Traditional 9.0.5 application servers continue to use Java SE 8.

Logging and tracing

From the Logging and tracing page, only the Diagnostic Trace and Change log detail level settings are available for a managed Liberty server target.

For information about changes to these pages, see the Diagnostic trace service and Change log detail levels sections.

To apply changes to settings to managed Liberty servers, you must synchronize the node after changing the settings.

Log and trace configuration

The Log and trace configuration page is available for Modernized Runtime Extension for Java only and is supported for managed Liberty servers only.

For more information about the Log and trace configuration page, see Log and trace configuration service settings.

Map modules to servers

The Map modules to servers page in the application installation wizard has changes for a managed Liberty server target.

• For Clusters and servers, select one managed Liberty server and, optionally, a web server. Supported modules include EAR and WAR files that run on Java SE 17 and Jakarta EE Core profile 10.

  EAR and WAR files can also run on Java SE 21.

• The Display clusters and servers in the following domain setting is not available for application installation on a managed Liberty server.

After deployment, the settings are on the Manage modules page.

Tip: A limitation deletes a mapping to a web server after you sync changes. For more information, see the WebServer plug-in section in Known issues and limitations. To map a managed Liberty server and a web server together, use a Manage modules page after you install the application and sync changes.

Map shared libraries

The Map shared libraries page in the application installation wizard and the Shared library reference and mapping settings page do not present application modules for selection. Shared libraries map to the application only.

Metadata for modules

The Metadata for modules page is not available for application installation on managed Liberty servers.

The metadata-complete attribute does not apply for applications that are targeted to a managed Liberty server and you cannot set the metadata-complete attribute.

Middleware servers

The Middleware servers page shows information about managed Liberty servers. The Version value shows the WebSphere Liberty and MoRE versions and the Type value is Managed Liberty server.

Some middleware server buttons do not support managed Liberty servers. For more information, see the Liberty servers and clusters limitations.

After MoRE is installed on a deployment manager, managed Liberty servers can be created. If MoRE is then uninstalled on the deployment manager, you can still view these orphaned managed Liberty servers on the All Servers page. However, the Details link for any orphaned managed Liberty servers is unavailable. When you select any managed Liberty server, only the New and Delete buttons are available.

When MoRE is enabled on the deployment manager, managed Liberty servers can also become orphaned when MoRE is uninstalled from the node to which the managed Liberty server is deployed. These orphaned managed Liberty servers are listed on the All servers page. However, the Details link for these orphaned servers is unavailable. When an orphaned managed Liberty server is selected, only the New and Delete buttons are available.

Middleware node

The Middleware node collection page shows information about all the nodes in a configuration. These nodes can include nodes that have a version of the product installed, or nodes that are running other types of servers. For nodes where IBM Modernized Runtime Extension for Java (MoRE) is installed, the version column displays both WebSphere Application Server Network Deployment version and the IBM Modernized Runtime Extension for Java version.

Node

The Node collection page is used to manage nodes in the WebSphere Application Server (base) environment. For nodes where IBM Modernized Runtime Extension for Java (MoRE) is installed, the version column displays both WebSphere Application Server Network Deployment version and the IBM Modernized Runtime Extension for Java version.

Preparing for application installation

The Preparing for application installation page in the application installation wizard has changes that enable you to select a Jakarta EE 10 module and a managed Liberty server target.

For the Path to the new application setting, the application to install must be an EAR or WAR file that can run on a managed Liberty server. Supported modules include EAR and WAR files that run on Java SE 17 and Jakarta EE Core profile 10.

EAR and WAR files can also run on Java SE 21.

Queue collection

On the Queue collection page, the Scope setting is available for managed Liberty servers. Unless otherwise specified, none of the other settings are available for managed Liberty servers.

Select installation options

The Select installation options page in the application installation wizard has several changes for a managed Liberty server target.

The Use binary configuration setting is selected when Target runtime is WebSphere Liberty in the application installation wizard, and you cannot edit it. The setting is deselected by default, and editable, when Target runtime is WebSphere Application Server traditional.

During application edit or update, the Distribute application and Use binary configuration settings are not shown. The settings are selected by default. If you deselect either of these settings for application installation on a managed Liberty server or cluster target runtime, the deployment fails.

The following settings are not on the Select installation options page when Target runtime is WebSphere Liberty in the application installation wizard.

• Asynchronous request dispatch type
• Precompile JavaServer Pages files
• Directory to install application
• Deploy enterprise beans
• Create MBeans for resources
• Override class reloading settings for web and EJB modules
• Reload interval in seconds
• Deploy web services
• Process embedded configuration
• File permission
• Business level application name
• Deploy client modules
• Client deployment mode
• Application edition
• Edition description
• Allow dispatching includes to remote resources
• Allow servicing includes from remote resources

In versions earlier than 9.0.5.25, the following options are unavailable:

• Allow EJB reference targets to resolve automatically (this setting is available but non-functional)

The settings are available when Target runtime is WebSphere Application Server traditional. For more information, see Deploying applications to managed Liberty targets.

Server cluster collection

ImmediateStop on the Server cluster collection page is unavailable for managed Liberty servers.

Server cluster setting

The Prefer local and Enable failover of transaction log recovery fields on the Server cluster setting page do not apply to managed Liberty servers.

Shared libraries settings

On the Shared libraries settings page, an isolated shared library is known as a common shared library, and a shared library that is not isolated is known as a private shared library for managed Liberty servers. Associating an isolated shared library to an application creates a common library reference in the application's class loader configuration in the managed Liberty server. Associating a non-isolated library to an application creates a private library reference in the application's class loader configuration.

Topic collection

On the Topic collection page, the Scope setting is available for managed Liberty servers. Unless otherwise specified, none of the other settings are available for managed Liberty servers.

Transaction service settings

On the Transaction service settings page, only certain transaction service settings are available for managed Liberty servers. Furthermore, some settings for these servers are not available for traditional application servers.

The following settings for managed Liberty servers are not available for traditional application servers:

• Heuristic retry interval
• Recover on startup
• Wait for recovery
• One PC Optimization
• Propagate XAResource transaction timeout
• Default maximum shutdown delay
• Transaction log size
• Data source JNDI name
• Transaction log database name
• Transaction log database suffix
• Enable log retries
• Log retry interval
• Log retry limit
• Shut down on log failure
• Recovery group
• Recovery identity
• Backend URL
• Lease length
• Lease check interval
• Lease expiry threshold
• Lease renewal threshold
• Enable timeout grace period
• Throw checked exceptions

TCP transport channel settings

The settings on the TCP transport channel settings page are available for managed Liberty servers except for the Thread pool setting.

The maximum open connections is preconfigured to a value of 128000 for any managed Liberty servers that are created by using the managed Liberty server template.

For managed Liberty servers, only the TCP inbound channel settings for the WC_defaulthost_secure channel are used. For more information, see the Liberty configuration and migration known issues and limitations.