Configuring a Linux or UNIX deployment definition

After you create a deployment definition, you can configure it by modifying or adding deployment definition properties.


  1. If the Deployment Definition editor is not already open, expand the Enterprise Extensions node, then the Deployments node. Right-click the deployment definition you want to configure and select Open Deployment Definition.
  2. In the Deployment Definition editor, go to the Overview tab.
    1. In the General Information Description field, briefly describe your deployment definition.
    2. Optional: Select Ignore warnings when computing overall status.
    3. In the Supporting Build Engines field, click Create to create a build engine, or select an existing build engine by clicking Add, selecting the build engine, then clicking OK. You must associate a build engine with your package definition. For more information, see Creating build engines.
    4. Optional: In the Pruning Policy field, select Prune build results, then set the number of successful and failed builds to save.
  3. Optional: Go to the Properties tab. From the Properties table, you can highlight an existing property that you want to edit. Click Edit and enter a value in the Value field. You can also click Add or Remove to add or remove properties.
  4. Optional: Go to the Ant tab.
    1. In the Build File and Targets section, specify the Ant build file and targets you want your definition to invoke. Reference properties using this format: ${propertyName}.
    2. In the Ant Configuration section, select Include the Jazz build toolkit tasks on the Ant library path if you want to add the -lib Ant argument with the path to the Jazz™ buildtoolkit directory.
    3. Specify any other configuration details, including the following:
      • Ant home
      • Ant arguments. The default is -verbose.
      • Working directory
      • Java™ home
      • Java VM arguments. The default is -Xquickstart.
      • Properties file
  5. Perform the following steps from the Linux/UNIX Deployment tab:
    1. In the Package field, select a package definition.
    2. In the Deployment field, you have the option of selecting Deploy complete package. You must also specify the following:
      • Deploy pre-command
      • Deploy post-command
      • Rollback pre-command
      • Rollback post-command
    3. In the Load field, select either Copy or FTP.
      If you select Copy, specify the following:
      • Local package root directory
      • Remote package root directory
      • Optional: Optional: Load pre-command
      • Optional: Optional: Load post-command
      If you select FTP, specify the following:
      • Host name
      • User ID
      • Password file
      • Local package root directory
      • Remote package root directory
      • Optional: Optional: Load pre-command
      • Optional: Optional: Load post-command
    4. In the Platform field, specify a runtime root directory.
    5. In the Publish field, select one or more of the following:
      • Publish delta deploy manifest
      • Publish cumulative deploy manifest
      • Publish rollback manifest
  6. Click Save to save your deployment definition.

video icon Video channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community forums library

support icon Support

IBM Support Community
Deployment wiki