This chapter explains the main features available in Enterprise Developer when the
AccuRev repository is synchronized with
Endevor.
Enterprise Developer combined with direct access to the
AccuRev repository provides the developer with powerful access to all sources of interest, as well as auditing and history information
about source changes. Furthermore, comparing and merging any source changes done during the development process is fully supported.
These capabilities are fully available for a cross-platform development environment where
- The developer wants to make source changes and debug/test source changes locally.
- The developer wants to promote the source changes into a team test environment on the mainframe in
Endevor.
- The next promote steps are done in
Endevor up to the production stage.
- The developer needs the ability to support emergency changes from the IDE directly on the mainframe.
The following sections describe main functions available in the standard AWM model for
Enterprise Sync. Although you may jump directly to a function of interest, the order of the next chapters is oriented towards the development
process:
- Creating an
AccuRev workspace on your local machine.
- Linking files and folders to COBOL or PL/I projects.
- Locking files in
Endevor (sign-out).
- Editing files which are linked to
AccuRev.
- Building, debugging and testing the application in a distributed environment (see
Getting started with Micro Focus Enterprise Developer for Eclipse).
- Promoting files in
AccuRev with synchronization to
Endevor.
- Testing the application on the mainframe (the supported integration with standard mainframe debuggers like the IBM Debug
Tool for z/OS or Compuware Xpediter are not part of this guide).
- Moving files in
Endevor up to the production stage while synchronizing the changes with
AccuRev.
- Changing files in
Endevor (for example an emergency change) and synchronizing this change to
AccuRev.
- Analyzing and Resolving conflicts in
AccuRev (for example: emergency change done in parallel to the next release change).
- Resolving conflicts when working on parallel releases.