1. test.htm: A sample user interface (a button) that calls the show bidroom status program JSP. (see http://www.jsptut.com/ for a JSP tutorial)
2. ShowBidRoomStatus.jsp: A ShowBidRoomStatus sample program.
3. ChronobotTaglib.tld: A web service definition file. It needs to be updated if a new service (class) is created.
4. web.xml: The database definition file. If the database definition is changed, this file needs to be updated. (For experimental application development, database definition file should not be changed!)
5. The Chronobot Bid Manager Documentation BidManagerDoc.pdf: The full documentation of the Chronobot Web service.
To develop an application you need to create the user interface (following the example test.htm), the jsp application program (following the example ShowBidRoomStatus.jsp), modify the web service definition file ChronobotTaglib.tld, and ftp these three files to the testbed's ftp directory. The database definition file should not be changed. Since all the students are sharing the same testbed, there may be occasional conflicts in updating the file ChronobotTaglib.tld. Therefore please always restore the original web service definition file when you are done.
An application example can be found at: http://chronobot.ksi.edu:8080/pitt2Chronobot/cs1631/login.html This example EX1 retrieves, creates and updates user profiles using chronobot webservice. (In the instructor's notebook it is in directory d:\cserviceEx1) To try it, user name is "admin1234" and password is "pitt1234". Or user name is "cb1" and password is "cb1".
The chronobot bid manager database has the following database schema: