This page describes how DPOD prepares the execution flow of a sync plan (using tasks) and subsequently - how the tasks themselves are executed

Task Creation Flow

General execution flow for a sync plan:

1. Verify that the system allows Syncs to run. (See Configurable Parameters and Settings to learn how to enable or disable all sync activities)
2. Verify that the current system time is within the maintenance window timeframe defined for the plan
3. Iterate over all the activities defined for the plan, and split them into executable tasks.
   For example: consider a plan with two activities, one to sync device PROD1 to DR1 and a second to sync domain pattern with source device = PROD1, source domain = Flight* and target device = PROD2
   DPOD will create eight tasks:
   a. Export task for source device/domain PROD1/Domain1 
   b. Import task for target device/domain DR1/Domain1
   c. Import task for target device/domain DR1/Domain2
   d. Import task for target device/domain DR1/Domain3
   e. Export task for source device/domain PROD1/Flight1 
   f. Import task for target device/domain PROD2/Flight1
   g. Export task for source device/domain PROD1/Flight2 
   h. Import task for target device/domain PROD2/Flight2
4. If all the created tasks are in "Skipped" state (because the devices are not available, or because no devices or domains matched the input patterns) - the plan will stop
5. If there are any tasks waiting to be executed - the Pre-Plan Script will be executed (if requested in the plan settings). The plan will stop if the script's return code is larger than 0.
   
   

Task Execution Flow

After the sync tasks are created, they will start to execute. The following is the general execution flow for a sync task:

1. Verify that the current system time is within the maintenance window timeframe defined for the plan.
2. Verify that both source and target devices' firmware levels are above 7.1.0.0
3. If a deployment policy was specified in the sync activity definition - ensure it exists
4. If a deployment policy variables object was specified in the sync activity definition - ensure it exists
5. Check that the source and target device type match (IDG > XB-62 > XI-52 > XG-45) - you can turn this check off in the sync activity definition
6. Check that the source device major firmware level is lower or equal to the target device major firmware level - you can turn this check off in the sync activity definition
7. Check that the target device contains the same licenses/features of the source device (e.g. B2B, SQL-ODBC, Tibco-ESM) - you can turn this check off in the sync activity definition
8. If both source and target devices have firmware level above 7.5.2.4, DPOD will try to check if the passphrase in both source and target match, and will stop the sync process if they do not.
   If one of the source or target devices' firmware is below level 7.5.2.4, DPOD will not sync any password map/alias objects
9. Export the source domain's configuration
10. If pre-quiesce was requested - check that the domain is not already quiesced
11. Run the user's pre-script (if requested in the activity), the task will stop if the script return value is larger than 0
12. Issue a Quiesce domain/device SOMA (if requested in the activity) 
13. Wait for the device or domain to finish quiescing. A timeout value may be specified for the Quiesce SOMA (see Configurable Parameters and Settings), 
    DPOD will cancel the task if the domain(s) are not yet quiesced 3 minutes after the specified timeout, and will issue an Unquiesce SOMA
14. Perform an Import Dry-run to try and detect any errors before the actual Import
15. Delete objects on the target domain (DPOD does not use "reset domain" in order to retain the passwords on the target domains) - 
    The following object types will be deleted:
    1. WSGateway
    2. MultiProtocolGateway
    3. XMLFirewallService
    4. SSLProxyService
    5. HTTPService
    6. B2BGateway
    7. TCPProxyService
    8. WebTokenService
    9. WebAppFW
    10. XSLProxyService
    11. CloudGatewayService 
    12. SQLDataSource
    13. MQQMGroup
    14. MQQM 
    15. ISAMReverseProxy
    16. TibcoEMSServer
    17. LoadBalancerGroup
    18. WebSphereJMSServer
        
        

16. Import the configuration into the target domain

17. Save config on the target domain
18. Unquiesce the device/domain (if it was previously quiesced by this task) 
19. Wait for the device/domain to unquiesce. A timeout value may be specified for this operation. 3 minutes after the timeout, DPOD will stop waiting for the unquiesce operation and will fail the task (the device's unquiesce operation will not be interrupted though)
20. Run the user's post-task script (if requested in the activity) 

When all the plan's tasks completed execution, the post-plan script will be executed (if requested in the plan settings).

Sync Execution Results

The Plan Details page shows the 40 most recent plan execution results

The following table outlines the details for each column in the plan execution table

*Click the red "Abort Pending Executions" to stop execution in status "WAITING_FOR_PRE_VALIDATION" that did not started yet.
**Click the status column to drill into the plan execution details page.

Click the status column to drill into the activity execution details page

Click the status column to drill into the task execution results page, this page will display the Import SOMA result for the task (if an Import was actually performed)