System Functionality and Architecture


The basic functionality of our Enterprise Procurement System (EPS) application is to:

  • Provide a Web-based interface that allows users to browse a catalog of goods and services from which they can select a particular part number.

  • Provide a Web-based interface that allows users to enter a part number to be located, the desired quantity, and whether the user is interested in optimizing for cost (if a high-volume product is being built) or for lead time (if a prototype needs to be built rapidly).

  • Connect to the Web services of a set of vendors and use the entered part number, quantity, and optimization criteria (cost or lead time) to get a price or lead time quote.

  • Analyze the returned values from the vendor Web services, and select the best choice.

  • Present the best price or lead-time from the available vendors that meet the user's procurement needs.

  • If the part cannot be located, consult another Web service to find alternate part numbers that may have similar functionality to that of the first part.

  • Present the alternate part number to the user; otherwise, inform the user that there is no such alternate part.

Figure 12-2 shows a block diagram depicting the overall system architecture of the EPS application.

Figure 12-2. Block diagram depicting the overall system architecture of the EPS application.

graphics/12fig02.jpg

The Web browser client first accesses the EPS.html file, which is a static HTML form where the user enters the desired part number, quantity, and optimization metric. A hyper link on the EPS.html page also takes the user to the EPSCatalog.html, which is another static HTML page displaying the vendors, part numbers, and product descriptions.

The form data from the EPS.html page is sent to a J2EE Servlet, ServiceServlet. The Servlet analyzes the form data and connects to the Web services of two vendors Vendor A and Vendor B in an effort to locate the best price or lead time for the given part number. If the two vendors do not have the part or do not have it in sufficient quantity, the Servlet then connects to the AltPart Web service in an effort to locate alternate part numbers. Based on the information from the Web services, the ServiceServlet formulates the information to be returned to the user and forwards it to the OutputServlet. The OutputServlet takes the information from the ServiceServlet and simply formats and presents it to the user.

The EPS application that we implement here is straightforward. Our objective is to demonstrate a real-world, enterprise usage of Web services and not to implement a full-featured procurement system. Additional capabilities such as a dynamic catalog that sources the parts available from each vendor Web service as well as an order placement and delivery management dashboard can be added.



Developing Enterprise Web Services. An Architect's Guide
Developing Enterprise Web Services: An Architects Guide: An Architects Guide
ISBN: 0131401602
EAN: 2147483647
Year: 2003
Pages: 141

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net