Developing and deploying applications
What you need to know to develop and deploy CICS Java applications using the CICS Explorer.
- Developing applications using the CICS Explorer SDK
The CICS Explorer Software Development Kit (SDK) provides an environment for developing and deploying Java applications to CICS, including support for OSGi and web projects. - Setting up the target environment
Before you start to develop your application, you must set up a target definition in Eclipse for the earliest level of CICS your application runs in. A target definition consists of a set of plug-ins and environment settings, for example, JCICS API, JRE and any custom APIs you might use. - Creating a plug-in project
You create your CICS Java application as an Eclipse plug-in project that complies with the OSGi specification. The OSGi Service Platform provides a mechanism for developing applications by using a component model and deploying those applications into a framework as OSGi bundles. - Updating the plug-in project manifest file
When you develop a JCICS application, or package an existing application in a plug-in project, you must update the project manifest file and include a CICS-MainClass declaration. - Creating a CICS Bundle project
- Adding a project to a CICS bundle project
When you create a CICS bundle project, the project contains only a manifest file and a properties file. You must add details of any projects that you want to include in the CICS bundle before you deploy everything to zFS. You can add OSGi projects, OSGi applications, or dynamic web projects to a CICS bundle project. - Getting started with the JCICS examples
The CICS Explorer SDK contains JCICS examples to help you start developing Java applications for CICS. - Developing web applications
To develop the presentation layer to a CICS application, you can use the Liberty profile tools to create a web application that uses Java to access CICS services. - Packaging existing applications to run in a JVM server
If you are running Java applications in pooled JVMs, you can move them to run in a JVM server. Because a JVM server can handle multiple requests for Java applications in the same JVM, you can reduce the number of JVMs that are required to run the same workload. - Creating an OSGi bundle fragment for vendor classes
If your application uses IBM or vendor classes that are supplied with the JRE, you must create an OSGi bundle fragment to make the classes available in the OSGi framework - Deploying a CICS bundle
You can deploy a CICS bundle by exporting it directly to a z/OS® UNIX System Services (z/OS UNIX) file system from CICS Explorer. Use a BUNDLE resource to locate the bundle in zFS and dynamically create the resources from the bundle in the CICS region. - Deploying a CICS non-OSGi Java application
The Java applications are included in a CICS bundle and can be deployed directly to a z/OS UNIX System Services (z/OS UNIX) file system from CICS Explorer. The exported bundle includes the application JAR files that are used by CICS. - Enabling a Java security manager
By default, Java applications have no security restrictions placed on activities requested of the Java API. To use Java security to protect a Java application from performing potentially unsafe actions, you can enable a security manager for the JVM in which the application runs. - Deploying OSGi bundles in a JVM server
To deploy a Java application in a JVM server, you must install the OSGi bundles for the application in the OSGi framework of the target JVM server.
Parent topic: CICS Java Developer Guide