z/OS Connect Everything you need to get started quickly. Get started
Welcome to the z/OS Connect content solution. You'll learn how to:
  • Integrate z/OS applications and data using OpenAPI 3 APIs with z/OS Connect.
  • Develop a z/OS Connect API starting from an existing OpenAPI 3.0 definition. Transform z/OS data with our functional mapping capabilities and feature-rich tooling.
  • Deploy your z/OS Connect APIs as isolated secure microservices, driving agility across the enterprise.
  • Take advantage of the improved security schemes provided by the OpenAPI 3 specification to deliver more granular control of user authorization at the API operation level.
See what z/OS Connect can do for your business.
Big picture 1. Develop APIs that expose your IBM Z applications and data. 2. Prepare and deploy a z/OS Connect API with DevSecOps. 3. Plan z/OS Connect API production workloads. How to get started
Overview

Develop APIs in your own z/OS Connect development environment containing an isolated z/OS Connect development server. Use Red Hat CodeReady Workspaces to do this or make the z/OS Connect Designer image available in your own image registries for self-service use with Docker Desktop.

The z/OS Connect Designer provides a new, intuitive, web-based development experience that allowing an application developer to:

  • Iteratively develop, run and test your API in isolation with your own z/OS Connect Development server
  • Start by importing from an OpenAPI 3 definition
  • Use JSONata, a powerful data transformation language, to supercharge your API mapping
  • Edit and refactor project files at any point with any IDE
  • Manage API project changes across your teams using your choice of source control management (SCM) systems.
Getting started with Red Hat CodeReady Workspaces

Red Hat CodeReady Workspaces provides a way to provision a pre-configured z/OS Connect Designer workspace for team members to develop API projects.

The z/OS Connect tutorial will take you through using the z/OS Connect Designer in Red Hat CodeReady Workspaces to create a sample Db2 API by defining rich mappings between an existing API definition and a z/OS System of Record (SoR) using JSONata expressions. Iteratively run and test your API within your project and when finished, checking it into SCM.

Using Red Hat CodeReady Workspaces to create your first Db2 API Cloud native development with Red Hat CodeReady Workspaces What is Red Hat OpenShift?
Getting started with Docker Desktop

Docker Desktop provides a container runtime for developing z/OS Connect API projects using the z/OS Connect Designer.

The z/OS Connect tutorials will take you through using the z/OS Connect Designer with Docker Desktop to create a Sample API of your choosing (CICS or Db2) by defining rich mappings between an existing API definition and a z/OS System of Record (SoR) using JSONata expressions. Iteratively run and test your API within your project and when finished, checking it into SCM.

Using Docker Desktop to create your first CICS API Using Docker Desktop to create your first Db2 API IBM Cloud Learn Hub: Docker What is Docker Desktop?
Overview

Deploy API's using cloud native DevSecOps best practices to benefit from shift left development and faster time to market.

Use Red Hat OpenShift pipelines to create an industry standard continuous integration, continuous delivery (CI/CD) pipeline to implement a DevSecOps approach for cloud native deployments of APIs. Treat configuration as code allowing deployments to be managed as part of your delivery process.

IBM Cloud Hub Learning: DevSecOps Introducing OpenShift Pipelines
Steps

Create a sample pipeline in Red Hat OpenShift taking a z/OS Connect Sample API project from source code management (SCM) to a deployed, callable API with these steps:

  1. Install the z/OS Connect operator and pull the z/OS Connect server image.
  2. Trigger automated builds in RedHat OpenShift Pipelines after each new commit to SCM.
  3. Add a pipeline step to build a .war file from the API project using Gradle.
  4. Add a pipeline step to create a z/OS Connect server image layering API project .war file.
  5. Define ConfigMaps and secrets to inject environment variables into the API container at deployment time.
  6. Call your new z/OS Connect API.
Steps to deploy API's with z/OS Connect What is a Red Hat OpenShift ConfigMap? What is a Kubernetes secret?
Overview

Learn how to manage your running z/OS Connect APIs within your open container platform.

Monitoring z/OS Connect APIs

Use Prometheus and Grafana to monitor z/OS Connect APIs using the metrics endpoints provided in every z/OS Connect server.

Monitor z/OS Connect APIs running in your cluster
High availability and disaster recovery of z/OS Connect APIs

z/OS Connect servers can leverage high availability mechanisms of an OpenShift cluster. Learn more about high availability in container platforms and how to benefit from a cloud native approach.

Defining high availability for your deployments in Red Hat OpenShift
Securing z/OS Connect APIs

Take advantage of the improved security schemes provided by the OpenAPI 3 specification to deliver more granular control of user authorization at the API operation level.

Securing z/OS Connect APIs
Frequently asked questions Q: How can I learn more about z/OS Connect?

A: For answers to questions around the new z/OS Connect capabilities and enhancements on offer, how this compares to the existing offering and how to get started, see frequently asked questions.

Documentation z/OS Connect Documentation

Read more about z/OS Connect.

Information about z/OS Connect in IBM Documentation.
Technical resources IBM z/OS Connect documentation Explore the z/OS Connect documentation API Enablement Community

Ask for help from, and give feedback on, z/OS Connect.

Get help from the community
GitHub samples

z/OS Connect getting started samples

Explore and download samples
Rate this content solution