Skip to main content

Zowe

Zowe is an open-source framework for z/OS that provides standardized APIs, command-line tools, and graphical interfaces to interact with mainframe services using modern workflows and tooling (mainframe access and integration).

  • Framework for accessing and managing z/OS resources through Representational State Transfer (REST) APIs, CLIs, and web interfaces (mainframe access and integration).
  • Extensible desktop-style web UI for interacting with mainframe applications and tools in a browser (developer tooling).
  • Command-Line Interface (CLI) for scripting and automating common z/OS tasks from distributed environments (automation and DevOps).
  • Application Programming Interface (API) mediation layer for hosting, routing, and securing REST APIs to z/OS services (API gateway and integration).
  • SDKs and extensibility model for integrating mainframe capabilities into enterprise DevOps pipelines and tools (DevOps integration).

More About Zowe

Zowe is an open-source project under the Open Mainframe Project that provides a framework for accessing, managing, and integrating IBM z/OS systems through standardized interfaces that align with common distributed and cloud practices (mainframe access and integration). It targets enterprises that operate mainframes and need to expose mainframe capabilities to modern development, automation, and operations workflows while retaining existing z/OS assets and processes.

The project centers on three primary elements: a web-based interface often referred to as the Zowe Desktop (developer tooling), a CLI for interacting with z/OS resources from terminals and automation scripts (automation and DevOps), and an API mediation layer that provides a unified gateway for REST APIs to z/OS services (API gateway and integration). Together, these components give developers and administrators browser, CLI, and programmatic options for working with datasets, JES, USS, and other core z/OS functions where supported by installed back-end services.

The Zowe Desktop (developer tooling) runs as a browser-based user interface that organizes plug-in applications, sometimes called apps, in a desktop-style layout. It provides panels and tools that interact with z/OS services via underlying APIs, allowing users to browse and edit datasets, submit and monitor jobs, and access terminal sessions when the corresponding capabilities are deployed. The desktop framework is extensible, enabling vendors and in-house teams to add custom apps that surface specific mainframe tools or workflows through a consistent web experience.

The Zowe CLI (automation and DevOps) exposes z/OS functions through commands that can be run from Windows, macOS, and Linux environments. It supports profiles for connecting to one or more mainframe endpoints and includes command groups for common operations where back-end services are available, such as working with datasets, jobs, USS files, and other system resources. Because the CLI can be integrated into shell scripts, Continuous Integration and Continuous Deployment (CI/CD) pipelines, and automation platforms, it provides a way to incorporate mainframe steps into enterprise DevOps workflows using the same tooling used for distributed systems.

The API Mediation Layer (API gateway and integration) serves as an API gateway for z/OS services, providing Single Sign-On (SSO) integration, service discovery, routing, and a standardized catalog of REST APIs that client tools can consume. It allows multiple z/OS-based services to register and present their APIs through a common endpoint and user-facing catalog, simplifying how developers locate and invoke available services. This layer also supports extensibility by allowing new services to be onboarded and exposed alongside existing APIs.

Zowe provides software development kits (SDKs) for building extensions and integrating its capabilities into external tools and applications (DevOps integration). These SDKs align with the core components, enabling the creation of desktop apps, CLI plug-ins, and API clients that Test Access Points (TAP) into the underlying z/OS services and Zowe infrastructure. Vendors and enterprise teams can use these extension points to integrate proprietary tools, monitoring solutions, or service orchestration workflows with the mainframe environment.

Enterprises typically deploy Zowe on or alongside z/OS to provide standardized interfaces for development, operations, and integration teams. By exposing mainframe resources through web, CLI, and API channels aligned with widely used patterns, Zowe supports cross-platform workflows in hybrid environments where mainframe and distributed systems coexist. Within an enterprise technical taxonomy, Zowe can be classified under mainframe access and integration, API gateway and integration, developer tooling, and automation and DevOps.