[go: up one dir, main page]

WO2002013018A2 - Système et procédé de surveillance de composante de transaction - Google Patents

Système et procédé de surveillance de composante de transaction Download PDF

Info

Publication number
WO2002013018A2
WO2002013018A2 PCT/US2001/024374 US0124374W WO0213018A2 WO 2002013018 A2 WO2002013018 A2 WO 2002013018A2 US 0124374 W US0124374 W US 0124374W WO 0213018 A2 WO0213018 A2 WO 0213018A2
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
trans
http
monitoring
command
Prior art date
Application number
PCT/US2001/024374
Other languages
English (en)
Other versions
WO2002013018A3 (fr
Inventor
Jules Damji
Original Assignee
Loudcloud, Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Loudcloud, Inc filed Critical Loudcloud, Inc
Priority to AU2001281030A priority Critical patent/AU2001281030A1/en
Publication of WO2002013018A2 publication Critical patent/WO2002013018A2/fr
Publication of WO2002013018A3 publication Critical patent/WO2002013018A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3086—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves the use of self describing data formats, i.e. metadata, markup languages, human readable formats
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • G06F11/3093—Configuration details thereof, e.g. installation, enabling, spatial arrangement of the probes
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • G06F11/3414—Workload generation, e.g. scripts, playback
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • G06F11/3495—Performance evaluation by tracing or monitoring for systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/87—Monitoring of transactions
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/875—Monitoring of systems including the internet

Definitions

  • the present invention relates generally to systems and methods for monitoring the functionality performance of computer-related transactions, e.g., those which occur on web sites. More particularly, the present invention relates to systems and methods for monitoring such transactions in a manner which is both scalable and customized.
  • the global, distributed computer network known as the Internet became a powerful tool for business.
  • Whole new categories of business, referred to by the umbrella term of "e-commerce" were created to take advantage of the potential efficiencies provided by rapid, global information exchange and these new businesses quickly captured the attention of both the public and private industry.
  • the Internet acts as a transport mechanism for the World Wide Web, which can be described as a global, interconnected system of navigational links between collections of data.
  • the World Wide Web is comprised of a very large number of web sites, each of which is a smaller group of linked data collections, e.g., web documents, that is accessible via the interconnected computer network.
  • TCP/IP Transfer Control Protocol/Internet Protocol
  • HTTP HyperText Markup Language
  • HTML HyperText Transfer Protocol
  • Web object addresses have been standardized by uniform resource locators (URLs) which uniquely identify a location of an object for retrieval via the World Wide Web.
  • URLs uniform resource locators
  • web sites employed in e-commerce were typically designed, constructed, and operated by the same organization, often by the same people. Such e-commerce companies therefore had complete control and understanding of all of the software used in running their web site.
  • This software included both high level graphical user interface and linking code, as well the business logic code (i.e., code performing business-related functions such as a shopping basket, order management, chat, searching, etc.) which underlies the display and document linking functionality of the web site. This provided the site operators with all of the knowledge needed to design and implement additional software for monitoring the operation of the business logic code.
  • mapping tools which aid in understanding the contents and linkages of data collections within a web site, or automated load and performance testing tools, whereby software simulates traffic to a web site to test the site's performance and identify bottlenecks.
  • An example of the former type of tool can be found in U.S. Patent No. 5,870,559, entitled “Software System and Associated Methods for Facilitating the Analysis and Management of Web Sites", assigned to Mercury Interactive, the disclosure of which is incorporated here by reference.
  • An example of the latter type of tool can be found in U.S. Patent No.
  • agent which term is intended to refer to a program which can be either continuously or intermittently rarrning) within their business logic code through a defined process, and to have this agent interact with universal monitoring software.
  • solutions according to the present invention are both scalable and provide customized, detailed feedback regarding the web site's operational status.
  • the customer is given guidelines and/or an implementation interface for creating one or more transaction monitoring agents which are specific to their web site.
  • the universal monitoring software invokes the agent(s) with a customer-defined periodicity using a predetermined URL.
  • the transaction monitoring agent(s) interact with the business logic code of the web site to determine whether the business logic code is functioning correctly, i.e., whether the customer's software components are both reachable and functional.
  • the transaction monitoring agent(s) then pass report data in a predetermined format, e.g. , an XML document have predefined fields, containing the results of the monitored transactions through the predetermined URL back to the universal monitoring software.
  • the document(s) can then be parsed, since they contain at least some predefined, universal components, and the resulting values can be evaluated by event logic coded within the universal monitoring software. Based upon this logic, a variety of actions can be taken, e.g. , notifying various people within either the web site hosting company or the e-commerce customer company of a particular problem with the web site.
  • the present invention therefore provides, among other advantages, the opportunity for the customer to leverage its knowledge of the business logic code employed within a web site to create and update transaction monitoring agents, and allow these transaction monitoring agents to interact with universal monitoring software ranning, for example, on a web hosting company's operational systems.
  • the web hosting company need only implement one universal monitoring architecture which can monitor, through interaction with the transaction monitoring agents, the functionality of any or all of their customer's web sites.
  • Figure 1 describes a transaction monitoring architecture according to exemplary embodiments of the present invention
  • FIG. 2 is a flowchart which illustrates an exemplary transaction monitoring method according to an exemplary embodiment of the present invention
  • Figure 3 conceptually depicts exemplary fields of a document that can be returned by the transaction monitoring agent according to the present invention
  • Figure 4 illustrates a universal monitoring module which monitors the transactions performed by transaction agents at multiple web sites.
  • Figure 1 depicts an exemplary architecture for transaction monitoring according to the present invention.
  • the architecture has been subdivided into two sections separated by a dotted line, specifically, a universal monitoring module 10 and a customer side which hosts the transaction agent 20.
  • This manner of illustrating an exemplary embodiment of the present invention has been selected for ease of description and should not be considered as limiting of the present invention, which is amenable to any desired architecture.
  • the software functionality of the customer to be monitored may, or may not, be hosted by a third party's hardware.
  • the term "customer" is intended to include all types of computer systems and software whose functionality can be monitored including, but not limited, to web sites.
  • the universal monitoring module 10 includes a number of functional modules.
  • a URL fetcher module 100 provides the requisite functionality for transmitting a command signal which invokes the customized transaction agent. This can occur with a periodicity which is defined by the web site owner.
  • the URL fetcher 100 can invoke the transaction agent by transmitting an HTTP GET command over the Internet or an intranet to a unique URL which has been provided for the web/application server 200.
  • the URL fetcher 100 operates as a "tickler" mechanism for initiating the customized transactions at the web site from which the monitoring results are gleaned.
  • the universal monitoring module 10 also includes, for example, an XML parser which receives, in this example, an XML document containing the results of the monitored transactions.
  • the XML parser 110 parses out of the XML document the values of various predefined fields, examples of which will be described below.
  • the universal monitoring module 10 further includes an event dispatcher 130 which contains the logic that is applied to the results of the transaction monitoring received from the XML parser 110. Based upon this logic, the event dispatcher may take a variety of different actions such as: notifying a network operations center (NOC), e.g., via an SNMP trap event, of a particular problem which is identified in the XML document (and/or the severity level of the problem), sending the results to a mail server to issue an e-mail page alert to interested parties (e.g.
  • NOC network operations center
  • a web/application server 200 is operative to receive HTTP commands and output responses thereto.
  • an LDAP server 210 Connected to the web/application server 200 in this particular example are an LDAP server 210, an application server 220 and a database 230.
  • a transaction agent may be developed on the customized side of the architecture to test the reachability and functionality of the LDAP server 210, the application server 220 and/or the database 230 to provide a balanced monitoring result regarding the operation of the web site supported by server 200.
  • the transaction monitoring agent itself may reside on any of the servers (the web server, the app server, etc.) within the architecture of the customer site. If there is more than one of a certain type of server, such as web server, then instances of the transaction agent can reside on any or all of the customer's web servers, e.g., to allow monitoring of each of these servers independently.
  • the universal monitoring module 10 will invoke a transaction agent 20 associated with the web site to be monitored.
  • a transaction agent 20 associated with the web site to be monitored.
  • universal monitoring module 10 can transmit an HTTP GET command to a predetermined URL associated with the intended transaction agent at step 240. Examples of such HTTP GET commands are provided below.
  • URLs can be authenticated or provided as a protected resource using either base 64 or MD5 digests. Such authentication or protection may be desirable in order to avoid unauthorized access to the monitoring tools provided by the transaction agents in a particular web site.
  • the transaction agent associated with the URL in the GET command is launched or activated.
  • This transaction agent will perform one or more transactions with components of the web site.
  • These components may include, for example, the LDAP server 210, the application server 220 or the database 230 illustrated in Figure 1.
  • components may include, for example, the LDAP server 210, the application server 220 or the database 230 illustrated in Figure 1.
  • the particular components, links and transactions which are predefined in the transaction agent for performance upon receipt of the HTTP GET command should be customized for any particular web site to provide an accurate monitoring result regarding the reachability and functionality of the web site components.
  • a more detailed example of a transaction agent is also provided below in Appendix A.
  • the predefined format permits the universal monitoring module 10 to operate on the results, regardless of the differences between the web sites that it monitors.
  • the predefined format is an XML document.
  • an XML document it is possible to use tags that describe the type of data contained within the XML document, however, those skilled in the art will further appreciate that the predefined format can take other forms than an XML document, e.g. , a text document.
  • an XML document based on the transaction results is generated, for example, by an application program interface (API).
  • API application program interface
  • the XML document is transferred to the universal monitoring module 10.
  • the XML document is then parsed at step 250 to extract the predefined fields. These predefined fields are then evaluated by the event dispatcher 120 at step 252. Based upon the field values which are identified as a result, the event dispatcher 120 will then selectively transmit one or more messages and/or take other desirable actions at step 254 to indicate the results of the monitored transactions.
  • the event dispatcher 120 may also store and/or post transaction results, e.g., to the performance database 160.
  • Transaction Agent URL Invoking the Transaction Agent and Response
  • a predetermined URL is assigned to each transaction agent 20 to provide a mechanism that permits the universal monitoring module 10 to invoke that agent.
  • Each web site that is monitored according to the present invention may have more than one such predetermined URLs if it is desirable to break up the monitored components into separate agents, e.g., if certain portions of the web site should be tested less frequently than other portions of the web site.
  • the format for the transaction agent URL may vary, but the following are examples of such URLs.
  • the transaction agent 20 is invoked by the transmission of a command by the universal monitoring module 10. These commands may be designed to require password protection or authentication prior to launching the transaction agent as a security precaution.
  • passwords are conveyed as arguments to the URL.
  • the request headers themselves can include the authentication credentials to be validated prior to launching the transaction agent. Examples of HTTP GET commands which can be used to invoke the transaction agent are provided below, one of which employs Base 64 encoding of an MD5 hashed username and password, whereas the second example just employs the Base 64 encoding.
  • the web/application server 200 which is hosting the transaction agent (as well as the web site to be tested) can then return a suitable response. For example, if the authentication is valid, the server 200 can transmit a response header back to the universal monitoring module 10 as:
  • the server 200 can send, for example, one of the following response headers back to the universal monitoring module: 2.
  • AGENT SERVER RESPONSE MD5 Authentication Fails
  • HTTP/1.1 401 Authorization Required Date- July 31, 2000 19:56:09 GMT WWW- Authenticate: MD5 realm "user" • Content-Type: text/plain
  • the results of the monitored transactions should be returned to the universal monitoring module 10 in a predetermined format and using certain predefined, recognizable values so that the universal monitoring module 10 can operate on results being returned from a wide variety of different web sites, as will be illustrated and described below.
  • an XML document with the predefined fields illustrated in Figure 3 can be used to return monitoring results to the universal monitoring module 10.
  • These predefined fields can be used to pass values which provide the following monitoring functionality.
  • trans category This field in the returned XML document contains a customizable token or group identifier which can be used by the universal monitoring module to group similar or identical transactions.
  • trans_no A field which contains a step number which can be automatically incremented to reflect a sequence of transactions.
  • trans_name A field which contains a name for the transaction being monitored.
  • trans desc A field which contains a customizable description of the transaction which will be meaningful for usage in messages transmitted by the event dispatcher 130. For example, this field could contain a string such as: "LDAP user/passwd authentication with LDAP server ldap.loudcloud.com:389". 5. trans_status. A field which contains a customizable status for the transaction, e.g., indicative of success or error for that transaction. Again, the contents of this field can be used by the event dispatcher as part of an alert mechanism. For instance, this field could contain the string: "Failed to establish Connection to LDAP server Idap,loudcloud.com:389".
  • trans_rtt_ms This field contains a value reflective of the response time e.g., in milliseconds, for the latency experienced in performing the transaction during the current step.
  • trans_lc.status This field contains a string having one of a plurality of predefined values known to the universal monitoring module 10, e.g., "SUCCESS” or "FAILURE” to provide an absolute indication of the status of the monitored transaction.
  • trans_lc.severity This field contains a string having one of a plurality of predefined values known to the universal monitoring module that reflects a level of severity associated with the condition reported in the trans_lc. status field, e.g., "NORMAL”, 'WARNING", “ERROR”, “FATAL".
  • a set of exemplary XML documents is also provided as Appendix B. These documents reflect exemplary output gathered by the exemplary Java servlet transaction agent which precedes them in the Appendix A.
  • a plurality of customers 1-N e.g., 400, 410, 420 and 430 are associated with a plurality of web sites to be monitored by a single universal monitoring module 10.
  • each of the customers has their own (at least one) URL enabled transaction monitoring agent which can be invoked by, for example, the transmission of a corresponding GET command thereto.
  • each customer site web server returns XML documents having the same or similar predefined fields to the universal monitoring module 10, so that the universal monitoring module 10 can parse the results of the transactions being monitored and take appropriate action.
  • the single universal monitoring module 10 can be used to monitor the activities of many different web sites, thus rendering monitoring techniques according to the present invention eminently scalable.
  • the monitoring feedback provided by universal monitoring module 10 can be focused on mission critical transaction components and provide customer-tailored alerting functionality.
  • the web site to be monitored may be hosted by a third party or not, the universal monitoring module may share a server or a network with the transaction monitoring agent(s), etc. All such variations and modifications are considered to be within the scope and spirit of the present invention as defined by the following claims.
  • Java Servlet import java.io.*; import java.util.*; importjava.net.*; import Java. sql.*; import j ava . security . * ; import j avax . servlet . * ; import javax.servlet.http. *;
  • TestTicklerAuthArgs extends HttpServlet ⁇ public void doGet (HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException
  • HttpServletResponse response String custName
  • IOException ⁇ super(request, response, custName); initO;
  • PrintWriter out new PrintWriter(getTransResponse() . getWriter()) ; if (!authCheck(getTransRequest())) ⁇ setAuthError(response, out); return;
  • doDbTrans(getTransRequest()) doXXXCheck(); doYYYCheckO; doZZZCheck(); doRPCCheckO; doVerityCheck(); doWrapUpO; ⁇
  • ⁇ catch (IOException e) ⁇ rt System. currentTimeMillisO - tl; setTransTagVal(TRANS_STATUS, e.getMessageO); setTransTagVal(TRANS_RTT_MS, Long . toString(rt)) ; setTransTagVal(TRANS_LC_STATUS , lcStatus[TRANS_LC_STATUS_FAIL]); setTransTagVal(TRANS_LC_SEVERITY, lcSeverity[TRANS_LC_SEVERITY_FATAL]);
  • Thread.sleep(1500); ⁇ catch (Exception e) ⁇ ⁇ rt System. currentTimeMillisO - tl; setTransTagVal(TRANS_RTT_MS, Long.toString(rt));
  • the client will receive a 401 error private void setAuthError(HttpServletResponse res, PrintWriter out) ⁇ try ⁇ res.sendError(res.SC UNAUTHORIZED);
  • trans_rtt_ms 601 ⁇ /trans_rtt_ms > ⁇ trans_lc_status > SUCCESS ⁇ /trans_lc_status > ⁇ trans_lc_severity>NORMAL ⁇ /trans_lc_severity> ⁇ /trans>
  • trans_rtt_ms 350 ⁇ /trans_rtt_ms > ⁇ trans_lc_status > SUCCESS ⁇ /trans_lc_status > ⁇ tr ans_lc_s e verity > NORMAL ⁇ /tr ans_lc_s e verity > ⁇ /trans >
  • trans_rtt_ms 350 ⁇ /trans_rtt_ms >
  • trans_lc_status SUCCE SS ⁇ /trans_lc_status > ⁇ tr ans_lc_s e verity > NORMAL ⁇ /tr ans_lc_s e verity > ⁇ /trans > ⁇ /transactions >

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Computer Hardware Design (AREA)
  • Library & Information Science (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

La présente invention concerne des systèmes et procédés de surveillance de transactions et de composantes sur des sites web. Un module de surveillance universelle, pour appeler un agent de transaction associé au site web, émet notamment une commande HTTP GET à destination d'un URL unique associé à cet agent de transaction. L'agent de transaction, qui peut avoir été personnalisé par le propriétaire du site web pour tester l'atteignabilité et la fonctionnalité des composantes du site web, réalise au moine une transaction sur le site web et communique les résultats selon un format de compte rendu normalisé facilement analysable par le module de surveillance universelle. Ce module de surveillance universelle réagit alors, notamment en alertant les intervenants responsables du site, sur la base des données communiquées. Le recours à ce type de surveillance permet des fonctions de surveillance personnalisées bien qu'adaptables en taille.
PCT/US2001/024374 2000-08-04 2001-08-03 Système et procédé de surveillance de composante de transaction WO2002013018A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001281030A AU2001281030A1 (en) 2000-08-04 2001-08-03 Web site monitoring system and method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US63293200A 2000-08-04 2000-08-04
US09/632,932 2000-08-04

Publications (2)

Publication Number Publication Date
WO2002013018A2 true WO2002013018A2 (fr) 2002-02-14
WO2002013018A3 WO2002013018A3 (fr) 2003-09-25

Family

ID=24537579

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/024374 WO2002013018A2 (fr) 2000-08-04 2001-08-03 Système et procédé de surveillance de composante de transaction

Country Status (2)

Country Link
AU (1) AU2001281030A1 (fr)
WO (1) WO2002013018A2 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7565662B2 (en) 2004-09-24 2009-07-21 International Business Machines Corporation Program agent initiated processing of enqueued event actions
US8103720B2 (en) * 1999-07-26 2012-01-24 Microsoft Corporation Apparatus and computer-readable media for processing HTTP requests
US8767707B2 (en) 2010-04-23 2014-07-01 Blackberry Limited Monitoring a mobile data service associated with a mailbox

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2751448B1 (fr) * 1996-07-17 1999-01-15 Bull Sa Procede de surveillance en temps reel d'un systeme informatique pour son administration et l'aide a sa maintenance en phase d'exploitation
JP2000122952A (ja) * 1998-10-16 2000-04-28 Fuji Xerox Co Ltd 情報処理装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8103720B2 (en) * 1999-07-26 2012-01-24 Microsoft Corporation Apparatus and computer-readable media for processing HTTP requests
US8359391B2 (en) 1999-07-26 2013-01-22 Microsoft Corporation Apparatus and computer-readable media for processing HTTP requests determine scoping mapping between a mapped resource name extension and a content type
US7565662B2 (en) 2004-09-24 2009-07-21 International Business Machines Corporation Program agent initiated processing of enqueued event actions
US8767707B2 (en) 2010-04-23 2014-07-01 Blackberry Limited Monitoring a mobile data service associated with a mailbox

Also Published As

Publication number Publication date
WO2002013018A3 (fr) 2003-09-25
AU2001281030A1 (en) 2002-02-18

Similar Documents

Publication Publication Date Title
US6874099B1 (en) Method and software for testing and performance monitoring
US7024662B2 (en) Executing dynamically assigned functions while providing services
US6665674B1 (en) Framework for open directory operation extensibility
US7246263B2 (en) System and method for portal infrastructure tracking
US7143444B2 (en) Application-layer anomaly and misuse detection
US6799147B1 (en) Enterprise integrated testing and performance monitoring software
US20020120685A1 (en) System for dynamically invoking remote network services using service descriptions stored in a service registry
US6859833B2 (en) Method and apparatus for redirection of server external hyper-link references
US8990262B2 (en) managing data center using web services
US6519714B1 (en) Evaluating computer resources
US7398291B2 (en) Method, system and program product for providing a status of a transaction with an application on a server
US8285778B2 (en) Protecting web application data
US8819831B2 (en) Remote procedure call (RPC) services fuzz attacking tool
Jepsen SOAP cleans up interoperability problems on the Web
US9092448B2 (en) System and method for portal infrastructure tracking
Benameur et al. XML rewriting attacks: existing solutions and their limitations
Davis et al. A comparative study of DCOM and SOAP
Mundy et al. An XML alternative for performance and security: ASN. 1
US9578031B2 (en) Non-invasive method and system for automated administration of diverse security constrained servers
WO2002013018A2 (fr) Système et procédé de surveillance de composante de transaction
CN113673991B (zh) 跨链数据处理方法和装置
Zhang et al. An approach to help select trustworthy Web services
Johnsen et al. A description of the manufacturing message specification (MMS)
Spielman et al. Using Advanced Servlet Features
HK40062630A (en) Cross-chain data processing method and apparatus

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP