Software agents incorporating message-driven beans for J2EE computing environment

• US 20050050540A1
• Filed: 08/25/2003
• Published: 03/03/2005
• Est. Priority Date: 08/25/2003
• Status: Abandoned Application

• Current Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Flocken, Philip A., Shaughnessy, Jay
• Application Number:
  US10/647,738
• Publication Number:
  US 20050050540A1
• Time in Patent Office: Days
• US Class Current: 718/1
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

Agent server software provides for simple workflow relationships among message-initiated tasks. The agent software runs as a Java J2EE application and supports software agents, each of which incorporates a message-driven bean. A required invoker agent accepts Java Messaging Service (JMS, original or as-translated from HTTP) messages requesting a goal to be accomplished. The invoker agent checks an agent-configuration file to identify an agent that can accomplish the goal; if the identified agent has prerequisites that are not met by the contents of the request, the invoker agent can invoke intermediate agents to fulfill the requirements. An intermediate agent can invoke the goal-fulfilling agent once all its prerequisites are met. Each request and each agent invocation is recorded in an agent-server database so that progress is tracked and so retries and recovery can be achieved in the event of a failure or fault.

Claims

1. On computer readable media, a computer program set for running in a J2EE environment including an application server and message-driven beans, said program set comprising:

software agents, each of which incorporates a respective message-driven bean;

configuration data external to said software agents for determining dependencies among said software agents so that an output of a first of said software agents can serve as an input to a second of said software agents; and

an agent server for implementing said agents and said dependencies, said agent server being coupled to said application server, said software agents, and said configuration data.

2. A computer program set as recited in claim 1 wherein said software agents include an invoker agent for receiving task requests from a client external to said agent server.

3. A computer program set as recited in claim 2 wherein said invoker agent selects said second agent for executing a task specified in said task request.

4. A computer program set as recited in claim 3 wherein said invoker selects said second agent as a function of said configuration data.

5. A computer program set as recited in claim 3 wherein said invoker agent determines said second agent has a prerequisite for executing said task, said invoker agent determining whether or not said prerequisite is met by said request and

if said prerequisite is met, invoking said second agent, and

if said prerequisite is not met, invoking said first agent of said agents, said third agent being invoked to meet said prerequisite.

6. A computer program set as recited in claim 5 wherein said invoker agent selects said first agent as a function of said configuration data.

7. A computer program set as recited in claim 5 wherein said first agent invokes said second agent once said prerequisite is met.

8. A computer program set as recited in claim 2 further comprising a database, said invoker agent storing said request in said database.

9. A computer program set as recited in claim 8 wherein each of said agents stores its status in said database.

10. A computer program set as recited in claim 1 wherein said agent server provides for configurable error handling, said configuration data specifying configurations for said error handling.

11. A computer-implemented method comprising:

a first software agent incorporating a first message-driven bean receiving a first message requesting a second software agent incorporating a second message-driven bean to achieve a goal;

said first software agent examining configuration data external to said first and second software agents to determine if said second software agent has any prerequisites that are not met by said first message;

if not, said first software agent invoking said second software agent by sending a second message to said second software agent; and

if yes, said first software agent examining configuration data external to said first and second software agents to identify a third software agent incorporating a third message-driven bean that meets a prerequisite of said second software agent that is not met by said request and then invokes said third software agent by sending a third message to it.

12. A method as recited in claim 11 wherein, if, when it is determined that said second software agent has prerequisites that are not met by first message, if said prerequisites are also not met by said third software agent, said third software agent invoking a fourth software agent incorporating a fourth message-driven bean agent that meets another prerequisite of said second software agent.

13. A method as recited in claim 11 wherein, if, when it is determined that said second software agent has prerequisites that are not met by first message, if said prerequisites are also not met by said third software agent, said first software agent also invoking a fourth software agent incorporating a fourth message-driven bean agent that meets another prerequisite of said second software agent, said fourth software agent being invoked in parallel with said third software agent.