Modular application collaboration

• US 5,913,061 A
• Filed: 01/08/1997
• Issued: 06/15/1999
• Est. Priority Date: 01/08/1997
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: Crossroads Software Incorporated
• Inventors: Gupta, Prashant, Mellen-Garnett, Katrina A.
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): COURTENAY III, ST JOHN
• Application Number:
  US08/780,593
• Time in Patent Office: 888 Days
• Field of Search: 395/680, 395/671, 395/682
• US Class Current: 719/310
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A modular application collaborator for providing inter-operability between applications including a plurality of connectors for communicating with a like plurality of applications and an interchange server. The interchange server includes an application collaboration module and a service module. The service module transfers messages between connectors and the application collaboration module. The application collaboration module defining the inter-operability between two or more applications and includes a trigger and a transaction responsive to the trigger. The trigger is activated upon receipt of data from one or more connectors resulting in the transaction delivering data to one or more connectors for transfer to an associated application.

Claims

1. A modular application collaborator implementing an inter-operability function between two disassociated and independently operated proprietary applications where each proprietary application belongs to a generic class of applications, comprising:

a pair of connectors external to and distinct from each proprietary application, each communicating with an associated proprietary application and including a business module having business methods and transforms for manipulating data received from a proprietary application in support of a vendor-specific portion of the inter-operability function; and

an interchange server including an application collaboration module and a service module, the service module transferring data and methods between connectors and the application collaboration module, the application collaboration module defining the generic portion of the inter-operability function for providing inter-operability between two generic classes of applications, the application collaboration module including a trigger and a transaction responsive to the trigger, the trigger for initiating the inter-operability function and being activated upon receipt of data from one or more connectors, and the transaction delivering data to one or more connectors for transfer to an associated proprietary application whereby the inter-operability function is realized while each proprietary application is executing independently in an unmodified state unaware of the defined inter-operability.

2. The apparatus of claim 1 wherein the interchange server service module includes a transaction service and an error service, the transaction in the application collaboration module including one or more actions, the transaction service for recording each action and a compensating action, the compensating action for undoing the associated action, the error service monitoring for errors in the interchange server and upon detection of an error stopping the execution of a transaction and triggering the execution of any required compensating actions to undo the interrupted transaction.

3. The apparatus of claim 1 wherein each connector includes an application interface and interchange server interface, the application interface including an API manipulator for receiving and transferring data and methods between a connector and its associated application and the interchange server interface for transferring data and methods between a connector and an application collaboration module.

4. The apparatus of claim 1 wherein a transaction includes a finite state machine.

5. The apparatus of claim 1 wherein data transfers between connectors and an application collaboration module are by objects transferred by the service module in the interchange server.

6. The apparatus of claim 1 wherein the service module includes an event service having subscription and publication services and where an application collaboration module subscribes to one or more connectors based on the trigger, such connectors publishing data to the event service upon receipt of trigger data from its associated proprietary application, and the publication service delivering the data to the application collaboration module.

7. The apparatus of claim 1 wherein the interchange server further includes RAS services and messaging services for assuring delivery of messages to interchange server components.

8. A method for providing inter-operability between two applications each operating on different processes, the method comprising:

defining an inter-operability function between a first and a second application;

dividing the inter-operability function into generic and vendor specific sub-pieces;

creating a generic application collaboration module for storing and executing the generic sub-piece of the inter-operability function;

creating two application specific connectors for storing and executing the vendor specific sub-pieces of the inter-operability function associated with the first and the second applications;

linking the generic application collaboration module and two application specific connectors;

linking the two application specific connectors to the first and second applications, respectively;

initiating and executing the inter-operability function at the generic application collaboration module externally from the first and second applications, resulting in inter-operability between the first and second applications while each application remains unaware of the inter-operability function.