CICS and z/OS Connect

z/OS Connect enables CICS® programs to be called with a JavaScript Object Notation (JSON) interface. z/OS Connect for CICS 1.0 was first introduced as an alternative to the JSON capabilities of the Java Pipelines for JSON that were provided in the CICS TS Feature Pack for Mobile Extensions and integrated into CICS TS Version 5.2. Since then, z/OS Connect has grown into a separate product, called z/OS Connect Enterprise Edition, with additional capabilities. This section describes the differences between the alternative offerings and the steps towards implementation.

For an overview of JSON services, see "CICS as a service provider for JSON requests in IBM Knowledge Center.

Maintenance considerations for z/OS Connect Enterprise Edition

Because z/OS Connect Enterprise Edition can run standalone or within Liberty embedded in CICS, the two environments must be described uniquely. You can run both environments concurrently, but they are not mutually exclusive, so care is needed when applying maintenance to the WebSphere Liberty Profile (WLP) client libraries that contain the BBOA* modules.

For more information, see Keeping CICS TS 5.3 and z/OS Connect EE 2.0 maintenance in sync.

z/OS Connect Enterprise Edition

z/OS Connect Enterprise Edition is a separately-orderable IBM product. It builds on the capabilities of z/OS Connect for CICS 1.0, which included support for JSON services. z/OS Connect Enterprise Edition enables API developers to construct JSON APIs from JSON services. The APIs are constructed and packaged with the Eclipse-based API Editor that is provided with z/OS Connect Enterprise Edition, then deployed to the z/OS Connect runtime. The API package includes Swagger 2.0 definitions to make it easier for developers to incorporate the APIs into their applications. Key z/OS Connect capabilities, such as authorization security checking for service invocation, creation of System Management Facility (SMF) records, and logging of RESTful service requests also apply to the APIs.

z/OS Connect Enterprise Edition can be configured to run in a Liberty server in CICS. This configuration enables local, high-performance connectivity to CICS programs.

JSON services that were developed for use with z/OS Connect for CICS 1.0, and most of the JSON services that were developed for use with the Java Pipelines for JSON, can be hosted in z/OS Connect Enterprise Edition. See z/OS Connect for CICS 1.0 for more details. However, users of the API Editor that is supplied with z/OS Connect Enterprise Edition should be aware of some restrictions. See Using APIs from z/OS Connect Enterprise Edition for more details.

For more information about z/OS Connect Enterprise Edition, see z/OS Connect Enterprise Edition documentation in IBM Knowledge Center.

z/OS Connect for CICS 1.0

z/OS Connect for CICS 1.0 is a no-charge feature provided in CICS TS from Version 5.2. It is broadly equivalent to the Java Pipelines for JSON and most JSON web Services can be redeployed from one environment to the other without changes to applications or WSBind files. However, the URI and security configuration can be different in each environment. JSON web services that are deployed to z/OS Connect for CICS 1.0 can also be deployed to z/OS Connect Enterprise Edition.

The version of z/OS Connect that is embedded in CICS TS shares much of the function of z/OS Connect in WebSphere Liberty for z/OS, but it is optimized for local access to CICS and uses standard CICS services. If you are familiar with z/OS Connect in WebSphere Liberty for z/OS, the main differences between this and z/OS Connect for CICS 1.0 are as follows:
  • z/OS Connect for CICS 1.0 supports only the deployment of JSON web services for CICS. It cannot be used to target other z/OS subsystems such as IMS or Batch.
  • z/OS Connect for CICS 1.0 integrates with CICS resources. JSON web services are deployed using WEBSERVICE and URIMAP resources.
  • JSON service-enablement techniques from the Java Pipelines for JSON are supported with z/OS Connect for CICS 1.0, including those that are not normally available in z/OS Connect.
  • JSON services can be developed by using both bottom-up and top-down development strategies.
  • JSON web services generated for Java Pipelines for JSON can be redeployed to z/OS Connect for CICS 1.0.
For more information about z/OS Connect in WebSphere Liberty for z/OS, see IBM z/OS Connect overview.

Java™ Pipelines for JSON (or the Feature Pack for Mobile Extensions)

The Mobile Extensions Feature Pack 1.0 worked with CICS TS for z/OS Version 5.1 and Version 4.2. The Feature Pack provided capability to expose CICS applications as RESTful web services with JSON payloads, call existing JSON applications, and convert JSON to and from application data. From Version 5.2, this capability was integrated into CICS TS.

Comparing z/OS Connect capabilities

This section compares the capabilities of z/OS Connect Enterprise Edition and z/OS Connect for CICS 1.0. A comparison for the Java Pipelines for JSON (or the Feature Pack for Mobile Extensions) is also included because it preceded z/OS Connect for CICS 1.0.

Table 1. Comparing the capabilities of z/OS Connect Enterprise Edition, z/OS Connect for CICS 1.0, and the Java Pipelines for JSON (or the Feature Pack for Mobile Extensions)
Capability z/OS Connect Enterprise Edition z/OS Connect for CICS 1.0 Java Pipelines for JSON (or the Feature Pack for Mobile Extensions)
Support for standard z/OS Connect capabilities Yes. Service Discovery requires extra configuration. Yes. Service Discovery requires extra configuration. No
Enable CICS programs as JSON web services Yes Yes Yes
Support for RESTful JSON services Yes Yes Yes
Support for RESTful APIs Yes No No
Support for starting remote JSON services No. Use DFHJSON. No. Use DFHJSON. No (use DFHJSON)
Support for CICS data transformation that uses the DFHLS2JS and DFHJ2LS assistants For services, yes. For APIs, use the z/OS Connect EE-supplied assistants Yes Yes
Support for JSON schema specification Yes (draft-04) Yes (draft-04) Yes (draft-04)
Choice of parser technologies for JSON transformation Yes Yes No
Support for PIPELINE handler programs No No Yes
Support for interceptor programs Yes, by using z/OS® Connect Interceptors Yes, by using z/OS Connect Interceptors Yes, by using Axis2 handlers
Application access to CICS control containers Yes Yes Yes
WSBind deployment through a CICS PIPELINE resource For services, yes. Deploying APIs involves additional artifacts (see the z/OS Connect EE documentation in IBM Knowledge Center for details). Yes Yes
Configuration with URIMAP and WEBSERVICE resources For services, yes Yes Yes
Network configuration Using WebSphere® Liberty Using WebSphere Liberty Using a TCPIPSERVICE resource
Security configuration Using WebSphere Liberty and CICS security Using WebSphere Liberty and CICS security Using CICS
Support for Transport Layer Security (TLS) Yes Yes Yes
Statistics, monitoring, user exits, and other diagnostics infrastructure Consistent with WebSphere Liberty in CICS Consistent with WebSphere Liberty in CICS Consistent with pipelines in CICS
JVM environment A Liberty JVM server that is preferably isolated for sole use by z/OS Connect A Liberty JVM server that is preferably isolated for sole use by z/OS Connect A non-OSGi JVM server configured with JAVA_PIPELINE=YES, preferably isolated for sole use by the Java Pipelines for JSON


zos_connect_overview.html | Timestamp icon Last updated: Sunday, 4 June 2017