Build package command

You can use the istool command-line interface (CLI) to build packages of IBM® InfoSphere® DataStage® and QualityStage® assets that are defined in the IBM InfoSphere Information Server Manager.

Purpose

The istool build package command is used to build a package ready for deployment. 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 that you specify resides in the metadata repository.

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

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> build package  
authentication options
[generic options]  
-package  package
[ -label "buildlabel" ]  
[ -comment "comment" ] 
[ -overwrite ]
[ -preview ]

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.
-comment "comment_text" or -c "comment_text": Adds a comment to the deployment package information.
-preview or -pre: Specify this option to preview the build operation without building a package.
-label "label_text" or -l "label_text": Specifies a label for the build. You can use the label to version different builds of your deployment package.
-overwrite or -o: Rebuilds an existing deployment package. This option removes all history from the package.

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> build package -help to see the list of possible exit codes for the build package command.

Error handling

When building a deployment package, if at least one object is successfully built, a deployment package file is created. If one or more objects fails to build, the command completes with a non-zero exit code.

Example

The following example shows how to build two versions of a package.

Define a package named DeployPackage1 by using the InfoSphere Information Server Manager to include tabledef1.tbd.

Build the package DeployPackage1, add the comment “my first package” to the build, and label the build "version 1.1":

istool> build package –domain myhost:9443
-username user1 -password pass1 -package DeployPackage1  
-label "version 1.1" –comment "my first package"

Modify tabledef1.tbd in the Designer client. For example, add a row.

Rebuild the same package, add the label "version 1.2", and add the comment "table def changes":

istool> build package –domain myhost:9443
-username user1 -password pass1 -package DeployPackage1  
 -label "version 1.2" –comment "table def changes"

When you open DeployPackage1 in the InfoSphere Information Server Manager, the History tab shows two builds, version 1.1. and version 1.2. You can deploy version 1.1 or version 1.2 of tabledef1.tbd by using the deploy package command and specifying the -label option.