EXTENDING A CUSTOMER RELATIONSHIP MANAGEMENT EVENTING FRAMEWORK TO A CLOUD COMPUTING ENVIRONMENT IN A SECURE MANNER

• US 20110307948A1
• Filed: 06/15/2010
• Published: 12/15/2011
• Est. Priority Date: 06/15/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ranjan, Shashi, Shah, Nirav, Hariharan, Mahesh
• Granted Patent: US 8,544,075 B2
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2101 Auditing as a secondary aspect
• CPC Class Codes: G06F 2221/2103 Challenge-response
• CPC Class Codes: G06Q 30/01 Customer relationship services
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/101 Access control lists [ACL]

Abstract

A customer relationship management (CRM) eventing framework may be extended to a cloud computing environment. A listening channel may be opened between a service and a service bus in a cloud computing environment. The cloud computing environment may also include an authenticating service. Service information for the service may be registered with a CRM. The CRM may receive a request made by a requester. The request may trigger a request processing pipeline in an eventing framework. The CRM may post event data responsive to the request to the service bus. The service may receive the event data, process it and may send back a confirmation or response. The CRM may finally send a response to the requester.

Claims

1. A computer-implemented method of extending a customer relationship management (CRM) eventing framework to a cloud computing environment, comprising:

registering, by a computer, service information for a service in the cloud computing environment, the cloud computing environment further comprising a service bus and an authenticating service, wherein a listening channel is opened between the service and the service bus prior to registering the service information;

receiving, by the computer, a request made by a requester, the request triggering a request processing pipeline in an eventing framework;

posting, by the computer, event data responsive to the request to the service bus; and

sending, by the computer, a response to the requester.

2. The method of claim 1, further comprising receiving, by the computer, a confirmation of retrieval of the event data from the service bus by the service.

3. The method of claim 1, further comprising:

prior to posting the event data, requesting an authentication token for the service bus from the authenticating service; and

receiving the authentication token for the service bus from the authenticating service.

4. The method of claim 3, wherein posting, by the computer, event data responsive to the request to the service bus comprises posting the authentication token for the service bus and the event data to the service bus in a custom header, wherein the authentication token for the service bus is validated by the service bus.

5. The method of claim 1, further comprising:

prior to posting the event data, retrieving a federated token for the service from the authenticating service;

retrieving an authentication token for the service bus from the authenticating service.

6. The method of claim 5, wherein posting by the computer, event data responsive to the request to the service bus comprises posting the event data, the federated token for the service and the authentication token for the service bus to the service bus, wherein the authentication token for the service bus is consumed by the service bus and the event data and the federated token for the service is forwarded from the service bus to the service, wherein the federated token for the service is validated by the service.

7. The method of claim 1, wherein posting, by the computer, event data responsive to the request to the service bus comprises at least one of:

utilizing a CRM workflow to post the event data to the service bus, wherein the CRM workflow is triggered upon a request by the requester for CRM data;

utilizing custom plug-ins to post the event data to the service bus;

posting the event data to the service bus via an intermediary router; and

at least one of synchronously and asynchronously posting the event data to the service bus.

8. The method of claim 1, further comprising:

sending a current request to post the event data to the service bus;

maintaining a count of previous successful and failed requests to post the event data to the service bus during a predetermined period;

throttling the current request to post the event data to the service bus based on at least one of;

the count of previous successful and failed requests during the predetermined period and a post priority, the post priority based on whether the current request to post the event data to the service bus is at least one of a synchronous request and an asynchronous request.

9. The method of 1, further comprising:

determining that a request to post the event data to the service bus has failed; and

resending the failed request to post the event data to the service bus.

10. A customer relationship management (CRM) computer system for extending a CRM eventing framework to a cloud computing environment, comprising:

a memory for storing executable program code; and

a processor, functionally coupled to the memory, the processor being responsive to computer-executable instructions contained in the program code and operative to;

register service information for a service in the cloud computing environment, the cloud computing environment comprising a service bus and an authenticating service, wherein a listening channel is opened between the service and the service bus prior to registering the service information;

receive a request made by a requester, the request triggering a request processing pipeline in an eventing framework;

post event data responsive to the request to the service bus;

receive a confirmation of retrieval of the event data from the service bus by the service; and

send a response to the requester.

11. The system of claim 10, wherein the processor is operative to:

prior to posting the event data, request an authentication token for the service bus from the authenticating service; and

receive the authentication token for the service bus from the authenticating service.

12. The system of claim 11, wherein the processor is operative to post the authentication token for the service bus and the event data to the service bus in a custom header, wherein the authentication token for the service bus is validated by the service bus.

13. The system of claim 10, wherein the processor is operative to:

prior to posting the event data, retrieve a federated token for the service from the authenticating service;

retrieve an authentication token for the service bus from the authenticating service.

14. The system of claim 13, wherein the processor is operative to post the event data, the federated token for the service and the authentication token for the service bus to the service bus, wherein the authentication token for the service bus is consumed by the service bus and the event data and the federated token for the service is forwarded from the service bus to the service, wherein the federated token for the service is validated by the service.

15. The system of claim 10, wherein the processor, in posting event data responsive to the request to the service bus, is operative to perform at least one of the following:

utilize a CRM workflow to post the event data to the service bus, wherein the CRM workflow is triggered upon a request by the requester for CRM data;

utilize custom plug-ins to post the event data to the service bus;

post the event data to the service bus via an intermediary router; and

at least one of synchronously and asynchronously post the event data to the service bus.

16. The system of claim 10, wherein the processor is further operative to:

send a current request to post the event data to the service bus;

maintain a count of previous successful and failed requests to post the event data to the service bus during a predetermined period; and

throttle the current request to post the event data to the service bus based on at least one of;

the count of previous successful and failed requests during the predetermined period and a post priority, the post priority based on whether the current request to post the event data to the service bus is at least one of a synchronous request and an asynchronous request.

17. The system of claim 10, wherein the processor is further operative to:

determine that a request to post the event data to the service bus has failed; and

resend the failed request to post the event data to the service bus.

18. A computer-readable storage medium comprising computer-executable instructions which, when executed by a computer, will cause the computer to perform a method of extending a customer relationship management (CRM) eventing framework to a cloud computing environment, comprising:

registering, in a CRM system, service information for a service in the cloud computing environment, the cloud computing environment comprising a service bus and an authenticating service, wherein a listening channel is opened between the service and the service bus prior to registering the service information;

receiving a user request made by a user of the CRM system, the request triggering a request processing pipeline in an eventing framework;

retrieving a federated token for the service from the authenticating service;

retrieving an authentication token for the service bus from the authenticating service;

at least one of synchronously and asynchronously posting event data responsive to the request to the service bus, wherein at least one of synchronously and asynchronously posting event data responsive to the request to the service bus comprises;

posting the event data, the federated token for the service and the authentication token for the service bus to the service bus, wherein the authentication token for the service bus is consumed by the service bus and the event data and the federated token for the service is forwarded from the service bus to the service, wherein the federated token for the service is validated by the service;

utilizing a CRM workflow to post the event data to the service bus, wherein the CRM workflow is triggered upon a request by the requester for CRM data;

utilizing sandbox and non-sandbox plug-ins to post the event data to the service bus; and

posting the event data to the service bus via an intermediary router;

receiving a confirmation of retrieval of the event data from the service bus by the service; and

sending a response to the user.

19. The computer-readable storage medium of claim 18, further comprising:

maintaining a count of previous successful and failed requests to post the event data to the service bus during a predetermined period;

throttling the current request to post the event data to the service bus based on at least one of;

the count of previous successful and failed requests during the predetermined period and a post priority, the post priority based on whether the current request to post the event data to the service bus is at least one of a synchronous request and an asynchronous request.

20. The computer-readable storage medium of claim 18, further comprising:

determining that a request to post the event data to the service bus has failed; and

resending the failed request to post the event data to the service bus.