Importing Site Topology File

Using the import option, you can import application and instances details along with the associated machine details using an existing Site Topology (.st) file used by BusinessEvents Monitoring and Management.

The site topology file contains information about the processing unit instances and associated machines that can be imported in the BusinessEvents Enterprise Administrator Agent. If the machine, specified in the ST file, is already present in the machine repository (matching all machine parameters), no new machine entry is created. Otherwise, the machine is added to the machine repository. If a machine already exists in the machine repository with the same name as mentioned in the site topology file, but other details are different, the agent auto-generates a unique name.

Prerequisites

BusinessEvents application site topology file which contains information about processing unit instances and associated machine details

Procedure

  1. Select the Application Deployments tab.
    The Application Deployment tab is the default start page for the BusinessEvents Enterprise Administrator Agent UI.
    The BusinessEvents Application Deployment page is displayed.
  2. Click Import Deployment.
    The Import Deployment page is displayed to enter the deployment details.
  3. Enter the details in the Import Deployment page and click Save.
    Field Description
    Site Topology Click Browse and select the site topology file for the BusinessEvents application.

    For example, C:\tibco\be\5.3\examples\standard\FraudDetectionCache\FraudDetectionCache\FraudDetectionCache.st for the FraudDetectionCache application.

    Cluster Deployment Descriptor Click Browse and select the CDD file for the BusinessEvents application.

    For example, C:\tibco\be\5.3\examples\standard\FraudDetectionCache\FraudDetectionCache\fdcache.cdd for the FraudDetectionCache application.

    Enterprise Archive Click Browse and select the EAR file for the BusinessEvents application.

    For example, C:\tibco\be\5.3\examples\standard\FraudDetectionCache\fdache.ear for the FraudDetectionCache application.

    Deployment Name Enter the deployment name for the BusinessEvents application.

    By default, the agent takes the name specified in the ST file. For example, FraudDetection for the FraudDetectionCache example.

    A new card for the BusinessEvents application (for example, FraudDetection) is displayed on the BusinessEvents Application Deployments page. The import confirmation message is displayed: <Application deployment> application deployment import successful.

Result

The import option has now added all the processing unit instances mentioned in the site topology file to the BusinessEvents Enterprise Administrator Agent. The machine details from the site topology file are added to the machine repository. The imported machine entry is also bounded to the respective processing unit instances.
Note: The concept of "Deployment Unit" of BusinessEvents Monitoring and Management is not used in BusinessEvents Enterprise Administrator Agent.