CN101174983B - System and method for managing a plurality of web services - Google Patents
System and method for managing a plurality of web services Download PDFInfo
- Publication number
- CN101174983B CN101174983B CN200710146445.0A CN200710146445A CN101174983B CN 101174983 B CN101174983 B CN 101174983B CN 200710146445 A CN200710146445 A CN 200710146445A CN 101174983 B CN101174983 B CN 101174983B
- Authority
- CN
- China
- Prior art keywords
- end points
- web service
- running time
- record
- uddi
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Abstract
The present invention relates to system for managing a plurality of web services WS1, WS2, WS3, WS1', WS2', WS3'). The system may include a registry (10) with a description (WSDL1, WSDL2, WSDL3) for at least one of the plurality of web services, wherein the description of the at least one web service may comprise a first endpoint (WS1, WS2, WS3) for a first runtime condition and a second endpoint (WS1', WS2', WS3') for a second runtime condition.
Description
Technical field
The present invention relates to be used to manage the system and method for a plurality of web services of service-oriented software architecture.
Background technology
The web service is to carry out the data exchange standard interface by computer network (for example, internet) between a computer and another computer.The web that application program can use server to provide serves by the computer network request from data in server.This request is usually included in the SOAP encapsulation, and HTTP transmits by use, and can comprise the XML in conjunction with other web relevant criterion.The application program of more advanced technology is served in conjunction with various web and is obtained or handle desirable data.Software configuration around a plurality of web service developments is known as service-oriented architecture (SOA).
In SOA, resource can the participant to network can be used with the stand-alone service of standardized way visit as the participant.Although the SOAP request that transmits by the HTTP/HTTPS based on TCP/IP is used in the definition of the majority of SOA, SOA can use any technology based on the web service.Web service is based on the formal definition that is independent of basic platform and programming language and interact (interoperate).Interface definition comprises concrete implementation.SOA is independent of concrete development technique (for example Java and .NET).Because interface conformance with standard and be independent of the basic implementation of web service logic, so component software becomes and can use once again.For example, the C# service can be used by the JAVA application program, and vice versa.
The developer of the new application program among the SOA need visit the various web services of being used by new application program.This has not only proposed the availability of the interface specification of related web service, and has proposed can be called to test actual effectively the providing of web service of new application program.Yet this test call must not disturb real world (real world).For example, calling web that the money that is used for test purpose shifts serve must not and cause real money transfer.
After exploitation, when new application program will be tested in a relatively large equipment before it is approved for the production use, similarly situation took place.In addition, owing to relate to the different requirements that stability during development phase and the test phase in relatively large equipment or result generate, may create new test sample by the web service of new application call.When the final approval of this application program is used to produce, must be to calling of various test web service by the replacement of calling to active service.The various replacement steps of the web service that exchange is used to develop, test and final production have the greater risk of mistake being introduced final application program on a large scale.
Therefore basic fundamental problem of the present invention provides a kind of system and method, this system and method overcomes the above-mentioned shortcoming of prior art, particularly, it helps to relate to the variation of new application program from the different development﹠ testing stages to actual disposition of one or more web services, and does not introduce wrong risk.
Summary of the invention
In one aspect of the invention, solve this problem by a kind of system that is used to manage a plurality of web services, this system comprises record (registry), this record comprises at least one the description that is used for a plurality of web service, the description of wherein said at least one web service comprise be used for first running time condition first end points and be used for second running time condition second end points.
Therefore, the web service that is used for different environment running time (landscape) (for example, exploitation, test, produce) can manage in single record, and does not lose the control to the risk of the service of environment and related introducing mistake.In use, correct end points can be according to condition and being selected automatically running time separately.As a result, can generate the various tests and the production environment of new application program automatically.
In one embodiment, this system also be applicable to during running time according to relate to by call the web service application program provided running time condition the assessment of environmental information select one of them of first and second end points.The value that therefore single variable in the application program is set allows to determine to use any environment, is applicable to the end points of condition running time (for example, test, configuration or the like) separately because one or more descriptions of the service of the web in the record comprise automatically.
In another embodiment, this system also is applicable to during running time one of them that select first and second end points according to condition running time in the record of being stored in.Thereby the information of the proper environment of the current state of reflection development process and the web service that selection is used for new application program for example can be stored in this record.
In one embodiment, first and second WSDL documents definition, first and second end points that are used for the web service in being stored in record, the first and second WSDL documents for example are relative to each other by quoting mutually, and wherein each of WSDL document can be at its of condition and being labeled concrete running time.
Yet, in currently preferred embodiments, being used for single WSDL document definition first and second end points of web service, preferably as the attribute assembly of WSDL document.As a result, WSDL of this record storage web service " equity side (twins) " description, wherein in the equity side be used to first running time condition and another is used to other condition running time.In one embodiment, the SOA module of the request of serving by use web during running time is determined the value of attribute assembly.
In currently preferred embodiments, first end points is applicable to the application program of at least one web of test call service, and second end points is applicable to that preferably configuration calls the application program of at least one web service.Yet principle of the present invention also can be used for selecting between other environment,, is used for other condition running time that is.Preferably, this system also comprise be used for the device of the end points that monitors a plurality of web services during running time and be used for web service by be used for first running time condition end points call and the 2nd web serve by be used for second running time condition the situation that end points called under the device that gives a warning.Function for monitoring has been avoided inconsistency, and inconsistency may cause mistake in the execution of new application program.
According to another aspect, the present invention relates to a kind of a plurality of web service method that are used to manage, this method comprises that at least one the description that will be used for a plurality of web service is stored in the step of record, the description of wherein said at least one web service comprise be used for first running time condition first end points and be used for second running time condition second end points.
Further favourable being modified in the further dependent claims of the embodiment of system and method for the present invention limits.
Description of drawings
In the detailed description hereinafter, further described currently preferred embodiment of the present invention with reference to the accompanying drawings.
Fig. 1: the general general introduction figure of the example of the SOA of simplification, this simplification SOA comprise the application program of calling the web service and have the record of the description of web service;
Fig. 2: have the simplification general introduction figure of the SOA of two kinds of environment, described two kinds of environment have a plurality of web services equity side; With
Fig. 3: show the flow chart of system and method performed step during running time according to an embodiment of the invention.
Embodiment
Fig. 1 has provided the general introduction figure of the SOA that extremely simplifies: application program 30 is to web service 20 requests of sending 31.For this reason, application program 30 at first need be served the description of 20 interface definition about web.This is described 40 and for example can provide with web services definition language (WSDL), and this describes 40 or can be directly obtain from web service 20, perhaps can obtain (with reference to figure 1) 10 from writing down.
Yet, when developing new application program 30, need repeatedly contact to be used for the relevant web service 20 of test purpose, for example need to verify the total interface in the web service call requires whether whether response satisfied and that serve from web is suitably received and handled by application program 30.If in fact adopt web service 20, then each of these test calls all can cause the operation (for example reservation of air ticket or the money transfer from an account to another account) of some real worlds.In this context, it is also noted that, web service 20 can be positioned on the internet somewhere and its operation can control by the developer of new application program 30.
Therefore according to a preferred embodiment, the invention provides the service " equity side " shown in the property as schematically shown in Figure 2: as seen from the figure, single the descriptions WSDL1-WSDL3 (but having a plurality of end points) of corresponding web service preferably stored in record 10, and each of these descriptions all has its of environment 50 or 50 ' quote affiliated running time.Term " environment " refers to the specific part of whole SOA 100, and it can be distinguished by specified attribute in certain.In simplified embodiment shown in Figure 2, there are independent test environment 50 and independent production environment 50 '.Two environment 50 and 50 ' provide to small part identical web service WS1-WS3 and WS1 '-WS3 ', but have only the web of production service WS1 '-WS3 ' at actual motion and for example cause business transaction.The beta version of the service of production usefulness (for example being provided by certain third party) can generate automatically and join in the record 10.
Also can use the environment of other types to distinguish, for example, development environment and relatively large test environment or be used for the environment of a company and be used for the environment of another company.In addition, not only can there be two environment, can also have three or three above environment.
For class service equity side illustrated above managing error-free, definition is used for the end points of two environment 50,50 ' (wherein having web service WS1-WS3 and WS1 '-WS3 ') in single record 10.Therefore, the web service interface is described WSDL1-WSDL3 and is shared between environment 50,50 ', and end points is not shared.
Yet, it is also noted that, the single WSDL that is used for web service WS1-WS3 and WS1 '-WS3 ' except use describes WSDL1-WSDL3, also can replacedly exist two groups of being stored in the record about describing WSDL1-WSDL3 and WSDL1 '-WSDL3 ' (not shown among Fig. 2), two the WSDL descriptions (for example WSDL1 and WSDL1 ') that wherein belong to service equity side are relative to each other.According to running time condition use one or another (maybe may be the 3rd) to describe.
In currently preferred embodiments,, be used for the end points of two environment 50 and 50 ' in the single wsdl document definition that is used for serving equity side with " attribute " extensibility mechanism that is provided among the WSDL 2.0.The operation time of " attribute " expression appointment, it influences the behavior of an aspect of web service interaction.For example, the SOAP module of a request can specified attribute be controlled end points.This illustrates in the following example of the exemplary wsdl document of describing service equity side:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<description
xmlns＝″http://www.w3.org/2006/01/wsdl″
targetNamespace＝″http://namespaces.softwareag.com/2004/wsdl/resSvc
″
xmlns:tns＝″http://namespaces.softwareag.com/2004/wsdl/resSvc″
xmlns:ghns＝″http://namespaces.softwareag.com/2004/schemas/resSvc″
xmlns:wsoap＝″http://www.w3.org/2006/01/wsdl/soap″
xmlns:soap＝″http://www.w3.org/2003/05/soap-envelope″
xmlns:wsdlx＝″http://www.w3.org/2006/01/wsdl-extensions″
>
<documentation>
This?document?describes?the?reservation?Web?service.
</documentation>
<types>
<xs:schema?xmlns:xs＝″http://www.w3.org/2001/XMLSchema″
targetNamespace＝″http://namespaces.softwareag.com/2004/schemas/re
Svc″xmlns＝″http://namespaces.softwareag.com/2004/schemas/resSvc″
<xs:element?name＝″checkAvailability″
type＝″tCheckAvailability″/>
<xs:complexType?name＝″tCheckAvailability″>
<xs:sequence>
<xs:element?name＝″checkInDate″type＝″xs:date″/>
<xs:element?name＝″checkOutDate″type＝″xs:date″/>
<xs:element?name＝″roomType″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:element?name＝″checkAvailabilityResponse″
type＝″xs:double″/>
<xs:element?name＝″invalidDataError″type＝″xs:string″/>
</xs:schema>
</types>
<interface?name＝″reservationInterface″>
<fault?name＝″invalidDataFault″
element＝″ghns:invalidDataError″/>
<operation?name＝″opCheckAvailability″
pattern＝″http://www.w3.org/2006/01/wsdl/in-out″
style＝″http://www.w3.org/2006/01/wsdl/style/iri″
wsdlx:safe＝″true″>
<input?messageLabel＝″In″element＝″ghns:checkAvailability″/>
<output?messageLabel＝″Out″
element＝″ghns:checkAvailabilityResponse″/>
<outfault?ref＝″tns:invalidDataFault″messageLabel＝″Out″/>
</operation>
</interface>
<binding?name＝″reservationSOAPBinding″
interface＝″tns:reservationInterface″
type＝″http://www.w3.org/2006/01/wsdl/soap″
wsoap:protocol＝″http://www.w3.org/2003/05/soap/bindings/HTTP″>
<fault?ref＝″tns:invalidDataFault″wsoap:code＝″soap:Sender″/>
<operation?ref＝″tns:opCheckAvailability″
wsoap:mep＝″http://www.w3.org/2003/05/soap/mep/soap-
response″/>
</binding>
<service?name＝″reservationService″
interface＝″tns:reservationInterface″>
<endpoint?name＝″reservationEndpointTest″
binding＝″tns:reservationSOAPBinding″
address＝″http://test.softwareag.com/2004/reservation″>
<property
ref＝″http://features.softwareag.com/landscapes/type″>
<documentation>
This?endpoint?belongs?to?the?test?landscape
</documentation>
<value>test</value>
</property>
</endpoint>
<endpoint?name＝″reservationEndpoint?Production″
binding＝″tns:reservationSOAPBinding″
address＝″http://production.softwareag.com/2004/reservation″>
<property
ref＝″http://features.softwareag.com/landscapes/type?″>
<documentation>
This?endpoint?belongs?to?the?production?landscape
</documentation>
<value>production</value>
</property>
</endpoint>
</service>
</description>
This shows that two end points are defined, one is used for test environment, and another is used for production environment.Therefore, the operation time of attribute assembly is determined in two possible end points, thereby and the web service of determining test environment still be that the web service of production environment will be suggested.
Perhaps, the end points of these two environment can be specified according to UDDI-XML pattern (UDDI 3.0), and is as follows:
<uddi:businessService
businessKey＝″uddi:35f2eca0-eef2-11da-a924-c9108119a4e5″
serviceKey＝″uddi:4fc7c540-ef08-11da-bf78-dc56dc1260cf″
xmlns:uddi＝″urn:uddi-org:api_v3″
xmlns:dsig＝″http://www.w3.org/2000/09/xmldsig#″
xmlns:scc14n＝″urn:uddi-org:schemaCentricC14N:2002-07-10″>
xmlns:xml＝″http://www.w3.org/XML/1998/namespace″
<uddi:name?xml:lang＝″en-US″>
reservationService
</uddi:name>
<uddi:description
xml:lang＝″en″>
Service?for?reservation?available?in?test?and?production
landscape
</uddi:description>
<uddi:bindingTemplates>
<uddi:bindingTemplate
bindingKey＝″uddi:50357b30-ef08-11da-bf78-80c376f5f0f0″
serviceKey＝″uddi:4fc7c540-ef08-11da-bf78-dc56dc1260cf″>
<uddi:access?Point?useType＝″endPoint″>
http://test.softwareag.com/2004/reservation
</uddi:access?Point>
<uddi:tModelInstanceDetails>
<uddi:tModelInstanceInfo
tModelKey＝″uddi:4fb24170-ef08-11da-bf78-8f16f66201d4″>
<uddi:instanceDetails?xmlns:uddi＝″urn:uddi-org:api_v3″>
<uddi:description?xml:lang＝″en-US″>
the?wsdl:binding?that?this?wsdl:port?implements
</uddi:description>
<uddi:instanceParms>
reservationSOAPBinding
</uddi:instanceParms>
</uddi:instanceDetails>
</uddi:tModelInstanceInfo>
<uddi:tModelInstanceInfo
tModelKey＝″uddi:4f8516f0-ef08-11da-bf78-c304af4ea516″/>
</uddi:tModelInstanceDetails>
<uddi:categoryBag>
<uddi:keyedReference
tModelKey＝″uddi:features.softwareag.com:landscapes″
keyValue＝″test″/>
</uddi:categoryBag>
</uddi:bindingTemplate>
<uddi:bindingTemplate
bindingKey＝″uddi:50357b30-ef08-11da-bf78-80c376f5f0f1″
serviceKey＝″uddi:4fc7c540-ef08-11da-bf78-dc56dc1260cf″>
<uddi:accessPoint?useType＝″endPoint″>
http://production.softwareag.com/2004/reservation
</uddi:accessPoint>
<uddi:tModelInstanceDetails>
<uddi:tModelInstanceInfo
tModelKey＝″uddi:4fb24170-ef08-11da-bf78-8f16f66201d4″>
<uddi:instanceDetails>
<uddi:description?xml:lang＝″en-US″>
the?wsdl:binding?that?this?wsdl:port?implements
</uddi:description>
<uddi:instanceParms>
reservationSOAPBinding
</uddi:instanceParms>
</uddi:instanceDetails>
</uddi:tModelInstanceInfo>
<uddi:tModelInstanceInfo
tModelKey＝″uddi:4f8516f0-ef08-11da-bf78-c304af4ea516″/>
</uddi:tModelInstanceDetails>
<uddi:categoryBag>
<uddi:keyedReference
tModelKey＝″uddi:features.softwareag.com:landscapes″
keyValue＝″production″/>
</uddi:categoryBag>
</uddi:bindingTemplate>
</uddi:bindingTemplates>
<uddi:categoryBag>
<uddi:keyedReference
keyName＝″service?namespace″
keyValue＝″http://namespaces.softwareag.com/2004/wsdl/resSvc″
tModelKey＝″uddi:uddi.org:xml:namespace″/>
<uddi:keyedReference
keyName＝″WSDL?type″
keyValue＝″service″
tModelKey＝″uddi:uddi.org:wsdl:types″/>
<uddi:keyedReference
keyName＝″service?local?name″
keyValue＝″reservationService″
tModelKey＝″uddi:uddi.org:xml:localname″/>
<uddi:keyedReference
keyValue＝″uddi:2dd13990-8991-11d9-8457-ca59ad32ca75″
tModelKey＝″uddi:2dafcee0-8991-11d9-8457-f2038ed2fcd0″/>
</uddi:categoryBag>
</uddi:businessService>
So, being used for searching the UDDI inquiry of the end points of given environment (for example, test environment) can be as follows:
<find_binding?xmlns＝″urn:uddi-org:api_v3″
serviceKey＝″uddi:4fc7c540-ef08-11da-bf78-dc56dc1260cf″>
<findQualifiers>
<findQualifier>exactNameMatch</findQualifier>
</findQualifiers>
<categoryBag>
<keyedReference
tModelKey＝uddi:features.softwareag.com:landscapes
keyValue＝″test″/>
</categoryBag>
</find_binding>
Therefore the terminal point information that shows in wsdl document or record (UDDI) can be used in the various situations, and wherein a kind of situation is described with reference to figure 3 below, and it illustrates three kinds of assemblies that relate to:
Web service execution assembly 70 is available in running time (for example running time of test run) for application program 30.Web service execution assembly 70 is employed program 30 in the web service in the time of will being performed and calls in step 200, and the unique identification of reception web service 20 is as input (for example, its UDDI key, or the URL of its wsdl document).In step 201, the execution that 70 preparations of web service execution assembly are called.In step 202, its visit is stored in the information in the record 10, for example to determine to want the end points of invoked web service based on the wsdl document that is obtained from writing down 10 in step 204.It is also noted that the end points that is produced depends on its that provide and be included in as above explanation by application program 30 input parameter (for example certain property value) in calling in step 204, be used to carry out certain environment of web service call with definition.If the end points in indication does not exist available web service, then misdirection.Otherwise web service execution assembly 70 calls the web service that is identified in step 205, and this web service is carried out so that the result can be returned to application program 30 in step 207 in step 206.
The above-mentioned management of the end points in the record allows in addition to determine before to be used to test all service endpoints of this application program in the setup time of after tested application program 30, and for good and all replaces them with the end points that is used for production environment that has been recorded in the record 10.In addition, the web service call can be monitored and environment can verification whether to occur staggered in running time, that is, web service that whether belongs to first environment (for example test environment 50) is called, and the web service that belongs to another environment (for example production environment 50 ') also is called.If notice this inconsistency at run duration, then give a warning.
In general, the sign of the environment of caller can be used number of mechanisms, for example the separating based on the DNS territory of test environment and production environment.Environmental information can be sent out with the web service call.The following example that is stored in the wsdl document in the record 10 needs this information and hypothesis to have a concrete SOAP module that is used for environmental information management:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<description
xmlns＝″http://www.w3.org/2006/01/wsdl″
targetNamespace＝″http://namespaces.softwareag.com/2004/wsdl/resSvc
″
xmlns:tns＝″http://namespaces.softwareag.com/2004/wsdl/resSvc″
xmlns:ghns＝″http://namespaces.softwareag.com/2004/schemas/resSvc″
xmlns:wsoap＝″http://www.w3.org/2006/01/wsdl/soap″
xmlns:soap＝″http://www.w3.org/2003/05/soap-envelope″
xmlns:wsdlx＝″http://www.w3.org/2006/01/wsdl-extensions″
>
<documentation>
This?document?describes?the?reservation?Web?service.
</documentation>
<types>
<xs:schema?xmlns:xs＝″http://www.w3.org/2001/XMLSchema″
targetNamespace＝″http://namespaces.softwareag.com/2004/schemas/res
Svc″xmlns＝″http://namespaces.softwareag.com/2004/schemas/resSvc″>
<xs:element?name＝″checkAvailability″
type＝″tCheckAvailability″/>
<xs:complexType?name＝″tCheckAvailability″>
<xs:sequence>
<xs:element?name＝″checkInDate″type＝″xs:date″/>
<xs:element?name＝″checkOutDate″type＝″xs:date″/>
<xs:element?name＝″roomType″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:element?name＝″checkAvailabilityResponse″
type＝″xs:double″/>
<xs:element?name＝″invalidDataError″type＝″xs:string″/>
</xs:schema>
</types>
<interface?name＝″reservationInterface″>
<fault?name＝″invalidDataFault″
element＝″ghns:invalidDataError″/>
<operation?name＝″opCheckAvailability″
pattern＝″http://www.w3.org/2006/01/wsdl/in-out″
style＝″http://www.w3.org/2006/01/wsdl/style/iri″
wsdlx:safe＝″true″>
<input?messageLabel＝″In″element＝″ghns:checkAvailability″/>
<output?messageLabel＝″Out″
element＝″ghns:checkAvailabilityResponse″/>
<outfault?ref＝″tns:invalidDataFault″messageLabel＝″Out″/>
</operation>
</interface>
<binding?name＝″reservationSOAPBinding″
interface＝″tns:reservationInterface″
type＝″http://www.w3.org/2006/01/wsdl/soap″
wsoap:protocol＝″http://www.w3.org/2003/05/soap/bindings/HTTP″>
<fault?ref＝″tns:invalidDataFault″wsoap:code＝″soap:Sender″/>
<operation?ref＝″tns:opCheckAvailability″
wsoap:mep＝″http://www.w3.org/2003/05/soap/mep/soap-
response″/>
</binding>
<service?name＝″reservationService″
interface＝″tns:reservationInterface″>
<endpoint?name＝″reservationEndpointTest″
binding＝″tns:reservationSOAPBinding″
address＝″http://test.softwareag.com/2004/reservation″>
<wsoap:module
uri＝″http://features.example.com/2005/modules/landscapes″
required＝″true″/>
<property
ref＝″http://features.softwareag.com/landscapes/type″>
<documentation>
This?endpoint?belongs?to?the?test?landscape
</documentation>
<value>test</value>
</property>
</endpoint>
<endpoint?name＝″reservationEndpointProduction″
binding＝″tns:reservationSOAPBinding″
address＝″http://production.softwareag.com/2004/reservation″>
<wsoap:module
uri＝″http://features.example.com/2005/modules/landscapes″
required＝″true″/>
<property
ref＝″http://features.softwareag.com/landscapes/type″>
<documentation>
This?endpoint?belongs?to?the?production?landscape
</documentation>
<value>production</value>
</property>
</endpoint>
</service>
</description>
Perhaps, record 10 can be stored about the information of development phase of certain application program and suitably select end points (for example, based on the application deployment that is write down).This can or carry out entire environment, perhaps also can carry out separately each web service.
Claims (20)
1. system that is used to manage a plurality of web services, this system comprises record (10), this record (10) comprises at least one the description (WSDL1 during described a plurality of web are served, WSDL2, WSDL3), described description (WSDL1, the WSDL2 of wherein said at least one web service, WSDL3) comprise be used for first running time condition the first end points (WS1, WS2, WS3) and be used for second running time condition second end points (WS1 ', WS2 ', WS3 '), it is characterized in that
Described system also comprises the described end points (WS1 that is used for monitoring described a plurality of web services during running time, WS2, WS3, WS1 ', WS2 ', WS3 ') device and be used for web service by be used for first running time condition end points call and the 2nd web serve by be used for second running time condition the situation that end points called under the device that gives a warning.
2. according to the system of claim 1, also be applicable to during running time according to relate to provided by the application program (30) of calling described web service running time condition the assessment of environmental information select described first end points (WS1, WS2, WS3) and described second end points (WS1 ', WS2 ', WS3 ') one of them.
3. according to the system of claim 1, also be applicable to during running time according to condition running time in the described record (10) of being stored in select described first end points (WS1, WS2, WS3) and described second end points (WS1 ', WS2 ', WS3 ') one of them.
4. according to each system in the aforementioned claim, wherein be used for the definition of the first and second WSDL documents described first end points (WS1, the WS2 of described web service, WS3) and described second end points (WS1 ', WS2 ', WS3 '), the described first and second WSDL documents are relative to each other.
5. according to each system among the claim 1-3, wherein at the single WSDL document (WSDL1 that is used for described web service, WSDL2, WSDL3) the described first end points (WS1 of definition in, WS2, WS3) and described second end points (WS1 ', WS2 ', WS3 '), as the attribute assembly of described WSDL document.
6. according to the system of claim 5, wherein the SOAP module of the request by using described web service is determined the value of described attribute assembly during running time.
7. according to the system of claim 1, wherein record (10) is the UDDI record.
8. according to the system of aforementioned claim 1, (WS1, WS2 WS3) are applicable to the application program that described at least one web of test call serves to wherein said first end points.
9. according to the system of aforementioned claim 1, wherein second end points (WS1 ', WS2 ', WS3 ') is applicable to that configuration calls the application program (30) of described at least one web service
10. according to the system of aforementioned claim 1, wherein said record (10) also comprise be used for the 3rd running time condition the 3rd end points.
11. one kind is used to manage a plurality of web service method, this method comprises and will be used at least one description (WSDL1 of described a plurality of web service, WSDL2, WSDL3) be stored in step in the record (10), the described description of wherein said at least one web service comprise be used for first running time condition first end points (WS1, WS2, WS3) and be used for second running time second end points (WS1 ', WS2 ', WS3 '), it is characterized in that
Described method is further comprising the steps of: the described end points (WS1 that monitors described a plurality of web services during running time, WS2, WS3, WS1 ', WS2 ', WS3 '), and web service by be used for first running time condition end points call and the 2nd web serve by be used for second running time condition the situation that end points called under give a warning.
12., further comprising the steps of according to the method for claim 11:
During running time according to relate to by call described web service application program provided running time condition the assessment of environmental information select described first end points (WS1, WS2, WS3) and one of them of described second end points (WS1 ', WS2 ', WS3 ').
13., further comprising the steps of according to the method for claim 11:
With running time condition be stored in the described record; And
During running time, select described first end points (WS1, WS2, WS3) and one of them of described second end points (WS1 ', WS2 ', WS3 ').
14. according to each method among the claim 11-13, the step that wherein said at least one the description that will be used for described a plurality of web service is stored in record comprises that storage is used for the WSDL document of indication first end points of described web service and the 2nd WSDL document that storage is used for indication second end points of described web service, and the wherein said first and second WSDL documents are used as relevant WSDL document storage in described record.
15. according to each method among the claim 11-13, wherein said at least one the description (WSDL1 that will be used for described a plurality of web service, WSDL2, WSDL3) step that is stored in the described record comprises that the attribute component stores of utilizing described first and second end points of indication is used for the single WSDL document of described web service.
16. according to the method for claim 15, wherein the SOAP module of the request by using described web service is determined the value of described attribute assembly during running time.
17. according to the method for claim 11, wherein said record (10) is the UDDI record.
18., also comprise and use described first end points (WS1, WS2 WS3) come the step of the application program of described at least one web service of test call according to the method for claim 11.
19., also comprise the step of using described second end points (WS1 ', WS2 ', WS3 ') to dispose the application program of calling described at least one web service according to the method for claim 11.
20. according to the method for claim 11, wherein said record (10) also comprise be used for the 3rd running time condition the 3rd end points.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP06015020.8 | 2006-07-19 | ||
| EP06015020A EP1881675B1 (en) | 2006-07-19 | 2006-07-19 | System and method for managing a plurality of web services |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101174983A CN101174983A (en) | 2008-05-07 |
| CN101174983B true CN101174983B (en) | 2011-04-06 |
Family
ID=37575002
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200710146445.0A Active CN101174983B (en) | 2006-07-19 | 2007-07-19 | System and method for managing a plurality of web services |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US8935370B2 (en) |
| EP (1) | EP1881675B1 (en) |
| CN (1) | CN101174983B (en) |
| AT (1) | ATE409384T1 (en) |
| DE (1) | DE602006002884D1 (en) |
| ES (1) | ES2315970T3 (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8972939B1 (en) * | 2007-04-13 | 2015-03-03 | United Services Automobile Association (Usaa) | Systems and methods for processing and producing content for web sites |
| US20090070335A1 (en) * | 2007-09-06 | 2009-03-12 | Cozianu Costin V | System and method for web processing monitoring |
| EP2093676A1 (en) * | 2008-02-20 | 2009-08-26 | Siemens Aktiengesellschaft | Method for generating function building blocks for web services |
| BR112013008597A2 (en) * | 2010-09-21 | 2017-07-25 | Ebay Inc | market supply for software services |
| GB2502998A (en) * | 2012-06-13 | 2013-12-18 | Ibm | Automatic creation of endpoint definition documents for different environments |
| CN108833135B (en) * | 2018-05-04 | 2023-06-06 | 深圳市共进电子股份有限公司 | Mesh networking management method, management equipment and extender |
| US10735300B1 (en) * | 2018-11-30 | 2020-08-04 | Intuit Inc. | Discovery and testing of program dependencies in computer networks |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005029807A1 (en) * | 2003-09-24 | 2005-03-31 | International Business Machines Corporation | Personalized web service description |
| EP1641215A2 (en) * | 2004-09-28 | 2006-03-29 | Layer 7 Technologies, Inc. | System and method for bridging identities in a service oriented architecture |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080281969A1 (en) * | 2000-12-15 | 2008-11-13 | Horton John C | Controlling access to versions of application software by a server, based on site ID |
| US20050160153A1 (en) * | 2004-01-21 | 2005-07-21 | International Business Machines Corp. | Publishing multipart WSDL files to URL |
| US7509398B2 (en) * | 2005-01-13 | 2009-03-24 | International Business Machines Corporation | System and method for protocol independent access and invocation of web services |
-
2006
- 2006-07-19 EP EP06015020A patent/EP1881675B1/en active Active
- 2006-07-19 ES ES06015020T patent/ES2315970T3/en active Active
- 2006-07-19 AT AT06015020T patent/ATE409384T1/en not_active IP Right Cessation
- 2006-07-19 DE DE602006002884T patent/DE602006002884D1/en active Active
-
2007
- 2007-07-18 US US11/779,317 patent/US8935370B2/en active Active
- 2007-07-19 CN CN200710146445.0A patent/CN101174983B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005029807A1 (en) * | 2003-09-24 | 2005-03-31 | International Business Machines Corporation | Personalized web service description |
| EP1641215A2 (en) * | 2004-09-28 | 2006-03-29 | Layer 7 Technologies, Inc. | System and method for bridging identities in a service oriented architecture |
Non-Patent Citations (2)
| Title |
|---|
| Roberto Chinnici et al.Part 1: Core Language.《Web Services Description Language (WSDL) Version 2.0》.2006,1-135. * |
| Roberto Chinnici et al.Part 1: Core Language.<<Web Services Description Language (WSDL) Version 2.0>>.2006,1-135. |
Also Published As
| Publication number | Publication date |
|---|---|
| US20080028316A1 (en) | 2008-01-31 |
| EP1881675B1 (en) | 2008-09-24 |
| US8935370B2 (en) | 2015-01-13 |
| CN101174983A (en) | 2008-05-07 |
| ES2315970T3 (en) | 2009-04-01 |
| DE602006002884D1 (en) | 2008-11-06 |
| ATE409384T1 (en) | 2008-10-15 |
| EP1881675A1 (en) | 2008-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11734734B2 (en) | System and method for web service billing | |
| CN101174983B (en) | System and method for managing a plurality of web services | |
| Pautasso et al. | Restful web services vs." big"'web services: making the right architectural decision | |
| CN101681489B (en) | Content distribution infrastructure | |
| EP1512265B1 (en) | A computing services grid | |
| US9519561B2 (en) | Method and system for configuration-controlled instrumentation of application programs | |
| US7272626B2 (en) | E-service management through distributed correlation | |
| US20020116454A1 (en) | System and method for providing communication among legacy systems using web objects for legacy functions | |
| CA2685892A1 (en) | Xml push and remote execution of a wireless applications | |
| US20090249370A1 (en) | Method and apparatus for dynamic web service composition and invocation | |
| US20100257587A1 (en) | System and method for facilitating the provision of web services across different internet security domains | |
| Bianco et al. | Architecting service-oriented systems | |
| US20050015771A1 (en) | Distributed computer system for telecommunications operational support | |
| US20040093580A1 (en) | System and methodology for mobile e-services | |
| Castellano et al. | An e-government cooperative framework for government agencies | |
| US10397342B2 (en) | Web service contract selection | |
| US7568020B2 (en) | Operational support system for telecommunication services | |
| JP2010521723A (en) | Remote customization module and system including the module | |
| KR101040891B1 (en) | System for Providing of Complex Service in Wireless Internet | |
| Kuropka et al. | Semantic enterprise services platform: motivation, potential, functionality and application scenarios | |
| Bunting et al. | Web services context (ws-context) ver1. 0 | |
| KR100562424B1 (en) | Apparatus and method for executing provisioning | |
| Ashford et al. | OSS design patterns: a pattern approach to the design of telecommunications management systems | |
| KR100566634B1 (en) | Postal code offer system and the method to use web service | |
| Qiao | Automatic quality of service adaptation for composite web services |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |