deployDeploymentGroup
Deploys an Informatica deployment group from a source to target server. The name of the deployment group to be migrated is taken from the build artifact created in the build operation.
Current plugin features are based on migration from one environment to other, which is different than FlexDeploy traditional build - save artifacts - deploy to more than one environment approach. Keep this mind when you plan to use FlexDeploy Informatica plugin.
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 deployment groups 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.
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
INFA_HOME | FDI_INFA_HOME | Yes | 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) |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
Input Name | Input code | Required | Description |
|---|---|---|---|
| Delete Deployment Group |
| No | Delete Deployment Group on target before the deployment. (Boolean) |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation consumes artifacts from the artifacts repository. The artifact contains the name of the deploymentgroup that will be migrated.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
Special Considerations
Make sure to setup your domain properly on all the endpoint servers. See https://kb.informatica.com/solution/11/Pages/101878.aspx for information on how to do that.
Reference to Deployment Group Control File can be found inhttps://docs.informatica.com/data-integration/powercenter/10-1/command-reference/working-with-pmrep-files/using-the-deployment-control-file.html
- style