Method and System for Generating Messages

• US 20090138585A1
• Filed: 11/25/2008
• Published: 05/28/2009
• Est. Priority Date: 11/27/2007
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Li, Min, Gou, Ying Chun, Wang, Qiang, Poddar, Indrajit, Wei, Li, Sachdeva, Naveen
• Granted Patent: US 8,321,500 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

The present invention discloses a method and system for generating Simple Object Access Protocol (SOAP) message, wherein, at least one first information sets are pre-stored and each of the first information sets contains at least one piece of information. The method comprises: generating a first SOAP message which contains a second information set that contains at least one piece of information; retrieving a first information set that corresponds to the second information set; and generating a second SOAP message using the retrieved first information set and the first SOAP message.

Claims

1. A method for generating Simple Object Access Protocol (SOAP) message, wherein, at least one first information set is pre-stored, and each first information sets comprises at least one piece of information, the method comprising:

generating a first SOAP message, wherein, the first SOAP message comprises a second information set which comprises at least one piece of information;

retrieving a first information set corresponding to the second information set; and

generating a second SOAP message based on the retrieved first information set and the first SOAP message.

2. The method according to claim 1, further comprising the step of:

sending the second SOAP message to a message mediation to invoke a service.

3. The method according to claim 2, wherein the first information sets comprise property information, which is used by the message mediation to dynamically route the second SOAP message to a corresponding service realization endpoint.

4. The method according to claim 2, wherein the second information set comprises service interface information necessary for invoking a service.

5. The method according to claim 1, wherein the second information set is provided in the body of the first SOAP message, the method comprising:

generating the second SOAP message by inserting the first information set into the header of the first SOAP message.

6. The method according to claim 1, wherein each of the at least one first information sets is associated with one unique endpoint, the method further comprising:

retrieving the first information set using the unique endpoint.

7. The method according to claim 6, wherein the first SOAP message is encapsulated in a HTTP message and the unique endpoint is written into the header of the HTTP message as the destination address.

15. The method of claim 1, wherein the first information sets are pre-stored in a repository located in a message mediation application.

8. A system for generating a Simple Object Access Protocol (SOAP) message, comprising:

a repository, which pre-stores at least one first information sets, each first information set comprising at least one piece of information; and

a message handler configured to receive a first SOAP message, wherein the first SOAP message contains a second information set that contains at least one piece of information, and wherein, the message handler is further configured to retrieve the first information set corresponding to the second information set from the repository, and generate a second SOAP message using the retrieved first information set and the first SOAP message.

9. The system according to claim 8, wherein the message handler is further configured to send the second SOAP message to a message mediation for invoking a service.

10. The system according to claim 9, wherein the first information sets comprise property information, which is used by the message mediation to dynamically route the second SOAP message to a corresponding service realization endpoint.

11. The system according to claim 9, wherein, the second information set comprises service interface information necessary for invoking a service.

12. The system according to any of claim 8, wherein the second information set is provided in the body of the first SOAP message, and the message handler is further configured to generate the second SOAP message by inserting the first information set into the header of the first SOAP message.

13. The system according to claim 8, wherein each of the at least one first information sets is associated with one unique endpoint, and the message handler is further configured to retrieve the first information sets using the unique endpoint.

14. The system according to claim 13, wherein the first SOAP message is encapsulated in a HTTP message and the unique endpoint is written into the header of the HTTP message as a destination address.