Liberty features

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

All features in Tables 2-14 relate to CICS integrated-mode Liberty. The features are also supported in CICS standard-mode Liberty without any of the restrictions, unless noted otherwise. Table 15 provides a set of CICS features to integrate Liberty features with the CICS qualities of service.

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. For information about editing the server.xml, see Server configuration.

List of tables

Table 1: Liberty features listed alphabetically

Table 2: Liberty features supported for Java EE 8 Full Platform and Jakarta EE 8 Platform

Table 3: Liberty features supported for Java EE 8 Web Profile

Table 4: Liberty features supported for Java EE 7 Full Platform

Table 5: Liberty features supported for Java EE 7 Web Profile

Table 6: Liberty features supported for Java EE 6 Technologies

Table 7: Liberty features supported for Java EE 6 Web Profile

Table 8: Liberty features supported for Enterprise OSGi

Table 9: Liberty features supported for Extended Programming Models

Table 10: Liberty features supported for MicroProfile

Table 11: Liberty features supported for Operations

Table 12: Liberty features supported for Security

Table 13: Liberty features supported for Systems Management

Table 14: Liberty features supported for z/OS®

Table 15: CICS Liberty features

Table 1. Liberty features alphabetically
Features A - EjbL	Features EjbP - Jpa-2.0	Features Jpa-2.1 - Mo	Features Mp - Z
adminCenter-1.0	ejbPersistentTimer-3.2	jpa-2.1	mpConfig-1.1
appClientSupport-1.0	ejbRemote-3.2	jpa-2.2	mpFaultTolerance-1.0
appSecurity-1.0	el-3.0	jsf-2.0	mpHealth-1.0
appSecurity-2.0	j2eeManagement-1.1	jsf-2.2	mpJwt-1.0
appSecurity-3.0	jacc-1.5	jsf-2.3	mpMetrics-1.0
batch-1.0	jakartaee-8.0	json-1.0	oauth-2.0
batchManagement-1.0 for JEE7	jaspic-1.1	jsonb-1.0	openidConnectClient-1.0
beanValidation-1.0 for JEE6	javaMail-1.5	jsonp-1.0	openidConnectServer-1.0
beanValidation-1.0 for JEE7	javaMail-1.6	jsonp-1.1	osgiConsole-1.0
beanValidation-1.1 for JEE6	javaee-7.0	jsp-2.2	osgi.jpa-1.0
beanValidation-1.1 for JEE7	javaee-8.0	jsp-2.3	restConnector-1.0
blueprint-1.0	jaxb-2.2 for JEE7	jta-1.1	servlet-3.0
cdi-1.0	jaxb-2.2 for JEE6	jta-1.2	servlet-3.1
cdi-1.2	jaxrs-1.1	jwt-1.0	servlet-4.0
cicsts:core-1.0	jaxrs-2.0	ldapRegistry-3.0	sessionDatabase-1.0
cdi-2.0	jaxrs-2.1	localConnector-1.0	springBoot-1.5
cicsts:defaultApp-1.0	jaxrsClient-2.0	managedBeans-1.0	springBoot-2.0
cicsts:distributedIdentity-1.0	jaxrsClient-2.1	mdb-3.1	ssl-1.0
cicsts:jcaLocalEci-1.0	jaxws-2.2 for JEE7	mdb-3.2	wab-1.0
cicsts:jdbc-1.0	jaxws-2.2 for JEE6	microProfile-1.0	wasJmsClient-1.1
cicsts:link-1.0	jca-1.6	microProfile-1.2	wasJmsClient-2.0
cicsts:security-1.0	jca-1.7	microProfile-1.3	wasJmsSecurity-1.0
cicsts:standard-1.0	jcaInboundSecurity-1.0 for JEE6	microProfile-1.4	wasJmsServer-1.0
cicsts:zosConnect-1.0	jcaInboundSecurity-1.0 for JEE7	microProfile-2.0	webCache-1.0
cicsts:zosConnect-2.0	jdbc-4.0	microProfile-2.1	webProfile-6.0
concurrent-1.0	jdbc-4.1	microProfile-2.2	webProfile-7.0
distributedMap-1.0	jdbc-4.2	microProfile-3.0	webProfile-8.0
ejb-3.2	jms-1.1	microProfile-3.2	websocket-1.0
ejbHome-3.2	jms-2.0	microProfile-4.0	websocket-1.1
ejbLite-3.1	jmsMdb-3.1	microProfile-4.1	wmqJmsClient-2.0
ejbLite-3.2	jndi-1.0	mongodb-2.0	zosTransaction-1.0
	jpa-2.0	monitor-1.0	zosSecurity-1.0

Table 2. Liberty features supported for Java EE 8 Full Platform and Jakarta EE 8 Platform.
Liberty feature	Liberty feature description	Using this feature in CICS
appClientSupport-1.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.
batch-1.0	Enables support for the Java Batch 1.0 API defined in JSR-352. This feature does not support Java batch applications that are packaged in an Enterprise Bundle Archive (EBA).
concurrent-1.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.
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.
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.	Jakarta EE 8 and Java EE 8 in Liberty Note: Jakarta 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 Jakarta EE 8 APIs, set the property `com.ibm.cics.jvmserver.wlp.wab=false` in the JVM profile.
javaee-8.0	Combines the Liberty features that support the Java EE 8.0 Full Platform.	Jakarta EE 8 and Java EE 8 in Liberty Note: In Java EE 8, the `jsonb-1.0` feature is enabled by `jaxrs-2.1` as an alternative to the IBM® JSON4J support provided in `json-1.0`. 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.
javaMail-1.6	Allows applications to use the JavaMail 1.6 API.
jaxws-2.2	Enables support for Java API for XML-Based Web Services 2.2. JAX-WS web services and clients communicate using XML.
jca-1.7	Enables the configuration of resource adapters to access Enterprise Information Systems (EIS) from applications.	Java EE Connector Architecture (JCA) Restriction: The use of JCICS API and Db2® JDBC type 2 connectivity capabilities is not supported in threads that are created by the JCA API `javax.resource.spi.BootstrapContext.createTimer()`. 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.2	Enables the configuration of DataSources to access Databases from applications.	Creating a default CICS Db2 DataSource with type 2 connectivity for Liberty Note: The `jdbc-4.0`, `jdbc-4.1` and `jdbc-4.2` implementations reside in the same Db2 JCC driver and are mutually exclusive.
j2eeManagement-1.1	Allows applications to utilize the interfaces defined in the JSR77 specification.
servlet-4.0	Enables support for HTTP Servlets written to the Java Servlet 4.0 specification, including support for the HTTP/2 protocol.
jms-2.0	Enables the configuration of resource adapters to access messaging systems using the Java Message Service API.	Java Message Service (JMS)
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)
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.

Table 3. Liberty features supported for Java EE 8 Web Profile
Liberty feature	Liberty feature description	Using this feature in CICS
appSecurity-3.0	Enables support for securing the server runtime environment and applications using Security-1.0 as defined in JSR-375.	Configuring security for a Liberty JVM server with the Java EE security API 1.0
beanValidation-2.0	Provides an annotation based model for validating JavaBeans.
cdi-2.0	Provides a common mechanism to inject component such as EJBs or Managed Beans into other components such as JSPs or other EJBs.
ejbLite-3.2	Enables support for Enterprise JavaBeans written to the EJB Lite subset of the EJB 3.2 specification.	Using EJB-related features
el-3.0	Enables support for the Expression Language (EL) 3.0 specification.
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.
jaxrs-2.1	Enables support for Java API for RESTful Web Services v2.1.
jaxrsClient-2.1	Enables support for Java Client API for JAX-RS 2.1.
jdbc-4.0 , jdbc-4.1, jdbc-4.2	Enables the configuration of DataSources to access Databases from applications.	Creating a default CICS Db2 DataSource with type 2 connectivity for Liberty Note: The `jdbc-4.0`, `jdbc-4.1` and `jdbc-4.2` implementations reside in the same Db2 JCC driver and are mutually exclusive.
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.
jpa-2.2	Enables support for applications that use application-managed and container-managed JPA written to the Java Persistence API 2.2 specification.
jsf-2.3	Enables support for applications that use application-managed and container-managed JPA.
jsonb-1.0	Provides a standard for converting between Java objects and JavaScript Object Notation (JSON).
jsonp-1.1	Provides a standardized method for constructing and manipulating data to be rendered in JavaScript Object Notation (JSON).
jsp-2.3	Enables support for Java Server Pages (JSPs) that are written to the JSP 2.3 specification.	Java EE and Liberty applications
managedBeans-1.0	Enables support for the Managed Beans 1.0 specification.
servlet-4.0	Enables support for HTTP Servlets written to the Java Servlet 4.0 specification, including support for the HTTP/2 protocol.
websocket-1.1	Enables a web browser or client application and a web server application to communicate by using one full duplex connection.
webProfile-8.0	Provides a convenient combination of the Liberty features that are required to support the Java EE 8 Web Profile.

Table 4. Liberty features supported for Java EE 7 Full Platform
Liberty feature	Liberty feature description	Using this feature in CICS
appClientSupport-1.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.
batch-1.0	Enables support for the Java Batch 1.0 API defined in JSR-352. This feature does not support Java batch applications that are packaged in an Enterprise Bundle Archive (EBA).
beanValidation-1.0	Provides an annotation-based model for validating JavaBeans.
concurrent-1.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.
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.	Using EJB-related features
ejbPersistentTimer-3.2	Enables the use of persistent timers in Enterprise JavaBeans.	Using EJB-related features 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.	Using EJB-related features
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
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.
j2eeManagement-1.1	Allows applications to utilize the interfaces defined in the JSR77 specification.
javaMail-1.5	Allows applications to utilize the JavaMail 1.5 API.
javaee-7.0	Combines the Liberty features that support the Java EE 7.0 Full Platform.
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.
jaxws-2.2	Enables support for Java API for XML-Based Web Services 2.2. JAX-WS web services and clients communicate using XML.
jca-1.7	Enables the configuration of resource adapters to access Enterprise Information Systems (EIS) from applications.	Java EE Connector Architecture (JCA) Restriction: The use of JCICS API and Db2 JDBC type 2 connectivity capabilities is not supported in threads that are created by the JCA API `javax.resource.spi.BootstrapContext.createTimer()`. 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.1jdbc-4.2	Enables the configuration of DataSources to access Databases from applications.	Creating a default CICS Db2 DataSource with type 2 connectivity for Liberty Note: The `jdbc-4.0`, `jdbc-4.1` and `jdbc-4.2` implementations reside in the same Db2 JCC driver and are mutually exclusive.
mdb-3.2	Enables the use of Message-Driven Enterprise JavaBeans written to the EJB 3.2 specification.
jms-2.0	Enables the configuration of resource adapters to access messaging systems using the Java Message Service API.	Java Message Service (JMS)
servlet-3.1	Enables support for HTTP Servlets written to the Java Servlet specification.	Java EE and Liberty applications
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)
webProfile-7.0

Table 5. Liberty features supported for Java EE 7 Web Profile
Liberty feature	Liberty feature description	Using this feature in CICS
appSecurity-2.0	Provides support for securing the server runtime environment and applications. `appSecurity-2.0` supersedes `appSecurity-1.0`.	Configuring security for a Liberty JVM server
beanValidation-1.1	Provides an annotation-based model for validating JavaBeans.
cdi-1.2	Provides a common mechanism to inject component such as EJBs or Managed Beans into other components such as JSPs or other EJBs.
ejbLite-3.2	Enables support for Enterprise JavaBeans written to the EJB Lite subset of the EJB 3.2 specification.	Using EJB-related features
el-3.0	Enables support for the Expression Language (EL) 3.0 specification.
jaxrs-2.0	Provides support for the Java API for RESTful Web Services (JAX-RS) in Liberty.
jaxrsClient-2.0	Enables support for the Java Client API for JAX-RS 2.0.	The jaxrsClient-2.0 feature is enabled by jaxrs-2.0. Configuring JAX-RS 2.0 client.
jdbc-4.0 , jdbc-4.1, jdbc-4.2	Enables the configuration of DataSources to access Databases from applications.	Creating a default CICS Db2 DataSource with type 2 connectivity for Liberty Note: The `jdbc-4.0`, `jdbc-4.1` and `jdbc-4.2` implementations reside in the same Db2 JCC driver and are mutually exclusive.
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.
jpa-2.1	Enables support for applications that use application-managed and container-managed JPA.
jsf-2.2	Provides support for web applications that use the JavaServer Faces (JSF) framework.
jsonp-1.0	Provides a standardized method for constructing and manipulating data to be rendered in JavaScript Object Notation (JSON).
jsp-2.3	Enables support for Java Server Pages (JSPs) that are written to the JSP 2.3 specification.	Java EE and Liberty applications
managedBeans-1.0	Enables support for the Managed Beans 1.0 specification.
servlet-3.1	Enables support for HTTP Servlets written to the Java Servlet specification.	Java EE and Liberty applications
webProfile-7.0	Combines the Liberty features that support the Java EE 7.0 Web Profile
websocket-1.0	Enables a web browser or client application and a web server application to communicate by using one full duplex connection.
websocket-1.1	Enables a web browser or client application and a web server application to communicate by using one full duplex connection.

Table 6. Liberty features supported for Java EE 6 Technologies
Liberty feature	Liberty feature description	Using this feature in CICS
jaxb-2.2	Provides support to map between Java classes and XML representations.
jaxrs-1.1	Enables support for the Java Architecture for XML Binding 2.2 specification, which provides easy mapping of Java classes to XML documents.
jaxws-2.2	Provides support for SOAP web services.
jca-1.6	Enables the configuration of resource adapters to access Enterprise Information Systems (EIS) from applications.	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	Enables the configuration of DataSources to access Databases from applications.	Creating a default CICS Db2 DataSource with type 2 connectivity for Liberty Note: The `jdbc-4.0`, `jdbc-4.1` and `jdbc-4.2` implementations reside in the same Db2 JCC driver and are mutually exclusive.
jms-1.1	Enables the configuration of resource adapters to access messaging systems using the Java Message Service API.	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.
mdb-3.1	Enables the use of Message-Driven Enterprise JavaBeans. MDBs allow asynchronous processing of messages within a Java EE component.
wasJmsClient-1.1	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 clients.	Java Message Service (JMS)
wasJmsServer-1.0	Enables an embedded messaging server in the server. Applications can operate on messages by using the `wasJmsClient` feature.	Java Message Service (JMS)

Table 7. Liberty features supported for Java EE 6 Web Profile
Liberty feature	Liberty feature description	Using this feature in CICS
appSecurity-2.0	Provides support for securing the server runtime environment and applications. `appSecurity-2.0` supersedes `appSecurity-1.0`.	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.
beanValidation-1.0	Provides an annotation-based model for validating JavaBeans.
beanValidation-1.1	Provides an annotation-based model for validating JavaBeans.
cdi-1.0	Provides a mechanism to inject components such as EJBs or Managed Beans into other components such as JSPs or EJBs.
ejbLite-3.1	Enables support for Enterprise JavaBeans written to the EJB Lite subset of the EJB specification.	Using EJB-related features
jdbc-4.0 jdbc-4.1jdbc-4.2	Enables the configuration of DataSources to access Databases from applications.	Creating a default CICS Db2 DataSource with type 2 connectivity for Liberty Note: The `jdbc-4.0`, `jdbc-4.1` and `jdbc-4.2` implementations reside in the same Db2 JCC driver and are mutually exclusive.
jndi-1.0	Provides support for a single Java Naming and Directory Interface (JNDI) entry definition in the server configuration of Liberty.
jpa-2.0	Enables support for applications that use application-managed and container-managed JPA.
jsf-2.0	Provides support for web applications that use the JavaServer Faces (JSF) framework.
jsp-2.2	Enables support for servlet and JavaServer Pages (JSP) applications.	Java EE and Liberty applications
servlet-3.0	Provides support for HTTP Servlets written to the Java Servlet specification.	Java EE and Liberty applications
managedBeans-1.0	Enables support for the Managed Beans 1.0 specification.
webProfile-6.0	Provides a convenient combination of the Liberty features that are required to support the Java EE 6 Web Profile.

Table 8. Liberty features supported for Enterprise OSGi
Liberty feature	Liberty feature description	Using this feature in CICS
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.
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.
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`.

Table 9. Liberty features supported for Extended Programming Models
Liberty feature	Liberty feature description	Using this feature in CICS
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 upgrading from jaxrs-2.0 to jaxrs-2.1 the json-1.0 feature is no longer enabled by default.
jta-1.1	Supports the Java Transaction API (JTA). Note: Java Transaction API is a protected Liberty feature.	Java Transaction API (JTA)
jta-1.2	Supports the Java Transaction API (JTA). Note: Java Transaction API is a protected Liberty feature.	Java Transaction API (JTA)
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.
springBoot-1.5	Provides support for Spring Boot applications using Spring Boot version 1.5.x.	Spring Boot applications
springBoot-2.0	Provides support for Spring Boot applications using Spring Boot version 2.0.x.	Spring Boot applications

Table 10. Liberty features supported for MicroProfile
Liberty feature	Liberty feature description	Using this feature in CICS
microProfile-1.0	Combines the Liberty features that support the MicroProfile for enterprise Java.	These versions of MicroProfile are for use with Java EE 6 and Java EE 7.
microProfile-1.2	Combines the Liberty features that support MicroProfile 1.2 for enterprise Java.
microProfile-1.3	Combines the Liberty features that support MicroProfile 1.3 for enterprise Java.
microProfile-1.4	Combines the Liberty features that support MicroProfile 1.4 for enterprise Java.
microProfile-2.0	Combines the Liberty features that support MicroProfile 2.0 for enterprise Java.
microProfile-2.1	Combines the Liberty features that support MicroProfile 2.1 for enterprise Java.
microProfile-2.2	Combines the Liberty features that support MicroProfile 2.2 for enterprise Java.
microProfile-3.0	Combines the Liberty features that support MicroProfile 3.0 for enterprise Java.
microProfile-3.2	Combines the Liberty features that support MicroProfile 3.2 for enterprise Java.
microProfile-4.0	Combines the Liberty features that support MicroProfile 4.0 for enterprise Java.	These versions of MicroProfile are for use with Java EE 8 or Jakarta EE 8.
microProfile-4.1	Combines the Liberty features that support MicroProfile 4.1 for enterprise Java.
mpConfig-1.1	Provides a unified mechanism to access configuration, providing a single view of multiple sources.
mpFaultTolerance-1.0	Provides support for the MicroProfile Fault Tolerance API for enterprise Java.	Restriction: MicroProfile Fault Tolerance 1.0 is not designed to work with transactions (UOW, JTA, etc.). Updates to CICS resources should not be made in methods annotated @Bulkhead, @CircuitBreaker, @Fallback, @Retry or @Timeout.
mpHealth-1.0	Provides support for the MicroProfile Health API for enterprise Java.
mpJwt-1.0	Enables web applications or microservices to use JSON Web Token (JWT) to authenticate users instead of, or in addition to, the configured user registry.	The default value for attribute `ignoreApplicationAuthMethod` is false. This indicates all requests 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.
mpMetrics-1.0	Provides support for the MicroProfile Metrics API for enterprise Java.

Table 11. Liberty features supported for Operations
Liberty feature	Liberty feature description	Using this feature in CICS
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.
distributedMap-1.0	Provides a local cache service, which can be accessed through the `DistributedMap` API.
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)
monitor-1.0	Enables performance monitoring of Liberty runtime components by using a JMX client.	Java Management Extensions API (JMX)
osgiConsole-1.0	Enables an OSGi console to aid with debug of the runtime.	Troubleshooting Java applications
restConnector-1.0	Enables remote access by JMX clients through a REST-based connector and requires SSL and user security configuration.	Java Management Extensions API (JMX)
sessionDatabase-1.0	Enables persistence of HTTP sessions to a datasource that uses JDBC.
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.
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.

Table 12. Liberty features supported for Security
Liberty feature	Liberty feature description	Using this feature in CICS
appSecurity-1.0	Provides support for securing the server runtime environment and applications.`appSecurity-2.0` supercedes `appSecurity-1.0`.	Configuring security for a Liberty JVM server
appSecurity-2.0	Provides support for securing the server runtime environment and applications. `appSecurity-2.0` supersedes `appSecurity-1.0`.	Configuring security for a Liberty JVM server
jwt-1.0	Allows runtime to create JWT tokens.
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 security for a Liberty JVM server by using distributed identity mapping
oauth-2.0	Enables web applications to integrate OAuth 2.0 for authenticating and authorizing users.	Authorization using OAuth 2.0 Configuring persistent OAuth 2.0 services
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.
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.
ssl-1.0	Provides support for Secure Sockets Layer (SSL) connections and SAF keyrings.	Configuring SSL (TLS) for a Liberty JVM server using RACF Setting up SSL (TLS) client certificate authentication in a Liberty JVM server Configuring SSL (TLS) for a Liberty JVM server using a Java keystore
transportSecurity-1.0	Enables support for Secure Sockets Layer (SSL) connections.

Table 13. Liberty features supported for Systems Management
Liberty feature	Liberty feature description	Using this feature in CICS
adminCenter-1.0	Enables the Liberty Admin Center, a web-based graphical interface for deploying, monitoring and managing Liberty servers in standalone environments.	Configuring Admin Center Restriction: Collectives are not supported in CICS.

Table 14. Liberty features supported for z/OS
Liberty feature	Liberty feature description	Using this feature in CICS
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.

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.

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.

Table 15. CICS Liberty features
CICS Feature	CICS Liberty mode	Description	Using this CICS feature
cicsts:core-1.0	Integrated-mode	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	Integrated-mode and standard-mode	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	Integrated-mode and standard-mode	Provides support for distributed identity mapping.	Configuring security for a Liberty JVM server by using distributed identity mapping
cicsts:jcaLocalEci-1.0	Integrated-mode	Provides a locally optimized JCA ECI resource adapter for calling CICS programs.	Using the JCA local ECI resource adapter Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:jcicsxServer-1.0	Integrated-mode	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	Integrated-mode and standard-mode	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	Integrated-mode	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	Integrated-mode and standard-mode	Provides integration of Liberty security with CICS security, including propagation of thread identity.	Configuring security for a Liberty JVM server Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:standard-1.0	Standard-mode	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
cicsts:zosConnect-1.0	Integrated-mode	Integrates z/OS Connect with CICS Liberty JVM server.	Note: This feature is stabilized. You can continue to use the feature. However, consider using the IBM z/OS Connect Enterprise Edition product. Restriction: The JVM server should be disabled before adding or removing this feature.
cicsts:zosConnect-2.0	Integrated-mode	Integrates z/OS Connect with CICS Liberty JVM server.	Note: This feature is stabilized. You can continue to use the feature. However, consider using the IBM z/OS Connect Enterprise Edition product. Restriction: The JVM server should be disabled before adding or removing this feature.