Environment-Aware Synchronization for TDI Packages in Orchestration

Changes in TDP 26.2

Previously, syncing a TimeXtender Data Integration (TDI) Data Provider created one package per environment per unique TDI package. A workspace with 18 unique TDI packages across three environments (Development, Testing, Production) would result in 54 package entries in Orchestration & Data Quality (ODQ). This caused confusion and added maintenance overhead.

With this release, sync deduplicates packages by their unique package GUID. The same TDI package, regardless of how many environments it appears in, is now represented by a single entry in ODQ. The correct environment (and its associated TDI instance) is resolved at execution time.

Before: 18 packages × 3 environments = 54 ODQ package entries
After: 18 packages × 1 = 18 ODQ package entries

TDI Data Provider — TDP Only

The TDI Data Provider configuration dialog is only available in the TimeXtender Data Platform (TDP) web interface.

If you open a TDI Data Provider in the desktop application, you will see an "Open in TDP" button instead of the configuration fields. Click it to be redirected to TDP where you can complete the configuration.

Configuring Instance-to-Environment Mapping

Instance mapping tells ODQ which TDI instance to use when executing a package in each environment. You configure this once per Data Provider.

Steps

1. Open TDP and navigate to the Data Providers section of your workspace.

2. Open the TDI Data Provider you want to configure.

3. Click Fetch Instances.

   • ODQ queries the TDI Gateway and retrieves all available instances across your Ingest, Prepare, and Deliver packages.

   • The instance list is persisted — it will be pre-populated next time you open this Data Provider.

4. For each unique TDI package, assign one instance to each environment column (Development, Testing, Production):

   • Use the dropdowns in the Development, Testing, and Production columns to select the appropriate instance.

   • Different packages can be mapped to different instances in the same environment.

5. Click Save.

Note: You do not need to re-sync after changing instance mappings. The mapping is read at execution time.

How Sync Deduplication Works

When you run a sync on a TDI Data Provider, ODQ:

1. Fetches all Ingest, Prepare, and Deliver packages from the configured TDI instances.

2. Groups the results by Package GUID. Packages that exist in multiple environments share the same GUID.

3. Creates or updates one ODQ package per unique Package GUID. If a package exists in multiple environments, the Development instance is used as the primary reference (lowest environment sort order), but all instances are tracked internally.

4. Creates a single Object Group for each set of packages that share the same instance grouping.

5. Creates a single Process Map for the Data Provider.

The result is a flat, deduplicated package list instead of environment-specific folders with duplicated entries.

Execution-Time Environment Resolution

When ODQ executes a TDI package, it resolves the correct TDI instance at runtime:

1. ODQ reads the current execution environment (Development, Testing, or Production) from the run configuration.

2. It looks up the instance mapping saved for that package + environment combination in the Data Provider settings.

3. It sends the execution request to the resolved instance via Service Bus.

Fallback behavior: If no instance mapping is configured for the current environment, ODQ falls back to the instance originally stored in the package row. This means existing packages continue to execute correctly after upgrade — before the user has configured any instance mappings or re-synced.

Migration Guide — Existing Workspaces

If your workspace was created before this release, you will have per-environment packages (e.g., separate Dev, Test, and Prod entries for the same TDI package).

Recommended Steps

1. No immediate action required. Existing packages will continue to execute as before. The fallback mechanism ensures backward compatibility.

2. Configure instance mappings in the TDI Data Provider (see Configuring Instance-to-Environment Mappingabove).

3. Re-sync the Data Provider. After sync, ODQ will create a single deduplicated package per unique TDI package. The old per-environment packages will be superseded.

4. Clean up duplicate packages (optional but recommended). A SQL script is available to delete the legacy per-environment duplicate packages from your workspace.

   • The script will remove packages not mapped to a retained environment.

   • This script is provided by TimeXtender Support and must be run manually. It is not applied automatically during upgrade.

   • Contact support or your TimeXtender representative to obtain the script and confirm which environment's packages to retain before running it.

Warning: Do not run the cleanup script without first confirming that your instance mappings are correctly configured and that a re-sync has completed successfully. Packages referenced in schedules should be verified after cleanup.

Summary of Key Behaviors