Enterprise-to-enterprise integration

• US 20060271939A1
• Filed: 05/11/2005
• Published: 11/30/2006
• Est. Priority Date: 05/11/2005
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Morley, Rick, De Schrijver, Philippe, Joris, Eric
• Application Number:
  US11/126,939
• Publication Number:
  US 20060271939A1
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

Enterprise-to-enterprise integration may be achieved by a variety of systems and techniques. In one general aspect, a system and technique for enterprise-to-enterprise integration may include the ability to receive a message at a first message interface, the first message interface facing an enterprise, and convert the message to a format for a second message interface, the second message interface facing an enterprise partner. The system and technique may also include the ability to receive a file at an enterprise-facing file transfer interface and convert the file to a format for the second message interface.

Claims

1. An enterprise-to-enterprise integration engine, the engine comprising:

a first message interface, the first message interface facing an enterprise;

an enterprise-facing file transfer interface;

a second message interface, the second message interface facing an enterprise partner; and

a communication mapper coupled to the first message interface, the file transfer interface, and the second message interface, the communication mapper operable to convert messages and files received at the first message interface and the file transfer interface to a format for the second message interface.

2. The engine of claim 1, wherein the first message interface comprises a Web services interface.

3. The engine of claim 1, wherein the file transfer interface comprises an enterprise-accessible memory drive.

4. The engine of claim 1, wherein the second message interface comprises an Extensible Markup Language interface.

5. The engine of claim 1, further comprising a third message interface, the communication mapper coupled to the third message interface and operable to convert enterprise-generated messages received at the third message interface to a format for the second message interface.

6. The engine of claim 1, wherein the communication mapper is operable to convert messages received at the second message interface to a format for the first message interface and the file transfer interface.

7. The engine of claim 1, wherein the communication mapper may be remotely managed by communications received through the second message interface.

8. The engine of claim 7, wherein managing the communication mapper includes provisioning the communication mapper.

9. The engine of claim 1, wherein the communication mapper is operable to validate messages received through the first message interface.

10. The engine of claim 1, wherein the communication mapper is operable to cache enterprise-partner data.

11. A method for enterprise-to-enterprise integration, the method comprising:

receiving a message at a first message interface, the first message interface facing an enterprise;

converting the message to a format for a second message interface, the second message interface facing an enterprise partner;

receiving a file at an enterprise-facing file transfer interface; and

converting the file to a format for the second message interface.

12. The method of claim 11, further comprising:

receiving an enterprise-generated message at a third message interface; and

converting the message to a format for the second message interface.

13. The method of claim 11, further comprising:

receiving a message at the second message interface; and

determining whether the content of the message is destined for the first message interface or the file transfer interface.

14. The method of claim 11, further comprising receiving management instructions through the second message interface.

15. The method of claim 14, wherein the management instructions comprise provisioning instructions.

16. The method of claim 11, further comprising validating messages received through the first message interface.

17. The method of claim 11, further comprising caching enterprise-partner data.

18. An article comprising a machine-readable medium storing instructions operable to cause one or more machines to perform operations comprising:

determining whether a message has been received at a first message interface, the first message interface facing an enterprise;

converting the message to a format for a second message interface, the second message interface facing an enterprise partner;

determining whether a file has been received at an enterprise-facing file transfer interface; and

converting the file to a format for the second message interface.

19. The article of claim 18, wherein the instructions are further operable to cause one or more machines to perform operations comprising:

determining whether an enterprise-generated message has been received at a third message interface; and

converting the message to a format for the second message interface.

20. The article of claim 18, wherein the instructions are further operable to cause one or more machines to perform operation comprising:

determining whether a message has been received at the second message interface; and

determining whether the content of the message is destined for the first message interface or the file transfer interface.