Apparatus, system, and method for setting/retrieving header information dynamically into/from service data objects for protocol based technology adapters
First Claim
1. A computer program product for providing a technology adapter in a service oriented architecture (SOA) system for translating a protocol-based message having a first format into a service data object having a second format, the computer program product comprising a computer useable storage medium including a computer readable program, wherein the computer program product when executed on a computer causes the technology adapter to:
- receive a protocol-based message in the first format, the protocol-based message having a conventional header defined by the protocol and a user-defined header that is not defined by the protocol, the user-defined header comprising one or more fields that are unknown to the technology adapter and that are not interpreted by the technology adapter, and wherein both the conventional header and the user-defined header both conform to a predefined header format, each header comprising a header name and a value;
identify each conventional header and user-defined header in the protocol-based message based on the predefined header format;
dynamically generate a header structure to store the header name and the value from each conventional header and user-defined header;
store the header structure in a set of header structures of a service data object having the second format; and
pass the service data object to an integration broker.
2 Assignments
0 Petitions
Accused Products
Abstract
An apparatus, system, and method are disclosed for processing a technology specific message. In one embodiment, a computer program product receives a message having a conventional header and a user-defined header that both conform to a predefined header format, each header comprising a header name and a value; identifies each header in the message based on the predefined header format; generates a header structure to store the header name and the value from each header; stores the header structure in a set of header structures of an extendable message business object; and passes the extendable message business object to an integration broker.
31 Citations
35 Claims
-
1. A computer program product for providing a technology adapter in a service oriented architecture (SOA) system for translating a protocol-based message having a first format into a service data object having a second format, the computer program product comprising a computer useable storage medium including a computer readable program, wherein the computer program product when executed on a computer causes the technology adapter to:
-
receive a protocol-based message in the first format, the protocol-based message having a conventional header defined by the protocol and a user-defined header that is not defined by the protocol, the user-defined header comprising one or more fields that are unknown to the technology adapter and that are not interpreted by the technology adapter, and wherein both the conventional header and the user-defined header both conform to a predefined header format, each header comprising a header name and a value; identify each conventional header and user-defined header in the protocol-based message based on the predefined header format; dynamically generate a header structure to store the header name and the value from each conventional header and user-defined header; store the header structure in a set of header structures of a service data object having the second format; and pass the service data object to an integration broker. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A computer program product for providing a technology adapter in a service oriented architecture (SOA) system for translating a protocol-based message having a first format into a service data object having a second format, the computer program product comprising a computer useable medium including a computer readable program, wherein the computer program product when executed on a computer causes the technology adapter to:
-
receive a service data object having a second format from an integration broker, wherein the service data object comprises a set of header structures, each header structure comprising a header name and a value; extract the set of header structures from the service data object received from the integration broker; generate a protocol-based message having a first format, the protocol-based message comprising a conventional header defined by the protocol and a user-defined header that is not defined by the protocol, the user-defined header comprising one or more fields that are unknown to the technology adapter and that are not interpreted by the technology adapter, and wherein both the conventional header and the user-defined header both conform to a predefined header format, each user-defined header comprising a header name and a value. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23)
-
-
24. A service oriented architecture (SOA) system for processing an email message using a technology adapter, wherein processing the email message comprises translating the email message into a service data object having a second format, the system comprising:
-
an integration broker comprising a mapping module configured to map between an extendable message business object for an email adapter and an EIS (Enterprise Information System) specific business object usable by an EIS specific adapter, wherein the extendable message business object is a service data object; an EIS specific adapter in communication with the integration broker, the EIS specific adapter configured to map between an EIS record and an EIS specific business object; and an integration email adapter in communication with the integration broker and configured to receive an email message from a mail transfer agent, the email message having a conventional header and a user-defined header that both conform to a predefined header format, the user-defined header comprising one or more fields that are unknown to the technology adapter and that are not interpreted by the technology adapter, each user-defined header comprising a header name and a value, the integration email adapter further configured; to identify each conventional header and user-defined header in the email message based on the predefined header format; to dynamically generate a header structure to store the header name and the value from each conventional header and user-defined header; to store the header structure in a set of header structures of an extendable message business object; and to pass the extendable message business object to the integration broker.
-
-
25. A method of providing a technology adapter service to process an email message in a service oriented architecture (SOA) system, the method comprising:
-
receiving a protocol-based message in a first format, the protocol-based message having a conventional header defined by the protocol and a user-defined header that is not defined by the protocol, the user-defined header comprising one or more fields that are unknown to the technology adapter and that are not interpreted by the technology adapter, and wherein both the conventional header and the user-defined header both conform to a predefined header format, each user-defined header comprising a header name and a value; identifying each conventional header and user-defined header in the protocol-based message based on the predefined header format; dynamically generating a header structure to store the header name and the value from each conventional header and user-defined header; storing the header structure in a set of header structures of a service data object having a second format; and passing the service data object to an integration broker.
-
-
26. A computer program product for providing a technology adapter in a service oriented architecture (SOA) system for dynamically setting header information in service data objects comprising a computer useable storage medium including a computer readable program, wherein the computer program product when executed on a computer causes the technology adapter to:
-
parse an email message having RFC822 compliant header fields that are supported under the RFC822 standard and a message body wherein at least one RFC822 header field is a conventional header specified in RFC822 and as least one RFC822 header field is a user-defined header field according to RFC822, which user-defined header field comprises one or more fields that are unknown to the technology adapter and that are not interpreted by the technology adapter; for each RFC822 header field, create a storage object comprising a field-name from the RFC822 header field and a field-body from the RFC822 header field; dynamically construct an email wrapper business object comprising the body of the email message; for each storage object, create a header business object having a header name equivalent to the field-name and a header value equivalent to the field-body and associate each header business object with the email wrapper business object; map the email wrapper business object to an application specific business object; and send the application specific business object to an application, wherein mapping the email wrapper business object transforms the email wrapper business object, including the user-defined field, for use by the application, and wherein the user-defined header field is an arbitrary header field. - View Dependent Claims (27, 28)
-
-
29. A method for deploying computing infrastructure in a service oriented architecture (SOA) system comprising a technology adapter, the method comprising:
-
receiving customer requirements for transfer of a user-defined header from a mail transfer agent to a destination Enterprise Information System (EIS); deploying an integration email adapter into the customer computing infrastructure, the integration email adapter configured to receive an email message from the mail transfer agent, the email message having a conventional header defined by a protocol and a user-defined header that is not defined by the protocol, the user-defined header comprising one or more fields that are unknown to the technology adapter and that are not interpreted by the technology adapter, and wherein the conventional header and the user-defined header both conform to a predefined header format, each user-defined header comprising a header name and a value, the integration email adapter further configured; to identify each conventional header and user-defined header in the email message based on the predefined header format; to dynamically generate a header structure to store the header name and the value from each conventional header and user-defined header; to store the header structure in a set of header structures of service data object having a second format; and to pass the service data object to an integration broker; and configuring the destination EIS to extract the user-defined header from the service data object for use by the destination EIS. - View Dependent Claims (30, 31, 32, 33, 34, 35)
-
Specification