Typically, modern business processes depend at least in part on software. While some of these processes are supported by a single application, many others rely on diverse software systems. This software has commonly been created at different times, on different computer platforms, and using different technologies. Given this, automating those business processes requires connecting diverse systems.
Two scenarios are important for application integration. One is connecting applications within a single organization, commonly referred to as enterprise application integration (EAI). The other, called business-to-business (B2B) integration, connects applications in different organizations.
For example, an inventory application 104 running on a mainframe type computer notices that the stock of an item is low and issues a message 118 including a request to order more of that item. This message 118 is sent to a business process orchestration 116 via an adapter 110. The adapter 110 converts the message from the inventory application 104 format to business process management server 102 format and then forwards the converted message to the business process orchestration 116.
Next, the business process orchestration 116 issues a request to this organization's ERP (Enterprise Resource Planning) application 106 requesting a purchase order. The ERP application 106 executes on another computer type and adapter 112 converts the request into a message 120 in a format required by the ERP application 106 and then sends the message 110 to the ERP application 106. In response to the message 120, the ERP application 106 issues a purchase order and sends a message 122 including the purchase order to the business process management server 102 via adapter 112. As described above, the adapter converts the message 122 from the ERP application format to the business process management server format and forwards the message to the business process orchestration 116.
Lastly, the business process orchestration 116 issues a request to a fulfillment application 108 requesting the item should be ordered. The fulfillment application 108 executes on yet another computer type and adapter 114 converts the request into a message 124 in a format required by the fulfillment application 108 and then sends the message 124 to the fulfillment application 108.
Thus, the simple example described above illustrates the need for adapters that can be easily configured to process many different messages types and computer protocols.
Embodiments of the invention include systems and methods for converting business process messages to SOAP (Simple Object Access Protocol) messages and vice versa. In an embodiment, the invention includes a method for converting a SOAP message into a business process message by a business process adapter. A body path and a node encoding type are defined for the business process adapter. When a SOAP message is received, the business process adaptor extracts the node of the SOAP message at the location defined by the body path and encodes the node according to the defined node encoding type. The business process message is generated from the extracted node and sent to the business process management server.
In another embodiment, a business process message is converted into a SOAP message by a business process adapter. A content encoding type and a format of the SOAP message are defined and associated with the business process adapter. When the business process message is received from the business process management server, the business process adapter encodes the body of the business process message according to the defined content encoding type and generates the SOAP message from the encoded body according to the defined format. The business process adapter sends the generated SOAP message via the business process adapter to an application.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Other features will be in part apparent and in part pointed out hereinafter.
Corresponding reference characters indicate corresponding parts throughout the drawings.
In an embodiment, the invention includes systems and methods for converting SOAP (Simple Object Access Protocol) messages to business process management server messages and vise versa.
The business process adapter 208 is configured with computer-executable instructions for receiving SOAP messages (e.g. inbound message 202). The computer-executable instructions for receiving SOAP messages include instructions for defining a body path 212, defining a node encoding type 214, receiving the SOAP message, extracting the node of the SOAP message, generating the business process message 216 and sending the business process message 216 to the business process management server 210.
The defined body path 212 is associated with the business process adapter 208 and specifies the location of a node of the SOAP message. The defined node encoding type 214 is associated with the business process adapter 208 and specifies the encoding of the node. In an embodiment, the node encoding type 214 includes one or more of the following: string, hexadecimal, base64, and XML.
The business process management server 210 receives the SOAP message via the business process adapter 208. Next, the business process adapter 208 extracts the node of the SOAP message. The node is located in the SOAP message at the location defined by the body path 212 and the node is encoded according to the defined node encoding type 214. By defining the node encoding type 214, the adapter can read the node according to the encoding type without first determining how the node was encoded. Advantageously, performance will increase because no further translation of the node is required and disk space is reduced in situations where the decoded node results in less data than the encoded node (i.e. base64 encoded node decoded to binary data instead of string).
The business process adapter 208 generates the business process message 216 from the extracted node. The content of the business process message 216 includes the extracted node. Next, the business process adapter 208 sends the business process message 216 to the business process management server 210. In an embodiment, the business process adapter 208 sends the business process message 216 to a business process orchestration 218 of the business process management server 210. The business process orchestration 218 includes the business rules and/or business logic for a business process. Alternatively, the business process orchestration 218 is bypassed. In this case, the business process adapter 208 sends the business process message 216 directly to a routing process that sends the business process message 216 to another application.
In another embodiment, the business process adapter 208 is configured with computer-executable instructions for sending SOAP messages (e.g. outbound message 204). The computer-executable instructions for sending SOAP messages include instructions for defining a format of the SOAP message (e.g., template 220), defining a content encoding type 222, receiving the business process message 216, encoding the body of the business process message 216, generating the SOAP message, and sending the SOAP message to an application 206.
The defined format of the SOAP message is associated with the business process adapter 208. In an alternative embodiment, the format is defined as a template 220. The template 220 includes a XML message body element which defines the format of the SOAP message and the content encoding type 222 of the SOAP message. The business process adapter 208 generates the SOAP message including the template 220 by replacing the XML message body element with the encoded message body of the businesses process message 216.
The defined content encoding type 222 for the SOAP message is associated with the business process adapter 208. The content encoding type 222 includes one or more of the following: string, hexadecimal, base64, and XML.
Next, the business process adapter 208 receives the business process message 216 from the business process management server 210. In an embodiment, the business process adapter 208 receives the business process message 216 from a business process orchestration 218 of the business process management server 210. Alternatively, the business process orchestration 218 is bypassed. In this case, the business process adapter 208 receives the business process message 216 directly from a routing process that received the business process message 216 from another application. The business process adapter 208 encodes the body of the business process message 216 according to the defined content encoding type 222.
Next, the business process adapter 208 generates the SOAP message from the encoded body of the business process message 216. The content of the SOAP message includes the encoded body. In an embodiment, if the node encoding type 214 is string and the extracted node includes escaped data for XML special characters, the generated business process message 216 will include the restored escaped characters.
The business process adapter 208 sends the generated SOAP message (e.g., outbound message 204) via the business process adapter 208 to the application 206. The computer 210 may operate in a networked environment using logical connections to one or more remote computers and/or applications. The remote computer may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to computer 210. The logical connections depicted in
In an embodiment, the system includes a user interface for defining one or more of the following: the body path 212 associated with the business process adapter 208, the node encoding type 214 associated with the business process adapter 208, the format of the SOAP message associated with the business process adapter 208, and the content encoding type 222 for the SOAP message associated with the business process adapter 208.
In another embodiment, system includes first business process adapter configured with computer-executable instructions for receiving SOAP messages, and a second business process adapter configured with computer-executable instructions for sending SOAP messages. In this embodiment, the first and said second business process adapters are not the same business process adapter.
In one embodiment of the invention, a computer such as the computer 210 is suitable for use in the other figures illustrated and described herein. The computer 210 typically has at least some form of computer readable media. Computer readable media, which include both volatile and nonvolatile media, removable and non-removable media, may be any available medium that may be accessed by computer 210.
By way of example and not limitation, computer readable media comprise computer storage media and communication media. Computer storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. For example, computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store the desired information and that may be accessed by computer 210.
Communication media typically embody computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and include any information delivery media. Those skilled in the art are familiar with the modulated data signal, which has one or more of its characteristics set or changed in such a manner as to encode information in the signal. Wired media, such as a wired network or direct-wired connection, and wireless media, such as acoustic, RF, infrared, and other wireless media, are examples of communication media. Combinations of any of the above are also included within the scope of computer readable media.
At 304, a body path 212 associated with the business process adapter 208 is defined. The body path 212 specifies the location of a node of the SOAP message. In an embodiment, the body path 212 is evaluated against the immediate child element of the SOAP body element of an incoming message. Advantageously, the node can be defined to include only the data without any SOAP or XML tags. In another embodiment, if the body path 212 matches more than one element, only the first matched element is used.
At 306, a node encoding type 214 associated with the business process adapter 208 is defined. The node encoding type 214 specifies the format of the node. In an embodiment, the node encoding type 214 includes one or more of the following: string, hexadecimal, base64, and XML. In another embodiment, the body path 212 and node encoding type 214 are defined by a user via a graphical user interface of the business process management server 210.
At 308, the business process adapter 208 receives the SOAP message (e.g., inbound message 202). In an embodiment, the business process adapter 208 receives the SOAP message from the application 206. The following is an exemplary SOAP message according to an embodiment of the invention:
At 310, the business process adapter 208 extracts the node of the SOAP message. The node is located in the SOAP message at the location by the body path 212 defined at 304. And, the node is encoded according to the node encoding type 214 defined at 306. For example, from the exemplary message from above, if the body path is defined at “/a/b” and the node encoding type is “string”, the business process adapter 208 extracts the node “Some text message here” using string encoding.
At 312, the business process adapter 208 generates the business process message 216 from the extracted node. The content of the business process message 216 includes the extracted node. In an embodiment, an empty business process message 216 is created if the extracted node does not include any data. In another embodiment, if the node encoding type 214 is defined as string and the extracted node includes escaped data for XML special characters, the generated business process message 216 will include the restored escaped characters. For example, if the matched node has escaped character data such as “<FirstName>CONTOSO</FirstName>”, the business process adapter 208 generates “<FirstName>CONTOSO</FirstName>” in the generated business process message 216.
In yet another embodiment, if the node encoding type 214 is defined as XML, the generated business process message 216 will include the outer XML defined by the body path 212. For example, if the business process adapter 208 receives the following SOAP message:
And, the body path 212 is “/*[local-name( )=‘Order’]/*[local-name( )=‘OrderDetail’]/*[local-name( )=‘CustomerID’]” and the node encoding type 214 is string, the character data “CONTOSO” is included in the business process message 216. In another example from the SOAP message above, if the body path 212 is “/*[local-name( )=‘Order’]/*[local-name( )=‘OrderDetail’]/*[local-name( )=‘CustomerID’]” and the node encoding type 214 is XML, the character data “<CustomerIDxmlns=“http://Samples.NetNamedPipe/OrderProcess”>CONTOSO</CustomerID>” is included in the business process message 216.
At 314, the business process adapter 208 sends the business process message 216 to the business process management server 210. In an embodiment, the business process adapter 208 sends the business process message 216 to a business process orchestration 218 of the business process management server 210.
At 402, a business process adapter 208 is created on the business process management server 210. At 404, a format of the SOAP message is defined and associated with the created business process adapter 208. And, at 406, a content encoding type 222 for the SOAP message is defined and associated with the business process adapter 208. In an embodiment, the content encoding type 222 includes one or more of the following: string, hexadecimal, base64, and XML. Alternatively, the format of the SOAP message and content encoding type 222 are defined by a user via a graphical user interface of the business process management server 210.
At 408, the business process adapter 208 receives the business process message 216 from the business process management server 210. In an alternative embodiment, the business process adapter 208 receives the business process message 216 from the business process orchestration 218 of the business process management server 210.
At 410, the business process adapter 208 encodes the body of the business process message 216 according to the defined content encoding type. And, at 412, the business process adapter 208 generates the SOAP message from the encoded body of the business process message 216. The content of the SOAP message includes the encoded body.
In alternative embodiment, the format of the SOAP message is defined as a template 220 including a XML message body element which defines the format of the SOAP message and the content encoding type 222 of the SOAP message. The generated SOAP message includes the template 220 where the encoded message body of the businesses process message replaces the XML message body element. The following is an example of a template according to aspects of an embodiment of the invention:
In another embodiment, if the template 220 is empty, an empty SOAP message is created. At 414, the business process adapter 208 sends the SOAP message (e.g., outbound message 204 to the application 206.
In another embodiment, if the content encoding type 222 is string, any XML special characters in the businesses process message are escaped when encoded and the generated SOAP message will include the escaped characters.
In yet another embodiment, if the content encoding type 222 is base64 or hex, the generated SOAP message will include the business process message 216 body encoded in at least one of the following: BinHex and Base 64.
For example, if content encoding type 222 is string and the template 220 is defined as:
Then the following message is generated:
If content encoding type 222 is base64 and the template 220 is defined as:
Then the following message is generated:
If content encoding type 222 is XML and the template 220 is defined as:
Then the following message is generated:
Referring again to
Generally, the data processors of computer 210 are programmed by means of instructions stored at different times in the various computer-readable storage media of the computer. Programs and operating systems are typically distributed, for example, on floppy disks or CD-ROMs. From there, they are installed or loaded into the secondary memory of a computer. At execution, they are loaded at least partially into the computer's primary electronic memory. Aspects of the invention described herein includes these and other various types of computer-readable storage media when such media contain instructions or programs for implementing the steps described below in conjunction with a microprocessor or other data processor. Further, aspects of the invention include the computer itself when programmed according to the methods and techniques described herein.
For purposes of illustration, programs and other executable program components, such as the operating system, are illustrated herein as discrete blocks. It is recognized, however, that such programs and components reside at various times in different storage components of the computer, and are executed by the data processor(s) of the computer.
Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, executed by one or more computers or other devices. Generally, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
In operation, computer 210 executes computer-executable instructions such as those illustrated in the figures to implement aspects of the invention.
The order of execution or performance of the operations in embodiments of the invention illustrated and described herein is not essential, unless otherwise specified. That is, the operations may be performed in any order, unless otherwise specified, and embodiments of the invention may include additional or fewer operations than those disclosed herein. For example, it is contemplated that executing or performing a particular operation before, contemporaneously with, or after another operation is within the scope of aspects of the invention.
Embodiments of the invention may be implemented with computer-executable instructions. The computer-executable instructions may be organized into one or more computer-executable components or modules. Aspects of the invention may be implemented with any number and organization of such components or modules. For example, aspects of the invention are not limited to the specific computer-executable instructions or the specific components or modules illustrated in the figures and described herein. Other embodiments of the invention may include different computer-executable instructions or components having more or less functionality than illustrated and described herein.
When introducing elements of aspects of the invention or the embodiments thereof, the articles “a,” “an,” “the,” and “said” are intended to mean that there are one or more of the elements. The terms “comprising,” “including,” and “having” are intended to be inclusive and mean that there may be additional elements other than the listed elements.
Having described aspects of the invention in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the invention as defined in the appended claims. As various changes could be made in the above constructions, products, and methods without departing from the scope of aspects of the invention, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense.
Number | Name | Date | Kind |
---|---|---|---|
5999908 | Abelow | Dec 1999 | A |
6633910 | Rajan et al. | Oct 2003 | B1 |
6763353 | Li et al. | Jul 2004 | B2 |
6775658 | Zothner | Aug 2004 | B1 |
6810429 | Walsh et al. | Oct 2004 | B1 |
7065566 | Menard et al. | Jun 2006 | B2 |
7103556 | Del Rey et al. | Sep 2006 | B2 |
7107224 | Weller et al. | Sep 2006 | B1 |
7111076 | Abjanic et al. | Sep 2006 | B2 |
7146618 | Mein et al. | Dec 2006 | B1 |
7194733 | Ringseth et al. | Mar 2007 | B2 |
7668815 | Hild et al. | Feb 2010 | B2 |
20020099578 | Eicher, Jr. et al. | Jul 2002 | A1 |
20030115119 | Schleicher | Jun 2003 | A1 |
20030181991 | Chau et al. | Sep 2003 | A1 |
20030236677 | Casati et al. | Dec 2003 | A1 |
20040177053 | Donoho et al. | Sep 2004 | A1 |
20040186891 | Panec et al. | Sep 2004 | A1 |
20040205765 | Beringer et al. | Oct 2004 | A1 |
20060143040 | Scheier et al. | Jun 2006 | A1 |
20060248536 | Eckert | Nov 2006 | A1 |
20070106998 | Zeldin et al. | May 2007 | A1 |
20080120283 | Liu et al. | May 2008 | A1 |
Number | Date | Country | |
---|---|---|---|
20090064175 A1 | Mar 2009 | US |