Developing Java applications to run in a Liberty JVM server
Configure the Liberty JVM server to run a web container if you want to deploy Java™ EE applications that use WebSphere® Application Server Liberty.
- Setting up the development environment
To develop Java EE applications that use the JCICS APIs, you must install the CICS Explorer and the CICS Explorer SDK for Java EE and Liberty features. - Java EE and Liberty applications
To provide modern interfaces to CICS applications, you can develop a presentation layer that uses web application technology. Eclipse-based web development tools provide the development platform to create these applications, and the IBM® CICS TS SDK for Java EE and Liberty that is optionally installed with CICS Explorer provides the support to build, package, and deploy them to run in CICS. - Migrating Java EE applications to run in Liberty JVM server
If you have a Java EE application running in a Liberty instance that accesses CICS over a network, you can run the application in a Liberty JVM server to optimize performance. - Linking to a Java EE application from a CICS program
You can link to a Java EE application 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. The Java EE application is required to be a plain Java object (POJO) packaged in a Web ARchive (WAR) or Enterprise Application Archive (EAR). This topic applies to CICS integrated-mode Liberty only. - Java Transaction API (JTA)
The Java Transaction API (JTA) can be used to coordinate transactional updates to multiple resource managers. - Java Persistence API (JPA)
The JPA can be used to create object oriented versions of relational database entities for developers to make use of in their applications. - Enterprise JavaBeans (EJB)
Enterprise JavaBeans (EJB) is a Java API, and a subset of the Java EE specification. EJBs contain the business logic of an application, and are fully supported by CICS Liberty, including the Lite subset. - Java Message Service (JMS)
Java Message Service (JMS) is an API that allows application components based on Java EE to create, send, receive, and read messages. JMS support in Liberty is supplied as a group of related features that support the deployment of JMS resource adapters. - Java Management Extensions API (JMX)
The Java Management Extensions API (JMX) is used for resource monitoring and management. - Java Authorization Contract for Containers (JACC)
Liberty supports authorization that is based on the Java Authorization Contract for Containers (JACC) specification in addition to the default authorization. When security is enabled in Liberty, the default authorization is used unless a JACC provider is specified. - Java Authentication Service Provider Interface for Containers (JASPIC)
The Java Authentication Service Provider Interface for Containers (JASPIC) specification defines a service provider interface (SPI). Authentication providers, that implement message authentication mechanisms, can be integrated in client or server message processing containers or runtimes. - Java EE Connector Architecture (JCA)
JCA connects enterprise information systems such as CICS, to the JEE platform. - Liberty web server plug-in
The web server plug-in allows the forwarding of HTTP requests from a supported web server, on to one or more Liberty application servers.
dfhpj_devjavaweb.html |
Last updated: Monday, 5 June 2017