Project Design Tutorial
You will configure, build, deploy, and test a TIBCO BusinessEvents project, with an emphasis on the basic project design.
Deployment activities are limited to the basic actions required to test a design.
The section The Fraud Detection Scenario explains the general tutorial scenario, the fraud detection criteria, and how a customer account can become Suspended. This section explains in more technical terms what happens at runtime given an example debit that triggers the fraud detection rules. (You will learn more details about the terms shown in italics below, as you complete the tutorial steps):
- A message arriving through a TIBCO BusinessEvents channel is transformed into an event. (At design time you create an event type for this purpose, with the appropriate properties.) The event instance is then asserted into the Rete network, an in-memory network of objects based on the Rete algorithm, which enables fast matching of facts with rule dependencies.
- The presence of this new event in the Rete network causes the inference engine to check for rules that are designed to be triggered when this event is asserted.
- A rule that is triggered by this event executes. A rule might make changes to concept instances, create an event and send it to a channel (and out of the TIBCO BusinessEvents application to some destination), and so on. The rule then consumes the event unless there is a reason to persist the event.
Note: It is important to consume events when they are no longer needed so that they do not trigger rules to fire erroneously. On the other hand, it is also important to use a long enough time-to-live (TTL) setting for an event, so that it exists long enough to perform all work needed, for example, to trigger rules that correlate multiple events and take appropriate actions.
- Import of Existing Projects into Your Workspace
It is recommended that you complete the tutorials yourself, because "learning by doing" is the most effective way to become proficient. - Importing an Example Project into Your Workspace
You can work on a sample project in BusinessEvents Studio after importing the project into the BusinessEvents Studio workspace. - Before you Create a Project
Before you can create a specific project, you need to create an empty project using TIBCO BusinessEvents Studio. - Creating the Fraud Detection Project
In this task, you will create a new project, place it in a desired location, and save it. - Adding an HTTP Channel and Destination
In this task you configure an HTTP channel with one destination. The AllOps destination listens for messages that come from HTTP forms embedded in the project’s readme.html file. - Events
In this task, you begin to build the project ontology by defining some events — or strictly speaking, event types. Before you define event types in a real-world project, you first examine the incoming and outgoing messages, as well as messages that you want to occur within the application, and configure each event type’s characteristics accordingly. You can use inheritance (as demonstrated here) to simplify configuration. - Defining the AccountOperations Event
This event is a parent to events that are used in the project. It has one property: AccountId. All its child events inherit this property, and extend the parent by adding more. - Account Concept
In this task, you define the Account concept, which holds basic information about an account: an ID, a balance, an average monthly balance, and an account status. You also learn some useful information about concepts and how they are used. - FraudCriteria Scorecard
In this task, you finish building the project ontology by creating a scorecard. The FraudCriteria scorecard will store the criteria used to determine fraud, not any specific data about customer accounts. In this example, you will use this scorecard in rules. - InitializeScorecard Rule Function
In this task, you configure a rule function that initializes values for the FraudCriteria scorecard. This rule function is used at system startup. (You’ll configure that connection later.) - PreProcessor Rule Function
HTTP is a request-reply protocol, and this step is required so that the HTTP server is ready to process the next request from the readme.html form. This rule function executes when an event is received. (You’ll configure that connection later.) - BadCreateAccount and CreateAccount Rules
In this task you create two rules, one called CreateAccount and one called BadCreateAccount. - ApplyDebit BadApplyDebit and CheckNegativeBalance Rules
It’s important to understand how conflict resolution and run to completion (RTC) cycles work. - FraudDetection Rule and Unsuspend Account Rule
Add the FraudDetection rule, typing in the Source view or Form view, according to your preference. - Project Analysis and Validation
In this task, you check the project for errors. - Cluster Deployment Descriptor (CDD) and the EAR File
To deploy a project you need a CDD file and an EAR file. The CDD is not included in the project EAR. This means you can reconfigure a project’s deployment configuration without having to rebuild the EAR.
Copyright © TIBCO Software Inc. All rights reserved.