Generating the Deployment Scripts

When you have configured the resources in the deployment project, you generate the deployment script.

Procedure

  1. Ensure that every resource that you want to include in the deployment script has a Deploy Action of:
    • New, if it is to be deployed for the first time,
    • Redeploy, Upgrade, or Reprovision if it has been deployed previously.

      Ensure that every resource that you want to include has a Status of Configured. Any resources that you do not need to include must have the Deploy Action set to Don’t Deploy.

      Note: The Generate Scripts button is only enabled when all the projects to be deployed (that is, not having Don't Deploy action) are Configured. If you change any configuration details, you must regenerate the scripts.
  2. Save the project.
  3. Click Generate Scripts.

Result

Once the scripts have been generated, they are visible in the file structure of the deployment project in Project Explorer.

In this file structure:

Note: You should not normally need to edit any of the files in this file structure, with the exception of run.properties and server.properties.

Note that the generated files (including run.properties and server.properties) are overwritten when the Generate Scripts button is clicked.

  • The Applications folder contains sub-folders for each application, named BPM_daaname or SOA_daaname, depending on the type of project. For each project:
    • daaname.deployment-build.xml contains the tasks based on the value selected for Deploy Action for the resource. The Ant target defaults to all.
    • daaname.deployment-config.xml contains the resource’s configuration details.
  • The DAAs folder contains the generated DAAs.
  • The Scripts folder contains the generated scripts.
    • build.xml is the build file which you will subsequently run, from the command line, to deploy the projects. The default Ant target run must be used. The run target invokes the target defined in the run.properties file ( deploy or import-and-deploy). The deploy target invokes the default target of an application as specified in its generated build file daaName.deployment-build.xml.
    • The log files error.log and report.log are generated in this folder when build.xml is run. The error.log file is where error details are written if script execution fails. The report.log file shows a summary of the script execution, in terms of actions performed and remaining actions in case of failure.
    • run.properties contains the properties to configure the build.xml file, including the task to execute (deploy or import-and-deploy), workspace locations, TIBCO_HOME location, import.locations, checkout script and location. Comments in the file explain what to set.
      Note: You can edit this file to specify the import-and-deploy target for the build.xml file when deploying the project.

      When you specify a location in run.properties , use either '\\' or '/' to introduce the pathname.

    • server.properties contains the properties for the selected deployment server including adminURL, username, password, httpConnection, and Timeout.
    • projectsList.properties lists the resources in the deployment project and defines their properties.
    • The projectname.deploy file includes user selections and configuration details.
      Warning: If this .deploy file is deleted, you will need to regenerate the project.
  • The lib folder inside the Scripts folder contains:
    • the Ant jar file
    • the log4j.properties file

      These files are used by Ant during the execution of generated scripts.