IBM DataPower Operations Dashboard v1.0.6.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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 five tasks:
    a. sync for source device/domain=PROD1/Domain1 and target device/domain DR1/Domain1
    b. sync for source device/domain=PROD1/Domain2 and target device/domain DR1/Domain2
    c. sync for source device/domain=PROD1/Domain3 and target device/domain DR1/Domain3
    d. sync for source device/domain=PROD1/Flight1 and target device/domain PROD2/Flight1
    e. sync for source device/domain=PROD1/Flight2 and 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 backup task:

Sync tasks will start to execute in the order they were created, which corresponds to the order which the activities were defined.
Two different tasks will not execute concurrent syncs on the same device, unless the option "Allow multiple sync tasks to run in parallel" was checked in the plan definition
  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 - make sure it exists
  4. If a deployment policy variables object was specified in the sync activity definition - make sure it exists
  5. Check that the source and target device type match (IDG > XB-62 > XI-52 > XG-45) - you can turn off this check 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 off this check 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 off this check in the sync activity definition
  • No labels