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. TIBCO BusinessEvents projects published by TIBCO Silver Fabric support the use of a Cluster Deployment Descriptor (CDD) XML file and a processing unit ID to configure a project EAR for publishing. You can provide the custom configuration file (.cfg file) to set or override the global variables, while deploying application with TIBCO Silver Fabric.

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

   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. When the EAR application is deployed to the BusinessEvents run time the project files are placed in the folder structure according to the file folder structure defined in the properties file, xml file, or EAR file.

   • .zip File
     A .zip archive is uploaded when it is required to override the global variables set in the EAR archive using TIBCO BusinessEvents Studio at runtime. The .zip file can contain:

     • EAR file which is, the application to be deployed.
     • A .cfg in which the global variables are defined.

       A .cfg file contains a list of value pair <property>=<value>, where the <property> is the global variable name and the <value> is the value of global variable. These values are used as a substitution to the global variables at the deployment.

     • Deployment configuration file which is an XML file containing application deployment configuration. For more refer section Creating a Deployment Configuration XML File.
     • A properties file (.properties) to specify the application deployment path. The file is used to define the full path of application to be deployed relative to the TIBCO Administrator root directory. For example create the CustomFolder.properties file with content "ApplicationFullPath=aaa/bbb/ccc ". This file is included in the .zip file to specify the deployment path.

       When the deployment path is not specified, the uploaded BusinessEvents project EAR and application files can be found in the Application Management directory at the root folder level of TIBCO Administrator.

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". If the specified CDD file doesnt exist in the EAR, enabler selects the first file from the available CDD files inside the EAR for deployment. Similarly, if the PUID provided is not valid, it selects the first one in the matching CDD file. Alternatively, you can also deploy applications from TIBCO Administrator or by using the AppManage domain utility.
4. Click OK to proceed.