Ideas for the Xml Soap Server for Quickbooks

To make it easier to build applications that access Quickbooks data, a xml soap server will need to be built that could be pointed to any number of company files.

Due to the limitations of the Quickbooks server, only one company file can be accessed at a time.

The Xml Soap server that is needed to provide the webservice methods to Quickbooks thru the Quickbooks Sdk should probably come in several flavors:

1. A standalone version.
2. A Windows service version.
3. A webserver version running as an IIS isapi dll.

The standalone version would be able to show a visual log of requests and responses. That would make it easy to determine qbxml request problems.

All versions should require either or both http basic login and webservice login user name and password. Certificates could be added for added security. Allow a raw user defined xml requests webservice method in addition to the defined webservice methods.

The xml server should allow defining the company file and ports to be used so that multiples of th server could installed which could point to a number of company files and be accessible thru a number of server ports.

At the beginning, only a single login user name and password will be assigned but future development should address allowing a table of users with their security rights to individual webservice methods. Example would be allowing corporate personnel access to customer and vendor files but website entry only allowed to create a new customer invoice and receipt.

To begin the project, the standalone version will be built so that we can see processing results to speed the application development process side.

We will keep in mind that the server should be built for easy installation not by developers only but also endusers when installed with the applications.

Also we will keep in mind that we will be reselling the server component to other developers.