Stabilized Liberty features and feature capabilities

If a feature or feature capability is stabilized, IBM® does not currently plan any further enhancements to the feature or feature capability, and future investment will be focused on the strategic alternative.

You do not need to change any of your existing applications and scripts that use a stabilized feature or feature capability. If a strategic alternative is available, consider using it for new applications.

Table 1. Stabilized features and feature capabilities
Fix pack when stabilized Category Stabilized function Strategic alternative
23.0.0.3 MicroProfile Tracing MicroProfile OpenTracing features:
  • mpOpenTracing-1.0
  • mpOpenTracing-1.1
  • mpOpenTracing-1.2
  • mpOpenTracing-1.3
  • mpOpenTracing-2.0
  • mpOpenTracing-3.0
OpenTracing features:
  • opentracing-1.0
  • opentracing-1.1
  • opentracing-1.2
  • opentracing-1.3
  • opentracing-2.0
 Use a MicroProfile Telemetry feature such as mpTelemetry-1.0. For more information, see the MicroProfile OpenTracing to MicroProfile Telemetry 1.0 migration document.
21.0.0.12 REST APIs OpenAPI V3 features:
  • openapi-3.0
  • openapi-3.1
 Use a MicroProfile OpenAPI feature such as mpOpenAPI-3.0. For more information, see Generating REST API documentation with MicroProfile OpenAPI.
21.0.0.8 Security openid-2.0 Use the openidConnectClient-1.0 feature. For more information, see Configuring an OpenID Connect Client in Liberty.
20.0.0.9 Cloud integration usageMetering-1.0 The usage metering feature is stabilized. It currently is used with WebSphere® Automation. For application development or general health status needs, consider using the MicroProfile metrics feature. For additional information about available metrics, see Monitoring with MicroProfile metrics.
19.0.0.6 Java EE Java Platform, Enterprise Edition (Java EE) 6 features that are not in Java EE 7 or later:
  • beanValidation-1.0
  • cdi-1.0
  • ejbLite-3.1
  • jaxrs-1.1
  • jca-1.6
  • jms-1.1
  • jpa-2.0
  • jsf-2.0
  • jsp-2.2
  • mdb-3.1
  • servlet-3.0
  • wasJmsClient-1.1
  • webProfile-6.0
  • wmqJmsClient-1.1
 Use Java EE 7 or 8 features. See the following information:
19.0.0.6 RTComm Real-Time Communications features:
  • mediaServerControl-1.0
  • rtcomm-1.0
  • rtcommGateway-1.0
 There is no strategic alternative.
19.0.0.6 REST APIs apiDiscovery-1.0 Use the openapi-3.0 feature, which supports the OpenAPI specification, or the mpOpenAPI-1.0 feature, which supports the MicroProfile OpenAPI specification, to generate your REST API documentation.
19.0.0.6 Monitoring timedOperations-1.0 Use the eventLogging-1.0 feature.
19.0.0.6 Security scim-1.0 There is no strategic alternative.
19.0.0.6 z/OS z/OS Connect features:
  • zosConnect-1.0
  • zosConnect-1.2
 Use the IBM z/OS Connect Enterprise Edition product.
19.0.0.4 Databases mongodb-2.0

This feature is stabilized because the MongoDB Java driver versions 2.10.0 to 2.14.2 that the feature supports are no longer in service.

 Create a CDI producer for Mongo. Use any Mongo version that meets your requirements.
18.0.0.2 Application programming model OSGi applications and the following features that support OSGi development:
  • blueprint-1.0
  • httpWhiteboard-1.0
  • osgiAppIntegration-1.0
  • osgiBundle-1.0
  • osgi.jpa-1.0
  • wab-1.0
 Develop Java applications that use the Java Platform, Enterprise Edition (Java EE) or MicroProfile features. See Liberty features.
18.0.0.2 Job Manager serverStatus-1.0

This feature is stabilized as a result of the deprecation of the Job Manager and Centralized Installation Manager (CIM) in WebSphere Application Server traditional.

 Because the Job Manager is deprecated, no strategic alternative is needed.
18.0.0.2 Monitoring productInsights-1.0

This feature is stabilized as a result of the removal of the IBM Cloud® Product Insights service. Although the productInsights-1.0 feature continues to exist, it will no longer function after the service is removed.

 There is no strategic alternative.
18.0.0.2 Systems management The SMB component of the Tivoli® Remote Execution and Access (RXA) toolkit For Windows platformsThe Server Message Block (SMB) protocol allows for remote method execution on Windows and is used by collectives. Version 1 of the SMB protocol (SMBv1) is insecure and should be disabled. As an alternative, install Cygwin as a SSH service on collective members and use SSH to connect to them. RXA is not compatible with Windows OpenSSH. Disable Windows OpenSSH before installing and running Cygwin.
Management of Docker containers by using Liberty collectives For managing Docker containers, run your Liberty applications in IBM® Cloud Pak for Applications for on-premises or bring-your-own infrastructure. For hosted environments, use Docker containers in IBM Cloud Kubernetes Service.
Management of Node.js processes by using Liberty collectives (V8 is the final supported Node.js version for the Liberty collective members) For on-premises or bring-your-own infrastructure environments, use Docker containers that are hosted and managed by IBM Cloud Private. For hosted environments, use Docker containers in IBM Cloud Kubernetes Service.
16.0.0.2 Installation The featureManager find, install, and uninstall actions Use the installUtility command instead. With the installUtility command, you can manage more asset types and install, find, or download assets from multiple repositories. For more information, see Installing assets using the installUtility command.
8.5.5.9 Java™ Platform, Enterprise Edition resources DataDirect Connect for JDBC property properties.datadirect.sqlserver in server configuration elements No strategic alternative is necessary. Although the DataDirect JDBC drivers are no longer certified with WebSphere Application Server, their use continues to be fully supported as detailed in the Other Configurations section of the IBM Support Statement.