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.)

Learning Points

What is an event preprocessor?
 An event preprocessor is a rule function that processes incoming messages before TIBCO BusinessEvents transforms them into events. In this case the preprocessor is used to send a response to the HTTP server. In real-world applications, however, a preprocessor might filter the messages so that only certain ones are used as events, and it might do other event enrichment actions. Preprocessors are multi-threaded and you can choose from various threading and queue options, as appropriate to handle the work load. By default the threading uses the system-wide shared queue and threads. See the topic Event Preprocessors in TIBCO BusinessEvents Architect’s Guide.
How are event preprocessors configured for use?
 A preprocessor is associated with a destination. It processes events arriving at that destination. See Cluster Deployment Descriptor (CDD) and the EAR File for details.
Note:
Applications that Use Concurrency Features Require Use of Locking
 Locking is used to ensure that multiple concurrent RTCs (whether in the same agent or different agents in a cache cluster) do not work with the same object at the same time, or read an out of date version of the object. This is especially important if you use Cache+Memory mode. Locking is usually done in event preprocessors. See Using Locks to Ensure Data Integrity Within and Across Agents in TIBCO BusinessEvents Architect’s Guide to understand how to use locking correctly.

More Information

  • See Event Preprocessors in TIBCO BusinessEvents Architect’s Guide.
  • See Event Preprocessors in TIBCO BusinessEvents Developer’s Guide.