Skip to main content
Version: v2.9.x LTS

Installation Checklist for Zowe z/OS Components for Testing and Minimum Viable Product (MVP)

Installation Checklist for Zowe z/OS Components for Testing and Minimum Viable Product (MVP)

Follow the steps in this checklist to guide you through the installation of Zowe z/OS Components for testing purposes or for the minimum viable product. Use this installation procedure to get familiar with Zowe installation time, performance and system requirements, or to develop a plug-in for a Zowe component. This procedure does not require configuration of high availability.

Planning and preparing for the installation

TaskResultsTime Estimate
Review the Zowe installation roadmapUnderstand the basic installation stages25 minutes
Plan the InstallationPlan the installation and address USS considerations for Zowe25 minutes
Address System requirementsSystem requirements are addressed:
    * z/OS
    * Node.js
    * Java
    * z/OSMF
      (recommended for full functionality)
    * z/OSMF HA
      (required for production)
1 day

Installing the Zowe z/OS runtime

Use one of the following installation options to install Zowe z/OS components.

TaskResultsTime Estimate
Option 1: Install Zowe runtime from a convenience build
Option 2: Install Zowe with SMP/E
Option 3: Install Zowe with a portable software instance
Executables and binaries are unpaxed on mainframe1 hour

Configuring Zowe z/OS Components

TaskResultsTime Estimate
1. Use one of the following options to initialize Zowe z/OS runtime.
Option 1: Initialize Zowe manually using zwe init command group
Option 2: Configure Zowe with z/OSMF workflows

2. Configure the z/OS system for Zowe
3. Grant users permission to access z/OSMF
4. Install and configure the Zowe cross memory server (ZWESISTC)
* All datasets are created and populated. See Initialize MVS Datasets Results
* Started tasks are copied to system libraries
* APF authorization is granted to load libraries
* Zowe user is created and is asigned all required permissions
* Your z/OS and security product are configured
4 hours

Configuring certificates

TaskResultsTime Estimate
Zowe is able to use PKCS12 certificates or certificates held in a z/OS Keyring.

Use one of the following options:
Option 1: Use zwe command group
* Configure PKCS12 certificates
* Configure JCERACFKS certificates in a key ring
Option 2: Set up Zowe certificates using workflows
Your certificates are configured and stored securely2 hours

Starting and Stopping Zowe

Start/Stop StepTaskResultsTime Estimate
Start and stop the cross memory server ZWESISTC on z/OSThe ZWESISTC task starts and stops the ZWESASTC task as neededThe cross memory server is run as a started task from the JCL in the PROCLIB member ZWESISTC5 minutes
Start and stop the Zowe main server ZWESLSTC on z/OSOption 1: Use zwe to start and stop the main Zowe server

Option 2: Manually start and stop the Zowe main server ZWESLSTC
You started or stopped Zowe main server ZWESLSTC on z/OS with zwe or manually20 minutes

Verifying Zowe installation on z/OS

Verification StepTaskResultsTime Estimate
Verify Zowe Application Framework installationOpen the Zowe Desktop from a supported browserYou should be able to open the Zowe Desktop from a supported browser.20 minutes
Verify API Mediation installationUse a REST API client to review the value of the status variable of the API Catalog service routed through the API GatewaySee the example presented in Verify API Mediation installation15 minutes
Verify z/OS Services installationZowe z/OS services usually are registered with Zowe APIML DiscoveryYou should see JSON format data of all jobs running on the system15 minutes