Developing applications using the CICS Explorer SDK

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

You can use the CICS Explorer SDK 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 the OSGi Alliance website.

You can use the CICS Explorer SDK 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 CICS Explorer SDK 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 CICS Explorer SDK automatically hides the Java classes that you cannot use.

If you are using the Liberty JVM server, the CICS Explorer SDK 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.



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