University of Wisconsin-Madison Skip navigationUW-Madison Home PageMy UW-MadisonSearch UW
UW-Madison > Middleware  

 

Architectural Overview of Middleware WebServices


THE USUAL APPLICATION SOLUTION: Applications incorporate clients for each type of database access. Connection and database implementation details are hard-coded in the application.
  • Step 1: The application, portal, or web site that end users interact with.
  • Step 2: Lots of overhead and implementation specific programming
  • Step 3: Data that exists in ORACLE and/or LDAP.


A BETTER SOLUTION: Applications use a web service client to interact with web service APIs. The database implementation and access details are removed from the client and encapsulated in the web service.
  • Step 1: The application, portal, or web site that end users interact with.
  • Step 2: Data is exchanged as XML via a request/response mechanism.
  • Step 3: Tables, data formats, entries, etc. not important to the client.

 
Middleware | UW Home

File last updated: Month 01, 2002
Feedback, questions or accessibility issues: mst-ws@lists.wisc.edu
Copyright © 2002 The Board of Regents of the University of Wisconsin System.