Liberty features

CICS supports features from WebSphere® Application Server Liberty, which enables Enterprise Java applications to be deployed into a Liberty JVM server.

The CICS Liberty features section lists the set of features that make up the CICS Liberty product extension. The CICS Liberty product extension extends Liberty with CICS capabilities and qualities of service. All features in Table 1 are supported by CICS Liberty in integrated-mode. The features in Table 1 are also supported in CICS Liberty standard-mode without any of the restrictions, unless noted otherwise.

Many features from Java EE 6 and Java EE 7, and Java EE 7 and Java EE 8 must not be used concurrently. For information about feature compatibility, see Supported Java EE 6 and 7 feature combinations and Supported Java EE 7 and 8 feature combinations. Additionally, Jakarta 9.1 and Jakarta 10 have different feature combinations between them and the previous Java EE levels. For more information, see the jakartaee-9.1 and jakartaee-10.0 full platform features. Migration between Java EE and Jakarta levels requires application upgrade considerations.

ƒ

For information about editing the server.xml, see Server configuration.

All features

A B C D E F H J L M O P R S T W X Z

Table 1. All supported CICS Liberty features
Liberty feature Liberty feature description Using this feature in CICS
A
adminCenter-1.0

Enables the Liberty Admin Center, a web-based graphical interface for deploying, monitoring and managing Liberty servers in standalone and collective environments.

For more information, see Setting up Admin Center.

 Configuring Admin Center
appAuthentication-2.0
appAuthentication-3.0
 Enables support for securing the server runtime environment and applications using Jakarta Authentication providers.  
appAuthorization-2.0
appAuthorization-2.1
 Enables support for the Jakarta Authorization SPI.  
appClientSupport-1.0
appClientSupport-2.0
 Enables the Liberty server to process client modules and support remote client containers.
Tip: The Application Client module runs in both the client and the server. The client executes the client specific logic of the application. The other portion of code runs in a client container on the server and communicates data from the business logic running on the server to the client. For more information, see Preparing and running an application client.
appSecurity-1.0
appSecurity-2.0
appSecurity-3.0
appSecurity-4.0
appSecurity-5.0
 Provides support for securing the server runtime environment and applications.appSecurity-2.0 supercedes appSecurity-1.0. Configuring security for CICS Liberty
B
batch-1.0
batch-2.0
batch-2.1

Enables support for the Java Batch API defined in JSR-352. This feature does not support Java™ batch applications that are packaged in an Enterprise Bundle Archive (EBA).

For more information, see Deploying Java batch applications in Liberty.

  
batchManagement-1.0 Provides managed batch support for the Java batch container. This includes the Batch REST management interface, job logging support, and a command line utility for external scheduler integration.  
batchSMFLogging-1.0 Collects information about Java batch jobs and records the information to the z/OS SMF data store. For information on how to enable Java batch logging, see Enabling Java batch SMF logging for Liberty on z/OS. For information on how to view SMF data, see Viewing the output data set.
beanValidation-1.0
beanValidation-1.1
beanValidation-2.0
beanValidation-3.0
 Provides an annotation-based model for validating JavaBeans.  
blueprint-1.0 Enables support for deploying OSGi applications that use the OSGi blueprint container specification.
Important: The transaction attribute NotSupported is respected by the JTA Liberty transaction system but not the CICS unit of work.
C
cdi-1.0
cdi-1.2
cdi-2.0
cdi-3.0
cdi-4.0

Provides a common mechanism to inject components such as enterprise beans or managed beans into other components such as JSPs or other enterprise beans.

For more information, see Administering Contexts and Dependency Injection applications on Liberty.

  
cicsts:core-1.0 Provides core CICS features, and Java Transaction API (JTA) 1.0. This feature is required when using Integrated-mode CICS Liberty.
Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:defaultApp-1.0 Verifies that the Liberty server is running and provides information on the server configuration. Browse the JVM Profile, the JVM server logs, the Liberty server.xml, and the messages log by using the FileViewer servlet. Configuring the CICS Default Web Application
cicsts:distributedIdentity-1.0 Provides support for distributed identity mapping. Configuring Liberty to use an LDAP user registry
cicsts:jcaLocalEci-1.0 Provides a locally optimized JCA ECI resource adapter for calling CICS programs. Using the JCA local ECI resource adapter
Stabilized feature:

Consider updating applications to use JCICS Link as an alternative. See also Stabilization notices and discontinued functions.

6.3 The JCA ECI adapter in Liberty JVM server is removed as of CICS TS 6.3.

6.16.2The JCA ECI adapter in Liberty JVM server is stabilized.

Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:jcicsxServer-1.0 When enabled in a Liberty JVM server in CICS, the server can receive remote requests from Java applications using JCICSX API classes. Configuring the environment for JCICSX
cicsts:jdbc-1.0 Provides support for applications to access a local CICS Db2® database that uses JDBC. This feature has been superseded by jdbc-4.0 and jdbc-4.1, except when used directly with DriverManager. Acquiring a connection to a database
Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:link-1.0 Provides support to start a Java EE application that is running in a Liberty JVM server either as the initial program of a CICS transaction or by using the LINK, START, or START CHANNEL commands from any CICS program. Linking to Java applications in a Liberty JVM server by using the @CICSProgram annotation
cicsts:security-1.0 Provides integration of Liberty security with CICS security, including propagation of thread identity. Configuring security for CICS Liberty
Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:standard-1.0 Enables users to port and deploy Liberty applications from other platforms to CICS without changing your application. Standard mode is ideal for hosting applications that are written for and rely on the Java EE Full Platform, but do not require full integration with CICS. CICS standard-mode Liberty: Java EE 7 Full Platform support without full CICS integration
Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:zosConnect-1.0
cicsts:zosConnect-2.0
 Integrates z/OS Connect with CICS Liberty JVM server.
Stabilized feature:

These Liberty features are stabilized. You can continue to use these features. However, consider using the IBM® z/OS® Connect Enterprise Edition product. See also Stabilization notices.

6.3 Liberty feature cicsts:zosConnect-1.0 is deprecated as of CICS TS 6.3. Liberty feature cicsts:zosConnect-2.0 is removed as of CICS TS 6.3.

6.2 Liberty features cicsts:zosConnect-1.0 and cicsts:zosConnect-2.0 are stabilized.

Restriction: The JVM server should be disabled before adding or removing this feature.
clusterMember-1.0 Allows a collective member to participate in a static cluster. Configuring a Liberty JVM server to use collectives
collectiveController-1.0 Allows a server to become the controller for a management collective. The collective controller acts as a command and control mechanism for administrative functions for the collective, and serves as a storage and collaboration mechanism for the collective and cluster members. Configuring a Liberty JVM server to use collectives
Restriction: Restrictions of Liberty JVM servers in collectives
collectiveMember-1.0 Enables a server to be a member of a management collective. Configuring a Liberty JVM server to use collectives
Restriction: Restrictions of Liberty JVM servers in collectives
concurrent-1.0
concurrent-2.0
concurrent-3.0
 Enables the creation of managed executors that allow applications to submit tasks to run concurrently, with thread context that is managed by the application server. It also enables the creation of managed thread factories to create threads that run with the threadcontext of the component that looks up the managed thread factory.
Restriction: The transaction property ManagedTask.SUSPEND is not supported by a Liberty JVM server.
Restriction: The user ID that is attached to the transaction of a new thread is always the user ID that is attached to the parent transaction.
Restriction: Use of a ManagedThreadFactory creates standard Java threads, not CICS-enabled Java threads.
Restriction: Use of the untimed invokeAll() and invokeAny() methods is not supported as these can cause a submitted task to run on the submitter's thread.
Restriction: Use of execute() and submit() when the executor's concurrencyPolicy specifies runIfQueueFull="true" is not supported as this can cause a submitted task to run on the submitter's thread.
connectors-2.0
connectors-2.1
 Enables the configuration of resource adapters to access Enterprise Information Systems (EIS) from applications.
Note: The connectorsInboundSecurity-2.0 feature is not available for Jakarta EE 10 but the same functionality is automatically enabled when the connectors and appSecurity features are enabled.
connectorsInboundSecurity-2.0 Enables security inflow for resource adapters.  
D
distributedMap-1.0 Provides a local cache service, which can be accessed through the DistributedMap API.  
dynamicRouting-1.0 Enables a server to run a REST service to which the WebSphere plug-in for Apache and IHS can connect to dynamically route to all servers in the liberty collective. Configuring a Liberty JVM server to use collectives
E
ejb-3.2 Enables support for Enterprise JavaBeans written to the EJB 3.2 specification. Enterprise JavaBeans (EJB)
Important: When using EJB-related features, the transaction attribute NotSupported is respected by the JTA Liberty transaction system but not the CICS unit of work.
ejbHome-3.2 Enables the use of home interfaces in Enterprise JavaBeans. Enterprise JavaBeans (EJB)
Important: When using EJB-related features, the transaction attribute NotSupported is respected by the JTA Liberty transaction system but not the CICS unit of work.
ejbLite-3.1
ejbLite-3.2
 Enables support for Enterprise JavaBeans written to the EJB Lite subset of the EJB specification.  
ejbPersistentTimer-3.2 Enables the use of persistent timers in Enterprise JavaBeans. Enterprise JavaBeans (EJB)
Important: When using EJB-related features, the transaction attribute NotSupported is respected by the JTA Liberty transaction system but not the CICS unit of work.
Restriction: Db2 JDBC type 2 connectivity is not supported for persisting EJB timers.
ejbRemote-3.2 Enables the use of remote interfaces in Enterprise JavaBeans. Enterprise JavaBeans (EJB)
Important: When using EJB-related features, the transaction attribute NotSupported is respected by the JTA Liberty transaction system but not the CICS unit of work.
el-3.0 Enables support for the Expression Language 3.0.  
enterpriseBeans-4.0

Enables support for Enterprise Beans written to the Jakarta Enterprise Beans 4.0 specification.

For more information, see Developing EJB applications on Liberty.

  
enterpriseBeansLite-4.0 Enables support for Jakarta Enterprise Beans that are written to the Enterprise Beans Lite subset of the Jakarta Enterprise Beans 4.0 specification.  
expressionLanguage-4.0
expressionLanguage-5.0
 Enables support for the Jakarta Expression Language.  
F
faces-3.0
faces-4.0
 Enables support for web applications that use the Jakarta Server Faces framework. This framework simplifies the construction of user interfaces.  
federatedRegistry-1.0 Provides support for treating one or more user registries as a single user registry. Configuring Liberty to use federated registries
H
healthAnalyzer-1.0 Provides health data collection for the health manager. Configuring a Liberty JVM server to use collectives
healthManager-1.0 Provides health monitoring and automatic actions based on health policies. Configuring a Liberty JVM server to use collectives
Restriction: Restrictions of Liberty JVM servers in collectives
J
j2eeManagement-1.1 Allows applications to use the interfaces defined in the JSR77 specification.  
jacc-1.5 Enables support for Java Authorization Contract for Containers (JACC) version 1.5. Developing a Java Authorization Contract for Containers (JACC) Authorization Provider
jakartaee-8.0

Combines the Liberty features that support the Jakarta EE 8.0 Platform.

For more information, see Jakarta EE and Java EE 8 in Liberty.

  
jakartaee-9.1

Combines the Liberty features that support the Jakarta EE 9.1 Platform.

For more information, see Jakarta EE 9.1 programming model support.

  
jakartaee-10.0

Combines the Liberty features that support the Jakarta EE 10.0 Platform.

For more information, see Jakarta EE 10 programming model support.

  
jaspic-1.1

Java Authentication SPI for Containers (JASPIC) allows a Java EE Application Server to use custom authentication. JASPIC providers are defined in JSR-196. If a JASPIC provider and a TAI are configured in the same server, then the TAI has no effect. Therefore, JASPIC is a standard Java EE technology and a more portable solution than a TAI for Java EE applications.

For more information, see Developing a custom JASPIC authentication provider for Liberty.

  
javaee-7.0

Combines the Liberty features that support the Java EE 7.0 Full Platform.

For more information, see Java EE 7 in Liberty.

  
javaee-8.0

Combines the Liberty features that support the Java EE 8.0 Full Platform.

For more information, see Jakarta EE and Java EE 8 in Liberty.
javaMail-1.5 Allows applications to use the JavaMail 1.5 API.  
javaMail-1.6 Allows applications to use the JavaMail 1.6 API.  
jaxb-2.2

Enables support for the Java Architecture for XML Binding 2.2 specification, which provides easy mapping of Java classes to XML documents.

For more information, see Liberty: The web services commands.

  
jaxrs-1.1
jaxrs-2.0
jaxrs-2.1
 Enables support for Java API for RESTful Web Services 1.1. JAX-RS annotations can be used to define web service clients and endpoints that comply with the REST architectural style.  
jaxrsClient-2.0
jaxrsClient-2.1
 Enables support for Java Client API for JAX-RS.  
jaxws-2.2

Enables support for Java API for XML-Based Web Services 2.2. JAX-WS web services and clients communicate using XML.

For more information, see Deploying JAX-WS applications to Liberty.

  
jca-1.6
jca-1.7

Enables the configuration of resource adapters to access Enterprise Information Systems (EIS) from applications.

For more information, see Configuring resource adapters.

 Java EE Connector Architecture (JCA)
Restriction: The use of JCICS API and Db2 JDBC type 2 connectivity capabilities are not supported within threads that are created by the JCA API javax.resource.spi.BootstrapContext.createTimer(). Instead, for the same effect, use the concurrent APIs (javax.enterprise.concurrent.ManagedScheduledExecutorService).
jcaInboundSecurity-1.0 Enables security inflow for resource adapters. Allows JCA inbound resource adapters to flow security contexts by extending the javax.resource.spi.work.SecurityContext abstract class.  
jdbc-4.0
jdbc-4.1
jdbc-4.2
jdbc-4.3
 Enables the configuration of data sources to access databases from applications.

The jdbc-4.0, jdbc-4.1, jdbc-4.2 and jdbc-4.3 implementations reside in the same Db2 JCC driver and are mutually exclusive.

Configuring database connectivity with JDBC
jms-1.1
jms-2.0

Enables the configuration of resource adapters to access messaging systems using the Java Message Service API.

For more information, see Enabling JMS messaging for Liberty.

 Java Message Service (JMS)
jmsMdb-3.1 Enables the use of JMS Message-Driven Enterprise JavaBeans. MDBs allow asynchronous processing of messages within a Java EE component.  
jndi-1.0

Enables the use of Java Naming and Directory Interface (JNDI) to access server configured resources such as DataSources or JMS Connection Factories.

For more information, see Naming.

  
jpa-2.0
jpa-2.1
jpa-2.2

Enables support for applications that use application-managed and container-managed JPA.

For more information, see Developing Java Persistence API (JPA) applications and Configuring JPA in Liberty.

  
jsf-2.0
jsf-2.2
jsf-2.3
 Enables support for web applications that use the Java Server Faces (JSF) framework. This framework simplifies the construction of user interfaces.  
json-1.0 Provides access to the JavaScript Object Notation (JSON4J) library that provides a set of JSON handling classes for Java environments.
Note: If you upgrade from jaxrs-2.0 to jaxrs-2.1, the json-1.0 feature is no longer enabled by default.
  
jsonb-1.0
jsonb-2.0
jsonb-3.0

Provides a standard for converting between Java objects and JavaScript Object Notation (JSON).

For more information, see Configuring JSON-B in Liberty.

  
jsonp-1.0
jsonp-1.1
jsonp-2.0
jsonp-2.1

Provides a standardized method for constructing and manipulating data to be rendered in JavaScript Object Notation (JSON).

For more information, see Configuring JSON-P in Liberty.

  
jsp-2.2
jsp-2.3

Enables support for Java Server Pages (JSPs). This framework simplifies the construction of user interfaces.

For more information, see Configuring Liberty for JavaServer Pages 2.3.

  
jta-1.1
jta-1.2
 Supports the Java Transaction API (JTA).
Note: Java Transaction API is a protected Liberty feature.
Java Transaction API (JTA)
jwt-1.0

Allows runtime to create JWT tokens.

For more information, see Configuring JSON Web Token in Liberty.

  
jwtSso-1.0 Allows the runtime to produce and consume MP-JWT cookies for authentication.  
L
ldapRegistry-3.0 Enables support for using an LDAP server as a user registry. Any server that supports LDAP Version 3.0 can be used. Multiple LDAP registries can be configured, and then federated to achieve a single logical registry view. Configuring Liberty to use an LDAP user registry
localConnector-1.0 Allows the use of a local JMX connector that is built into the JVM to access JMX resources in the server. Java Management Extensions API (JMX)
M
mail-2.0
mail-2.1
 Allows applications to use the Jakarta Mail API.  
managedBeans-1.0
managedBeans-2.0
 Managed Beans provide a common foundation for different Jakarta EE components types that are managed by a container. Common services provided to Managed Beans include resource injection, lifecycle management and the use of interceptors.  
mdb-3.1
mdb-3.2

Enables the use of Message-Driven Enterprise JavaBeans. MDBs allow asynchronous processing of messages within a Java EE component.

For more information, see Deploying message-driven beans within Liberty.

  
messaging-3.0
messaging-3.1
 Enables the configuration of resource adapters to access messaging systems by using the Jakarta Messaging API.  
messagingClient-3.0 Provides applications with access to the message queues that are hosted on WebSphere Application Server through the Jakarta Messaging 3.0 API.  
messagingSecurity-3.0 Enables the WebSphere Embedded Messaging Server to authenticate and authorize access from Jakarta Messaging clients.  
messagingServer-3.0 Enables an embedded messaging server that is Jakarta Messaging compliant. Applications can send and receive messages by using the messagingClient-3.0 feature.  
microProfile-1.0
microProfile-1.2
microProfile-1.3
microProfile-1.4
microProfile-2.0
microProfile-2.1
microProfile-2.2
microProfile-3.0
microProfile-3.2
microProfile-3.3
microProfile-4.0
microProfile-4.1
microProfile-5.0
microProfile-6.0
microProfile-6.1
 Combines the Liberty features that support MicroProfile.
Note: microProfile-4.0 does not support mpReactiveMessaging-1.0, mpReactiveMessaging-3.0, mpReactiveStreams-1.0, and mpReactiveStreams-3.0 features.
 Developing microservices with MicroProfile
monitor-1.0 Enables performance monitoring of Liberty runtime components by using a JMX client. Java Management Extensions API (JMX)
mongodb-2.0 Provides support for the MongoDB Java Driver and allows remote database instances to be configured in the server configuration. Applications interact with these databases through the MongoDB APIs.  
mpConfig-1.1
mpConfig-1.2
mpConfig-1.3
mpConfig-1.4
mpConfig-2.0
mpConfig-3.0
mpConfig-3.1
 Provides a unified mechanism to access configuration, providing a single view of multiple sources.  
mpFaultTolerance-1.0
mpFaultTolerance-1.1
mpFaultTolerance-2.0
mpFaultTolerance-2.1
mpFaultTolerance-3.0
mpFaultTolerance-4.0
 Supports the MicroProfile Fault Tolerance API.  
mpHealth-1.0
mpHealth-2.0
mpHealth-2.1
mpHealth-2.2
mpHealth-3.0
mpHealth-3.1
mpHealth-4.0
 Provides support for the MicroProfile Health specification.  
mpJwt-1.0
mpJwt-1.1
mpJwt-1.2
mpJwt-2.0
mpJwt-2.1
 Enables web applications or microservices to use the Eclipse MicroProfile JSON Web Token specification.  
mpMetrics-1.0
mpMetrics-1.1
mpMetrics-2.0
mpMetrics-2.2
mpMetrics-2.3
mpMetrics-3.0
mpMetrics-4.0
mpMetrics-5.0
mpMetrics-5.1
 Provides support for the Eclipse MicroProfile Metrics specification for enterprise Java.  
mpOpenAPI-1.0
mpOpenAPI-1.1
mpOpenAPI-2.0
mpOpenAPI-3.0
mpOpenAPI-3.1
 Provides support for the Eclipse MicroProfile OpenAPI specification for enterprise Java.  
mpOpenTracing-1.0
mpOpenTracing-1.1
mpOpenTracing-1.2
mpOpenTracing-1.3
mpOpenTracing-2.0
mpOpenTracing-3.0
 Provides a mechanism to access an opentracing.io Tracer.  
mpReactiveMessaging-1.0
mpReactiveMessaging-3.0
 The Eclipse MicroProfile Reactive Messaging specification provides asynchronous messaging support based on Reactive Streams for MicroProfile.
Restriction: Netty and Reactive.IO are not supported.
mpReactiveStreams-1.0
mpReactiveStreams-3.0

Provides support for the MicroProfile Reactive Streams 1.0 API

Provides support for the MicroProfile Reactive Streams 3.0 API
Restriction: Netty and Reactive.IO are not supported.
mpRestClient-1.0
mpRestClient-1.1
mpRestClient-1.2
mpRestClient-1.3
mpRestClient-1.4
mpRestClient-2.0
mpRestClient-3.0
 Provides a type-safe mechanism for invoking RESTful services.  
mpTelemetry-1.0
mpTelemetry-1.1
mpTelemetry-2.0
 Enables support for the Eclipse MicroProfile Telemetry specification.  
O
oauth-2.0 Enables web applications to integrate OAuth 2.0 for authenticating and authorizing users.
Configuring OAuth 2.0 for authorization
Configuring OAuth 2.0 for authorization
How it works: OAuth 2.0
openidConnectClient-1.0 Enables web applications to integrate OpenID Connect Client 1.0 for authenticating users instead of, or in addition to, the configured user registry. How it works: OpenID Connect
openidConnectServer-1.0 Enables web applications to integrate OpenID Connect Server 1.0 for authenticating users instead of, or in addition to, the configured user registry. How it works: OpenID Connect
osgiConsole-1.0 Enables an OSGi console to aid with debug of the runtime. Troubleshooting Java applications
osgi.jpa-1.0 This feature is superseded by the blueprint-1.0 and jpa-2.0 features that both include OSGi capability. When those features are both added to the server, this feature is added automatically.  
P
pages-3.0
pages-3.1
 Enables support for Jakarta Server Pages that are written to the Jakarta Server Pages specification. This framework simplifies the construction of user interfaces.  
persistence-3.0
persistence-3.1
 Enables support for applications that use application-managed and container-managed persistence.  
R
requestTiming-1.0 Provides warnings and diagnostic info for slow or hung requests. For information on how the requestTiming-1.0 feature works, see Slow and hung request detection.
restConnector-1.0
restConnector-2.0
 Enables remote access from a Java client or directly through an HTTPS call. Java Management Extensions API (JMX)
restfulWS-3.0
restfulWS-3.1
 Enables support for Jakarta RESTful Web Services. These annotations can be used to define web service clients and endpoints that comply with the REST architectural style.  
restfulWSClient-3.1 Enables support for the Jakarta RESTful Web Services Client API.  
S
servlet-3.0
servlet-3.1
servlet-4.0
servlet-5.0
servlet-6.0
 Enables support for HTTP Servlets written to the Java Servlet specification, including support for the HTTP/2 protocol.  
sessionCache-1.0 Enables persistence of HTTP sessions that uses JCache.  
sessionDatabase-1.0 Enables persistence of HTTP sessions to a data source that uses JDBC.  
springBoot-1.5
springBoot-2.0
springBoot-3.0
 Provides support for Spring Boot applications. Spring Boot applications
ssl-1.0 Provides support for Secure Sockets Layer (SSL) connections and SAF keyrings.
Configuring TLS for a Liberty JVM server by using RACF
Configuring TLS client authentication for a Liberty JVM server by using RACF
Configuring confidentiality and integrity
T
transportSecurity-1.0 Enables support for Secure Sockets Layer (SSL) connections.
Configuring TLS for a Liberty JVM server by using RACF
Configuring TLS client authentication for a Liberty JVM server by using RACF
Configuring confidentiality and integrity
W
wab-1.0 Provides support for web application bundles (WAB) that are inside enterprise bundles (EBA). Creating an OSGi Application Project
Note: This feature is automatically added by CICS when the JVM system property com.ibm.cics.jvmserver.wlp.wab=true.
wasJmsClient-1.1
wasJmsClient-2.0
 Provides applications with access to message queues hosted in Liberty through the JMS API. Java Message Service (JMS)
wasJmsSecurity-1.0 Enables an embedded messaging server to authenticate and authorize access from JMS clients. Java Message Service (JMS)
wasJmsServer-1.0 Enables an embedded messaging server that is JMS compliant. Applications can send and receive messages using the wasJmsClient feature. Java Message Service (JMS)
webCache-1.0 Enables local caching for web responses. It includes the distributedMap feature and performs automatic caching of web application responses to improve response times and throughput.  
webProfile-6.0 Combines the Liberty features that support the Java EE 6.0 Web Profile.  
webProfile-7.0 Combines the Liberty features that support the Java EE 7.0 Web Profile.  
webProfile-8.0 Combines the Liberty features that support the Java EE 8.0 Web Profile.
Note: Java EE 8, which includes new versions of features such as servlet-4.0 cannot be used with the wab-1.0 feature. To prevent CICS automatically including wab-1.0, and to take advantage of Java EE 8 APIs, set the property com.ibm.cics.jvmserver.wlp.wab=false in the JVM profile.
webProfile-9.1 Combines the Liberty features that support the Jakarta EE 9.1 Web Profile.  
webProfile-10.0 Combines the Liberty features that support the Jakarta EE 10.0 Web Profile.  
websocket-1.1
websocket-2.0
websocket-2.1

Enables support for WebSocket applications.

For more information, see Developing WebSocket applications in Liberty.

  
wmqJmsClient-2.0 Provides applications with access to message queues hosted on IBM MQ through the JMS 2.0 API.
Restriction: Only supported when the JMS application connects to IBM MQ using the client mode transport. Requires V9.0.1 of the IBM MQ Resource Adapter for Liberty.
Important: This restriction also applies to CICS standard-mode Liberty.
X
xmlBinding-3.0
xmlBinding-4.0
 Enables support for the Jakarta XML Binding specification, which provides easy mapping of Java classes to XML documents.  
xmlWS-3.0
xmlWS-4.0
 Enables support for Jakarta XML Web Services. These web services and clients communicate using XML.  
Z
zosRequestLogging-1.0 Collects HTTP request information and writes an SMF record for each request. For information on how to enable z/OS request logging, see Enabling request logging for Liberty on z/OS. For information on how to view SMF data, see Viewing the output data set.
zosSecurity-1.0 Enables the server to use the SAF Registry in the z/OS platform for authenticating users and authorizing access to applications
Restriction: zosSecurity-1.0 is enabled by cicsts:security-1.0.
zosTransaction-1.0 Enables Liberty to synchronize and manage transactional activity between the z/OS Resource Recovery Services (RRS), the transaction manager of the application server, and the resource manager.
Restriction: zosTransaction-1.0 is only supported for JMS applications that connect to IBM MQ using BINDINGS mode transport in CICS standard-mode Liberty.

The following categories of features are documented in the preceding table.

CICS Liberty features

The following table provides a set of CICS features to integrate Liberty features with the CICS qualities of service. The Liberty JVM server mode can be set by specifying CICS_WLP_MODE in the JVM profile.

Integrated-mode
Standard-mode

Jakarta EE 10 Platform Liberty features

You can use jakartaee-10.0 to enable all these features in one go, or you can enable them separately.

Jakarta EE 9 Platform Liberty features

You can use jakartaee-9.1 to enable all these features in one go, or you can enable them separately.

Java EE 8 Full Platform and Jakarta EE 8 Platform Liberty features

You can use jakartaee-8.0 or javaee-8.0 to enable all these features in one go, or you can enable them separately.

Java EE 7 Full Platform Liberty features

You can use javaee-7.0 to enable all these features in one go, or you can enable them separately.

Java EE 6 Technologies Liberty features

You can use javaee-6.0 to enable all these features in one go, or you can enable them separately.

MicroProfile Liberty features

The MicroProfile convenience features enable a subset of more features. To discover the individual features, use the link in the following list for the convenience feature level you need. You can also individually enable the features if you don't want to enable the full set with the convenience feature.

There are some considerations when you are using specific MicroProfile features in CICS. The feature mpFaultTolerance-1.0, which comes under convenience features microProfile-1.2 and microProfile-1.3, is not designed to work with transactions (UOW, JTA, and so on). Updates to CICS resources must not be made in methods annotated @Bulkhead, @CircuitBreaker, @Fallback, @Retry, or @Timeout. The feature mpJwt-1.0, which comes under convenience features microProfile-1.2 and microProfile-1.3, sets the default value for attribute ignoreApplicationAuthMethod as false. This indicates all requests that are received by Liberty need to have a JWT token in the HTTP header. The default value for attribute mapToUserRegistry is false. For integration with CICS security set this value to true.

microProfile-6.1
microProfile-6.0
microProfile-5.0
microProfile-4.1
microProfile-4.0
microProfile-3.3
microProfile-3.2
microProfile-3.0
microProfile-2.2
microProfile-2.1
microProfile-2.0
microProfile-1.4
microProfile-1.3
microProfile-1.2
microProfile-1.0

Web Profiles Liberty features

The Web Profile convenience features enable a subset of more features. To discover the individual features, use the link in the following list for the convenience feature level you need. You can also individually enable the features if you don't want to enable the full set with the convenience feature.

There are some considerations when you are using specific features. The jdbc-4.0, jdbc-4.1, jdbc-4.2, and jdbc-4.3 implementations reside in the same Db2 JCC driver and are mutually exclusive. These JDBC features are included in all the Web Profiles.

The jaxrsClient-2.0 feature is enabled by jaxrs-2.0. Both features are included in webProfile-7.0.

The Application Client module runs in both the client and the server. The client executes the client specific logic of the application. The other portion of code runs in a client container on the server and communicates data from the business logic running on the server to the client. The Application Client is included in webProfile-6.0.

webProfile-10.0
webProfile-9.1
webProfile-8.0
webProfile-7.0
webProfile-6.0

Liberty features supported for Enterprise OSGi

Extended Programming Models Liberty features

Operations Liberty features

Security Liberty features

Systems Management Liberty features

z/OS Liberty features

For more information about the function in these features, see the documentation for Liberty at Liberty overview. For details of Liberty restrictions, see Runtime environment known restrictions.