Upgrading JSON web services
If you use JSON web services, you have some changes to make when you upgrade your version of CICS®. This information applies to all currently supported CICS TS releases, regardless of your current release and the target release.
If you are upgrading from an end-of-service release, you might need to take additional actions that are relevant to your current, end-of-service release, along with the actions summarized in the upgrade instructions in this information. For details, see Upgrading from end-of-service releases.
Upgrade actions
Table 1 lists the actions you must perform when upgrading to a higher CICS release, regardless of your current release and the target release. The sections that describe these actions in detail are tagged with All versions.
| Action | Mandatory or optional? |
|---|---|
| Take advantage of non-Java support for JSON web services | Optional |
Take advantage of non-Java support for JSON web services
All versions
From CICS TS 5.3, the processing of JSON messages in CICS regions without any Java™ configuration is supported. Therefore, you do not need to configure and install a JVM server. Performance and throughput for many workloads is better than when a JVM server is used to process JSON messages.
To set up CICS as a non-Java JSON service provider, you must configure a provider pipeline that uses the CICS-supplied program DFHPIJT as the terminal handler. For detailed instructions, see Creating the CICS infrastructure for a non-Java JSON service provider.