Vault Application Architecture

[happyj]

I am attempting to put together an architectural overview of Vault. It is from the infrastructure viewpoint of Vault so I am looking for how the application works at the server level. Our design will use an enterprise MSSQL backend and I can depict that connection and protocol usage pretty easily. What I need it what components does Vault use on the IIS\Vault server? ex. Client connects via Java to IIS, IIS connects to OS through what component? Or Admin tool (thick) client connects to a comm object...

GOt any ideas on how i can geet this kind of information. I know i could figure it out with proccessmon or and equivilant.

Thanks in advance.
Happyj

[Beth]

Vault's entire architecture is a multi-tier architecture utilizing SOAP/We Services.

a) Client connects to IIS / Vault Server through HTTP/SOAP requests.
The presentation tier is handled by the various clients (GUI, IDE, VSIP, Eclipse, Web, etc.)

b) Server is an IIS/ASP.NET application which handles all client and admin requests. Server also contains a "data-tier" component which connects directly to SQL Server and strictly controls data retrieved and stored by the server.