Facilitating communication between enterprise software applications
View Patent ↗Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for facilitating communication between enterprise software applications. Some enterprise software systems communicate using a message protocol designed for use with an exchange system. Those systems require the exchange system to communicate using that message protocol. To communicate with systems using that message protocol, a local system can build a message formatted in accordance with the message protocol, even without an exchange system. The local system stores configuration data and uses the configuration data to build the message.
1. A method performed by one or more computers, the method comprising:
receiving, from a sending enterprise software application executing on one or more local computers, i) a first request to send a first outbound message to a destination enterprise software application executing on one or more destination computers, and ii) a second request to send a second outbound message to the destination enterprise software application executing on the one or more destination computers, the first and second requests specifying a respective message payload and a message protocol, the message protocol specifying a message format for messages to send to an exchange system that translates messages between enterprise software applications;
reading configuration data, stored by the one or more local computers, for the sending enterprise software application and the destination enterprise software application;
building the first and the second outbound messages at the one of more local computers, including:
for the first outbound message, building a message header using the configuration data and including the message header and the respective message payload in the first outbound message;
for the second outbound message, including the respective message payload in the second outbound message;
sending the first outbound message to the destination enterprise software application by communicating directly with the one or more destination computers; and
sending the second outbound message to the exchange system for communicating the second outbound message to the destination enterprise software application.
2. The method of claim 1 , wherein the configuration data includes technical addressing information, and wherein building the first outbound message includes building the message header using the technical addressing information, and wherein the technical addressing information specifies one or more of: a connection scheme, a network address for the one or more destination computers, a network port for the one or more destination computers, a network path for the one or more destination computers, and a timeout value.
3. The method of claim 1 , wherein the configuration data includes authentication data, and wherein building the first outbound message includes building the message header using the authentication data.
4. The method of claim 3 , wherein the authentication data specifies an authentication method and data specific to the authentication method.
5. The method of claim 1 , wherein the configuration data includes logical addressing information, and wherein building the first outbound message includes building the message header using the logical addressing information, and wherein the logical addressing information specifies a logical receiver party name for the destination enterprise software application.
6. The method of claim 5 , wherein the logical addressing information specifies a logical sender party name for the local enterprise software application.
7. The method of claim 6 , wherein the logical addressing information specifies a sender service or a receiver service or both.
8. The method of claim 1 , wherein the configuration data includes a mapping of interface names, and wherein building the first outbound message includes mapping an internal interface name for the local enterprise software application to an external interface name for the destination enterprise software application using the mapping of interface names, and wherein building the outbound message includes building the message header using the external interface name.
9. The method of claim 1 , wherein sending the first outbound message to the destination enterprise software application further comprises communicating the first outbound message directly to the one or more destination computers exclusive of communicating the first outbound message to the exchange system.
10. The method of claim 1 , wherein sending the first outbound message to the destination enterprise software application further comprises communicating the first outbound message directly to the one or more destination computers while bypassing communicating the first outbound message to the exchange system.
11. A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that when executed by one or more computers cause the one or more computers to perform operations comprising:
receiving, from a sending enterprise software application executing on one or more local computers, i) a first request to send a first outbound message to a destination enterprise software application executing on one or more destination computers, and ii) a second request to send a second outbound message to the destination enterprise software application executing on the one or more destination computers, the first and second requests specifying a respective message payload and a message protocol, the message protocol specifying a message format for messages to send to an exchange system that translates messages between enterprise software applications;
reading configuration data, stored by the one or more local computers, for the sending enterprise software application and the destination enterprise software application;
building the first and the second outbound messages at the one of more local computers, including:
for the first outbound message, building a message header using the configuration data and including the message header and the respective message payload in the first outbound message;
for the second outbound message, including the respective message payload in the second outbound message;
sending the first outbound message to the destination enterprise software application by communicating directly with the one or more destination computers; and
sending the second outbound message to the exchange system for communicating the second outbound message to the destination enterprise software application.
12. The non-transitory computer storage medium of claim 11 , wherein the configuration data includes technical addressing information, and wherein building the first outbound message includes building the message header using the technical addressing information, and wherein the technical addressing information specifies one or more of: a connection scheme, a network address for the one or more destination computers, a network port for the one or more destination computers, a network path for the one or more destination computers, and a timeout value.
13. The non-transitory computer storage medium of claim 11 , wherein the configuration data includes authentication data, and wherein building the outbound message includes building the message header using the authentication data.
14. The non-transitory computer storage medium of claim 13 , wherein the authentication data specifies an authentication method and data specific to the authentication method.
15. The non-transitory computer storage medium of claim 11 , wherein the configuration data includes logical addressing information, and wherein building the first outbound message includes building the message header using the logical addressing information, and wherein the logical addressing information specifies a logical receiver party name for the destination enterprise software application.
16. The non-transitory computer storage medium of claim 15 , wherein the logical addressing information specifies a logical sender party name for the local enterprise software application.
17. The non-transitory computer storage medium of claim 16 , wherein the logical addressing information specifies a sender service or a receiver service or both.
18. The computer storage medium of claim 11 , wherein the configuration data includes a mapping of interface names, and wherein building the first outbound message includes mapping an internal interface name for the local enterprise software application to an external interface name for the destination enterprise software application using the mapping of interface names, and wherein building the outbound message includes building the message header using the external interface name.
19. A system of one or more computers configured to perform operations comprising:
receiving, from a sending enterprise software application executing on one or more local computers, i) a first request to send a first outbound message to a destination enterprise software application executing on one or more destination computers, and ii) a second request to send a second outbound message to the destination enterprise software application executing on the one or more destination computers, the first and second requests specifying a respective message payload and a message protocol, the message protocol specifying a message format for messages to send to an exchange system that translates messages between enterprise software applications;
reading configuration data, stored by the one or more local computers, for the sending enterprise software application and the destination enterprise software application;
building the first and the second outbound messages at the one of more local computers, including:
for the first outbound message, building a message header using the configuration data and including the message header and the respective message payload in the first outbound message;
for the second outbound message, including the respective message payload in the second outbound message;
sending the first outbound message to the destination enterprise software application by communicating directly with the one or more destination computers; and
sending the second outbound message to the exchange system for communicating the second outbound message to the destination enterprise software application.
20. The system of claim 19 , wherein the configuration data includes technical addressing information, and wherein building the first outbound message includes building the message header using the technical addressing information, and wherein the technical addressing information specifies one or more of: a connection scheme, a network address for the one or more destination computers, a network port for the one or more destination computers, a network path for the one or more destination computers, and a timeout value.
21. The system of claim 19 , wherein the configuration data includes authentication data, and wherein building the outbound message includes building the message header using the authentication data.
22. The system of claim 21 , wherein the authentication data specifies an authentication method and data specific to the authentication method.
23. The system of claim 19 , wherein the configuration data includes logical addressing information, and wherein building the first outbound message includes building the message header using the logical addressing information, and wherein the logical addressing information specifies a logical receiver party name for the destination enterprise software application.
24. The system of claim 23 , wherein the logical addressing information specifies a logical sender party name for the local enterprise software application.
25. The system of claim 24 , wherein the logical addressing information specifies a sender service or a receiver service or both.
26. The system of claim 19 , wherein the configuration data includes a mapping of interface names, and wherein building the first outbound message includes mapping an internal interface name for the local enterprise software application to an external interface name for the destination enterprise software application using the mapping of interface names, and wherein building the outbound message includes building the message header using the external interface name.