JP2007080053A - Xml/web service information management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an XML/Web service information management system allowing registration, deletion or the like of XML/Web service information in a UDDI registry according to a situation of XML/Web service. <P>SOLUTION: An XML/Web service registration information generation part 120 of an XML/Web service server 100 acquires information from a header part of a prescribed format previously included in a service code of the XML/Web service 110A, 110B, etc. stored in an XML/Web service storage part 110, and generates XML/Web service registration information and XML/Web service management information. An XML/Web service information management part 150 monitors a state of the XML/Web service, decides an operation state of deletion, a disclosure stop, restoration or the like, and performs the registration, the deletion, reregistration or the like of the XML/Web service information to the UDDI registry on the basis of a decision result. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a system for managing registration / deletion of XML / Web service information to / from an UDDI server in an XML / Web service system in which an XML / Web service, a Web service client, and a UDDI server operate in cooperation.

In recent years, client / server system applications and Web application systems on the Internet and intranets have become widespread as applications. Under such circumstances, a technology called XML / Web service has emerged in response to a request for linking applications held by each company / organization, and this XML / Web service is currently attracting attention in the information processing industry. I'm bathing. Here, the XML / Web service employs XML (eXtensible Markup Language) technology as an interface with the outside, thereby enabling cooperation between business applications without human intervention. As technologies that form the core of XML / Web services, SOAP (Simple Object Access Protocol) as a message transmission / reception technology and WSDL (Web Service Description Language) as an interface description language are generally used.
Further, when using such an XML / Web service, the location where the XML / Web service is hosted is disclosed to a Web service client (application that intends to use the Web application) and a UDDI (Universal). Technology called Description, Discovery, and Integration) is used. This is a technology for receiving information on XML / Web service information corresponding to a certain condition from a Web service client using the XML / Web service and providing information on the XML / Web service corresponding to the search condition. .

Here, in the conventional XML / Web service system, processing such as registration and deletion of service information and the like in UDDI involves registration work by a service provider or a UDDI administrator (for example, patents). Reference 1).
Japanese Patent Laid-Open No. 2005-099969

  However, as described in Patent Document 1, if processing such as registration or deletion of service information or the like in UDDI is all based on registration work of a service provider or a UDDI administrator or the like, service disclosure and disclosure There has been a problem that appropriate service information cannot be managed and provided according to the status of the XML / Web service server, such as suspension or republication.

  The present invention is to solve the above-mentioned problem, and XML / Web service information management that enables registration / deletion of XML / Web service information in the UDDI registry according to the status of the XML / Web service server. The purpose is to provide a system.

In order to solve the above problems, the present invention registers in advance XML / Web service information to be provided to a Web service client in the XML / Web service information registration means, and passes through the XML / Web service information registration means. An XML / Web service information management system for providing XML / Web service information to a Web service client, an XML / Web service storage unit for storing an implementation code constituting the XML / Web service, and the XML / Web service An XML / Web service management information storage unit that stores management information corresponding to the XML / Web service stored in the storage unit, and an XML / Web service corresponding to the XML / Web service stored in the XML / Web service storage unit Information to be registered in the service information registration means An XML / Web service information storage unit to be stored, the implementation code is acquired from the XML / Web service storage unit, and XML / Web service information and service provider information in a predetermined format included in the implementation code are defined in advance. XML / Web service registration information generating means for storing the XML / Web service management information storage unit, the XML / Web service information storage unit, and the XML / Web service information storage unit. The XML / Web service information stored in the XML / Web service information is managed, the newly stored XML / Web service information is acquired, and is registered in the registration destination XML / Web service information registration means designated in advance. And stored in the XML / Web service management information storage unit. It characterized in that it comprises a XML / Web service information management means for setting a dynamic state in public.
Further, the XML / Web service information management means may be configured such that when the XML / Web service implementation code stored in the XML / Web service storage unit is deleted from the XML / Web service storage unit, the registration destination XML is stored. The XML / Web service information registered in the / Web service information registering unit is deleted, and the operation state stored in the XML / Web service management information storage unit is further set to delete.
Further, the XML / Web service information management means determines the operation status of the XML / Web service stored in the XML / Web service storage unit, and when the determination result is that the XML / Web service publication is stopped. And a means for deleting the XML / Web service information registered in the registration destination XML / Web service information registering means and for setting the operation state stored in the XML / Web service management information storage unit to the public stop. It is characterized by that.
Further, the XML / Web service information managing means, when the determination result of the operation status for the XML / Web service whose operation state is set to stop publishing is the XML / Web service release restart, The XML / Web service information stored in the information storage unit is re-registered in the registration destination XML / Web service information registration unit, and the operation state stored in the XML / Web service management information storage unit is reset to public. It is characterized by further comprising means for performing.

With the above configuration, according to the present invention, it is possible to easily register and manage XML / Web service information in the UDDI registry, and it is possible to greatly reduce the development man-hours and operation man-hours of the XML / Web service.
Also, by registering with the UDDI registry based on the information included in the service code (implementation code) of the XML / Web service, there is no human error when registering the XML / Web service information, and there is no inconsistency between them. Is possible.
In addition, since the status of the XML / Web service is monitored and the registered XML / Web service information is deleted from the UDDI registry in response to the deletion of the XML / Web service, the XML / Web service information is deleted via the UDDI registry. It is possible to provide only information on the XML / Web service that can be actually used to the Web service client that uses the Web service.
In addition, since the XML / Web service information is deleted and re-registered in response to the suspension / restoration of the XML / Web service, more appropriate XML / Web service information can be provided in the UDDI registry. It becomes possible.

An XML / Web service information registration system according to an embodiment of the present invention will be described below with reference to the drawings.
FIG. 1 is a block diagram showing a schematic configuration of an XML / Web service server constituting the XML / Web service information registration system according to the present embodiment.
The XML / Web service server 100 according to the present embodiment includes an XML / Web service storage unit 110, an XML / Web service registration information generation unit 120, an XML / Web service management information storage unit 130, and XML / Web service information. A storage unit 140, an XML / Web service information management unit 150, and a UDDI communication unit 160 are provided.
In the XML / Web service storage unit 110, one or a plurality of XML / Web services 110A, 110B,... Provided by each service provider are stored. In this case, service codes (implementation codes) constituting the XML / Web services 110A, 110B,... Are stored, and the service code includes a header portion of a predetermined format indicating XML / Web service information and provider information. It shall be included in advance.
The XML / Web service registration information generation unit 120 acquires information from the XML / Web services 110A, 110B,... Stored in the XML / Web service storage unit 110, and generates XML / Web service registration information. XML / Web service information reading processing unit 121, XML / Web service information conversion processing unit 122, XML / Web service information storage processing unit 123, XML / Web service provider information reading processing unit 124, XML / Web service provision Person information conversion processing unit 125, XML / Web service provider information storage processing unit 126, and schema file 127 used for each information conversion process.
The XML / Web service information reading processor 121 reads the header information of the XML / Web service code. The XML / Web service information conversion processing unit 122 reads the schema file 127 and converts information included in the header information read by the XML / Web service information reading processing unit 121 into information for UDDI registry registration. The XML / Web service information storage processing unit 123 registers the information converted for UDDI registry registration in the XML / Web service management information storage unit 130 and the XML / Web service information storage unit 140.
The XML / Web service provider information reading processing unit 124 reads XML / Web service provider information from the XML / Web service code. The XML / Web service provider information conversion processing unit reads the schema file 127 and converts the information read by the XML / Web service provider information reading processing unit 124 into information for UDDI registry registration. The XML / Web service provider information storage processing unit 126 registers the information converted for UDDI registry registration in the XML / Web service management information storage unit 130 and the XML / Web service information storage unit 140.
The XML / Web service information management unit 150 monitors the status of the XML / Web service and registers, deletes, re-registers XML / Web service information in the UDDI registry as XML / Web service information registration means. An XML / Web service information UDDI registration unit 151, an XML / Web service status monitoring unit 152, an XML / Web service information UDDI deletion unit 153, and an XML / Web service information registry change processing unit 154.
The XML / Web service information UDDI registration unit 151 registers the XML / Web service information in the UDDI registry based on the information registered in the XML / Web service management information storage unit 130 and the XML / Web service information storage unit 140. . The XML / Web service status monitoring unit 152 monitors the status of the XML / Web service, and detects deletion / release stop / recovery. Specifically, for example, “deletion” periodically checks whether an XML / Web service in which XML / Web service information is registered is stored in the XML / Web service storage unit 110. “Unpublished” means that a request request is sent to each XML / Web service at a predetermined timing, the presence / absence of a response message, the time until the response message returns, or the XML format of the response message is correct. Judgment is made based on whether or not there is. “Recovery” transmits a request request to the XML / Web service in the “public stop” state at a predetermined timing, and makes a determination about the same content as the case of “public stop” for the response message. The XML / Web service information UDDI deletion unit 153 deletes the XML / Web service information registered in the UDDI registry according to the monitoring result of the XML / Web service state monitoring unit 152. The XML / Web service information registry change processing unit 154 stores information registered in the XML / Web service management information storage unit 130 and the XML / Web service information storage unit 140 according to the monitoring result of the XML / Web service state monitoring unit 152. Make changes.
The UDDI communication unit 160 communicates a processing request from the XML / Web service information UDDI registration unit 151 or the XML / Web service information UDDI deletion unit 153 to a UDDI registry connected via a network such as the Internet.

FIG. 2 is a schematic configuration diagram of an XML / Web service system including the XML / Web service server according to the present embodiment.
FIG. 2 is a block diagram showing a schematic configuration of a general XML / Web service system.
FIG. 2 shows a configuration in the case where a Web application provided in the WWW server 201 uses an XML / Web service in business processing in response to a request from the user terminal 202.
As shown in FIG. 2, the WWW server 201 or user terminal 202 as a Web service client performs business processing in response to a request from a browser or a user operation, and uses an XML / Web service as necessary.
When using the XML / Web service, a search request for the XML / Web service is transmitted to the UDDI server 203, and the UDDI server 203 searches the UDDI registry 204 according to the search condition. Here, in the UDDI registry 204, information of a plurality of XML / Web service servers 100 is registered in advance as XML / Web service information registration means. As a result of the search, when the corresponding XML / Web service is searched, information of all searched XML / Web services is returned to the Web service client as a response message.
The Web service client that has received the response message transmits the request message to the XML / Web service server 100 based on the XML / Web service information included in the response message, and receives the service result as the response message. Execute business processing based on service results.
In the present embodiment, the XML / Web service information management unit 150 performs processing such as information registration and deletion in the UDDI registry 204 performed according to the state of the XML / Web service (public, public stop, recovery, deletion, etc.). Is supposed to do.

FIG. 3 is a diagram illustrating an example of a service code indicating an XML / Web service stored in the XML / Web service storage unit 110.
In the present embodiment, the service code 300 indicating the XML / Web service includes a header portion 301 that stores information indicating the contents of the XML / Web service in advance and a header portion 302 that stores information on the Web method.
In this example, for example, the header section 301 includes a service name, service contents, and an address for connecting to the service.

FIG. 4 is a diagram illustrating an example of provider information included in the service code of the XML / Web service.
In the present embodiment, the XML / Web service provider information file 400 is included in the service code indicating the XML / Web service.
In this example, for example, an XML / Web service provider information file 400 includes a service provider name, a contact address, and the like.

5 and 6 are diagrams illustrating an example of the schema file.
The schema files 500 and 600 are one of schema files for analyzing the service code of the XML / Web service and extracting information stored in the XML / Web service management information storage unit 130 and the XML / Web service information storage unit 140. Part.
A schema file 500 shown in FIG. 5 shows a portion corresponding to the XML / Web service provider information file 400 shown in FIG.
A schema file 600 shown in FIG. 6 shows portions corresponding to the header portions 301 and 302 of the service code 300 shown in FIG.

Next, each information storage unit that stores service code data according to an analysis result using the schema files 500 and 600 will be described.
FIG. 7 is a diagram illustrating an example of the data structure of the XML / Web service management information storage unit 130.
The XML / Web service management information storage unit 130 includes an XML / Web service table 710 and a registration destination UDDI table 720.
The XML / Web service table 710 includes data items of service ID 711, operation state 712, update date 713, and registrant 714. The service ID 711 is for uniquely identifying each XML / Web service in the XML / Web service server, and is set by the XML / Web service information storage processing unit 123. The operation status 712 stores statuses “public”, “public stop”, and “delete” based on the monitoring result of the XML / Web service status monitoring unit 150. Here, “public” indicates a state in which the XML / Web service stored in the XML / Web service storage unit 110 can be provided. “Public stop” indicates a state in which provision of XML / Web services is stopped, or a state in which provision of services to the outside is substantially impossible due to a physical factor such as server down. “Deleted” indicates a state in which the XML / Web service is deleted from the XML / Web service storage unit. The update date and time 713 indicates the date and time when the registration information of the XML / Web service table 710 is updated. The registrant 714 indicates a service provider for the XML / Web service.
The registration destination UDDI table 720 includes data items of service ID 721, UDDI registration ID 722, UDDI registry URL 723, update date 724, and registrant 725. The service ID 721 corresponds to the service ID 711 in the XML / Web service table 710. The UDDI registration ID 722 indicates the order (item number) registered in the UDDI registry. The UDDI registry URL 723 indicates a URL of a UDDI registry arbitrarily designated by a service provider or the like as a registration destination of XML / Web service information. The update date / time 724 and the registrant 725 are the same as the update date / time 713 and the registrant 714 in the XML / Web service table 710. In addition, a service ID set in each registration destination UDDI registry may be included.

The XML / Web service information storage unit 140 stores each information with the same data structure as the UDDI registry. The data structure of the UDDI registry will be described below.
FIG. 8 is a configuration diagram showing the data structure of the UDDI registry. The UDDI registry data mainly includes a Business Entity element 801, a Business Service element 802, a Business Template element 803, and a tModel element 804.
A Business Entity element 801 indicates company information corresponding to XML / Web service provider information, and is associated with the Business Service element 802 by a Business Key attribute 805. Since one company that is an XML / Web service provider may provide a plurality of services, one Business Entity element 801 may have a plurality of Business Service elements 802.
A BusinessService element 802 indicates service information as a child element of the BusinessEntity element 801, and is associated with the BusinessTemplate element 803 by a ServiceKey attribute 806.
A Business Template element 803 indicates technical information as a child element of the Business Service element 802.
The tModel element 804 is referred to by the reference information incorporated in the Business Template element 803 and indicates a service specification.

FIG. 9 is a diagram showing the contents of each data element constituting the UDDI registry.
As shown in FIG. 9, a Business Entity element 801 indicates business information such as a company name as an XML / Web service provider, a contact information of the XML / Web service provider, and an industry classification code.
A Business Service element 802 indicates service information such as a name, content, and classification of a service provided by an XML / Web service provider.
A Business Template element 803 indicates technical information such as an access point and parameters for the XML / Web service.
A tModel element 804 indicates a service specification such as an XML / Web service specification or a URL of a WSDL document.

10 to 13 are diagrams illustrating an example of each element constituting the UDDI registry.
In the BusinessEntity element 801, for example, as shown in FIG. 10, a company ID, a company information acquisition URL, a company name, a contact address, etc. are described in XML. In the BusinessService element 802, for example, as shown in FIG. As described above, XML describes a service ID, a company ID, a service name, a service description, and the like.
In the BusinessTemplate element 803, for example, as shown in FIG. 12, a service ID, a technical information ID, a description of the technical information, an address for connecting to the service, a tModelID, and the like are described by XML.
In the tModel element 804, for example, as shown in FIG. 13, a tModel ID, a service name, a description of the service, a description of the use of the XML / Web service, a URL of the specification of the XML / Web service, and the like are described by SML. .
The UDDI information storage unit according to the present embodiment stores XML / Web service information and XML / Web service provider information with the same data structure as in FIGS.

Based on the above configuration, UDDI information management processing performed by the XML / Web service server according to the present embodiment will be described.
FIG. 14 is a flowchart illustrating an XML / Web service information generation processing procedure performed by the XML / Web service information generation processing unit and the XML / Web service information management unit.
In this process, first, the service provider stores a service code as an XML / Web service execution environment file in the XML / Web service storage unit (step 1401), and based on the information included in the service code, the XML / Web service is stored. Registration processing of information and XML / Web service provider information is performed.
In the XML / Web service information registration process, first, the XML / Web service information reading processing unit 121 acquires the service code stored in the XML / Web service storage unit 110 and reads the header part (step 1402).
The XML / Web service information conversion processing unit 122 reads the UDDI schema file 127 (Step 1403), and stores the XML / Web service information included in the header read by the XML / Web service information reading processing unit 121 for storing the UDDI registry. (Step 1404).
On the other hand, in the XML / Web service provider information registration process, the XML / Web service provider information reading processing unit 124 acquires the service code stored in the XML / Web service storage unit 110 and reads the provider information ( Step 1405).
The XML / Web service provider information conversion processing unit 125 reads the UDDI schema file 127 (Step 1406), and converts the provider information read by the XML / Web service provider information reading processing unit 124 into information for storing the UDDI registry. Conversion is performed (step 1407).
The XML / Web service information storage processing unit 123 and the XML / Web service provider information storage processing unit 126 convert the information converted for storing the UDDI registry in Steps 1404 and 1407 to the XML / Web service management information storage unit 130. And stored in the XML / Web service information storage unit 140 (step 1408).
The XML / Web service information UDDI registration unit 151 refers to the XML / Web service management information storage unit 130 and the XML / Web service information storage unit 140 (step 1409), and stores the XML / Web service information in the UDDI registry via the UDDI communication unit 160. Service information is registered (step 1410). In this case, registration is performed in the UDDI registry indicated by the external UDDI service URL stored in the registration destination UDDI table, the UDDI registration ID acquired from the UDDI registry is stored in the UDDI registration ID of the registration destination UDDI table, and the update date / time is set. Update.
With the above processing, the XML / Web service server in which XML / Web service information is registered in the UDDI registry becomes a search target in the UDDI registry and can provide the XML / Web service.

The XML / Web service information management unit 150 stores the XML / Web service information in the UDDI registry, and then performs processing according to the state of the XML / Web service.
FIG. 15 is a flowchart showing a processing procedure performed by the XML / Web service information management unit 150 in response to the deletion of the XML / Web service.
The XML / Web service status monitoring unit 152 monitors the XML / Web service storage unit. When the XML / Web service provider or the like deletes the XML / Web service (step 1501), the XML / Web service status monitoring unit 152 detects the deletion of the XML / Web service (step 1502), and the following XML / Web service information deletion processing is performed.
In the XML / Web service information deletion process, the XML / Web service status monitoring unit 152 obtains the URL of the UDDI registry in which the deleted XML / Web service information is registered from the XML / Web service management information storage unit 130 (step). 1503).
Based on the URL acquired by the XML / Web service status monitoring unit 152 in step 1503, the XML / Web service information UDDI deletion unit 153 deletes the XML / Web service information from the UDDI registry via the UDDI communication unit 160 (step 1504). .
The XML / Web service information change processing unit 154 displays information corresponding to the XML / Web service information deleted from the UDDI registry by the XML / Web service information UDDI deletion unit 153, and the XML / Web service management information storage unit 130 and the XML / Web. Delete from the service information storage unit 140. In this case, the XML / Web service management information storage unit 130 sets the operation state to “deleted” in the XML / Web service table, and deletes only the information on the registration destination UDDI table (step 1505).

FIG. 16 is a flowchart illustrating a processing procedure performed by the XML / Web service information management unit in response to the suspension of the XML / Web service disclosure.
When the XML / Web service provider stops publishing the XML / Web service (step 1601), the XML / Web service status monitoring unit 152 detects the publishing stop of the XML / Web service (step 1602). XML / Web service disclosure stop processing is performed.
In the XML / Web service publishing stop process, the XML / Web service status monitoring unit 152 obtains the URL of the UDDI registry in which the information of the XML / Web service whose publishing has been registered is registered from the XML / Web service management information storage unit 130 ( Step 1603).
Based on the URL acquired by the XML / Web service status monitoring unit 152 in step 1603, the XML / Web service information UDDI deletion unit 153 deletes the XML / Web service information from the UDDI registry via the UDDI communication unit 160 (step 1604). .
The XML / Web service information change processing unit 154 searches the XML / Web service table of the XML / Web service management information storage unit 130 for information corresponding to the XML / Web service whose publication has been suspended, (Step 1605).

FIG. 17 is a flowchart illustrating a processing procedure performed by the XML / Web service information management unit in response to the restoration of the XML / Web service.
When the XML / Web service that has been suspended by the XML / Web service provider is restarted (step 1701), the XML / Web service status monitoring unit 152 detects the resumption of the XML / Web service (step 1701). 1702), the following XML / Web service information re-registration process is performed.
In the XML / Web service information re-registration process, the XML / Web service status monitoring unit 152 uses the XML / Web service management information storage unit 130 to set the URL of the UDDI registry that is the registration destination of the XML / Web service that has been suspended from being published. (Step 1703).
Based on the URL acquired by the XML / Web service state monitoring unit 152 in step 1703, the XML / Web service information UDDI registration unit 151 registers the XML / Web service information in the UDDI registry via the UDDI communication unit 160 (step 1304). .
The XML / Web service information change processing unit 154 searches the XML / Web service table of the XML / Web service management information storage unit 130 for information corresponding to the resumed XML / Web service, and sets the operation status to “public”. (Step 1705).

An example of an XML / Web service system using the UDDI server shown in each embodiment will be described above.
FIG. 18 is a diagram showing an outline of an XML / Web service system connected via the Internet.
In the XML / Web service system 1800, a user terminal 1801 or a WWW server 1802 as a Web service client includes an application that uses the XML / Web services 1803-1806.
In this example, as an XML / Web service 1803-1806, a reservation service is provided in each of an airline company, a railway company, an inn, and a hotel.
The UDDI server 1807 stores and discloses information such as access points and types of services to be provided for the XML / Web services 1803 to 1806.
In such a system configuration, when an application provided in the user terminal 1801 or a Web application in the WWW server 1802 is executed by the user, the Web service client performs an XML / The Web service 1803-1806 is searched and inquired by the UDDI server 1807.
The UDDI server 1807 uses the search means to search for registration information based on the search conditions received from the Web service client, and returns information on the XML / Web services 1803-1806 corresponding to the search conditions to the Web service client.
Based on the search result, the Web service client accesses the XML / Web services 1803 to 1806 and receives provision of the XML / Web services 1803 to 1806.
For example, in the case where there is a business for making an airline ticket reservation using a Web application in the WWW server 1802, when a travel agent's WWW server 1802 is accessed by a browser of the user terminal 1801, a reservation condition designation screen or the like Is displayed.
The Web application causes the user to input necessary information regarding the air ticket on the reservation condition specifying screen and the like, and accordingly, searches and inquires the designated airline's passport reservation XML / Web services 1803-1806 on the UDDI server 1807.
The search means of the UDDI server 1807 returns the information on the passport reservation XML / Web service of the airline corresponding to the search condition to the Web application of the WWW server 1802.
The Web application uses the passport reservation XML / Web service of the designated airline based on the information related to the passport reservation XML / Web service of the designated airline.
The Web application displays the result of use of the designated airline's passport reservation XML / Web service (result of passport reservation) on the browser in the user terminal 1801, and informs the user of the result.

  In the above-described embodiment, the XML / Web service information generation unit, the XML / Web service information management unit, and each information storage unit are provided in the XML / Web service server. It is good also as providing a part or all of a part or an information storage part in another terminal (server etc.).

It is a block diagram which shows schematic structure of the XML / Web service server which concerns on one embodiment of this invention. It is a figure which shows schematic structure of the XML / Web service system containing the XML / Web service server which concerns on one embodiment of this invention. It is a figure which shows an example of the service code stored in an XML / Web service storage part. It is a figure which shows an example of the company information file stored in an XML / Web service storage part. It is a figure which shows an example of the schema file corresponding to provider information. It is a figure which shows an example of the schema file corresponding to XML / Web service information. It is a figure which shows an example of the database schema of an XML / Web service management information storage part. It is a figure which shows the data structure of a UDDI registry. It is a figure which shows the content of each data element which comprises a UDDI registry. It is a figure which shows an example of BusinessEntity element. It is a figure which shows an example of BusinessService element. It is a figure which shows an example of BusinessTemplate element. It is a figure which shows an example of a tModel element. It is a flowchart which shows the registration process of XML / Web service information. It is a flowchart which shows the process according to XML / Web service deletion. It is a flowchart which shows the process according to a XML / Web service public stop. It is a flowchart which shows the process according to XML / Web service reopening. It is an image figure which shows the specific example of an XML / Web service.

Explanation of symbols

100 XML / Web service server, 110 XML / Web service storage unit, 111A, 111B XML / Web service, 120 XML / Web service information generation unit, 121 XML / Web service information reading processing unit, 122 XML / Web service information conversion processing , 123 XML / Web service information storage processing unit, 124 XML / Web service provider information reading processing unit, 125 XML / Web service provider information conversion processing unit, 126 XML / Web service provider information storage processing unit, 130 XML / Web service management information storage unit, 140 XML / Web service information storage unit, 150 XML / Web service information management unit, 151 XML / Web service information UDDI registration unit, 152 XML / Web service status monitoring unit, 153 ML / Web service information UDDI deletion unit, 154 XML / Web service information change processing unit, 160 UDDI communication unit.

Claims (4)

XML / Web service information registration means registers in advance XML / Web service information to be provided to a Web service client, and the XML / Web service information is registered in the Web service client via the XML / Web service information registration means. An XML / Web service information management system that provides
An XML / Web service storage unit for storing an implementation code constituting the XML / Web service;
An XML / Web service management information storage unit for storing management information corresponding to the XML / Web service stored in the XML / Web service storage unit;
An XML / Web service information storage unit for storing information to be registered in the XML / Web service information registration unit corresponding to the XML / Web service stored in the XML / Web service storage unit;
The implementation code is acquired from the XML / Web service storage unit, XML / Web service information in a predetermined format and service provider information included in the implementation code are converted based on a predefined schema file, and the XML XML / Web service registration information generating means for storing in each of the / Web service management information storage unit and the XML / Web service information storage unit,
The XML / Web service information storage unit manages the XML / Web service in which XML / Web service information is stored, obtains the newly stored XML / Web service information, and specifies a pre-designated registration destination XML / Web XML / Web service information management, comprising: XML / Web service information management means for registering in the service information registration means and setting the operation state stored in the XML / Web service management information storage unit to open system. The XML / Web service information management means includes:
When the XML / Web service implementation code stored in the XML / Web service storage unit is deleted from the XML / Web service storage unit, the XML / registered in the registration destination XML / Web service information registration unit 2. The XML / Web service information management system according to claim 1, further comprising means for deleting Web service information and setting the operation state stored in the XML / Web service management information storage unit to deletion. . The XML / Web service information management means includes:
Means for determining the operation status of the XML / Web service stored in the XML / Web service storage unit, and if the determination result is that the XML / Web service disclosure is stopped, the registration destination XML / Web service information registration means 3. The information processing apparatus according to claim 1, further comprising means for deleting the registered XML / Web service information and setting the operation state stored in the XML / Web service management information storage unit to the public stop. An XML / Web service information management system according to claim 1. The XML / Web service information management means includes:
The XML / Web service information stored in the XML / Web service information storage unit when the determination result of the operation status for the XML / Web service whose operation state is set to stop publishing is XML / Web service release restart. And a means for re-registering the operation state stored in the XML / Web service management information storage unit to open to the public. 3. The XML / Web service information management system according to 3.

Images