Introduction

In Dimensions CM 12.x and later you can perform deployment operations asynchronously in the background. The asynchronous processing is executed by a Dimensions CM server component called the deployment server (dmdeploysrv.exe). The following diagram shows the deployment server in the business logic tier in the Dimensions CM architecture:

biz_logic_tier.png

The deployment server is started by the pool manager. The deployment server then reads the configuration file (DM_ROOT/dfs/deploy_config.dat) and begins to monitor the deployment job queues for any new deployment jobs that need to be executed in each base database.

As users execute deployment related commands such as promote, demote, build, and audit, these commands submit new deployment jobs into the deployment job queue of the base database. A deployment job includes information about:

As new deployment jobs are added to the deployment job queue, the deployment manager automatically reads the details of the new jobs and executes them.

The deployment server uses the following rules to execute deployment jobs, which ensures that jobs are processed efficiently:

The deployment server does not access the deployment areas. Instead, it uses application servers to perform any relevant database meta data queries, obtain connections to library servers on deployment area nodes, and carry out the deployment operations in each area.