NOTES: See Installing Inresponse Service Manager for instructions on installing the optional Inresponse Service Manager.
To run the Inresponse Web Service Host, you must install the Inresponse Service Manager.
The Inresponse workflow engine provides a flexible and scalable framework that supports and augments user-defined workflows. Its primary purpose is to respond to actual system events by performing predefined asynchronous Actions when required.
The architecture of Inresponse is designed to be both flexible and scalable. The infrastructure allows for an unlimited number of Action Queues, Action Types, and Action Processors. The two primary working components of Inresponse are the MS SQL Server Service Broker system and Inresponse instances. Inresponse instances perform the core processing of Inresponse together with the Insight database.
The following figure provides a high-level conceptual model of the Inresponse architecture.
An Action is known as a task when flowing through the Inresponse architecture. An Action is actually an XML string that contains the parameters necessary to complete the task.
MS SQL Server Message Broker
Service Broker provides queuing and reliable messaging for SQL Server. Its primary role in the Inresponse architecture is to facilitate the communication and queuing of unprocessed Inresponse tasks. As new Actions or tasks are placed into the Service Broker queue, they are arranged into unique conversations, essentially a dedicated communication channel for each Action Type defined in the <%INSIGHT ONLY%> database. From these conversation channels, tasks are retrieved one at a time by waiting Inresponse instances.
Inresponse (formerly known as Task Workers)
You can run Inresponse instances on one or more computers in the same network as the Insight database. Inresponse, when started, creates a worker thread for each Action Type that it is configured to process. The role of each worker thread is to request and accept tasks from its corresponding Service Broker queue conversation channel and process the task with the DLL defined for its Action Type. When complete, it updates the status of the task in the Insight database and waits for the next available task in the queue.
To process Actions, the Insight system requires Inresponse to run on at least one workstation in the network.
RELATED TOPICS:
Installing Inresponse Service Manager
Understanding Inresponse Processing in the Workflow Management chapter of the online Help.
NEXT TOPIC: To install an Inresponse instance