PROVISIONING HIGHLY AVAILABLE SERVICES FOR INTEGRATED ENTERPRISE AND COMMUNICATION

• US 20110004701A1
• Filed: 12/24/2009
• Published: 01/06/2011
• Est. Priority Date: 12/29/2008
• Status: Abandoned Application

• Current Assignee: Drishti-Soft Solutions Pvt Ltd. (Exotel Techcom Pvt. Ltd.)
• Original Assignee: Drishti-Soft Solutions Pvt Ltd. (Exotel Techcom Pvt. Ltd.)
• Inventors: Panda, Debashish, Jain, Nayan Kumar
• Application Number:
  US12/647,281
• Publication Number:
  US 20110004701A1
• Time in Patent Office: Days
• US Class Current: 709/242
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

A development, deployment and execution environment for a plurality of application components present in a distributed system in a service oriented architecture paradigm, the plurality of application components comprising both enterprise application components and communications application components and a method for application component life cycle management as well as registration, discovery, routing and processing of both synchronous and asynchronous service requests among the plurality of application components.

Claims

1. A method for routing service requests in an execution environment, the execution environment comprising a plurality of nodes, the method comprising:

a. Registering a service with at least one node, the at least one node comprising an application component, the application component being associated with the service, wherein registering comprises associating a service instance of the service with the application component;

b. Receiving a request for a service reference of the service from a requesting node, the requesting node being one of the plurality of nodes;

c. discovering an application component instance associated with the application component at a first node in response to the request for a service reference, the first node being one of the at least one node;

d. Sending a stub to the requesting node, the stub comprising an application component instance information and service method invocation types, the application component instance information being associated with the application component instance;

e. Receiving at least one service request from the requesting node, the service request being sent by the requesting node using the information in the stub; and

f. Routing the at least one service request to an execution node for execution using the application component instance information.

2. The method of claim 1, wherein the step of discovering an application component instance comprises:

a. Selecting a first node, wherein selection is done according to load distribution logic;

b. Creating an application component instance at the first node.

3. The method of claim 1, wherein the step of discovering comprises identifying an application component instance running at a first node wherein the application component instance is associated with the application component.

4. The method of claim 1 wherein the service method invocation type is one of synchronous and asynchronous.

5. The method of claim 1 wherein the execution node is the first node.

6. The method of claim 1 wherein the step of routing further comprises:

a. Identifying an execution node where the application component instance is present;

b. Routing the service request to the execution node for execution.

7. The method of claim 6 wherein the execution node is the first node.

8. A method of executing service requests in an execution environment, the execution environment comprising a plurality of nodes, a service being registered with at least one node, the at least one node comprising an application component associated with the service, a service instance of the service being associated with the application component, the service being associated with a queuing policy, the method comprising:

a. Receiving at least one service request related to the service from a requesting node, the service request being received through an invocation thread, the service request comprising an application component instance information and a service method invocation type, the application component instance information being associated with an application component instance;

b. Routing the service request to an execution node using the application component instance information, the execution node being one of the at least one node;

c. Queuing the service request for execution in a message queue at the execution node, wherein queuing is based on the queuing policy and the service method invocation type, the message queue being associated with the service;

d. Submitting the service request to the service instance for execution; and

e. Receiving a response message from the service instance after the execution of the service request.

9. The method of claim 8 further comprises the step of extracting a response handler parameter and other parameters from the service request when the service method invocation type is asynchronous.

10. The method of claim 8 further comprises the step of releasing the invocation thread after receiving the service request, when the service method invocation type is asynchronous.

11. The method of claim 8 further comprises the step of tracking the state of the application component instance during the execution of the service request.

12. The method of claim 11 further comprises the steps of:

a. Identifying an event of execution node failure during the execution of the service request, the identification being done based on the tracking;

b. Identifying a second execution node based on the identification of the event;

c. Routing the service request to the second execution node based on predefined conditions.

13. The method of claim 8, wherein the response message received is encoded using a delegate response handler for service method with asynchronous invocation.

14. The method of claim 8, wherein the step of submitting, wherein the service method invocation type is asynchronous, comprises:

a. Submitting the service request to a thread pool based on a scheduling algorithm;

b. Allocating a thread from the thread pool to the service instance; and

c. Submitting the service request to the service instance for execution.

15. The method of claim 8, wherein the service method invocation type is asynchronous, further comprising the steps of:

a. Updating state of the application component instance after the execution;

b. Sending the response message to the requesting node using a delegate response handler; and

c. Submitting the response message in a queue for processing, wherein the queue is based on the response handler parameter.

16. The method of claim 8, wherein the service method invocation type is synchronous, further comprising the steps of:

a. Updating state of the application component instance after the execution; and

b. Sending the response message to the requesting node, wherein the response message is returned in the invocation thread.

17. An execution environment, the execution environment comprising:

a. A plurality of nodes;

b. a service registrar, the service registrar configured to register a service with at least one node, the at least one node comprising an application component, each application component being associated with the service, wherein registering comprises associating a service instance of the service with each application component;

c. a component factory, the component factory configured to;

i. Receive a request for a service reference from a requesting node, the requesting node being one of the plurality of nodes;

ii. discover an application component instance associated with the application component at an first node in response to the request for a service reference, wherein discovering is done according to load distribution logic based on discovery information;

d. a messaging layer, the messaging layer configured to;

i. receive an application component instance information from the component factory;

ii. Send a stub to the requesting node, the stub comprising the application component instance information and a service type, the application component instance information being associated with the application component instance;

iii. Receive a service request from the requesting node, the service request comprising information in the stub;

iv. Route the service request to the first node for execution using the application component instance information;

v. Receive a response message from the application component after the execution of the service request;

18. The execution environment of claim 17 further comprising a process control layer, the process control layer configured to:

a. receive the service request routed by the messaging layer;

b. Queue the service request for execution in a queue at the first node, wherein queuing is based on the queuing policy and the service type;

c. Submit the service request to the application component for execution, wherein submitting is based on a scheduling algorithm;

19. The execution environment of claim 17, wherein the component factory further comprises a component handler, the component handler configured to create the application component instance.

20. The execution environment of claim 17 further comprises a component context controller, the component context controller configured to:

a. Track the state of the application component during execution of the service request; and

b. update state of the application component after execution of the service request.