JP2005078339A - Wsdl document preparation device and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily attain failure recovery when any failure occurs concerning a technology to execute load distribution by using a WSDL (Web Services Description Language). <P>SOLUTION: A WSDL server 2 is provided with: a network interface part 21 which receives a message of requesting a WSDL document from a client 1; a Web service table 23 which stores the information of a Web service; a WSDL generating part 22 which generates the WSDL document by referring to the request message and the Web service table 23; an AP server monitoring part 25 which monitors the operating status of each AP server 3; a monitor information file 26 which stores the operation information of each AP server 3 collected by the AP server monitoring part 25; and a load distribution processing part 24 which distributes the request of the Web service to each AP server 3 on the basis of the operation information of the monitor information file 26. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a technique for distributing and processing Web service requests, and more particularly to a technique for performing load distribution using WSDL (Web Services Description Language).

  Web service technology is one of Web related technologies. Web service technology refers to technology that links applications existing on a network by exchanging messages in XML (eXtensible Markup Language) format. An application using Web service technology is called a Web service. As a language for describing a web service interface, a destination, and the like, there is XML format WSDL (Web Services Description Language). In the Web service, a WSDL document described in WSDL is prepared, and interface information necessary for using the Web service is described.

  In addition, as a method for load distribution of Web services, it is common to use a load distribution device that distributes requests from clients to a plurality of servers (for example, Non-Patent Document 1).

"Nikkei Internet Solution", Nikkei BP, May 2003, p74-82

  By the way, unlike a conventional Web system in which a server processes a request from a client and transmits the processing result to the client, the Web service itself calls a plurality of other Web services, It can be performed in one process (one transaction). That is, the Web service itself can serve as a client and make a request to another server.

  However, the conventional load balancer does not consider failure recovery when a failure occurs when calling a plurality of Web services in one process (one transaction). For example, when a Web service that has received a commit instruction from a client performs processing with two-phase commit, a failure may occur after the end of the first phase and before the end of the second phase. In this case, since the request from the client is distributed to a plurality of servers by the conventional load balancer, the client itself does not know the destination of the server that provides the Web service. For this reason, it is very difficult to perform this failure recovery processing.

  In addition, when a conventional load distribution apparatus is applied to a Web service, it is necessary to use at least one load distribution apparatus for each Web service, as shown in FIG. In the example illustrated in FIG. 8, the client 1 calls a Web service of service A or service D. In the Web service of service A, the Web service itself calls the Web service of service B, and the Web service of service B calls the Web service of service C. In this case, a load distribution apparatus 8a for service A that distributes requests to a plurality of servers 81 that provide service A, a load distribution apparatus 8b for service B that distributes requests to a plurality of servers 82 that provide service B, At least one load distribution device 8c for service C that distributes requests to a plurality of servers 83 that provide service C is required. The Web service of service D calls the Web service of service E by itself. Also in this case, at least one load distribution device 8d for service D and one load distribution device 8e for service E are required.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to facilitate failure recovery when a failure occurs. Another object of the present invention is to reduce the investment burden of a redundantly configured system and distribute Web service requests.

  In order to solve the above problem, in the present invention, a terminal device directly requests a Web service from a server using a WSDL document generation device that dynamically generates a WSDL document.

  For example, the WSDL document generation apparatus according to the present invention includes a message accepting unit that accepts a request message including a service name, which requests a WSDL document, from the terminal device, and a service name of the Web service for each at least one Web service, Service information storage means storing interface information and at least one address information, and stored in the service information storage means in association with the service name included in the request message received by the message reception means. WSDL generation means for generating a WSDL document using the interface information and address information, and a WSDL transmission means for transmitting the WSDL document generated by the WSDL generation means to the terminal device that is the transmission source of the request message; Have.

  The WSDL document generation apparatus of the present invention may further include a selection unit that selects one piece of address information from the plurality of pieces of address information.

  Embodiments of the present invention will be described below.

  FIG. 1 is an overall configuration diagram of a Web service system 10 to which an embodiment of the present invention is applied.

  As shown in the figure, the Web service system 10 of this embodiment includes a plurality of clients 1, a WSDL server 2, and a plurality of application servers (hereinafter referred to as AP servers) 3. The client 1 is connected to the WSDL server 2 and the AP server 3 via a network 9a such as the Internet. Further, the WSDL server 2 and each AP server 3 are connected by a network 9b such as an intranet in order for the WSDL server 2 to monitor the operating state of the AP server 3.

  The client 1 is a terminal device of a Web service user. When calling (requesting) a Web service, the client 1 first requests a WSDL document for generating a stub required for calling the Web service from the WSDL server 2 via the network 9a. Then, the client 1 dynamically generates a stub from the WSDL document generated by the WSDL server 2 and calls a Web service to the AP server 3 using this stub. A stub is an object that runs on a client and communicates with an application of another device.

  The WSDL server 2 is a device that receives a request from the client 1 via the network 9a, generates a WSDL document for calling a Web service based on the request, and transmits the generated WSDL document to the requesting client 1. is there. Then, the WSDL server 2 sets a destination of the AP server 3 and generates a WSDL document in order to distribute the load among the AP servers 3.

  The AP server 3 is a device that provides a Web service that is an application using a Web service technology. The AP server 3 stores application programs and data necessary for the Web service, and provides various Web services in response to requests from the client 1. For example, in the Web service system 10 of FIG. 1, the AP server (A) 3 and the AP server (B) 3 provide the Web service of the service A. The AP server (N) 3 provides a service B Web service.

  Next, each configuration of the client 1 and the WSDL server 2 will be described.

  First, the client 1 will be described. As shown in FIG. 1, the client 1 includes a network interface unit 11, a WSDL request unit 12, a stub generation unit 13, a web service call unit 15, and a business processing unit 16.

  The network interface unit 11 transmits and receives messages or data to and from the network 9a.

  The WSDL request unit 12 requests a WSDL document from the WSDL server 2 via the network interface unit 11. Specifically, the WSDL request unit 12 receives a Web service call instruction with a service name and protocol type (communication procedure) of the Web service from an input device (not shown), and a WSDL request message including the service name and protocol type. Send.

  The stub generation unit 13 dynamically generates the stub 14 from the WSDL document acquired from the WSDL server 2 via the network interface unit 11. Alternatively, the stub generation unit 13 may extract the destination of the AP server 3 from the WSDL document dynamically acquired by the WSDL request unit 12 and set the destination of the AP server 3 in a stub generated in general. Good. Here, the stub 14 is an object for communicating with the Web service generated by the stub generation unit 13.

  The Web service calling unit 15 uses the stub 14 dynamically generated by the stub generating unit 13 to call (request) the Web service to the AP server 3 that provides the Web service set in the WSDL document. Then, the business processing unit 16 receives the processing result of the Web service from the AP server 3 and performs predetermined business processing.

  Next, the WSDL server 2 will be described. As shown in FIG. 1, the WSDL server 2 includes a network interface unit 21, a WSDL generation unit 22, a web service table 23, a load distribution processing unit 24, an AP server monitoring unit 25, a monitoring information file 26, Have

  The network interface unit 21 transmits and receives messages or data to and from the network 9a. For example, the network interface unit 21 receives a WSDL request message from the client 1 via the network 9a, and outputs a WSDL document generated based on the WSDL request message.

  The WSDL generation unit 22 refers to the Web service table 23 based on the WSDL document request message received by the network interface unit 21 and generates a WSDL document. The generation of the WSDL document will be described later with reference to FIGS.

  The web service table 23 is stored in a storage device (not shown), and information on web services provided by the web service system 10 is registered. For example, the Web service table 23 has a structure as shown in FIG. That is, in the Web service table 23, a service name 231 of the Web service and an interface definition 232, a protocol type 233, and an address 234 are registered corresponding to the service name 231.

  In the service name 231, the name of the Web service is registered, and in the example illustrated in FIG. 2, service A and service B are registered.

  The interface definition 232 describes the format of an input message for requesting a Web service and an output message for providing a service result. For example, the data type for each message (string, string, decimal, etc.), parameters embedded in the input message, etc. are described. In addition, information of a port in which related messages are combined is described. Specifically, the message definition and port definition of a WSDL document (see FIG. 6) to be described later are described in WSDL.

  In the protocol type 233, a communication procedure (remote calling procedure) used when calling a Web service to the AP server 3 is registered. For example, there are SOAP (Simple Object Access Protocol) protocol, EJB (Enterprise JavaBeans) call, Java (registered trademark) local function call, and the like. In the example shown in FIG. 2, a SOAP protocol, an EJB call, and a Java local function call are registered as communication procedures for calling the service A.

  In the address 234, a Web service providing location corresponding to the service name and the protocol type is registered. The address 234 includes information for specifying the AP server 3 that provides the Web service (the destination of the AP server 3). For example, a URL (Uniform Resource Locator) may be used for the address 234. In the example illustrated in FIG. 2, the URLs of the AP server (A), the AP server (B), and the AP server (C) are registered as addresses of Web services that provide the service A using the SOAP protocol. In the present embodiment, each AP server 3 provides one Web service. That is, each AP server 3 has a corresponding Web service address 234.

  The AP server monitoring unit 25 continuously measures (or collects regularly from each AP server 3) the operating state of each AP server 3, for example, the CPU usage rate, the memory usage rate, the number of connection requests per unit time, and the like. ) And monitor. For example, the AP server monitoring unit 25 issues a command for measuring the CPU usage rate or the like to each AP server 3 at a predetermined time interval and measures the CPU usage rate or the like. Alternatively, log information output by an OS (Operating System) function of each AP server 3 is periodically referred to, and a CPU usage rate or the like is acquired.

  Then, the AP server monitoring unit 25 stores these measured or collected information in the monitoring information file 26. The AP server monitoring unit 25 also monitors whether or not a failure has occurred in each AP server 3 and sets a failure flag in the monitoring information file 26 when a failure has occurred.

  The monitoring information file 26 is stored in a storage device (not shown), and operation information of each AP server 3 measured or collected by the AP server monitoring unit 25 is stored. For example, the monitoring information file 26 has a structure as shown in FIG. That is, the monitoring information file 26 stores the above-described Web service address 261, CPU usage rate 262, memory usage rate 263, and failure flag 264 for each AP server 3.

  When there are a plurality of Web service addresses of the specified protocol type (communication procedure) with the service name specified in the WSDL request message from the client 1, the load distribution processing unit 24 corresponds to each of the plurality of addresses. One AP server 3 is specified so that the load among the AP servers 3 to be distributed is distributed. For example, the load distribution processing unit 24 refers to the monitoring information file 26 (see FIG. 3) described above, compares the CPU usage rate of each of the target AP servers 3, and has the lowest CPU usage rate. 3 is specified. Further, the load distribution processing unit 24 may refer to the monitoring information file 26 and compare the memory usage rates to identify the AP server 3 having the lowest memory usage rate. Alternatively, the load of each AP server 3 may be determined using both the CPU usage rate and the memory usage rate, such as specifying the AP server 3 having the lowest value of the CPU usage rate and the memory usage rate. . Then, the load distribution processing unit 24 can specify the address of one corresponding Web service by specifying one AP server 3. Further, the load distribution processing unit 24 excludes the AP server 3 in which the failure flag is set from the target.

  As described above, the load distribution processing unit 24 refers to the monitoring information file 26, determines only the load of each normal AP server 3 and determines the load of each normal AP server 3, and the AP having the lowest load. The server 3 is specified. Thereby, fine load distribution according to the processing capability of the AP server 3 can be realized.

  Further, the load distribution processing unit 24 may specify the AP server by round robin. That is, the load distribution processing unit 24 sequentially specifies the addresses of a plurality of Web services determined by the service name and protocol type (communication procedure) specified by the client 1 in a predetermined order. For example, the Web service table 23 may be referred to and the addresses of the Web service may be sequentially specified in the registered order in the address 234 column of the Web service table 23.

  Thereby, it is possible to prevent requests from being concentrated on one AP server 3, to equalize the number of connection requests among a plurality of AP servers 3, and to distribute the load.

  In the present embodiment, a plurality of WSDL servers 2 having the above-described configuration may be provided. In this case, each WSDL server 2 independently accepts a WSDL request message from each client 1 and transmits the generated WSDL document to the requesting client 1.

  The client 1, WSDL server 2, and AP server 3 described above all include, for example, a CPU 901, a memory 902, an external storage device 903 such as an HDD, and an input device 904 such as a keyboard and mouse as shown in FIG. 4. And a general-purpose computer system including an output device 905 such as a monitor or a printer and a communication control device 906 for network connection, the CPU 901 executes a predetermined program loaded on the memory 902. Realized. For example, each function of the WSDL server 2 and the client 1 is realized by the CPU 901 of the client 1 executing the program for the client 1 and the CPU 901 of the WSDL server 2 executing the program for the WSDL server 2 respectively. Is done. In this case, the memory 902 or the external storage device 903 is used for the Web service table 23 and the monitoring information file 26 of the WSDL server 2.

  Next, the processing procedure of the WSDL server 2 will be described using the flowchart shown in FIG.

  First, the network interface unit 21 receives a WSDL request message including a service name and a protocol type from the client 1 (S11), and sends the received message to the WSDL generation unit 22. Then, the WSDL generation unit 22 refers to the Web service table 23 (S12), and selects the address of the target Web service from the service name and protocol type included in the WSDL request message (S13).

  Next, the WSDL generation unit 22 determines whether there are a plurality of addresses of the selected Web service (S14). When there are a plurality of Web service addresses (S14: YES), the WSDL generation unit 22 delivers the information of the selected plurality of addresses to the load distribution processing unit 24. As described above, the load distribution processing unit 24 refers to the monitoring information file 26 and identifies the AP server 3 with the least load from the plurality of AP servers 3 respectively corresponding to the selected plurality of addresses. . Then, the load distribution processing unit 24 specifies the address of the Web service corresponding to the specified AP server 3 (S15). Alternatively, the load distribution processing unit 24 specifies the addresses of the Web services in order by round robin from the selected addresses of the Web services (S15).

  Then, the WSDL generation unit 22 determines the address of the Web service specified by the load distribution processing unit 24 as the Web service destination of the WSDL document (S16). If the address of the target Web service is one (S15: NO), the WSDL generation unit 22 determines the address of the Web service as the Web service destination of the WSDL document (S16).

  Next, the WSDL generation unit 22 generates a WSDL document (S17). Taking the WSDL document shown in FIG. 6 as an example, generation of a WSDL document will be described. As shown in the figure, the WSDL document is described in an XML format, and includes an XML declaration 60, a message definition 61, a port definition 62, a binding definition 63, and a service definition 64.

  The XML declaration 60 is stored in advance in a storage device (not shown) of the WSDL server 2, and the WSDL generation unit 22 generates the XML declaration 60 using the stored XML declaration 60.

  The message definition 61 defines interfaces (formats) of input messages and output messages used in the Web service. The port definition 62 defines a port that is a combination of the messages defined in the message definition 61. The message definition 61 and the port definition 62 are registered in advance in the interface definition 232 of the Web service table 23 as described above. After generating the XML declaration 60, the WSDL generation unit 22 generates the message definition 61 and the port definition 62 using the interface definition 232 corresponding to the service name included in the WSDL request message.

  The binding definition 63 defines the protocol type (communication procedure) of the port defined in the port definition 62. In the example shown in FIG. 6, it is described that the SOAP definition is used in the binding definition 63. After generating the message definition 61 and the port definition 62, the WSDL generation unit 22 uses the service name and protocol type included in the WSDL request message, the message definition 61, and the port definition 62, and the WSDL description format of the protocol type. Thus, the binding definition 63 is generated.

  The service definition 64 defines a destination (address) of the Web service at the port defined by the binding definition 63. In the example illustrated in FIG. 6, a URL described after “soap: address location” is defined. After generating the binding definition 63, the WSDL generating unit 22 determines the address of the Web service determined in S16, the service name and protocol type included in the WSDL request message, the message definition 61, the port definition 62, and the binding definition 63. And the service definition 64 is generated in the WSDL description format of the protocol type.

  As described above, the WSDL generation unit 22 generates a WSDL document from information included in the WSDL request message, information registered in the Web service table 23, and information necessary for generating the WSDL document such as a WSDL description format. (S17). Then, the WSDL generation unit 22 transmits the generated WSDL document to the requesting client 1 via the network interface unit 21 (S18).

  Next, the processing of the client 1 will be described using the flowchart shown in FIG.

  The WSDL request unit 12 receives a web service call instruction with a service name and a protocol type (communication procedure) from an input device (not shown). Upon receiving this call instruction, the WSDL request unit 12 transmits a WSDL request message to the WSDL server 2 via the network interface unit 11 (S21). This WSDL request message includes a service name and a protocol type (communication procedure). Then, the WSDL request unit 12 receives the WSDL document generated by the above-described processing of the WSDL server 2 (see FIG. 5) from the WSDL server 2 (S22).

  Next, the stub generation unit 13 generates a stub 14 from the received WSDL document (S23). Then, the web service calling unit 15 uses the generated stub 14 to call the web service with the address of the web service set in the WSDL document as a destination (S24). The business processing unit 16 receives the processing result of the Web service and performs a predetermined business process (S25).

  When the Web service itself called by the client 1 calls another Web service, the AP server 3 that provides the called Web service performs the same process as the client 1 (see FIG. 7). Then, the WSDL document of the Web service to be called next is acquired. That is, the AP server 3 acquires a WSDL document by transmitting a WSDL request message to the WSDL server 2 and acquires an address of a Web service set in the WSDL document. Then, the AP server 3 calls the next Web service with the address of this Web service as a destination. In this case, the AP server 3 needs to have the same function as the client 1 (see FIG. 1).

  As a result, even when a plurality of Web services are called in one transaction, it is possible to perform load distribution processing between a plurality of AP servers that provide each Web service. In addition, since the client 1 or the AP server 3 always obtains the address of the Web service that provides the Web service called by the client 1 or the AP server 3 after the end of the first phase of the two-phase commit, the client 1 or the AP server 3 Even if a failure occurs before the end of the second phase, the failure recovery process can be easily performed.

  In addition, as a method of calling another Web service by the Web service itself called by the client 1, an address of a Web service that provides a Web service to be called next by the Web service called by the client 1 is set in advance. It is good also as setting. Accordingly, it is possible to easily call another Web service without accessing the WSDL server 2.

  In the present embodiment, the client 1 directly calls (requests) the Web service to the AP server 3 having the address of the Web service described in the WSDL document dynamically acquired in consideration of the load status from the WSDL server 2. . As a result, even if a failure occurs when calling a plurality of Web services in one process (one transaction), the failure recovery operation can be easily performed.

  In the present embodiment, the WSDL server 2 performs load distribution processing for each Web service in response to requests for all Web services (including requests that the Web service becomes a client and issues to other Web services). Do. That is, the WSDL server 2 of this embodiment is a load distribution apparatus that can be shared by a plurality of Web services. Thereby, it is not necessary to provide a load distribution device for each Web service, and a simple system configuration can be realized.

  In addition, this invention is not limited to said embodiment, Many deformation | transformation are possible within the range of the summary. For example, in the Web service table 23 (see FIG. 2) of the above embodiment, the contents of the interface definition of the WSDL document are stored in the interface definition 232 field as they are. However, the file storing the interface definition contents may be separately stored in a storage device, and in the Web service table 23, the file name storing the interface definition may be stored in the interface definition 232 column.

  The WSDL request message transmitted by the client 1 of the above embodiment includes a service name and a protocol type. However, the protocol type may not be included in the WSDL request message. In this case, a default protocol type for each Web service is preset in the Web service table 23, and the WSDL generation unit 22 may generate a WSDL document of this default protocol type.

  Further, the AP monitoring unit 25 and the monitoring information file 26 of the above embodiment are included in the WSDL server 2. However, an operation server different from the WSDL server 2 may be provided, and this operation server may realize the functions of the AP monitoring unit 25 and the monitoring information file 26. In addition, the AP monitoring unit 26 not only measures or collects the operation information of each AP server 3, but also collects information necessary for registration of the Web service table 23 from each AP server at a predetermined timing. Maintenance such as addition, change, or deletion of 23 may be automatically performed.

  In the above embodiment, each AP server 3 provides one Web service, and each AP server 3 has one Web service address. However, one AP server 3 may provide a plurality of Web services. In this case, the AP server 3 has a plurality of Web service addresses.

FIG. 1 is a diagram showing an overall configuration of a Web service system to which an embodiment of the present invention is applied. FIG. 2 is a diagram illustrating an example of the data structure of the Web service table. FIG. 3 is a diagram illustrating an example of the data structure of the monitoring information file. FIG. 4 is a diagram illustrating a hardware configuration example of the client, the WSDL server, and the AP server. FIG. 5 is a flowchart showing the processing procedure of the WSDL server. FIG. 6 is a diagram illustrating an example of a WSDL document. FIG. 7 is a flowchart showing the processing procedure of the client. FIG. 8 is a diagram showing a configuration of a Web service system using a conventional load distribution apparatus.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Client, 2 ... WSDL server, 3 ... AP server, 9a ... Network, 9b ... Network, 10 ... Web service system, 11 ... Network interface part, 12 ... WSDL request part, 13 ... Stub generation part, 14 ... Stub, DESCRIPTION OF SYMBOLS 15 ... Web service calling part, 16 ... Business processing part, 21 ... Network interface part, 22 ... WSDL production | generation part, 23 ... Web service table, 24 ... Load distribution processing part, 25 ... AP server monitoring part, 26 ... Monitoring information file

Claims (10)

A WSDL document generation device that provides a WSDL document used for a web service request provided by an information processing device to a terminal device,
Message accepting means for requesting a WSDL document and receiving a request message including a service name from the terminal device;
Service information storage means for storing the service name, interface information, and at least one address information of at least one Web service;
WSDL generation means for generating a WSDL document using interface information and address information stored in the service information storage means in association with the service name included in the request message received by the message reception means;
A WSDL document generation device, comprising: a WSDL transmission unit configured to transmit the WSDL document generated by the WSDL generation unit to the terminal device that is a transmission source of the request message. The WSDL document generation device according to claim 1,
When there are a plurality of the address information, the plurality of address information is allocated to a plurality of different information processing devices,
A selection unit that selects one piece of address information from the plurality of address information; and an operation information storage unit that stores operation information of each of the plurality of information processing apparatuses,
The selection means includes operation information of each information processing apparatus corresponding to a plurality of address information stored in the service information storage means in association with a service name included in the request message received by the message reception means. Is searched from the operating information storage means, one address information is selected based on the searched operating information,
The WSDL document generation device, wherein the WSDL generation unit generates a WSDL document of the Web service using the address information selected by the selection unit. The WSDL document generation device according to claim 1,
A selection means for selecting one address information from the plurality of address information;
The selection means selects one of a plurality of address information stored in the service information storage means in association with a service name included in the request message received by the message reception means according to a predetermined order. ,
The WSDL document generation device, wherein the WSDL generation unit generates a WSDL document of the Web service using the address information selected by the selection unit. The WSDL document generation device according to any one of claims 1 to 3,
The service information storage means stores the address information in association with the protocol type used by the Web service,
The message accepting means accepts the request message including a service name and a protocol type from the terminal device,
The WSDL generation unit uses the address information stored in the service information storage unit in association with the service name and the protocol type included in the request message received by the message reception unit. A WSDL document generation apparatus characterized by generating a WSDL document. A program that operates in a WSDL document generation device that provides a WSDL document used for a Web service request provided by an information processing device to a terminal device,
The program is stored in the WSDL document generation device.
A message receiving means for requesting a WSDL document and receiving a request message including a service name from the terminal device;
Service information storage means for storing the service name, interface information and at least one address information of the Web service for each at least one Web service;
WSDL generation means for generating a WSDL document using the interface information and address information stored in the service information storage means in association with the service name included in the request message received by the message reception means; and ,
A program that causes a WSDL document generated by the WSDL generation unit to function as a WSDL transmission unit that transmits the request message to the terminal device that is a transmission source of the request message. A WSDL document generation method for generating a WSDL document used for a web service request provided by an information processing apparatus and providing the WSDL document to a terminal apparatus,
Receiving a request message including a service name for requesting a WSDL document from the terminal device;
A reference step for referring to a storage unit storing a service name, interface information, and at least one address information of the Web service for each of at least one Web service;
A WSDL generation step of generating a WSDL document using the interface information and the address information stored in the storage means in association with the service name included in the request message received in the reception step;
A WSDL document generation method, comprising: a transmission step of transmitting the WSDL document generated by the WSDL generation step to the terminal device that is a transmission source of the request message. A terminal device that makes a request for a Web service provided by the information processing apparatus to the information processing apparatus,
WSDL request means for requesting a WSDL document used for the request of the Web service, sending a request message including a service name to the WSDL document generation device, and receiving the WSDL document of the Web service from the WSDL document generation device; ,
Stub generation means for generating a stub used for the request of the Web service using the WSDL document received by the WSDL request means;
A terminal device comprising: request means for transmitting a request for the Web service to an information processing apparatus that provides the Web service using the stub generated by the stub generation means. A program that runs on a terminal device that makes a request for a Web service provided by the information processing device to the information processing device,
The program is stored in the terminal device.
WSDL request means for requesting a WSDL document used for the Web service request, including a service message including a service name, and receiving the WSDL document of the Web service from the WSDL document generation device;
Stub generation means for generating a stub used for the request of the Web service using the WSDL document received by the WSDL request means; and
A program that causes an information processing apparatus that provides the Web service to function as a request unit that transmits a request for the Web service, using the stub generated by the stub generation unit. A method of requesting an information processing apparatus for a Web service provided by the information processing apparatus,
A WSDL request step for requesting a WSDL document used for the request of the Web service, transmitting a request message including a service name to the WSDL document generation device, and receiving the WSDL document of the Web service from the WSDL document generation device; ,
Using the WSDL document received in the WSDL request step, a stub generation step for generating a stub for use in the Web service request;
A method for performing a web service request, comprising: a transmission step of transmitting the web service request to an information processing apparatus that provides the web service using the stub generated in the stub generation step. A WSDL document generation system for providing a WSDL document used for a web service request provided by an information processing device to a terminal device,
The WSDL document generation system includes a WSDL document generation device and at least one terminal device,
The WSDL document generation device
Message accepting means for requesting a WSDL document and receiving a request message including a service name from the terminal device;
Service information storage means for storing the service name, interface information, and at least one address information of at least one Web service;
WSDL generation means for generating a WSDL document using interface information and address information stored in the service information storage means in association with the service name included in the request message received by the message reception means;
WSDL transmitting means for transmitting the WSDL document generated by the WSDL generating means to the terminal device that is the transmission source of the request message,
The terminal device
A WSDL requesting unit for requesting a WSDL document, transmitting a request message including a service name to the WSDL document generating device, and receiving the WSDL document transmitted by the WSDL transmitting unit;
Stub generation means for generating a stub used for the request of the Web service using the WSDL document received by the WSDL request means;
A WSDL document generation system comprising: request means for transmitting a request for the Web service to an information processing apparatus having address information of the Web service using the stub generated by the stub generation means.