System and method for routing messages between applications

• US 8,639,843 B2
• Filed: 08/28/2012
• Issued: 01/28/2014
• Est. Priority Date: 03/26/2001
• Status: Expired due to Term

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Brouk, Lev, Norton, Kenneth, Douglas, Jason, Panec, Peter
• Primary Examiner(s): TRUONG, LAN DAI T
• Application Number:
  US13/596,973
• Publication Number:
  US 20120324125A1
• Time in Patent Office: 518 Days
• Field of Search: 709/238, 709/224, 709/244, 709/246, 709/247, 709/242
• US Class Current: 709/238
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• 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 9/40 Network security protocols

Abstract

A system and method for enabling the interchange of enterprise data through an open platform is disclosed. This open platform can be based on a standardized interface that enables parties to easily connect to and use the network. Services operating as senders, recipients, and in-transit parties can therefore leverage a framework that overlays a public network.

Claims

1. A system that routes a message between a first service and a second service on behalf of an entity in a message routing service, the system comprising:

a router including at least one processor and memory coupled to the processor, the memory loaded with instructions that implement a message routing service and cause the processor to;

(a) receive an authentication request for the entity at the message routing service;

(b) generate at the message routing service an identifier for the authentication request, the identifier indicating authentication of the entity to the message routing service;

(c) send at least one provisioning message to at least one of the first service and the second service using the message routing service, the at least one provisioning message including the identifier for provisioning the entity with the at least one of the first service and the second service; and

(d) subsequent to the receiving, generating and sending;

receive a message at the message routing service from the first service, the message including the identifier, the message further being directed to the second service;

authenticate the message at the message routing service using the identifier;

determine, upon authenticating, at the message routing service a route and a transformation comprised of one or more of no modification of the message, a modification of the message, and a translation of the message; and

route an output message to the second service according to the route and the transformation of the message to form the output message from the first service, the output message including the identifier.

2. The system of claim 1, wherein the message routing service authenticates the message without further authentication of the entity with either the first service or the second service by the message routing service.

3. The system of claim 2, wherein the message includes XML data and the transformation comprises a translation of the message such that the output message includes the data after transformation according to one or more extensible stylesheet language transformations (XSLTs).

4. The system of claim 2, wherein the second service comprises a mapped service, the mapped service comprising an entity specific mapping to a third service, and wherein the routing the output message to the second service comprises routing the output message to the third service.

5. The system of claim 2, wherein the route includes a third service to receive the output message prior to routing to the second service.

6. The system of claim 5, wherein the identifier in the output message capable of use by the third service for authentication of the output message.

7. The system of claim 2, wherein the identifier in the message in an encrypted form.

8. A system that routes a message between a first service and a second service on behalf of an entity in a message routing service, the system comprising:

a router including at least one processor and memory coupled to the processor, the memory loaded with instructions that implement a message routing service and cause the processor to;

(a) receive an authentication request for the entity at a message routing service;

(b) generate at the message routing service an identifier for the authentication request, the identifier indicating authentication of the entity to the message routing service;

(c) send at least one provisioning message to at least one of the first service and the second service using the message routing service, the at least one provisioning message including the identifier for provisioning the entity with the at least one of the first service and the second service; and

(d) subsequent to the receiving, generating and sending;

receive a message at the message routing service from the first service, the message including the identifier, the message further being directed to the second service;

authenticate the message at the message routing service using the identifier;

determine, upon authenticating, at the message routing service a route and a transformation comprised of one or more of no modification of the message, a modification of the message, and a translation of the message; and

route an output message to the second service according to the route and the transformation of the message to form the output message from the first service, the output message including the identifier.