Web service Search and execution engine (5)-system running interface display

In order to better expand the following summary document, I first paste the system running example-some interfaces first, in the following interface, they all participate in system activities as Web service consumers, but are not posted on the Web service provider's system interface. The following shows the interface in two parts, the first part is browser-based users, and the second part is mobile client-based users.

Web service Search and calling process (based on browser)

(The JSP page shown below is our cactus team Li kaike students (happy20110231@yahoo.com.cn) concentrate on the design, thank him for his hard work!

After successfully logging on to the web service user, go to the following page:

Figure 1 service consumer's personal consumption service record page Figure 1 shows his service consumption record, which records the service that the consumer consumed before, and whether the operations of the Service are successfully performed. You can click the home page or return to enter the search page: Figure 2 search page, enter the service keyword you want to execute, such as course selection, and click search, go to the search results page. Figure 3 the search results page is a remote web service. Select the one you want and click it to enter the following page: figure 4 service details figure 4 all operations of the web service on the left, and some basic information of the service provider and service on the right, which is similar to the information provided by the UDDI service resource library, for example, in the yellow pages, you can enter the information and perform any operation. Enter the course number to obtain the course information, as shown in Figure 5. On the service information entry page, enter the course number 1111, you can get the course information with the course number 1111 (here we do it ourselves. and click Submit. The execution result is displayed. Figure 6 shows the service execution result page, our system background shields users from complicated traditional operations. Service search and calling process (based on mobile phone)

Considering that the mobile client is a limited display space and other constraints, this module currently has some functional limitations, such as only providing web services for users to search and execute web services, that is to say, Web service providers cannot publish web services to our system through mobile phones. In addition, during the development of the mobile client, I developed the mobile client with the touch simulator of Motorola 1200, but the simulator does not support Chinese Characters During the debugging process, therefore, it can only be run after packaging. the JAD file starts a default simulator provided by Sun that supports Chinese characters for debugging. The client program of this mobile phone has passed the real machine test of Motorola's 1200 mobile phone. After successfully logging on to the web service user, go to the Web Service search page: Figure 7 after the user enters the keyword weather of the Web service to be searched on the service search page, the agent connects to the servlet of the J2EE server and searches for the result. The result is displayed to the mobile phone user. Figure 8 Web Service search result page after you select the first service, the detailed information about the Web Service is displayed. Figure 9 user-selected operation 2 on the service operation information page, and then the page for this operation is displayed. 10. Enter the city name Shenyang that you want to search for, and click "run, we can see all the weather information about the city of Shenyang, 11: Figure 10 web service operation information page Figure 11 the operation execution result page displays only a part of the information displayed on the client when the system is running. Many details are not posted. The system's server programs run on our lab's personal desktop. When we register a campus network number, browser users can access the test via the Internet: http: // 202.118.22.171: 8080/serviceengine/index. JSP