| Table of Contents | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The details of the Provider Services (in Integration Framework) are available in the Integration Framework Database as shown in the Figure:001. Please note that, only the providers which are active (IsActive=1) are hosted as WCF Services for serving their clients. The corresponding binaries for these provider services are available in the location that is configured in the App.config as shown in the Figure:002.
Figure:001
...
Figure:002
...
How are these provider services hosted?
The "IntegrationFramework.Host.Windows.Service" project in the "Integration Framework Solution" as shown in the Figure:003 is responsible for loading the active providers from the Integration Framework Database, loading their binaries from the configured location, and hosting them as WCF Services to serve their clients. For technical details on how to host these provider services, please click here.
Figure:003
...
Listener Service
Listener Service (in MetaField) is hosted as a WCF Service that is called back from the Provider Service (in Integration Framework) in order to make some changes in the MetaField application (please note that, not all the provider services will require a listener WCF service. however, the Forney Provider Service requires it's listener service.). This means that there is a 2-way data exchange and manipulation between MetaField and Integration Framework. For example, MetaField calls the Forney Service (which is hosted as WCF Service in Integration Framework) for fetching the Forney Test Results data. This Forney Service, after fetching the Forney Test Results data, will call the Listener WCF Service in order to update the MetaData database with these test results data. This is illustrated in the Figure:004
Figure:004
...
How is the Listener WCF Service hosted?
...