XML-based multi-format business services design pattern
IPC분류정보
국가/구분
United States(US) Patent
등록
국제특허분류(IPC7판)
G06F-015/00
G06F-017/00
출원번호
US-0981453
(2001-10-18)
등록번호
US-7296226
(2007-11-13)
발명자
/ 주소
Junkermann,Jens B.
출원인 / 주소
Accenture GmbH
대리인 / 주소
Brinks Hofer Gilson & Lione
인용정보
피인용 횟수 :
31인용 특허 :
21
초록▼
A design pattern for a software architecture includes a business services layer comprising ApiService class, BusinessService class, Message class and Field class. ApiService class accepts a request that includes request parameters and utilizes corresponding instances of Message class and Field class
A design pattern for a software architecture includes a business services layer comprising ApiService class, BusinessService class, Message class and Field class. ApiService class accepts a request that includes request parameters and utilizes corresponding instances of Message class and Field class to translate the request to an input message. The instances of Message and Field class contain the request parameters in self-describing form, namely, field names and associated values. The input message is forwarded to the appropriate subclass of BusinessService class by ApiService class. The subclass of BusinessService class uses the input message to retrieve data and generate an output message containing the data. The output message is generated in self-describing form utilizing Message class and Field class. ApiService class translates the output message to a presentation format identified by the request.
대표청구항▼
What is claimed is: 1. A method of operating a business services application for retrieving data with delivery technologies, the method comprising: receiving at a server a request for information initiated with a delivery technology; translating the request to a first document object model document
What is claimed is: 1. A method of operating a business services application for retrieving data with delivery technologies, the method comprising: receiving at a server a request for information initiated with a delivery technology; translating the request to a first document object model document with an ApiService class operable on the server; during the translation with the ApiService class to the first document object model document, limiting with a Message class that is a wrapper of the document object model document a first data structure of the first document object model document to representation as an input message with a plurality of fields, wherein the first data structure is limited by a plurality of methods included in the Message class to represent a field data type that is pre-specified with the methods; executing custom application code to retrieve data based on the first document object model document; reading said data into a second document object model document with the custom application code; while said data is being read in with the custom application code, limiting a second data structure of the second document object model document with the methods included in the Message class to representation as an output message with a plurality of fields, wherein the second data structure is limited with the methods to represent the field data type that is pre-specified with the methods; and translating the second document object model document with the ApiService class to generate an output message in a format that is compatible with the delivery technology. 2. The method of claim 1, wherein limiting the first data structure of the first document object model document comprises populating a plurality of text nodes within the first document object model document with request parameters contained in the request that are translated with the methods to a format identified with the field data type. 3. The method of claim 2, wherein limiting the first data structure of the first document object model document further comprises limiting the field datatype to a string datatype. 4. The method of claim 1, wherein limiting the first data structure of the first document object model document comprises populating an attribute node within the first document object model document with an attribute of the request that is translated to a format identified with the field data type. 5. The method of claim 1, further comprising selecting, as a function of a mode debug flag, to use one of a short field name or a long field name as a field name for each of the fields in the first and second document object model documents. 6. The method of claim 1, wherein the field data types is selected from a pre-specifled group of data types consisting of a string datatype, a long datatype, an integer data type, a boolean data type and a group data type. 7. The method of claim 1, wherein limiting the first data structure of the first document object model document comprises loading a static declaration of a datatype based on a list of fields expected in the request. 8. The method of claim 1, wherein limiting the second data structure of the second document object model document comprises populating a plurality of text nodes within the second document object model document with said data read in to the second document object model document, wherein the format of said data that is read in is converted based on the field data type. 9. The method of claim 1, wherein limiting the second data structure of the second document object model document comprises populating an attribute node within the second document object model document with an attribute read in to the second document object model document that is translated to a format identified with the field data type. 10. The method of claim 1, wherein translating the second document object model comprises translating the second document object model document to extensible markup language text. 11. The method of claim 1, wherein translating the second document object model comprises translating the second document object model document to at least one of a hypertext markup language and a website meta language as a function of at least one extensible stylesheet language stylesheet. 12. The method of claim 1, wherein limiting the first data structure of the first document object model comprises standardizing the format of the document object model to be substantially similar for a similar request received from any one of a plurality of different delivery technologies. 13. The method of claim 12, wherein limiting the second data structure of the second document object model comprises standardizing the format of the second document object model to be compatible with any one of the different delivery technologies. 14. The method of claim 13, wherein executing the custom application code comprises executing the same custom application code for a similar request from any one of the different delivery technologies to provide a response. 15. The method of claim 1, wherein executing the custom application code comprises executing the same custom application code for a similar request from any one of a plurality of different delivery technologies. 16. The method of claim 15, wherein while the data is read in, limiting the second data structure of the second document object model document comprises similarly limiting the second document object model in response to similar requests from any of the different delivery technologies. 17. The method of claim 1, wherein translating the request comprises translating the request to a first instance of the Message class with the ApiService class, and creating the first document object model document with the first instance of the Message class. 18. The method of claim 17, wherein translating the request to the first instance of the Message class comprises adding an instance of a Field class to the first instance of the Message class for each of a plurality of request parameters included in the request. 19. The method of claim 17, wherein executing custom application code to retrieve data comprises executing the custom application code with the ApiService class to retrieve said data based on the first instance of the Message class. 20. The method of claim 19, wherein executing custom application code further comprises the custom application code storing said data in a second instance of the Message class through use of at least one of the methods included in the Message class, and returning to the ApiService class the second instance of the Message class. 21. The method of claim 20, wherein reading said data into a second document object model document comprises reading the document object model document from the second instance of the Message class with the ApiService class. 22. The method of claim 20, wherein storing said data in a second instance of the Message class further comprises: translating a value of said data, with at least one of the methods of the Message class, to a text value; and storing the text value in the second document object model document, the text value is one of a group of data types comprising a long integer data type, an integer data type, or a boolean data type. 23. The method of claim 20, wherein storing said data in a second instance of the Message class further comprises storing data type information from a MESSAGEDEFINTION class and a value in the second document object model document, the value generated with at least one of the methods of the Message class. 24. The method of claim 1, wherein the Message class comprises a plurality of instances of a Field class, the Field class operable as a second wrapper of a document object model Element class associated with the first document object model document. 25. The method of claim 24, wherein translating the request comprises translating the request to a first instance of the Message class with the ApiService class by adding an instance of the Field class to the first instance of the Message class for each of a plurality of request parameters included in the request, and creating the first document object model Element class with the instance of the Field class for each of the request parameters. 26. The method of claim 1, wherein translating the second document object model document with the ApiService class comprises translating the second document object model into one of XML or a presentation format based on the request. 27. The method of claim 26, wherein the presentation format is HTML. 28. The method of claim 26, wherein translating the second document object model further comprises using at least one XSL stylesheet to transform the second document object model to the presentation format. 29. A system to provide an interface between a back-end systems layer and a front-end systems layer, the system comprising: a server computer; an ApiService class operable within the server computer to translate a request to an input message that includes a plurality of fields; a document object model class operable within the server computer to represent the input message as a document object model document; a Message class operable within the server computer as a wrapper of the document object model class to restrict a format of the document object model document; a MESSAGEDEFINITION class operable in the server, wherein the MESSAGEDEFINITION class includes a listing of pre-specified fields each of which describe a corresponding pre-specified data type, and wherein the Message class is further operable, within the server during translation, to limit a format of fields included in the input message to a predetermined data structure based on the described corresponding pre-specifled data type; a BusinessService class operable within the server computer to execute custom application code based on the input message, wherein the custom application code includes a pre-specified data type to limit the format of those fields included in the input message that do not correspond to the listing of pre-specified fields, the custom application code is operable to process the input message to retrieve data, the custom application code and the Message class operable to translate the data to an output message that is transmitted by the server in response to the request. 30. The system of claim 29, wherein the output message is in the form of a document object model document with restricted and standardized content based on the pre-specifled data type included in the custom application code that, during translation with the Message class, is operable to limit a format of each of a plurality of fields included in the output message to a predetermined data structure. 31. The system of claim 29, wherein the ApiService class is operable to direct the conversion of the output message to a presentation format defined by the request. 32. The system of claim 29, wherein the input message and the output message comprises a root element and a plurality of sub-elements. 33. The system of claim 29, further comprising a Fldtypes class operable within the server computer, wherein the Fldtypes class comprises definitions of the format of datatypes for fields within the input message. 34. The system of claim 29, wherein the document object model document comprises a plurality of field names, the field names selectable with a mode debug flag as one of a short field name and a long field name. 35. The system of claim 34, wherein the short field name and the long field name are defined in the MESSAGEDEFINITION class operable within the server computer. 36. The system of claim 29, wherein the document object model class comprises a Document class, a document object model Element class and a plurality of ProcessingInstruction classes, the Message class operable as a wrapper of the Document class, the document object model Element class and the Processing Instruction classes. 37. The system of claim 29, wherein the document object model class comprises a document object model setAttribute method, and a Field class operable as a wrapper of the document object model setAttribute method. 38. The system of claim 29, wherein the BusinessService class comprises a subclass of the custom application code responsive to the request. 39. The system of claim 29, wherein the Message class is operable, during representation of the input message as the document object model document, to restrict manipulation of the document object model document. 40. The method of claim 29, wherein the pre-specified datatype is selected from the group consisting of integer, long, Boolean, string and group. 41. The system of claim 29, wherein the Message class is a first wrapper of the document object model document, and the system further comprises a Field class that is a second wrapper of a document object model Element class included in the document object model class, the Field class is operable to restrict a value stored in an instance of the document object model Element class. 42. The system of claim 41, wherein the Message class is operable to restrict creation of element nodes included in the document object model document and population of text nodes that correspond to the element nodes, and the Field class is operable to restrict creation of attribute nodes included in the document object model document. 43. The system of claim 29, wherein the Message class comprises a plurality of methods, and a format of a data structure of the document object model document is limited to data types that are pre-specified with the methods. 44. The system of claim 29, wherein the ApiService class is further operable to translate the output message to an XML format, wherein the ApiService class is operable to transmit the XML format as a response to the request. 45. The system of claim 29, wherein the ApiService class is further operable to translate the output message to a presentation format using a plurality of XSL stylesheets and to transmit the presentation format as a response to the request. 46. The system of claim 45, wherein the ApiService class is further operable to select the plurality of XSL stylesheets based on a format of the request. 47. An e-commerce architecture for providing a framework to interface delivery technologies with data, the e-commerce architecture comprising: a server computer operable to execute instructions to convert a request from a delivery technology to a first document object model document in an extensible markup language, the first document object model document comprising a plurality of request parameters extracted from the request; the server computer operable to execute instructions included in a Message class that is operable as a wrapper of the document object model document to restrict the conversion to the first document object model document based on a listing of data types that are pre-specified for the request parameters by a plurality of methods included in the Message class, wherein the data types limit a first data structure of a plurality of fields included in the first document object model document to a predetermined data structure specified by the data types; the server computer operable to execute instructions to retrieve data responsive to the request, and convert the data to a second document object model document in the extensible markup language based on the request parameters; the server computer operable to execute instructions included in a Message class that is operable as a wrapper of the document object model document to restrict the conversion of the data to the second document object model document to limit a second data structure of a plurality of fields included in the second document object model document to the predetermined data structure specified by the methods included in the Message class; and the server computer operable to execute instructions to generate an output message in a format that is compatible with the delivery technology. 48. The e-commerce architecture of claim 47, wherein the instructions to restrict the conversion of the first and second document object model documents further comprise instructions executable by the server computer to identify the first and second document object model documents with a predefined name included in the request. 49. The e-commerce architecture of claim 47, wherein the instructions to restrict the conversion of the first and second document object model documents further comprise instructions executable by the server computer to create a plurality of element nodes and populate a plurality of corresponding text nodes with the respective request parameters and the respective data. 50. The e-commerce architecture of claim 49, wherein the instructions to restrict the conversion of the first and second document object model documents further comprise instructions executable by the server computer to define the data type of each of the text nodes from among a predefined group of data types. 51. The e-commerce architecture of claim 47, wherein the Message class is operable as a wrapper of a plurality of classes included within a document object model class that include a document class and a document object model element class. 52. The e-commerce architecture of claim 47, wherein the instructions to restrict the conversion comprises a Field class operable as a wrapper of a document object model setAttribute method in a document object model element class. 53. The e-connnerce architecture of claim 47, wherein the instructions to retrieve data responsive to the request are identified with a request name that is included in the request.
연구과제 타임라인
LOADING...
LOADING...
LOADING...
LOADING...
LOADING...
이 특허에 인용된 특허 (21)
Allen, Paul V., Apparatus and method for generic data conversion.
Schwerdtfeger, Richard S.; Weiss, Lawrence F.; Dutta, Rabindranath, Electronic document delivery system employing distributed document object model (DOM) based transcoding and providing assistive technology support.
Lipkin, Daniel S.; Mehra, Gaurav, Method and apparatus for an improved security system mechanism in a business applications management system platform.
Bahrs, Peter C.; Chancey, Raphael Poole; Modh, Manish Mahesh, Method and apparatus in a data processing system for systematically separating application graphical user interface component placement from component sequencing and compound creation.
Lindberg, Henrik; Hallgren, Thomas, Method and system for transferring information between a user interface and a database over a global information network.
Burkett, Charles; Hind, John Raithel; Lection, David Bruce; Telford, Richard Dean; Tidwell, II, Leonard Douglas; Unger, Jay, Method for producing composite XML document object model trees using dynamic data retrievals.
Claussen, Christopher Shane; Flurry, Gregory Alan; McClain, Matthew Dale; Xu, Lin; ZumBrunnen, Benjamin Charles, Method for verifying context between multiple related XML tags in document object model (DOM).
Britton, Kathryn H.; Ims, Steve Dale; Topol, Brad B., Systems, methods and computer program products for tailoring web page content in hypertext markup language format for display within pervasive computing devices using extensible markup language tools.
Ankireddipally, Lakshmi Narasimha; Yeh, Ryh-Wei; Nichols, Dan; Devesetti, Ravi, Transaction data structure for process communications among network-distributed applications.
Dinh, Thu-Tram T.; Ho, Shyh-Mei F.; Hung, Jenny ChengYin; Lo, Kevin Yu Chang, Apparatus for facilitating transactions between thin-clients and message format service (MFS)-based information management systems (IMS) applications.
Saylor, Michael Jerry; Bouzid, Ahmed Tewfik; Durgani, Prakash Bhagwan; Rennyson, David James; Perera, Prasanna Sajeewa Naleen, Communication of information during a call.
Christensen, Erik Bo; Balayoghan, Vaithiakingam B.; Coulson, Michael James; Sturgell, Ryan Thomas; Jethanandani, Natasha Harish; Marucheck, Michael Jon; Purdy, Douglas M.; Wolf, Kenneth David; Vernal, Michael Steven; Pharies, Stefan Harrington; Wortendyke, David, Flexibly transferring typed application data.
Dinh, Thu-Tram T.; Ho, Shyh-Mei F.; Hung, Jenny ChengYin; Yo, Kevin Yu Chang, Method for facilitating transactions between thin-clients and message format service (MFS)-based information management system (IMS) applications.
Haller, Daniel M.; Ho, Shyh-Mei F.; Hughes, Gerald D.; Hung, Jenny C.; Huyah, Bill T.; Kuo, Steve T., System and method for facilitating XML enabled IMS transactions.
Chiang, Chenhuei J.; Ho, Shyh-Mei F.; Sheats, Benjamin Johnson; Yep, Eddie Raymond, System and method for representing MFS control blocks in XML for MFS-based IMS applications.
Haller,Daniel M.; Ho,Shyh Mei F.; Hughes,Gerald D.; Hung,Jenny C.; Huynh,Bill T.; Kuo,Steve T., System and method to facilitate XML enabled IMS transactions between a remote client and an IMS application program.
Dinh,Thu Tram T.; Ho,Shyh Mei F.; Hung,Jenny ChengYin; Lo,Kevin Yu Chang, System for facilitating transactions between thin-clients and message format service (MFS)-based information management system (IMS) applications.
※ AI-Helper는 부적절한 답변을 할 수 있습니다.