Packaging a Composite in a DAA

You can package a composite from the canvas, the project explorer, or the distribution editor. A wizard steps you through the packaging steps.

Procedure

  1. Choose a starting point and follow the appropriate procedure:
    Starting Point Procedure
    Canvas
    1. Right-click the canvas and select Create DAA....
    Project Explorer
    1. Right-click the composite file and select Create DAA....
    Distribution Editor
    1. Click the Create DAA... button in the top-right of the editor.
  2. Accept the default folder to contain the archive, or type or select a new folder.
  3. Accept the default file name or type a new name. Click Next.
  4. Select one of the following options and click Next.
    • Do not use a distribution file.
    • Create a new distribution file. If you create a distribution file, the wizard invokes the New Distribution wizard.
  5. Uncheck the checkboxes next to resource templates you do not want to package in the archive and click Next.
    The Features screen displays the composite's dependencies on plug-ins packaged in custom features. If the code is present in the workspace, by default the wizard packages the custom features together with the application.
  6. Choose the features to package in the archive and click Next >. By default, the features containing component implementations and features required by the component implementations are included. Features that require a different version of the platform on the node are not displayed.
    • Remove a feature - click the feature and click Remove.
    • Add a feature - click Add, click a feature, and click OK.
    You can select additional custom features to package in the DAA. Added custom features might depend on other product features.
  7. Choose the DAA specification options and whether to generate CLI scripts:
    1. Choose whether to save the DAA specification file.
    2. To change the qualifier replacement string, check the Qualifier Replacement checkbox and edit the Qualifier Replacement field.
    3. To launch a wizard to create an Administrator Command-Line Interface after the composite is packaged, check the Launch Administrator CLI Script Generation Wizard checkbox.
    4. To save the specified DAA configuration as a TIBCO Business Studio Command-Line Interface script, check the Save Configuration as CLI Script checkbox.
  8. Click Finish.

Result

A DAA file is created is the specified folder. If you chose to launch the Administrator CLI script wizard, the wizard displays. If you chose to save the specified DAA configuration as a TIBCO Business Studio command-line script, a build file named DAAName.build.xml and a properties file named DAABuild.properties is created in the specified folder. The build file contains targets to import all of the required projects, generate a DAA, and create an Administrator CLI script to deploy the DAA. The properties file contains the paths to the component and component implementation projects and sets the deployment environment and node to DevEnvironment and DevNode.