Hi Chris,

Okay, so you run IIS on a windows machine, that's fine for the SOAP toolkit. Here in short the pieces needed in the puzzle:

a) a COM server DLL, that could be as simple as this prg compiled as a Multi Threaded DLL:

Define Class registration as Session olepublic
Procedure register()
Lparameters tcUsername, tcSerialnumber

* code to store that registration in a database
* check it with existant registrations etc.

Return .T. && successful registration
EndProc

Procedure unregister()
Lparameters tcUsername, tcSerialnumber

* code to delete a registration in a database

Return .T. && successful unregistration
EndProc
EndDefine


b) a WSDL web service description and WSML Web service mapping file

Both these file are created, if you start the soap toolkit WDL Generator. You can either choose these files to be generated for more direct execution of the webservice via ISAPI listerner or let it generate an ASP listener skript, with which you can also interfere soap messages. Follow the steps of the Generator and you will also get an idea where to upload the files.

c) IIS with the server component of the soap toolkit (SOAPIS30.DLL) installed and configured correctly.

That's it, mostly.

So you will at least once need access to IIS administration/management to setup the IIS for accepting web service calls.

Each piece of the puzzle is simple. Perhaps the greatest hurdle is to have a webhost enabling IIS with the SOAPIS30.DLL.

Oh, take a look at the SOAP Toolkit help that's in start menu.

Bye, Olaf.