CN101087312B - System and method for managing web services - Google Patents
System and method for managing web services Download PDFInfo
- Publication number
- CN101087312B CN101087312B CN2007101107097A CN200710110709A CN101087312B CN 101087312 B CN101087312 B CN 101087312B CN 2007101107097 A CN2007101107097 A CN 2007101107097A CN 200710110709 A CN200710110709 A CN 200710110709A CN 101087312 B CN101087312 B CN 101087312B
- Authority
- CN
- China
- Prior art keywords
- service
- registry
- web
- request
- filter
- 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]
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
Abstract
A system for managing a plurality of web services of a service oriented architecture (SOA) comprising a registry (30) including a description of each of the plurality of web services (20) registered in the registry, a service filter (40) adapted to filter at least one request of a client (10) invoking at least one of the web services (20) registered in the registry, wherein the service filter (40) is adapted for gathering run-time information about the request in accordance with the description of the respective web service in the registry (30).
Description
Technical field
The present invention relates to be used to manage the system and method for the web service of service-oriented software architecture.
Background technology
The web service is to be used for through computer network (for example internet) from the standard interface of a computer to another computer swap data.Application can utilize the web service that is provided by server to pass through computer network to the server requests data.This request is enclosed in during the SOAP that utilizes HTTP to transmit seals usually, and can comprise XML and other standards relevant with web.The various web services of technical more senior application combination are to obtain or to handle expected data.Software architecture around a plurality of web service developments is called as service-oriented architecture (SOA).
In SOA, resource is available for the participant in the network, and it is taken as the participant can be by the stand-alone service of standardized way visit.Though the SOAP request that transmits via the HTTP/HTTPS on the TCP/IP is used in the definition of the great majority of SOA, SOA can use any technology based on the web service.The web service is based on the formal definition collaborative work, and the platform and the programming language of formal definition and lower floor have nothing to do.Interface definition has encapsulated the specific implementation mode.SOA and specific development technique (for example Java and .NET) have nothing to do.It is highly reusable that component software becomes, because interface is deferred to standard, and irrelevant with lower floor's implementation of web service logic.For example, C# (C Sharp) service can be used by the JAVA application, and vice versa.
Yet management SOA is the task of a complicacy and difficulty.The global view (some web service possibly dynamically change in time) of safeguarding the overall condition of web service is very important for guaranteeing that the application of using various web to serve is correctly worked.Therefore, known in the prior art registry (registry)/storage (repository) that a kind of centralization is provided, for example CentraSite or Systinet 2.Its working principles of this registry/repository is shown in Fig. 1.
As shown in the figure, the registry of centralization comprises the description to the web service of SOA.Each web serves by web service description language (sdl) (WSDL) file description, and utilizes API (for example UDDI) registration.Wsdl document comprises the information about function, data, data type and the exchange agreement of corresponding web service usually.Want the client of the request of sending to a certain web service to serve self or to obtain wsdl document, to find out the web service of how visiting from web from registry/repository.As shown in Figure 1, registry/repository provides and has been used for the information and the various APIs that are used for its management of access stored at registry.Except the registration of WSDL document and service, registry/repository also can be used for storing and the workpiece of serving relevant any kind (artefact), for example strategy.
The registry of centralization can be used for the design time of the new application of SOA.The developer who relates to the new application of one or more web service can use the web service of institute's canned data related SOA in guaranteeing to use to receive the data of its needs, and can be by desired such mutual of new application.Yet, (runtime) information run time that the registry of Fig. 1 not providing any, and do not allow to carry out (enforce) and relevant strategy or the service level agreements of one or more web services.Run time the information performance and the stability that for example help to improve or keep watch on the new application of a plurality of web services that relate to SOA.
WO 2004/10297 discloses a kind of autonomous ageng, and it is disposed between client and the web service.After by user's configuration, the operation of web service can kept watch on and influence to autonomous ageng, and do not influence web service self.Yet the complex system structure that the instruction of WO 2004/10297 is applied to have a large amount of web services need be carried out time-consuming manual configuration to same a large amount of autonomous ageng.
Therefore, the technical problem that the present invention will solve provides a kind of mode more efficiently that is used to manage the web service of SOA, and it allows to obtain the run time information about the web service of SOA, thereby overcomes the above-mentioned deficiency of prior art.
Summary of the invention
In one aspect of the invention; This problem is solved by a kind of system that is used to manage a plurality of web services of service-oriented architecture (SOA); This system comprises registry and service filter; Registry be included in register in the registry to each the description in a plurality of web service; Service filter is suitable for filtering at least one at least one request of client that is invoked in the web service of registering in the registry, and wherein service filter is suitable for according in the registry run time information about request being collected in the description of corresponding web service.
Therefore, service filter of the present invention uses the available description to the web service to collect the run time information about the web service.Therefore; The description that in registry, defines not only can be used for deriving these a plurality of web services and how to work when design; Also defined in addition run time the information that will collect from corresponding web service, that is, when the request reality from client provides service by the web service.Therefore, registry of the present invention is the central point of whole SOA.Do not need additional step/manual steps guarantee from web service run time data collection.
In one embodiment, service filter also is suitable for request being revised in the description of corresponding web service at run duration in according to registry.The request of modification can for example comprise that the request of going to web service is redirected to the 2nd web that in registry, registers serves (or end points).This can help load balance or dynamically substitute the web service of breaking down.
Preferably; Service filter also is suitable for collecting the statistics about the operating position of invoked web service, the usage count of for example a certain web service, bandwidth usage, identity, distribution, response time and the data volume or the like of (time in one day or longer time period) in time.
In addition, preferably, service filter also is suitable for supervising the availability of invoked web service, and preferably serves under the disabled situation at invoked web and give the alarm.The strategy that is used for reporting to the police (being used to initiate the condition of alarm, the method and the recipient of warning) can be stored in registry, thereby allows single configure alert point.In addition, the governance information (owner, responsibility) of registry stores web service, it can be used for dynamically confirming the recipient of alarm.Thereby can reduce the down time of the application of using the web service of breaking down.
Preferably, service filter is suitable for carrying out in registry at run duration at least once searches, and the result who wherein searches confirms that service filter is to request and/or from the processing of the response of web service.Therefore, service filter use the up-to-date description of web service confirm its to run time information collecting.
The run time information of being collected by service filter in one embodiment, preferably together is stored in the registry of system with the description that web is served.Therefore, developer or any other user can easily visit the run time information and to the description of corresponding web service that is obtained.With run time information stores in registry, can also realize the search (for example being used for fraud detection) of abnormal use pattern and distinguishing of trend, for example be used to predict following use pattern.
In a kind of alternative, service filter is disposed on the service broker, the service broker in addition possibly operate in the different machine of web service self on.Use independently Agent components or even use independently that machine provides the maximum flexibility that is used to realize service filter, and regardless of the specific implementation mode of web service.
According to another aspect, the present invention relates to a kind of a plurality of web service method that are used to manage service-oriented architecture (SOA), may further comprise the steps:
Registry is provided, this registry be included in register in the registry to each the description in a plurality of web service,
Service filter is provided, and this service filter is suitable for filtering at least one at least one request of client that is invoked in the web service of registering in the registry, and
Utilize service filter according in the registry run time information about at least one web service being collected in the description of corresponding web service.
Define further modification in the dependent claims to this method.
Description of drawings
In the detailed description below, further described currently preferred embodiments of the present invention with reference to accompanying drawing, in the accompanying drawings:
Fig. 1: according to the registry that has of prior art to the description of web service;
Fig. 2: according to the global view of system implementation example of the present invention;
Fig. 3: according to the global view of another embodiment of system of the present invention;
Fig. 4: the flow chart of the various steps that the information run time of being used to collect according to an embodiment of the invention of illustrating is performed;
Fig. 5: in one embodiment of the invention with description to corresponding web service together be stored in the registry run time information sample output; And
Fig. 6: be stored in the registry with to the number of the request of various web service relevant run time information another sample output.
Embodiment
Below, only there is the simplification of the single client 10 of accessing individual web service 20 to arrange the embodiment that describes system and method for the present invention to management.Yet, should be appreciated that main purpose of the present invention is the management that promotes the extensive layout of tens of or hundreds of web services with the request of serving a plurality of clients.
As shown in the figure, this system comprises registry 30.Registry preferably include be used for storing with retrieve stored the wsdl document of registry and run time information (being described below) one or more API 31.In addition, preferably include the Administration API 32 that is used to manage registry 30.
Shown in the two-way horizontal arrow among Fig. 2, client 10 request of sending 11 to web services 20 are for example in order to obtain some data.Preferably, all being taken as the XML file from the request of client 10 and response utilizes the SOAP on the HTTP for example to send.Yet, do not handled by web service 20 immediately from the request that client 10 receives, but at first filtered by service filter 40.Data are revised in the request that service filter 40 interceptings get on demand, subsequently request are delivered to original web service 20.Can be served filter 40 in opposite direction once more from the response of web service 20 afterwards in the request of having handled and handled, and finally turned back to client 10.By this way, service filter 40 obtains the information about request and its possible response in run duration, and this information is forwarded subsequently and is stored in the registry 30, shown in the arrow among Fig. 2 35.In this embodiment, the run time information that is collected that is used for service filter 40 is to utilize the API of service filter 41 realizations with the transmission that configuration is provided with, and API 41 communicates by letter with the API 31 of registry 30.
In a kind of very simple situation, the run time information that is provided by service filter 40 possibly only be when to call the information of which web service about which entity of SOA.In more senior embodiment, service filter 40 will obtain more information, the size of the user account that for example relates to, request and its response, processing time, fault or the like.From more structurized visual angle, can distinguish following four kinds of different techniques fields, by service filter 40 collect run time information maybe be relevant with these fields:
At first, information can be disclosed in the statistical information of the web service that relates among the SOA run time.Such as usage count, have that bandwidth is used and the providing of the interconnection network of identity, the statistical information distribution and response time and the data volume that is sent out of (one day time or longer time period) provides the concentrated view to the operating position of related web service as the keeper of SOA in time.
Be the technical surveillance of SOA on the other hand, it relates under the situation that some incident (for example web service unavailable) occurs and sends alarm to correct connector.The supervision that is provided by service filter 40 also can relate to virus and safety inspection, for the debugging support of the exploitation of new application, and generally also relates to the assessment of the service quality that the web service by SOA is provided.Because all information that are collected are all fed back to registry 30, so registry 30 allows to make the SOA that is kept watch on to begin to move from central point always, and based on its success of historical data assessment.
Except collecting the information about SOA, in more senior embodiment, service filter 40 can also initiatively change processing of request.Be redirected to another web service (not shown in Fig. 2) if service filter 40 will be gone to the request of a certain web service 20 at first, then can realize the dynamic concept such as loose couplings.This technical characterictic allows in the request from client 10, to use dynamic endpoints; For example under the situation of a certain web service in the face of a large amount of requests of surpassing its disposal ability, be used for load balance, perhaps the request that allows to send to the web service of breaking down of this technical characterictic is redirected to subsequent use web service (not shown in Fig. 2) automatically.The condition and the details that are redirected also can be stored in the registry, thereby single control point is provided.
Finally, run time information collecting can be used for implementation strategy or service level agreements, for example about web service the predetermined response time to a certain request.
In the embodiment of Fig. 2; The service filter 40 of carrying out above-mentioned functions is implemented as additional (add-on) function of web service 20; The installed platform based on J2EE or Java Servlet of service 20 from special-purpose web server and .Net environment (IIS, ASP) to web for example, the details of these platforms is known to those skilled in the art.
Fig. 3 representes the alternative embodiment of system of the present invention, and wherein service filter 40 is served as with web and served the service broker 45 that 20/ application server is separated, itself in addition possibly operate in web and serve on the 20 different machines.In this case, in registry 30, the description of web service 20 is made amendment to client, thereby the actual endpoint of web service 20 is alternative by agency 45 URL.Why this is possible, is because the description (it is registered to registry 30) of each web service of 30 couples of SOA of registry has control completely.Because the change of URL will be called agency 45 in run duration client 10, agency 45 is information and/or revised and actual web has been transferred in request after the request and serve 20 run time having collected subsequently.For the response from web service 20, identical process takes place in the other direction.
Below, specify the exemplary process of carrying out by the service filter 40 of the embodiment of Fig. 2 or 3 to the request of getting into reference to the flow chart of figure 4.
Start from step 100 to getting into processing of request, confirm in step 100 whether the request of getting into is the SOAP request.In the non-limiting example of Fig. 4, the information run time of having only the SOAP request to be filtered with acquisition.If this request is the SOAP request; Then in step 101, being utilized in the URL identification of asking the head middle finger to show asks the web service of institute's addressing (if not only filter the SOAP request; Also filter the request of other types, then other technologies can be used for being identified in the web service of addressing in the request of entering).
If being labeled, corresponding web service do not report (that is, not being labeled information run time of the collection), perhaps even do not known that then it is forwarded and by the web service processing of institute's addressing, and no longer relates to service filter in step 104 by filter.In this case, can send alarm and have the such fact of unknown service to inform.
Otherwise information run time of in step 105, the collection from request is for example with relevant information such as requesting client, main frame, timestamp and sizes.All to run time information above-mentioned replacement (and possibly revise) to the request of getting into can in this step, obtain by filter.The run time information that is obtained can be stored in this locality, and is as shown in Figure 4, perhaps sent to the registry (not shown) immediately.
After the information, this request is forwarded to the web service in step 106 run time of in step 105, from request, the collection.Response from the web service is served filter process in step 107, and likewise is stored in this locality or is forwarded to registry immediately.If the result of step 105 and 107 is stored in this locality, then also have another step 108, wherein all results are sent to registry.Subsequently, the response from the web service is returned client in step 109.Yet, this response also can run time information be sent to before the registry or be forwarded to client with it simultaneously.In addition, the data that obtained can be sent to registry immediately after each request, but are periodically sent to registry after for example only after having passed through a certain amount of time, perhaps having handled the request of predetermined number.
As a result, registry 30 comprises all information of the web service of being registered, promptly its describe and run time information.This run time information exemplarily be presented in the snapshot of Fig. 5.As shown in the figure, the table that is shown comprises each row with information exemplary run time.And a leftmost row sign web service, the IP address of the client of the 3rd row indication contact service.Row indication request size in addition and its response and user, the server that the web service is provided, the port and the URL of server, this URL is used in the request with contact web service.Last two row comprise the timestamp of request and corresponding response.This simplification example can derive the valuable information about the performance of web service, is used to the response time that respective request provides service because the time difference between these two timestamps has reflected.
The web service that Fig. 6 representes can to obtain from registry 30 and registered relevant run time information another example.Circular branchs trrellis diagram (pie chart) is illustrated in during the section sometime the comparative result of some requests that the web to SOA serves.Thereby the keeper can easily discern more normal requested web service (for example, web service " XCITransformerService ").
If web service is by too much request, then this situation will be reflected in the circle branch trrellis diagram of Fig. 6, and the keeper can start counter-measure immediately, and other requests that for example will go to the web service of overload are redirected to another end points.As a result, described system and method allows the user to obtain static state and the dynamically global view and the control of aspect to the SOA that is managed.
Claims (16)
1. system that is used to manage a plurality of web services of service-oriented architecture comprises:
A. registry (30), be included in registration in the said registry (30) to each the description in said a plurality of web services (20);
B. service filter (40), it is suitable for filtering at least one at least one request (11) of client in the said web service (20) that is invoked at registration in the said registry (30);
C. wherein said service filter (40) is suitable for the system is characterized in that according in the said registry (30) the run time information that provides the web of service to serve (20) about described request (11) with for this request being collected in the description of corresponding web service (20):
D. this system is suitable for information of being collected by said service filter (40) and the description of said web being served (20) together are stored in the said registry (30).
2. the system of claim 1, wherein said service filter (40) also are suitable for described request (11) being revised in the description of said corresponding web service (20) at run duration in according to said registry (30).
3. system as claimed in claim 2 wherein revises request (11) and comprises the 2nd web service that the request (11) of going to web service is redirected to registration in said registry (30).
4. like any one the described system among the claim 1-3, wherein said service filter (40) also is suitable for collecting the statistics about the operating position of invoked web service (20).
5. like any one the described system among the claim 1-3, wherein said service filter (40) also is suitable for supervising the availability of invoked web service (20).
6. system as claimed in claim 5, wherein said service filter (40) also are suitable under invoked web service (20) disabled situation, giving the alarm.
7. like any one the described system among the claim 1-3; Wherein said service filter (40) also is suitable for carrying out in said registry (30) at run duration at least once searches, and the wherein said result who searches confirms to described request (11) and/or from the processing of the response of said web service (20).
8. like any one the described system among the claim 1-3, wherein said service filter (40) is served as service broker (45).
9. a plurality of web service method that are used to manage service-oriented architecture may further comprise the steps:
A., registry (30) is provided, said registry (30) be included in registration in the said registry (30) to each the description in said a plurality of web services (20);
B., service filter (40) is provided, and said service filter is suitable for filtering at least one at least one request (11) of client (10) in the said web service (20) be invoked at registration in the said registry (30); And
C. according in the said registry (30) description of corresponding web service (20) being utilized the run time information that said service filter (40) is collected provides the web of service to serve (20) about at least one request (11) with for this request, the method is characterized in that:
D. said service filter (40) together is stored in collected information and the description of said web being served (20) in the said registry (30).
10. method as claimed in claim 9, wherein said service filter (40) is revised request (11) to the description of said corresponding web service (20) at run duration in according to said registry (30).
11. method as claimed in claim 10, wherein said service filter (40) will be gone to the 2nd web service that the request (11) of web service is redirected to registration in said registry (30).
12. like any one the described method among the claim 9-11, wherein said service filter (40) is collected the statistics about the operating position of invoked web service (20).
13. like any one the described method among the claim 9-11, the availability of the invoked web service of wherein said service filter (40) supervision (20).
14. method as claimed in claim 13, wherein said service filter (40) are served under (20) disabled situation at invoked web and are given the alarm.
15. like any one the described method among the claim 9-11, wherein said service filter (40) is carried out in said registry (30) at run duration and is at least once searched.
16., also comprise providing said service filter (40) to serve as the step of service broker (45) like any one the described method among the claim 9-11.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP06011491.5 | 2006-06-02 | ||
| EP06011491A EP1863258B1 (en) | 2006-06-02 | 2006-06-02 | System and method for managing web services |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101087312A CN101087312A (en) | 2007-12-12 |
| CN101087312B true CN101087312B (en) | 2012-07-04 |
Family
ID=37451042
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101107097A Active CN101087312B (en) | 2006-06-02 | 2007-06-01 | System and method for managing web services |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US8180849B2 (en) |
| EP (1) | EP1863258B1 (en) |
| CN (1) | CN101087312B (en) |
| AT (1) | ATE421221T1 (en) |
| DE (1) | DE602006004856D1 (en) |
| HK (1) | HK1115776A1 (en) |
Families Citing this family (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2073123B1 (en) | 2007-12-21 | 2014-03-12 | Software AG | Method and system for monitoring a service oriented architecture |
| CN101471939B (en) * | 2007-12-28 | 2012-07-04 | 中国科学院声学研究所 | Multitime user authentication method for fusion business system with SOA architecture |
| FR2934099B1 (en) * | 2008-07-17 | 2012-10-19 | Alcatel Lucent | METHOD FOR ACCESSING WEB RESOURCES AND SERVER USING SUCH A METHOD |
| US8161055B2 (en) * | 2008-09-26 | 2012-04-17 | International Business Machines Corporation | Filter extraction in a service registry environment |
| EP2172879A1 (en) | 2008-10-06 | 2010-04-07 | Software AG | Method and monitoring system for the rule-based monitoring of a service-oriented architecture |
| US8041722B2 (en) * | 2008-10-07 | 2011-10-18 | International Business Machines Corporation | Refining collections of entities in a service registry environment |
| CN101414945B (en) * | 2008-10-15 | 2011-05-25 | 上海道仑软件有限公司 | Method for processing service by construction platform system of information system |
| US8341212B2 (en) * | 2008-10-30 | 2012-12-25 | International Business Machines Corporation | Service description refinement based on actual service use |
| US8707259B2 (en) * | 2008-11-19 | 2014-04-22 | Microsoft Corporation | Framework for open dynamic reflective applications |
| US8219532B2 (en) | 2008-12-22 | 2012-07-10 | International Business Machines Corporation | Smart mediation system in a service oriented architecture |
| US8271615B2 (en) | 2009-03-31 | 2012-09-18 | Cloud Connex, Llc | Centrally managing and monitoring software as a service (SaaS) applications |
| MY164485A (en) * | 2009-07-20 | 2017-12-29 | Mimos Berhad | A method and system for an intelligent framework of a service orientated architecture |
| US10971032B2 (en) * | 2010-01-07 | 2021-04-06 | John Allan Baker | Systems and methods for providing extensible electronic learning systems |
| US20120072307A1 (en) * | 2010-09-21 | 2012-03-22 | Farhang Kassaei | Providing a marketplace for software services |
| CN102571727A (en) * | 2010-12-31 | 2012-07-11 | 青岛海尔软件有限公司 | Digital family-service-oriented architecture system |
| US9389922B2 (en) | 2011-03-11 | 2016-07-12 | International Business Machines Corporation | Declarative service domain federation |
| EP2557752B1 (en) * | 2011-08-11 | 2017-09-27 | Siemens Aktiengesellschaft | Method and device for producing an end-to-end communication between two networks |
| US9626700B1 (en) | 2011-09-29 | 2017-04-18 | Amazon Technologies, Inc. | Aggregation of operational data for merchandizing of network accessible services |
| US8776043B1 (en) | 2011-09-29 | 2014-07-08 | Amazon Technologies, Inc. | Service image notifications |
| US9530156B2 (en) | 2011-09-29 | 2016-12-27 | Amazon Technologies, Inc. | Customizable uniform control user interface for hosted service images |
| CN102571989A (en) * | 2012-03-09 | 2012-07-11 | 东莞华中科技大学制造工程研究院 | Service-oriented architecture based cloud cutting layout system and implementation method for same |
| US9397987B1 (en) * | 2012-03-23 | 2016-07-19 | Amazon Technologies, Inc. | Managing interaction with hosted services |
| US9258371B1 (en) | 2012-03-23 | 2016-02-09 | Amazon Technologies, Inc. | Managing interaction with hosted services |
| WO2014101926A1 (en) * | 2012-12-27 | 2014-07-03 | Telecom Italia S.P.A. . | Method for guaranteeing service continuity in a telecommunication network and system thereof |
| KR101534153B1 (en) * | 2013-08-23 | 2015-07-06 | 주식회사 엘지씨엔에스 | Method of designing business logic, server performing the same and storage media storing the same |
| EP3063652B1 (en) | 2013-10-30 | 2020-04-29 | Hewlett-Packard Enterprise Development LP | Application programable interface (api) discovery |
| US9026652B1 (en) | 2014-07-09 | 2015-05-05 | Fmr Llc | Web service asset management and web service information storage |
| CN104133717A (en) * | 2014-08-26 | 2014-11-05 | 中电海康集团有限公司 | Service automatic generation and deployment method for data open system |
| US11240286B2 (en) | 2015-06-29 | 2022-02-01 | International Business Machines Corporation | Software request-filtering predictive technique based on resource usage probabilities |
| US10158551B2 (en) * | 2015-12-16 | 2018-12-18 | Software Ag | Systems and/or methods for automated testing and monitoring of backend services |
| US10270846B2 (en) * | 2016-08-11 | 2019-04-23 | Dell Products L.P. | System and method for monitoring a service-oriented architecture in a load-balanced environment |
| CN109165152B (en) * | 2018-07-31 | 2022-11-15 | 上海幻电信息科技有限公司 | Method, system and storage medium for monitoring performance of WEB system |
| US11375032B2 (en) * | 2018-12-20 | 2022-06-28 | Ebay Inc. | Traffic mirroring |
| CN110012053B (en) * | 2018-12-25 | 2021-07-20 | 创新先进技术有限公司 | System calling method, device and equipment under SOA system architecture and SOA system architecture |
| CN109783257B (en) * | 2019-01-29 | 2020-11-03 | 清华大学 | Batch Web service passive fault-tolerant selection and replacement method and system |
| US11080114B2 (en) * | 2019-11-26 | 2021-08-03 | International Business Machines Corporation | Controlling interaction with a scalable application |
| US11356524B1 (en) | 2020-12-18 | 2022-06-07 | International Business Machines Corporation | Coordinating requests actioned at a scalable application |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7549153B2 (en) * | 2002-07-22 | 2009-06-16 | Amberpoint, Inc. | Apparatus and method for content and context processing of web service traffic |
| US20040111506A1 (en) * | 2002-12-10 | 2004-06-10 | International Business Machines Corporation | System and method for managing web utility services |
| US20040193703A1 (en) * | 2003-01-10 | 2004-09-30 | Guy Loewy | System and method for conformance and governance in a service oriented architecture |
| WO2005060203A1 (en) * | 2003-12-10 | 2005-06-30 | International Business Machines Corporation | Method of redirecting client requests to web services |
| US8516123B2 (en) * | 2004-02-12 | 2013-08-20 | Oracle International Corporation | Runtime validation of messages for enhanced web service processing |
| US8484348B2 (en) * | 2004-03-05 | 2013-07-09 | Rockstar Consortium Us Lp | Method and apparatus for facilitating fulfillment of web-service requests on a communication network |
| WO2005114488A2 (en) * | 2004-05-21 | 2005-12-01 | Computer Associates Think, Inc. | System and method for actively managing service-oriented architecture |
| US8738759B2 (en) * | 2004-09-23 | 2014-05-27 | Hewlett-Packard Development Company, L.P. | System and method for service response monitoring |
| US20060235733A1 (en) * | 2005-04-13 | 2006-10-19 | Marks Eric A | System and method for providing integration of service-oriented architecture and Web services |
| US20070233782A1 (en) * | 2006-03-28 | 2007-10-04 | Silentclick, Inc. | Method & system for acquiring, storing, & managing software applications via a communications network |
| US8230448B2 (en) * | 2006-05-09 | 2012-07-24 | Netiq Corporation | Methods, systems and computer program products for web service interaction with a resource management system |
| US7865584B2 (en) * | 2006-06-20 | 2011-01-04 | Alcatel Lucent | Network service performance monitoring apparatus and methods |
-
2006
- 2006-06-02 AT AT06011491T patent/ATE421221T1/en not_active IP Right Cessation
- 2006-06-02 EP EP06011491A patent/EP1863258B1/en active Active
- 2006-06-02 DE DE602006004856T patent/DE602006004856D1/en active Active
-
2007
- 2007-05-09 US US11/746,150 patent/US8180849B2/en active Active
- 2007-06-01 CN CN2007101107097A patent/CN101087312B/en active Active
-
2008
- 2008-05-26 HK HK08105805.6A patent/HK1115776A1/en not_active IP Right Cessation
Also Published As
| Publication number | Publication date |
|---|---|
| EP1863258A1 (en) | 2007-12-05 |
| EP1863258B1 (en) | 2009-01-14 |
| US20070300240A1 (en) | 2007-12-27 |
| ATE421221T1 (en) | 2009-01-15 |
| DE602006004856D1 (en) | 2009-03-05 |
| US8180849B2 (en) | 2012-05-15 |
| CN101087312A (en) | 2007-12-12 |
| HK1115776A1 (en) | 2008-12-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101087312B (en) | System and method for managing web services | |
| CN111443940B (en) | Complete software life cycle management method and system based on DevOps | |
| US20060282886A1 (en) | Service oriented security device management network | |
| CN101605056B (en) | J2EE server monitoring device and monitoring method employing same | |
| US7272626B2 (en) | E-service management through distributed correlation | |
| US8751573B2 (en) | Cloud-processing management with a landscape directory | |
| US6983317B1 (en) | Enterprise management system | |
| US8078922B2 (en) | Internal server error analysis | |
| US7930381B2 (en) | Efficient monitoring of heterogeneous applications | |
| CN1934538B (en) | Anomaly management scheme for a multi-agent system | |
| Chu et al. | Open sensor web architecture: Core services | |
| US8683587B2 (en) | Non-intrusive monitoring of services in a services-oriented architecture | |
| CN111552556B (en) | GPU cluster service management system and method | |
| MX2007012895A (en) | Apparatus and method for managing a network of intelligent devices. | |
| CN101297536A (en) | A method and system for preparing execution of systems management tasks on endpoints | |
| EP3796167A1 (en) | Router management by an event stream processing cluster manager | |
| US20080162690A1 (en) | Application Management System | |
| US7660702B2 (en) | Monitor for an information technology system | |
| CN109460307B (en) | Micro-service calling tracking method and system based on log embedded point | |
| CN101174983B (en) | System and method for managing a plurality of web services | |
| EP1118952A2 (en) | System, method and computer program product for providing a remote support service | |
| Cowan et al. | BlueJADE–A service for managing software agents | |
| Deussen et al. | An on-line test platform for component-based systems | |
| Xu et al. | The Information Integration Platform for Satellite Earth Station based on The Dynamic Workflow Model | |
| CN117880098A (en) | Method and system for real-time management of micro-service configuration |
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 |