Using the control file and environment instance properties, you can set up the plugin to perform the task in a number of different ways. For example, if you have 3 environments, you can choose to migrate using static-version deploymentgroups from dev to test, and dev to prod, or from dev to test, migrating the deployment group as well, and then from test to prod. The latter ensures that the migrated data has been tested before going to production, so it is the recommended approach.
If you select option to move from Dev to Test and Dev to Prod then Source details will be for Dev on all Environment / Instances.
|Absolute path to INFA Home. For example, /opt/informatica. FlexDeploy will look for server/bin folder under this location.|
|Source repository domain||FDI_SOURCE_DOMAIN_NAME||Yes||The domain of the source repository (-d parameter)|
|Source User Security Domain||FDI_SOURCE_USER_SECURITY_DOMAIN||No||The domain that the source repository user is authorized in (-s parameter)|
|Source User||FDI_SOURCE_USER_NAME||Yes||The user name to connect to the source repository with (-n parameter)|
|Password for Source User||FDI_SOURCE_PASSWORD||Yes||The password to connect to the source repository with (-x parameter)|
|Source Repository||FDI_SOURCE_REPOSITORY_NAME||Yes||The name of the source repository (-r parameter)|
|Target User||FDI_TARGET_USER_NAME||Yes||The user name to connect to the target repository with (-n parameter)|
|Password for Target User||FDI_TARGET_PASSWORD||Yes||The password to connect to the Target repository with (-x parameter)|
|Target Domain||FDI_TARGET_DOMAIN_NAME||Yes||The domain name of the target repository (-d parameter)|
|Target Repository||FDI_TARGET_REPOSITORY_NAME||Yes||The name of the target repository (-r parameter)|
|Target User Security Domain||FDI_TARGET_USER_SECURITY_DOMAIN||No||The domain that the target repository user is authorized in (-s parameter)|
|Deploy DeploymentGroup Control File Path||FDI_DEPLOY_CONTROL_FILE_PATH||Yes||Absolute path to the control file (xml file) that will be used to pass options to the deployDeploymentGroup Command (-c parameter)|