Triggering EBI via Outside Events

Triggering EBI via Outside Events

TAGS: EXTOL Business Integrator / EXTOL API / EXTOL Webservices /

Sometime EXTOL Business Integrator (EBI) is viewed as a Any-to-Any solution on a one-way island. Meaning, EXTOL processes can run when and where they want, however little input can be made from an outside source/process.

EBI has multiple ways to trigger an EBI Event from an outside process.

  • Filesystem Monitors
  • Database Monitors
  • External Notification API
  • External Communications Adapter


A Filesystem Monitor (FSM) is designed to “listen” for the file(s) specified in a location at an indicated frequency and then move the file(s) to a location and perform an EBI Event.

The Filesystem Monitor sends a Notification to EBI (with the file as the payload) and invokes the associated Business Process.


Database Monitors can automate responses to business events that are manifested as database actions (insertion, deletion, and updating of database content), for Oracle, Microsoft SQL Servers and IBM DB2 i DBMSs.


External Notification APIs can send notifications to EBI, along with additional properties to launch EBI events.

Provided by EXTOL to call EBI events from external programs. See documentation included in EBI install directory.


A Communications Adapter allows for messaging system and application programming interface (API) to communicate with EBI. One such example of an API would be SOAP and REST Web Services


By: on

Warning: DOMDocument::load( failed to open stream: HTTP request failed! HTTP/1.0 404 Not Found in /home/seanho8/ on line 4

Warning: DOMDocument::load(): I/O warning : failed to load external entity "" in /home/seanho8/ on line 4

A free web counter provided by GoStats.