Running an IBM z/OS Connect Server within CICS

z/OS Connect can be run inside a CICS® Transaction Server for z/OS (CICS TS) Liberty JVM server as an alternative to running in a standalone WebSphere® Application Server Liberty instance. CICS TS version 5.6 or later is required to use a JCICS connection.

Warning: When using CICS TS 6.3 or later, the z/OS Connect APAR PH68476 is required.

zosConnect-3.0 Applies to zosConnect-3.0.

Important:
    • JCICS connections are only available for API provider.
    • The use of tracking tokens when monitoring JCICS connections is not supported.
    • If you are using z/OS Connect Server that is running within CICS, take care when you start and stop the server. Ending the CICS address space that is running z/OS Connect shuts down CICS. Instead, use the appropriate A launch icon to indicate a link opens a new tab or window.CEMT SET JVMSERVER commands to control the z/OS Connect Server.
    • CICS bundles can be called only if you use a JCICS connection. HTTP requests cannot be sent directly to the bundle. For more information, see A launch icon to indicate a link opens a new tab or window. Defining CICS bundles.
    • JVM server has a thread limit of 256 for a single JVM server in CICS. For more information, see A launch icon to indicate a link opens a new tab or window.CICS task and thread management.
    • The CICS JVM adds its own configuration to server.xml. For more information, see A launch icon to indicate a link opens a new tab or window.Configuring a Liberty JVM server.
    • Liberty JVM servers cannot be members of a collective scaling controller. For more information, see A launch icon to indicate a link opens a new tab or window.Restrictions of Liberty JVM servers in collectives.
    • Use CICS commands to modify the z/OS Connect Server. For more information, see A launch icon to indicate a link opens a new tab or window.CEMT PERFORM JVMSERVER.