There are multiple ways of dealing with multiple environments.
Our corporate clients use multiple servers and multiple repositories
DEV dev-sever connected to dev-repository loading data into dev-database
UAT uat-server connected to uat-repository loading data into uat-database
PROD prod-sever connected to prod-repository loading data into prod-database
They do all development in DEV env then they copy transformations/ packages from to UAT and from UAT to PROD
Or you can use global variables and package variables to load data into different environments
The global variables point to dev env
for example, you have 3 SQL servers
SQL-DEV
SQL-UAT
SQL-PROD
Create a global variable called SERVER_NAME and set it to SQL-DEV
create 4 packages
1 LOAD DATA
2 LOAD DATA into SQL-DEV
3 LOAD DATA into SQL-UAT
4 LOAD DATA into SQL-PROD
The first step of package 2 set the SERVER_NAME variable to SQL-DEV
The first step of package 3 set the SERVER_NAME variable to SQL-UAT
The first step of package 4 set the SERVER_NAME variable to SQL-PROD
The second step of all packages calls package LOAD DATA
This gives you a flexible way of loading data into multiple env.
Please read the following wiki articles
Global variables
/wiki/advanced-etl-processor/getting-started/options/
Package variables
www.etl-tools.com/wiki/advanced-etl-proc.../packages/variables/
Set variable action
/wiki/advanced-etl-processor/packages/actions/set-variable-action/