Overview

The concept is based around creating a single point of entry for all interface requests to and from ITAS, to run as a Windows/Web Service (ITAS WebServices). This framework is principally (but not limited to) required to allow data imports and extract requests directed through the ITAS Global Interface (IGI).  To this end IWS is simply redirecting the notify/request message to the ETL layer.

 

It has been kept sparse with two simple methods; Request (for all outbound/extract requests) and Notify (for all inbound/import notifications). IWS will maintain references to the specific functionality DLL's, for example to access the extract routine the Export method in the ITASetl.dll will be called.

 

To keep things simple the client software calling IWS passes the procedure (method) name as well as specific data parameters in a single xml-style string (see ETL Variations). Taking this approach allows full extensibility without the need to keep creating new points of access to IWS.

Details

Resides:	itasfolder\exec\net35
Dependencies:	ITASWindowsService.exe.config, ITASetl.dll
Comments:	C# project, runs as a Windows Service named ITAS WebServices
Executable:	ITASWindowsService.exe
Test Harness:	TestITASws.exe

 

Installation Notes

·     Requires .NET Framework 4 or above

·     Open config file and ensure <host><baseAddress=http://appserver name or IP:8000/iws />

·     NOTE: in some cases the IP address is used rather than localhost as it is expected that remote (off-system/network) requests will be necessary

·     From v4 folder (or equivalent) run the following command;

·     InstallUtil.exe itasfolder\exec\net35\ITASWindowsService.exe

·     Test harness has own config file (TestITASws.exe.config) which maintains endpoint and identity

·     NOTE: where the test harness is run on the app server the endpoint can refer to localhost and identity of host/localhost otherwise it will be necessary to use a suitable network account