To install Zowe™ on z/OS, there are two parts. The first part is the Zowe runtime that consists of three components: Zowe Application Framework, z/OS Explorer Services, and Zowe API Mediation Layer. The second part is the Zowe Cross Memory Server. This is an authorized server application that provides privileged services to Zowe in a secure manner.
Review the installation diagram and the introduction in this topic to see the general installation sequence and the most important tasks that are to be performed during installation and configuration. You can click each step on the diagram for detailed instructions.
Before you start the installation, review the information on hardware and software requirements and other considerations. See Planning the installation for details.
Ensure that the software requirements are met. The prerequisites are described in System requirements.
Choose the method of installing Zowe on z/OS.
The Zowe z/OS binaries are distributed in the following formats. They contain the same contents but you install them by using different methods. You can choose which method to use depending on your needs.
The Zowe z/OS binaries are packaged as a PAX file. You install this build by running shell script within a UNIX System Services (USS) shell. Convenience builds are full product installs.
The Zowe z/OS binaries are packaged as the following files that you can download. You install this build through SMP/E.
- A pax.Z file, which contains an archive (compressed copy) of the FMIDs to be installed.
- A readme file, which contains a sample job to decompress the pax.Z file, transform it into a format that SMP/E can process, and invoke SMP/E to extract and expand the compressed SMP/E input data sets.
While the procedure to obtain and install the convenience build or SMP/E build are different, the procedure to configure a Zowe runtime are the same irrespective of how the build is obtained and installed.
Obtain and install the Zowe build.
After successful installation of either a convenience build or an SMP/E build, there will be a zFS folder that contains the unconfigured Zowe runtime
<RUNTIME_DIR>, a SAMPLIB library
SZWESAMP that contains sample members, and a load library
SZWEAUTH that contains load modules. The steps to prepare the z/OS environment to launch Zowe are the same irrespective of the installation method.
You can configure the Zowe runtime with one of the following methods depending on your needs.
- Use JCL and shell scripts
- Use z/OSMF Workflows
A SAMPLIB JCL member
ZWESECURis provided to assist with the configuration. You can submit the
ZWESECURJCL member as-is or customize it depending on site preferences.
If Zowe has already been launched on the z/OS system from a previous release of Version 1.8 or later, then you are applying a newer Zowe build. You can skip this security configuration step unless told otherwise in the release documentation.
If you have already created a keystore directory from a previous release of Version 1.8 or later, then you may reuse the existing keystore directory.
The Zowe keystore directory contains the key used by the Zowe desktop and the Zowe API mediation layer to secure its TLS communication with clients (such as web browsers or REST AI clients). The keystore directory also has a truststore where public keys of any servers that Zowe communicates to (such as z/OSMF) are held.
A keystore directory needs to be created for a Zowe instance to be launched successfully, and a keystore directory can be shared between Zowe instances and between Zowe runtimes, including between different Zowe releases, unless specified otherwise in the release documentation.
(Only required for launching the Zowe desktop) Configure and start the
ZWESISTCcross memory server and install the load libraries. For instructions, see Installing and configuring the Zowe cross memory server (ZWESISTC).
The cross memory server is only required if you want to use the Zowe desktop. The cross memory server is not used by API Mediation Layer. If you want to use Zowe API Mediation Layer only, you can skip this step.
Which components of Zowe are started is determined by the
LAUNCH_COMPONENT_GROUPSvalue in the
instance.envfile in the Zowe instance directory, see Creating and configuring the Zowe instance directory.
Create and customize an instance directory that contains configuration data required to launch a Zowe runtime and is where log files are stored. For instructions, see Creating and configuring the Zowe instance directory and Configuring Zowe with z/OSMF workflows.
A single Zowe runtime can be launched multiple times from different instance directories, each specifying different port ranges, applications to include at start-up, paths of associated runtimes (Java, Node, z/OSMF).
Next, you will install and configure the Zowe started tasks. Zowe has two high-level started tasks:
ZWESVSTCthat launches the Zowe desktop and API mediation layer address spaces, and
ZWESISTCthat is a cross memory server that runs all of the APF-authorized code. The JCLs for the tasks are included in the PDS SAMPLIB
SZWESAMPinstalled by Zowe and the load modules for the cross memory server are included in the PDS load library
See Zowe runtime configuration parameters for more information about the Gateway parameters that can be set during the Zowe runtime configuration.
Configure and start the
ZWESVSTCstarted task. For instructions, see Installing the Zowe started task (ZWESVSTC).
Verify that Zowe is installed correctly on z/OS. See Verifying Zowe installation on z/OS.
If you encounter unexpected behavior when installing or verifying the Zowe runtime on z/OS, see the Troubleshooting section for tips.