Mapping Rules

Endevor Stages are mapped to streams in AccuRev.

By default, when synchronizing files from Endevor to AccuRev, the Endevor logical element structure in stages using system, subsystem and type are converted into directories within streams.

System FINANCE
Subsystem ACCTPAY
Type COBOL
File FINAPP01

This is translated to the following path structure: FINANCE\ACCTPAY\COBOL\FINAPP01.cbl.

There are, however, cases when you would want to overwrite this default behavior:

The AccuRev stream structure has been designed using different streams for each Endevor system. Therefore there is no need to have the system name in the path structure.

The Endevor system or subsystem name changes when moving files in Endevor to the next stage.

Environment	SMPLPROD	SMPLTEST	SMPLTEST	SMPLTEST	SMPLTEST
Stage	PROD	QA	QA	TEST	TEST
System	FINANCE	FINANCEA	FINANCEB	FINANCEA	FINANCEB
Subsystem	ACCTPAY	ACCTPAY	ACCTPAY	ACCTPAY	ACCTPAY
Type	COBOL	COBOL	COBOL	COBOL	COBOL
File	FINAPP01	FINAPP01	FINAPP01	FINAPP01	FINAPP01

The sample above shows a typical Endevor scenario which can be used to support parallel development in one Endevor environment by using a specific suffix in the system's name. When moving files to the next environment the suffix is omitted.

For synchronizing files from Endevor to AccuRev you would normally require for the three stages used in the sample above three corresponding AccuRev streams. But because Endevor system names were used to support parallel release development it is required to create parallel streams in AccuRev. Even more AccuRev requires a consistent directory structure in a stream hierarchy. This means the directory structure cannot change when promoting files to the next stream. Therefore a stream structure like the one shown below is required. The directory structure cannot be calculated by the default rules, but should look like this one in all streams: ACCTPAY\COBOL\FINAPP01.cbl

Enterprise Sync supports any kind of mappings from one or more combinations of Endevor environment, stage, system and subsystem to a corresponding stream and any kind of mappings from a combination of environment, system and subsystem to a configured directory path.

Using the example above you would create a property file with the following content:

SMPLPROD.FINANCE.ACCTPAY=acctpay
SMPLPROD.FINANCEA.ACCTPAY=acctpay
SMPLPROD.FINANCEB.ACCTPAY=acctpay

See Creating a Data Source for details how to configure this in Enterprise Sync.

Note: This path mapping does neither depend on the Endevor type nor on the stage. The Endevor type must be part of the AccuRev directory structure and is therefore not required in the properties file. The Endevor stage is not relevant, because a synchronization from AccuRev to Endevor only updates the Endevor entry stage in an environment and therefore it is not required for Enterprise Sync to know in which Endevor stage within an environment the systems and subsystems are valid names.