After restarting the system, data persists With a cache-based system, you lose all data in the event of a total system shutdown. With the backing store in place, data remains available after the system restarts. You can experiment with this by adding data then restarting all engines.
You can simply open the example readme.html file and follow instructions there. In order to send events into the engines, you must enter information into the forms provided in the readme. Navigate to BE_HOME/examples/standard/FraudDetectionStore (or the location where you copied it to) and open readme.html in your browser. Follow the instructions in the readme file to start two or more engines and send events to the inference agent.See Dependency of Interactive Readme File on a Higher Level Directory to understand the requirements for using the interactive readme file.
1. Open a command window, change directory to the example directory, and at the command prompt, start the TIBCO BusinessEvents engine using the following command. This command starts the cache agent. Always start cache agents first. Substitute your actual value for BE_HOME:
cd BE_HOME/examples/standard/FraudDetectionStoreBE_HOME/bin/be-engine --propFile BE_HOME/bin/be-engine.tra -u cache -c FraudDetectionStore/fdstore.cdd fdstore.ear
For example, if you are simply running the provided example, you would use this command line to start the cache agent:c:/tibco/be/5.0/bin/be-engine --propFile c:/tibco/be/5.0/bin/be-engine.tra -u cache -c FraudDetectionStore/fdstore.cdd fdstore.ear
2. When the cache agent has started, open a second command window, change directory to the example directory, and at the command prompt, start the TIBCO BusinessEvents engine using the following command. This command starts the inference agent. Substitute your actual value for BE_HOME:
cd BE_HOME/examples/standard/FraudDetectionStoreBE_HOME/bin/be-engine --propFile BE_HOME/bin/be-engine.tra -u default -c FraudDetectionstore/fdstore.cdd fdstore.ear
For example, if you are simply running the provided example, you would use this command line to start the inference agent:c:/tibco/be/5.0/bin/be-engine --propFile c:/tibco/be/5.0/bin/be-engine.tra -u default -c FraudDetectionStore/fdstore.cdd fdstore.earSend some events such that one more debit could cause an account to be suspended. Stop both engines. Then start them up again. Send one or more events such that the threshold for account suspension is crossed. You’ll see that the account is suspended, based on data that was retrieved from the backing store as well as data you just entered.You can now continue to Chapter 5, TIBCO BusinessEvents Monitoring and Management Tutorial, if you have not already completed that tutorial.Troubleshooting
Copyright © TIBCO Software Inc. All Rights Reserved.