Deploy package command

You can use the istool command-line interface (CLI) to deploy packages of IBM® InfoSphere® DataStage® and QualityStage® assets that you have previously built.

Purpose

The istool deploy package command copies the contents of a package to a target metadata repository of IBM InfoSphere Information Server. You must first define the package in the InfoSphere Information Server Manager, including specifying the assets that it contains and the build and deploy paths. In a clustering environment, set the build and deploy paths to shared directories that are accessible from every cluster node. The package is built by using the istool build package command.

To deploy a package, you must have an InfoSphere DataStage and QualityStage role that grants you permission to edit assets in the target project.

Command syntax

The preferred way to run this command is in the istool command-line window. If you run this command in your operating system command-line window or in scripts, you must add istool to the command name.

istool> deploy package 
authentication options
[generic options] 
[-package package |-file deployfile | -localfile deployfile]
[-label "buildlabel"]
[-preview]

-datastage '[-replace] server/project'

Command options

authentication options: Use authentication options to connect to a specific installation of InfoSphere Information Server.
generic options: Use the generic options to request help on command syntax, or to specify silent or verbose operation.
-package name or -pkg name: Specifies the name of an existing deployment package definition in the metadata repository. The package must already be built. The -package, -file, and -localfile options are mutually exclusive.
-file name or -f name: Specifies a deployment package file name in the target system. The specified file name must be relative to the deploy directory in the target system. Use this option to deploy assets that were packaged on a different computer. You must first transfer the package file from the source system build directory to the target system deploy directory. The -package, -file, and -localfile options are mutually exclusive.
-localfile name or -lf name: Specifies the fully qualified name of a deployment package file on the local file system of the client. The -package, -file, and -localfile options are mutually exclusive.
-label "label_text" or -lab "label_text": Specifies the label for the build of the package to be deployed.
-preview or -pre: Specify this option to preview the action of the command without changing the repository.
-datastage 'server/project' or -ds 'server/project': Specifies that InfoSphere DataStage and QualityStage assets are to be deployed to the target server and project.
-replace or -repl: Specifies that assets in the deployment package replace any existing assets in the target project that have the same identity.

Exit status

A return value of 0 indicates successful completion, any other value indicates failure. The list of exit codes is shown in the command help. Enter istool> deploy package -help to see the list of possible exit codes for the deploy package command.

Error handling

When you deploy a package, the operation continues until the entire deployment package is processed. As many objects are imported as possible. If there is failure in deploying one or more objects to the project, a non-zero exit status is returned.

Examples

The following command deploys an existing package named localpackage to the target project named myProject. The target project is on the same computer. If there are any assets with the same name in the target project, they are replaced with assets from the deployment package.

istool> deploy package –domain myserver:9443  
-username user1 -password pass1  
-package localpackage
-datastage '-replace sliver/myProject'

The following command deploys a package named remotePackage that was created on a different computer. The package file has already been copied to the deploy directory on the target computer. The package is deployed from the file to the project named OtherProject.

istool> deploy package –domain myserver:9443  
-username user1 -password pass1 
-file  remotePackage.pkg
-datastage 'slice/OtherProject'