Automatic Token Node Identification for Purge Execution

Problem Statement

In clustered Sterling Integrator environments, purge activities often require identification of the active token node responsible for executing cleanup operations.

Currently, administrators may need to manually determine:

• Which node currently owns the token
• Which node should execute the purge
• Whether the token has shifted after failover or restart

This manual verification process increases operational effort and can delay housekeeping activities.

Proposed Enhancement

Introduce a built-in capability in Sterling Integrator to automatically identify the active token node responsible for purge execution.

The enhancement should:

• Detect the current token-owning node automatically
• Route or trigger purge execution on the correct node
• Eliminate manual token node verification
• Support clustered and HA environments
• Handle token movement during failover scenarios

Suggested Features

• Automatic token node discovery
• Purge execution validation against active token node
• Dashboard/API visibility showing current token owner
• Audit logging for token ownership changes
• Automatic reassignment handling after node restart/failover
• Scheduler integration for purge jobs

Benefits

• Reduced manual operational effort
• Simplified purge management
• Improved housekeeping reliability
• Faster operational recovery during failovers
• Reduced risk of purge execution failures

Business Value

This enhancement would improve operational efficiency and simplify maintenance activities for enterprise Sterling Integrator clustered deployments by automating token node identification required for purge execution.