Modular application collaboration
First Claim
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.
5 Assignments
0 Petitions
Accused Products
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.
-
Citations
8 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. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
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.
-
Specification