Rules, not retyping · Validated migration
CCA RDRS Environment Migration Automation
Move your RDRS environment—without the manual rework.
CCA RDRS Environment Migration Automation generates the transformation rules Rocket’s BatchMigrate utility needs to move an RDRS repository between environments, so DEV, SIT and Production configurations stay in step without hand-editing every definition.
RDRS repositories hold hundreds of environment-specific values—agent addresses, output target connections, input table references, process definition parameters. Promoting a configuration from DEV to SIT, or SIT to UAT, or UAT to Production, means updating every one of those values to match the target environment. Done by hand, that is slow, repetitive and error-prone: one missed value surfaces later as a failed process or, worse, data routed to the wrong place.
CCA RDRS Environment Migration Automation turns that into a repeatable, validated process. It reads an RDRS repository backup, builds the regular expression patterns Rocket’s BatchMigrate applies to transform record definitions, and generates the post-migration SQL that updates the parameters BatchMigrate does not cover—so each environment move follows the same controlled path, every time.
Generate, transform and validate with less effort.
A Windows utility that removes the tedious parts of RDRS repository migration.
Automated rule generation
Builds the exact Regular Expression patterns Rocket’s BatchMigrate needs for input tables, output targets, process definitions, agents and data sources—no manual regex authoring.
Post-migration SQL
Generates SQL to update ProcessDefinitions parameter values (DBIDs, file numbers, input source names, TCP/IP details, output targets, state save settings) that BatchMigrate does not transform.
Backup-based validation
Parses an RDRS repository backup file to preview transformation results before anything touches the live repository—repeatable check-and-validate cycles.
Saved migration paths
Migration configurations persist per path—DEV to SIT, SIT to UAT, UAT to PROD—so common environment pairs are re-used, not re-entered.
A controlled path from source environment to target.
Move configuration between environments in four steps, with BatchMigrate doing the heavy lifting.
-
1 Source
Configure
Load the RDRS repository backup and define the source and target environment parameter values.
-
2 Split
Generate
Create the regex patterns and post-migration SQL that transform the selected objects.
-
3 Join
Migrate
Run the migration through Rocket’s BatchMigrate utility—using the generated pattern file, with a simulate/dry-run option before committing.
-
4 Verify
Validate
Check parameter values against the backup file, fix and re-validate, then promote with confidence.
Useful for the people who run RDRS.
Give every team a safer, faster route between RDRS environments.
RDRS administrators
Cut the time and risk of environment promotion—no more hand-editing hundreds of definition values.
Platform and migration teams
Run controlled, repeatable moves across the environment chain, with evidence that values are correct before cutover.
Project teams
Keep DEV, SIT and Production configurations consistent through a common, documented workflow.
Move between RDRS environments with a repeatable, validated process.
Talk to CCA about RDRS Environment Migration Automation and how it fits alongside CCA RDRS Script Monitor and the wider CCA RDRS utilities.