...
See Repeatable DataStage Project Deployments for more details on how the -project-cache parameter is used to implement incremental imports.
Syntax
| Include Page | ||||
|---|---|---|---|---|
|
Examples
Import all jobs from a given directory
| Code Block | ||
|---|---|---|
| ||
$> mettleci isx import \ -domain test2-svcs.datamigrators.io:59445 \ -username myuser -password mypassword \ -server test2-engn.datamigrators.io \ -project myproject \ -location /tmp/isx_location Analyzing test2-engn.datamigrators.io/myproject Optimising assets for import Attempting to import with 1 working threads. Importing DataStage assets... * Import 'test2-engn.datamigrators.io/myproject/Jobs/Load/LD_SALE.pjb' - COMPLETED * Import 'test2-engn.datamigrators.io/myproject/Jobs/Load/LD_STOCK_HOLDING.pjb' - COMPLETED * Import 'test2-engn.datamigrators.io/myproject/Jobs/Load/LD_STOCKITEM.pjb' - COMPLETED * Import 'test2-engn.datamigrators.io/myproject/Jobs/Load/LD_SUPPLIER.pjb' - COMPLETED Import complete |
Incrementally import project binaries
...
only
This example incrementally imports project binaries, ignoring Job design information. Any Jobs in the project which do not exist in the source directory are deleted from the project. C:/shared/myproject/export is a directory containing ISX files (with binaries) to be imported and C:/shared/myproject/cache contains state files related to incremental operations performed against myproject:
...