The Transaction Requester is a collection of SQL database tables and database triggers that eConnect uses to make Dynamics GP data changes available to the Outgoing Service. The following diagram illustrates the Transaction Requester:
When you install the Transaction Requester, the installer creates three tables in each specified Microsoft Dynamics GP database:
For example, assume you want your application to be updated when a new customer is added to Microsoft Dynamics GP. To begin, you use the eConnect Requester Setup utility to specify the customer object and the SQL insert operation. The eConnect Requester Setup adds a SQL trigger to the database. When a new customer record is inserted, the SQL trigger creates a record of the event in the eConnect_Out table.
The eConnect Outgoing Service periodically queries the eConnect_Out table. The service uses the record in the table to create an XML document that describes the new customer document.
The Outgoing Service then places the XML document in a message queue where it can be retrieved and used by your application.
To configure the eConnect Transaction Requester, use the eConnect Requester Setup utility. The eConnect Requester Setup utility allows you to specify Dynamics GP objects and operations you want to export to another application. The utility then adds SQL triggers to Dynamics GP that populate the eConnect_Out table for the specified objects and operations. For a detailed explanation of how to use the eConnect Requester Setup utility, see the eConnect Installation and Administration Guide.
Refer to Customizing the Transaction Requester for information about using and customizing the Transaction Requester Service.