Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Introduction

MetaField requires Integration Framework to utilize one or more services for the features it has, such as "DocuSign", or "Forney Integation".  As such, Integration Framework has many services that can be hosted on a server (for this wiki article, we assume the server is localhost) and then MetaField can call these services for CRUD operations for some of its specific features as mentioned before. These services are also called as "Provider Services".

Provider Service

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?

Listener Service

How is the Listener WCF Service hosted?

Steps to host the Provider Service (as WCF Service), and the Listener WCF Service

Host the Provider Service (Integration Framework) as WCF Service on localhost

Host the Listener WCF Service (MetaData) on localhost

Steps to debug the Forney data retrieval for a sample created and tested on “USQATEST” environment using the WCF Services hosted on localhost

  File Modified
No files shared here yet.
  • No labels