Technical overview
You can use each component of IBM Wazi Developer standalone or integrate them to form a pipeline. The following diagram illustrates the overall architectural view of IBM Wazi Developer.
- Wazi Sandbox
- Runs on Red Hat OpenShift. After setting up the subcomponents of Wazi Sandbox, you can provision a personal z/OS system on Red Hat OpenShift. When your personal z/OS system is up, you can connect to the system from the IDE. See more.
- Wazi Code
- You can choose one of the following IDEs, and connect to a z/OS system to access z/OS resources
for development. See more.
- IBM Wazi Developer for Workspaces: Runs on Red Hat OpenShift. It provides an in-browser IDE built on the Red Hat CodeReady Workspaces project, allowing you to code, build, test, and run applications as they run in production from any machine.
- IBM Wazi Developer for VS Code: Runs on desktop. It provides a set of Microsoft VS Code extensions to extend VS Code to deliver a simple and familiar edit, build, and debug experience.
- IBM Wazi Developer for Eclipse: Runs on desktop. It is an Eclipse-based IDE, and offers development teams that have chosen Eclipse as their preferred IDE a familiar edit, build, and debug experience that works with the on-premises Eclipse framework.
- Wazi Analyze
- Wazi Analyze is pre-installed in the Docker container. You can install Docker and load the Wazi Analyze Docker container on your desktop. When you want to make changes to your source code, Wazi Analyze helps you quickly discover the relationship between files or relationship between programs of the COBOL application. See more.
- Pipeline
- Runs on Red Hat OpenShift. After you validate the modified code and debug it in the IDE, the CI/CD pipeline takes the committed code. Then, the CI/CD pipeline automatically builds, tests, qualifies and deploys the code to the target z/OS system. See more.
Next step
Learn the end-to-end workflow.