Liberty features

CICS® supports features from WebSphere® Application Server Liberty, which enables Java™ EE applications to be deployed into a Liberty JVM server. All features in Tables 2-10 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 11 provides a set of CICS features to integrate Liberty features with the CICS qualities of service.

Java EE 6 and Java EE 7 are generally incompatible and must not be used concurrently.

CICS Liberty features

Table 2. Liberty features supported for Java EE 7 Web Profile
Liberty feature Liberty feature description Using this feature in CICS
beanValidation-1.0 Provides an annotation-based model for validating JavaBeans.  
beanValidation-1.1 Provides an annotation-based model for validating JavaBeans.  
Start of changecdi-1.2End of change Provides a mechanism to inject components such as EJBs or Managed Beans into other components such as JSPs or EJBs.  
Start of changeejbLite-3.2End of change Enables support for Enterprise JavaBeans written to the EJB Lite subset of the EJB specification.
Restriction: The transaction attribute NotSupported is not supported by a Liberty JVM server.
Start of changeel-3.0End of change Enables support for the Enterprise Language (EL) 3.0 specification.  
Start of changejaxrs-2.0End of change Provides support for the Java API for RESTful Web Services (JAX-RS) in Liberty.  
Start of changejdbc-4.1End of change 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 and jdbc-4.1 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.  
Start of changejpa-2.1End of change Enables support for applications that use application-managed and container-managed JPA.
Note: If you are using jpa-2.1 and you have applied CICS APAR PI67640, which supplies fixpack 16.0.0.4 for Liberty, you might see the following warning message:
CWWJP9991W Exception Description: Server platform class is not valid: null
This message can be ignored.
Start of changejsf-2.2End of change Provides support for web applications that use the JavaServer Faces (JSF) framework.  
Start of changejsonp-1.0End of change Supports the definition of a Java API to process JavaScript Object Notation. Including the support for the JSON parse, generate, transform, and query function.  
Start of changejsp-2.3End of change Enables support for servlet and JavaServer Pages (JSP) applications. Java EE and Liberty applications
managedBeans-1.0 Provides a common foundation for different Java 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.  
Start of changeservlet-3.1End of change Provides support for HTTP Servlets written to the Java Servlet specification. Java EE and Liberty applications
Restriction: The use of servlet login and logout API does not propagate the user ID to the CICS task.
Start of changewebProfile-7.0End of change Provides a convenient combination of the Liberty features that are required to support the Java EE 7 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 3. Liberty features supported for Java EE 7 Full Platform
Liberty feature Liberty feature description Using this feature in CICS
Start of changeappClientSupport-1.0End of change 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.
Start of changebatch-1.0End of change 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).
Restriction: DB2 JDBC type 2 connectivity is not supported for batch persistence.
Start of changeconcurrent-1.0End of change Enables managed executors to be created, which then permit applications to submit tasks that can run concurrently.
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.
Start of changeejb-3.2End of change Enables support for Enterprise JavaBeans written to the EJB 3.2 specification.  
Start of changeejbHome-3.2End of change Provides support for the EJB 2.x APIs.  
Start of changeejbPersistentTimer-3.2End of change Provides support for persistent EJB timers.
Restriction: DB2 JDBC type 2 connectivity is not supported for persisting EJB timers.
Start of changeejbRemote-3.2End of change Provides support for remote EJB interfaces.  
Start of changejacc-1.5End of change Enables support for Java Authorization Contract for Containers (JACC) version 1.5. Developing a Java Authorization Contract for Containers (JACC) Authorization Provider
Start of changejaspic-1.1End of change 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.  
Start of changej2eeManagement-1.1End of change Provides a set of interfaces to manage and monitor applications within the JEE application server.  
Start of changejavaMail-1.5End of change Enables applications to use the JavaMail 1.5 API.  
jaxb-2.2 Provides support to map between Java classes and XML representations.  
jaxws-2.2 Provides support for SOAP web services.  
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 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).
Start of changejcaInboundSecurity-1.0End of change Allows JCA inbound resource adapters to flow security contexts by extending the javax.resource.spi.work.SecurityContext abstract class.  
Start of changemdb-3.2End of change Enables the use of Message-Driven Enterprise JavaBeans written to the EJB 3.2 specification. MDBs allow asynchronous processing of messages within a Java EE component.  
Start of changewasJmsClient-2.0End of change 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 4. 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.  
jta-1.1 Supports the Java Transaction API (JTA).
Note: Java Transaction API is a protected Liberty feature.
Java Transaction API (JTA)
Start of changejta-1.2End of change Supports the Java Transaction API (JTA).
Note: Java Transaction API is a protected Liberty feature.
Java Transaction API (JTA)
Start of changemicroProfile-1.0End of change Combines the Liberty features that support the Micro Profile for enterprise Java.  
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.  
Table 5. 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.
Restriction: The transaction attribute NotSupported is not supported by a Liberty JVM server.
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: The wab-1.0 feature is required by CICS and installed as part of cicsts:core-1.0 and cicsts:standard-1.0.
Table 6. Liberty features supported for Operations
Liberty feature Liberty feature description Using this feature in CICS
Start of changebatchManagement-1.0End of change 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.  
Start of changewmqJmsClient-2.0End of change 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 7. 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 supercedes appSecurity-1.0. Configuring security for a Liberty JVM server
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
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

Table 8. Liberty features supported for z/OS
Liberty feature Liberty feature description Using this feature in CICS
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.
Table 9. Liberty features supported for Java EE 6 Web Profile
Liberty feature Liberty feature description Using this feature in CICS
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.
Restriction: The transaction attribute NotSupported is not supported by a Liberty JVM server.
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
Restriction: The use of servlet login and logout API does not propagate the user ID to the CICS task.
webProfile-6.0 Provides a convenient combination of the Liberty features that are required to support the Java EE 6 Web Profile.  
Table 10. 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 Provides support for the Java API for RESTful Web Services (JAX-RS) in Liberty.  
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).
Start of changejcaInboundSecurity-1.0End of change Allows JCA inbound resource adapters to flow security contexts by extending the javax.resource.spi.work.SecurityContext abstract class.  
jdbc-4.0 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 and jdbc-4.1 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)

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.

The following table provides a set of CICS features to integrate Liberty features with the CICS qualities of service.

Table 11. CICS Liberty features
CICS Feature CICS Liberty mode Description Using this CICS feature
cicsts:core-1.0 Integrated-mode Provides core CICS features, Java Transaction API (JTA) 1.0 and wab-1.0.  
Start of changecicsts:defaultApp-1.0End of change 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
Start of changecicsts:distributedIdentity-1.0End of change Integrated-mode and standard-mode Provides support for distributed identity mapping. Configuring security for a Liberty JVM server by using distributed identity mapping
Start of changecicsts:jcaLocalEci-1.0End of change Integrated-mode Provides a locally optimized JCA ECI resource adapter for calling CICS programs. Using the JCA local ECI resource adapter
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. Manually configuring a CICS DB2 JDBC type 2 driver data source for Liberty
Start of changecicsts:link-1.0End of change 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 a Java EE application from a CICS program
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
Start of changecicsts:standard-1.0End of change 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. This feature includes wab-1.0 which is required by 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. Configuring z/OS Connect EE
cicsts:zosConnect-2.0 Integrated-mode Integrates z/OS Connect with CICS Liberty JVM server. Configuring z/OS Connect EE


liberty_features.html | Timestamp icon Last updated: Monday, 5 June 2017