The following deployment commands were added in Dimensions CM 12.1:
PMI: promote item
PMRQ: promote request
PMBL: promote baseline
DMI: demote item
DMRQ: demote request
DMBL: demote baseline
SDPI: deploy item
SDPRQ: deploy request
SRRQ: deploy baseline
SRAV: rollback area version
For details see the Command-Line Reference.
When deployment areas are geographically remote from the main Dimensions server, you can associate a library cache area with a deployment area to improve deployment performance.
To associate a library cache area with a deployment area, use the CA (Create Area) or UA (Update Area) commands and supply the /LIBRARY_CACHE_AREA=<area_id> qualifier.
For example:
The following command creates a new UAT deployment area and associates it with the ST-LC-1 library cache area:
CA UAT1 /net=st3859 /dir=c:\deploy\uat1 /user=dmsys /pass=<password> /type=deployment /stage=uat /library_cache_area=st-lc-1
The following command associates an existing UAT deployment area with the ST-LC-2 library cache area:
UA UAT2 /library_cache_area=st-lc-2
When a build is performed in a deployment area, the search path sequence is:
The area where the build is being performed.
All areas specified in the build configuration that are at the same or a higher stage in the GSL as the area's stage, and which reside on the same area node.
If the area where a build is being performed is a work area, and the DM_SP_START_STAGE build template symbol has a value, the search path consists of the work area, followed by all stages at the same or higher stages as DM_SP_START_STAGE, and which reside on the same area node. In both cases, the search path is in increasing stage order, although the precise order may vary within the stage.
By default a work area is never locked and a deployment area is always locked. The BLD command qualifier [NO]LOCK_SEARCH_PATH enables you to control the locking of all areas in the search path in addition to the build area (for both deployment and work area builds).
Notes:
For information about the DM_SP_START_STAGE build template symbol see the Developer’s Reference.
For information about the BLD command and the [NO]LOCK_SEARCH_PATH qualifier see the Command Line Reference.
A check for whether two areas are on the same system is performed in terms of the area node, irrespective if this is a physical or a logical name. Therefore the logical name defines the system the build is being performed on.
Any deployment operation performed for a particular user session is single threaded. Two builds from two build commands issued one after the other will execute serially. Similarly, a deployment, followed by a build, followed by a deployment to the same area, followed by another build will execute serially.