eConnect installs a collection of components that
work together to provide programmatic access to Microsoft Dynamics
GP data. The following diagram illustrates the basic
The diagram illustrates eConnect’s two key layers
and the components that make up those layers. The two layers are as
The data access layer contains the
eConnect business objects. The business objects are a collection of
SQL stored procedures installed on the Microsoft Dynamics GP
server. eConnect uses the business objects to perform all retrieve,
create, update, and delete operations.
The runtime layer contains a collection of
files, Windows services, and components that provide the
application programming interfaces (API) you use to send or
retrieve XML documents. The API enable your application to use the
business objects. You must install the components of the runtime
layer on the same computer as your integrating application. When
you develop a new application, install and use the API that best
meets your integration needs.
The diagram shows that
an integrating application can bypass the API layer and use the
eConnect business objects directly.
The Transaction Requester is an interface you use
to retrieve specified types of eConnect XML documents. Typically,
the Transaction Requester uses the Outgoing Service to publish
document to an MSMQ queue. The Transaction Requester includes the
eConnect Requester Setup tool that you use to specify the types of
transactions the Outgoing Service publishes as an XML document.