Version: v2.11.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
Task | Results | Time Estimate |
---|---|---|
Review the Zowe installation roadmap | Understand the basic installation stages | 25 minutes |
Plan the Installation | Plan the installation and address USS considerations for Zowe | 25 minutes |
Address System requirements | System 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.
Task | Results | Time 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 mainframe | 1 hour |
Configuring Zowe z/OS Components
Task | Results | Time 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
Task | Results | Time Estimate |
---|---|---|
Zowe is able to use PKCS12 certificates or certificates held in a z/OS Keyring. Read the article Zowe certificate configuration overview. Then use one of the following options: Option 1: Review Zowe certificates configuration questionnaire and certificate configuration scenarios to determine which scenario best applies to your use case. Once you have imported or generated a certificate, see Use certificates. Option 2: Set up Zowe certificates using workflows | Your certificates are configured and stored securely | 2 hours |
Starting and Stopping Zowe
Start/Stop Step | Task | Results | Time Estimate |
---|---|---|---|
Start and stop the cross memory server ZWESISTC on z/OS | The ZWESISTC task starts and stops the ZWESASTC task as needed | The cross memory server is run as a started task from the JCL in the PROCLIB member ZWESISTC | 5 minutes |
Start and stop the Zowe main server ZWESLSTC on z/OS | Option 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 manually | 20 minutes |
Verifying Zowe installation on z/OS
Verification Step | Task | Results | Time Estimate |
---|---|---|---|
Verify Zowe Application Framework installation | Open the Zowe Desktop from a supported browser | You should be able to open the Zowe Desktop from a supported browser. | 20 minutes |
Verify API Mediation installation | Use a REST API client to review the value of the status variable of the API Catalog service routed through the API Gateway | See the example presented in Verify API Mediation installation | 15 minutes |
Verify z/OS Services installation | Zowe z/OS services usually are registered with Zowe APIML Discovery | You should see JSON format data of all jobs running on the system | 15 minutes |