Integrating Engineering Workflow Management and Developer for z/OS

Developer for z/OS integrates with Engineering Workflow Management to provide developers an integrated collaborative z/OS application development environment. This integrated solution provides the value of the individual development environment of Developer for z/OS with the team collaboration capabilities of Engineering Workflow Management.

IBM® Engineering Workflow Management is a team collaboration tool that supports cross-platform development and features native hosting of the Jazz® Team Server on z/OS and Linux® for z Systems®. It includes an integrated set of collaborative software delivery lifecycle tools for z/OS development, including source control, change management, and build and process management. Using Developer for z/OS and Engineering Workflow Management together, software development teams can develop artifacts remotely in a user-specific sandbox using the z/OS integrated development environment (zIDE) provided by Developer for z/OS, and the planning, team collaboration, build, source control management, and defect tracking tools provided by Engineering Workflow Management.

The products have two primary integration points:
The following terms are used in the help content for the integrated products:
A logical group of artifacts that share a common context; for example, all of the artifacts in a component might comprise part of an application.
Data set definition
A Jazz model object that is stored in the Jazz repository. It contains all of the information related to a given data set on a z/OS system. Every data set that a build process references must correspond to a data set definition.
Data set prefix
On z/OS, IBM Engineering Workflow Management uses a data set prefix together with the data set name (indicated in the data set definition) to identify the data set you want to allocate to Engineering Workflow Management. With your own prefix, you can modify IBM Engineering Workflow Management artifacts in isolation from other contexts.
Repository workspace
A (source control) workspace that holds a developer's private copy of the source file base.
An unstructured location on the file system to which you can extract a source file base from a source control system.
Describes a single build step; namely, the step wherein a translator executable program is started with the required inputs and outputs. Inputs and outputs are the same as z/OS data sets, so a translator definition must reference multiple data set definitions. For example, a COBOL program that contains SQL statements and runs in a CICS® environment must go through several build steps. Depending on the COBOL compiler version you use, these steps might include the following:
  • Db2® precompile
  • CICS precompile
  • COBOL compile
  • Link-edit
  • Db2 bind
A location on a file system with an Eclipse-oriented structure that contains a collection of resources (files, folders, projects).
zComponent Project
A specialized Eclipse project that contains source or build artifacts (such as build scripts or link-edit files), along with metadata that describes how these artifacts should be organized and built when you extract them to the z/OS file system.
An Eclipse file that represents a member of an extended partitioned data set (PDSE) on MVS.
An Eclipse folder that is associated with a PDSE on MVS. During a build, zFiles in a given zFolder are extracted to the data set that is associated with that zFolder.

To learn more about IBM Engineering Workflow Management, see the Getting Started, Tutorial, and Glossary sections in the IBM Engineering Workflow Management product documentation in IBM Documentation.