Developing applications using the IBM CICS SDK for Java

CICS Explorer® includes the IBM® CICS® SDK for Java™ and optionally the IBM CICS SDK for Java EE and Liberty. This IBM CICS SDK for Java provides an environment for developing and deploying Java applications to CICS, including support for OSGi and web projects.

If you want to develop Java applications without using the SDK, see Developing applications using Maven or Gradle.

You can use the IBM CICS SDK for Java to create new applications, or repackage existing Java applications to comply with the OSGi specification. OSGi provides a mechanism for developing applications by using a component model and deploying those applications to a framework as OSGi bundles. An OSGi bundle is the unit of deployment for an application and contains version information, dependencies, and application code. The main benefit of OSGi is that you can create applications from reusable components that are accessed only through well-defined interfaces called Java packages. You can then use OSGi services to access the Java packages. You can also manage the lifecycle and dependencies of Java applications in a granular way. For information about developing applications with OSGi, see OSGi Alliance.

You can use the IBM CICS SDK for Java to develop a Java application to run in any supported release of CICS. Different releases of CICS support different versions of Java, and the JCICS API is also extended in later releases to support more features of CICS. To avoid use of the wrong classes, the IBM CICS SDK for Java provides a feature to set up a target platform or project libraries. You can define which release of CICS you are developing for, and the IBM CICS SDK for Java automatically hides the Java classes that you cannot use.

If you are using the Liberty JVM server, the IBM CICS SDK for Java can help you work with Dynamic Web Projects and OSGi Application Projects. You can create an application that has a modern web layer and business logic that uses JCICS to access CICS services. If your web application needs to access code from another OSGi bundle, it must be deployed as an OSGi Application Project (EBA file). You must either include the other OSGi bundle in the application manifest, or install the other bundle in the Liberty bundle_repository as a common library. The EBA file must include a web-enabled OSGi bundle (WAB file) to provide the entry point to the application and to expose it as a URL to a web browser.