Enabling destinations only when needed by the application.
Article ID: KB0086131
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
In some cases it is necessary to execute some initialization rules before the engine begins fully processing events, and it requires that the destinations are to be enabled only when needed.
Environment:
==========
TIBCO Business Events 3.x and 4.x versions.
Resolution:
=========
Configure a startup function in your TIBCO Business Events project and call the function to suspend the destinations. Then execute the initialization rules and at the end of the rule execution you can trigger another event which resumes these destinations.
See the attached sample which disables the destination/channel at startup and enables it via another event.
Attachment
=========
ExternalEventAndConceptRepo3.zip
Description:
============
In some cases it is necessary to execute some initialization rules before the engine begins fully processing events, and it requires that the destinations are to be enabled only when needed.
Environment:
==========
TIBCO Business Events 3.x and 4.x versions.
Resolution:
=========
Configure a startup function in your TIBCO Business Events project and call the function to suspend the destinations. Then execute the initialization rules and at the end of the rule execution you can trigger another event which resumes these destinations.
See the attached sample which disables the destination/channel at startup and enables it via another event.
Attachment
=========
ExternalEventAndConceptRepo3.zip
Issue/Introduction
Enabling destinations only when needed by the application.
Attachments
Feedback
Yes
No
Powered by
