Uploading a BusinessEvents Project

Upload BusinessEvents archives to publish and run BusinessEvents projects. You can upload Enterprise archive (EAR) or files (.zip files) one at a time. You can choose to specify a custom CDD file to be used for deployment instead of using the one inside the EAR. Custom CDD files can be provided with the EAR inside the zip

You can configure Kafka, StreamBase, or FTL channels by using by setting the corresponding global variables in CDD file. For more information refer section Configuring Kafka, StreamBase, or FTL Channels by Using Custom CDD file.

Procedure

  1. Click the Add button in the Upload, Remove, or Reorder Archive Files panel.
  2. Click the Choose button in the Archive Management Feature Info panel to navigate to the EAR or .zip file

    At a time you can upload one of two types of archive files :

    • EAR File

      When you upload a BusinessEvents EAR file, it uses the default value of the global variables set in TIBCO BusinessEvents Studio.

    • .zip File

      You can create a .zip file that contains an EAR file and one or more custom CDD files. A .zip archive is uploaded when it is required to set or override the global variables set in the EAR archive at deployment time.

  3. Specify a CDD (Cluster Deployment Descriptor), PUID (Processing Unit ID) file specification as required. BusinessEvents projects uploaded by using TIBCO Silver Fabric, supports the use of a Cluster Deployment Descriptor (CDD) XML file and a processing unit ID to configure a project EAR for deploying. The value of CDD is the name of the *.cdd file. The value of PUID is what you set in the *.cdd file or "default".
    The order in which Enabler searches for the specified CDD file is as follows:
    1. Matching CDD file from the .zip.
    2. If the matching CDD file is not found, then the first CDD file from available CDD files in the .zip.
    3. If no CDD file is selected from the.zip or if the uploaded archive is EAR, then the CDD file from the EAR with the matching name.
    4. If no matching CDD file is found in the EAR, then first CDD file from available CDD files in the EAR.

Note: Similarly, if the PUID provided is not valid, it selects the first one in the matching CDD file.

  1. Click OK to proceed.