TIBCO BusinessEvents Monitoring and Management Tutorial : Configure the Site Topology File

Configure the Site Topology File
The topology file contains deploytime 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, for example information about the machines’ operating system, IP address, and login credentials.
Instructions in this section are for the tutorial scenario: all components running on one Windows machine.
Learning Points
What is a processing unit configuration?  You define processing units in the CDD file. One PU deploys as one engine. In the site topology file you select processing units and add deploy-time configuration settings to them. They are then known as processing unit configurations (PUCs).
What is a deployment unit  A deployment unit deploys as one or more engines. It consists of one or more processing unit configurations. It also specifies the location of the deployed EAR file and CDD file, generated by MM at deploy time. A DU can be re-used for different machines, unless it has machine-specific settings.
What is a predefined engine?  A predefined engine is one that is configured in the site topology file. You can deploy predefined engines and monitor and manage them using MM. Unpredefined engines can be monitored if they are running but can’t be started or deployed if they are not running.
Can I edit the site topology file in a text editor?  Editing in TIBCO BusinessEvents Studio is always preferable because it can validate the file, and the graphical editor maintains the correct structure. However, when you can’t use the graphical editor, you can use the template file to help you work with the settings in a text editor:
BE_HOME/mm/config/site_topology_template.st
More Information
Task D Configure the Site Topology in TIBCO BusinessEvents Studio
1.
Begin with the project you configured in Chapter 3, Cache OM Tutorial. Or, as needed, import the FraudDetection Cache project into your workspace. See Importing 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.
a.
Enter the name fdcacheSt. As desired, enter a description.
b.
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.
c.
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:
Cluster
4.
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\4.0\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 BusinessEvents Version field appears in red, edit it to show the current version.
Deployment Units
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.
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 to.
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.
A known issue in this release means you can’t save the DU until you make a change in another field than Deployed CDD and Deployed EAR. You must make a change in the Deployment Unit Name field to enable the Save button. For example, you can add and then remove a letter.
Processing Unit Configurations
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 default processing unit. (The list displays the PUs defined in the CDD).
9.
Replace the default name with CacheServer, because this engine will run one cache agent.
Select the cache processing unit.
Host
10.
Add one host. In the Site Topology section of the palette, click the Host icon, and then click the canvas. A host icon appears on the canvas. Right-click in the canvas area to stop adding hosts.
11.
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 Copssh username and password you activated in Task A. 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 BusinessEvents Home and TRA file locations. By default BusinessEvents Home is C:\tibco\be\4.0 and the TRA file is here: C:\tibco\be\4.0\bin\be-engine.tra.
If the 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.)
12.
Right-click to stop connecting.
13.
Summary and Next Steps
Now the site topology file is configured, you just have to specify its location in the MM.cdd file, to make the connection between the MM server and the cluster it will manage.