The import script is a command line utility that pulls content into an enterprise or database repository from two kinds of files: Individual KJB or KTR files, or complete repository export XML files.
You must also declare a rules file that defines certain parameters for the data integration content you're importing. We provide a sample file called import-rules.xml, included with the standard Data Integration client tool distribution. It contains all of the potential rules with comments that describe what each rule does. You can either modify this file, or copy its contents to another file; regardless, you must declare the rules file as a command line parameter.
The table below defines command line options for the import script. Options are declared with a dash, followed by the option, then the (equals) sign and the value.
sh import.sh -rep=PRODUCTION -user=admin -pass=12345 -dir=/ -file=import-rules.xml -rules=import-rules.xml -replace -comment="New version upload from UAT"
|Parameter||Definition or Value|
|rep||The name of the enterprise or database repository to import into.|
|user||The repository username you will use for authentication.|
|pass||The password for the username you specified with user.|
|dir||The directory in the repository that you want to copy the content to.|
|limitdir||Optional. A list of comma-separated source directories to include (excluding those directories not explicitly declared).|
|file||The path to the repository export file that you will import from.|
|rules||The path to the rules file, as explained above.|
|comment||The comment that will be set for the new revisions of the imported transformations and jobs.|
|replace||Set to Y to replace existing transformations and jobs in the repository. Default value is N.|
|coe||Continue on error, ignoring all validation errors (Y/N). Default value is N.|
|version||Shows the version, revision, and build date of the PDI instance that the import script interfaces with.|
|norules||Do not use a rules file (Y/N). Default value is N.|