IBM z/OS Connect system requirements

Detailed system requirements to run IBM z/OS Connect.

Table 1. IBM z/OS Connect hardware requirements
Hardware requirements
IBM z/OS Connect Server zosConnect-2.0zosConnect-3.0Started task	z/OS
IBM z/OS Connect Server (container image) zosConnect-3.0Containers	zos/s390x linux/s390x linux/amd64
IBM z/OS Connect Designer (container image) zosConnect-3.0Containers	linux/s390x linux/amd64
z/OS Connect development tools for Visual Studio Code zosConnect-3.0	Windows Mac Linux
z/OS Connect API toolkit zosConnect-2.0	Windows Mac Linux
z/OS Connect build toolkit zosConnect-2.0	Windows Mac Linux z/OS

Attention: Containers

The IBM z/OS Connect Server and IBM z/OS Connect Designer zosConnect-3.0 images are supported by OCI-compliant container platforms. For example, Red Hat® OpenShift®, IBM z/OS Container Platform, IBM z/OS Container Extensions, Docker Desktop, Rancher, or Podman.

Table 2. IBM z/OS Connect software requirements
Software requirements
IBM z/OS Connect Server zosConnect-2.0zosConnect-3.0Started task	z/OS 2.5 or later from z/OS Connect 3.0.55; z/OS 3.1 from z/OS Connect 3.0.73 and z/OS 3.2 from z/OS Connect 3.0.98 and later versions. The IBM z/OS Connect Server supports the following Java™ levels: Java Technology Edition 8.0.0 or later service refresh and fix pack level. IBM Semeru Runtime Certified Edition for z/OS 11.0.21.0 or later service refresh and fix pack level from 3.0.81. IBM Semeru Runtime Certified Edition for z/OS 17.0.12.0 or later service refresh and fix pack level from 3.0.81. IBM Semeru Runtime Certified Edition for z/OS 21.0.0.0 or later service refresh and fix pack level from 3.0.87.
IBM z/OS Connect Server (container image) zosConnect-3.0Containers	An OCI-compliant container platform of your choice. For example, IBM z/OS Container Platform 1.1 or later, Red Hat OpenShift 4.9 or later.
IBM z/OS Connect Designer (container image) zosConnect-3.0Containers	An OCI-compliant container runtime of your choice. For example, Docker Desktop 19.0.3 or later.
z/OS Connect development tools for Visual Studio Code zosConnect-3.0	Visual Studio Code 1.99 or later. API provider Gradle plug-in 1.4.11 or later. API requester Gradle plug-in 1.2.6 or later.
API provider Gradle plug-in zosConnect-3.0	API provider Gradle plug-in 1.0 to 1.0.2 supports Gradle 6.8.3 to 8.0.2. API provider Gradle plug-in 1.1.0 to 1.4.10 supports Gradle 7.6.1 to 8.12.1. API providerGradle plug-in 1.4.11 and later versions support Gradle 7.6.1 to 9.0.0. See Note 1.
API requester Gradle plug-in zosConnect-3.0	API requester Gradle plug-in 1.0 to 1.0.2 supports Gradle 6.8.3 to 8.0.0. API requester Gradle plug-in 1.0.3 to 1.2.5 supports Gradle 7.6.1 to 8.12.1. API requester Gradle plug-in 1.2.6 and later versions support Gradle 7.6.1 to 9.0.0. See Note 2.
z/OS Connect API toolkit zosConnect-2.0	IBM Explorer for z/OS Aqua 3.3 or later.
z/OS Connect build toolkit zosConnect-2.0	Java 8 or later on any platform.
OpenTelemetry in systems of record	IBM CICS Transaction Server 6.3 and later. Db2 13 at any function level starting at V13R1M100 through the following APAR PH67971: Db2 for z/OS OpenTelemetry Distributed Tracing Support

Note:

On z/OS, API provider Gradle plug-in 1.1.0 and later versions support Gradle 7.6.1 to 8.3 and 8.8 and later. For more information, see IBM z/OS Connect capabilities compatibility.
On z/OS, API requester Gradle plug-in 1.0.3 and later versions support Gradle 7.6.1 to 8.3 and 8.8 and later. For more information, see IBM z/OS Connect capabilities compatibility.

Important:

Minimum required service levels are listed where appropriate. If a specific level is not listed, support is provided for the General Availability (GA) release of the product. Service levels later than those listed are also supported, if the product provides upward compatibility between service releases.
For supported versions of Systems of Records (SoRs) or z/OS application, see the IBM Documentation for that product.
The runtime z/OS Java™ requirements also apply to all the product-supplied user scripts such as securityUtility.

zosConnect-3.0 requirements

Table 3. Requirements for zosConnect-3.0
Requirements for zosConnect-3.0	Details
Artifacts (WAR files)	zosConnect-3.0 WAR files can be deployed in a z/OS Connect Server that is at the same release level or later than the release level of the z/OS Connect Designer that was used to generate the artifacts. For more information, see z/OS Connect artifact compatibility. Restriction: zosConnect-3.0 artifacts (WAR files) should not be deployed to a z/OS Connect Server that is an older release version than the release version of the z/OS Connect Designer, the z/OS Connect API provider Gradle plug-in or the z/OS Connect API requester Gradle plug-in.
Creating APIs to access z/OS subsystems Containers	The z/OS Connect Designer, the container image-based tool for creating APIs, requires installation of the z/OS Connect Designer container image. For more information, see Download the IBM z/OS Connect Designer image.
Creating API requesters to access RESTful APIs Started task	Gradle must be installed and configured to access the z/OS Connect API requester Gradle plug-in that is used to generate the API requesters and associated artifacts. For more information, see Building IBM z/OS Connect APIs with Gradle and Using the API requester Gradle plug-in. z/OS Connect must be installed by using SMP/E and the z/OS Connect Server configured. For more information, see Installing IBM z/OS Connect and Configuring z/OS Connect zosConnect-3.0 API requesters.
Creating APIs to access z/OS subsystems and API requesters to access RESTful APIs	Visual Studio z/OS Connect development tools for Visual Studio Code must be installed. For more information, see Installing the IBM z/OS Connect development tools for Visual Studio Code extension.