Propagating assets

DataStage supports import and export of assets as .zip files through cpdctl. You can use the dsjob command-line interface to migrate assets from a designated development project to a project designated for testing to a project designated for production. For more information about import and export commands, see Command-line tools.

If you are importing assets from InfoSphere DataStage, import an ISX file into a development project and make any necessary changes before further propagation. For more information, see Migrating DataStage jobs. Propagating directly from traditional DataStage to a production project in modern DataStage is not recommended.

As you develop your DataStage flows, you can incrementally propagate changes using dsjob commands. For more information, see Command-line tools.

Change considerations

The following considerations apply when moving assets between development, testing, and production environments.

Connections

When a connection is migrated between environments, adjust the connection credentials to match the database used in the new environment.

Parameter set

When a parameter set is migrated between environments, update parameters to match the new environment's configuration.

Runtime environment

You may need to manually redefine environment variables after migration.

Config files

Changes to a configuration file must be manually propagated. Copy changes over or replace the old file.

Deployment

You can propagate changes from project to project, but this means that users will be able to modify assets in each environment. If you want to limit permissions more, you can propagate from a project to a Space, where users can only update connections, update parameter sets, and run jobs. For more information, see Deployment spaces in DataStage.