Configuring the Site Topology in TIBCO BusinessEvents Studio

The site topology file contains deploy-time information such as what processing units to deploy to specific machines in your environment. You need to know information about the machines that will host the agents you plan to deploy.

Procedure

  1. Begin with the project you configured in Cache OM Tutorial. Or, as needed, import the FraudDetection Cache project into your workspace.
    See Import of Existing Projects into Your Workspace for guidelines on working with example projects.
  2. Right-click the project name, FraudDetectionCache, and select New > Other > TIBCO BusinessEvents > Site Topology.

    The Fraud Detection Cache example project ships with a configured site topology file, so give yours a different name.

    Do not change the FraudDetectionCache.st file in the example location. It is referenced by the MM CDD file as shipped.

  3. At the New Site Topology Wizard, do the following:
    1. Enter the name fdcacheSt. As desired, enter a description.
    2. In the Cluster Deployment Descriptor field, browse to and select fdcache.cdd. Only CDD files within the studio project you are configuring are available for selection.
    3. Click Finish.
      You see the site topology editor, showing the cluster bar icon and site globe icon, ready for you to build the site topology diagram:
  4. Click the blue bar, which represents the cluster. In the Cluster Properties tab, do the following:
    • Copy the value of the Project CDD field to the Master CDD field.
    • In the Master EAR field, enter the location of the EAR file used for the Fraud Detection Cache project. If you are using the project in its shipped location, you would enter:

      C:\tibco\be\5.1\examples\standard\FraudDetectionCache\fdcache.ear

      The project CDD is used at design time to provide information about the processing units.

      The MM server reads the master files at deploy time and copies them to the remote deployment locations specified in the deployment units.

      If the TIBCO BusinessEvents Version field appears in red, edit it to show the current version.

  5. In the Site Topology section of the palette to the right of the canvas, click the deployment unit (DU) icon and then click the canvas.
    A DU icon appears on the canvas. Right-click the canvas to stop adding units. (If the palette is not visible, click Window > Show View > Palette, or Window > Reset Perspective.)

    A connection arrow appears automatically, connecting the deployment unit to the cluster. For the tutorial you need only one DU. For a production system, you would need more, of course.

  6. Click the DU icon on the canvas and configure the Deployment Unit Properties tab settings.
    • The Deployment Unit Name field defaults to DU_1. Change it to DU_WindowsOS.
      Tip: It can be useful to put the operating system in the DU name because paths must be specified as appropriate for the deployed machine’s OS. Other settings can be specific to a machine. It’s good to use the name as a reminder about where you can deploy the unit.
    • In the Deployed CDD and Deployed EAR fields, specify the directory where MM will put the files when it deploys this DU to the host machine. For the example deployment, this tutorial specifies c:\temp\fdcache.cdd and c:\temp\fdcache.ear. You can select different directories.
  7. In the DU property sheet, Click Add two times.
    Two processing unit configuration (PUC) entries appear:

  8. Double-click the first PUC. (You can also click the PUC icon shown within the DU icon in the diagram). The Processing Unit Configuration properties appear. Configure the PUC as follows:
    • Replace the default name with the more descriptive name InferenceAgent, because this engine will run one inference agent.
    • Select the option to use the PUC name as the engine name. This makes log files and the console easier to read.
    • Select the defaultprocessing unit. (The list displays the PUs defined in the CDD.)
    • Set the JMX port to 5500.
  9. Double-click the second PUC and configure it as follows:
    • Replace the default name with CacheServer, because this engine will run one cache agent.
    • Select the option to use the PUC name as the engine name.
    • Select the cacheprocessing unit.
    • Set the JMX port to 5501. When multiple PUs are running on one host, each PU must have a different JMX port.
  10. Add one host. In the Site Topology section of the palette, click the Hosticon, and then click the canvas. A host icon appears on the canvas. Right-click in the canvas area to stop adding hosts.
  11. Click the host icon and configure the host properties:
    • In the General tab, configure the host name as your actual machine name. Do not use localhost. In the Host IP field, enter the actual IP address of the machine.
    • As desired enter the Openssh username and password you activated in Installing Openssh Software for Remote Start and Deployment. If you leave these fields blank you are prompted for the credentials at deploy time, for every action, such as deploy, start, and so on.
    • In the Installation tab, enter the TIBCO BusinessEvents Home and TRA file locations. By default TIBCO BusinessEvents Home is C:\tibco\be\version and the TRA file is in C:\tibco\be\version\bin\be-engine.tra.

      If the TIBCO BusinessEvents Version field appears in red, edit it to show the current version. (This happens only when an older ST file is copied to a later version’s project.)

    • In the Start-PU-Method tab, select Use SSH(the default).
  12. Connect the host to the deployment unit:
    • In the Links section of the palette, click the Connecticon.
    • Click the host and then the title bar of the deployment unit, to connect them.

      Right-click to stop connecting.

  13. Click Save.

Result

Now for MM to parse and load the site topology file, you must put the site topology file under BE_HOME/mm/config. By default, the property be.mm.topology.file points to the absolute path of the site topology file of the Fraud Detection Cache example. When TIBCO BusinessEvents Express is installed, the property points to the absolute path of the site topology file of the Fraud Detection example instead.

For MM to monitor other projects, you must remove this property from the MM.cdd file or set its value to “”(empty string).