Skip to main content
Version: v2.8.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.

Preparing and Installing

Preparation/Installation StepTaskResultsTime Estimate
Plan the Installation
and address system requirements
1. Plan the Installation
2. Address USS considerations for Zowe
3. Address System requirements:
    * z/OS
    * Node.js
    * Java
    * z/OSMF
      (recommended for full functionality)
    * z/OSMF HA
      (required for production)
All prerequisites satisfied to install Zowe z/OS components1 day
Install z/OS ComponentsUse one of the following installation options:
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

Configuration StepTaskResultsTime Estimate
Configure base1. Initialize Zowe
    Use one of the following options:
    Option 1: Initialize Zowe manually
    using zwe command group
      a. Prepare zowe.yaml configuration file
          if the file does not already exist
      b. Initialize Zowe custom data sets
         (zwe init mvs)
      c. APF authorize load libraries
         (zwe init apfauth)
      d. Initialize Zowe security configurations
         (zwe init security)
      e. Install Zowe main started tasks
         (zwe init stc)
    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
Configure the Caching Service storageUse one of the following storage methods:
* Use inMemory
(This method is designed only to perform a quick start of a service for test purposes. This method is the simplest to implement and recommended for testing.)
* Use Infinispan
* Use VSAM
(Infinispan and VSAM are the recommended storage methods for production and required to use Zowe in High Availability mode.)
Storage for the Caching service is configured1 hour
Configure certificatesZowe 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
(This method allows you to create a self-signed PKCS12 certificate, and is the simplest configuration for mvp)
   or
* 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

Verify 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