Method and system for integration of software applications

• US 20030105887A1
• Filed: 09/18/2002
• Published: 06/05/2003
• Est. Priority Date: 12/03/2001
• Status: Abandoned Application

• Current Assignee: Juldi, Inc.
• Original Assignee: Juldi, Inc.
• Inventors: Cox, Burke David, Crane, Doug Matthew
• Application Number:
  US10/246,375
• Publication Number:
  US 20030105887A1
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

An integration server includes a predefined, fixed system API that pre-defines the low level interfaces between software applications. The process for integrating these application programs comprises initializing an integration administrator; defining operations and operation resources for transactions between a client and target application programs; configuring an integration server to accept transactions from the client application program via client code and from the target application via a solution server code; configuring the client code consistent with a client application interface and a predetermined integration server API, and solution server code consistent with a target application interface and the integration server API; and deploying the client code and solution server code. In operation, client code creates an operation object including at least one dataset at a first program using a predetermined integration API; submits the operation object to an integration server; processes the operation object to create a further request object including said dataset, and forwards the request object to a solution program; and processes the request object by the solution program to extract the dataset, forward the dataset for processing at a second program according to functionality associated the operation object, and return a response.

Claims

1. An integration code for use in facilitating integration of plural application programs having different APIs, said integration code comprising a set of predetermined and fixed processes operable as a common API between said plural application programs.

2. The integration code of claim 1, wherein said processes comprise a predetermined job class and operation class forming a predetermined framework for requesting and receiving responses from an integration server.

3. The integration code of claim 2, further comprising a resource class operable to associate at least one dataset with an operation object, wherein the.

4. The integration code of claim 3, further comprising a connector class operable to create and manage job class objects.

5. The integration code of claim 4, wherein said job class is a java class having derivative request and responses classes operable to facilitate XML transactions between said plural application programs and said integration server.

6. A method for operating transactions between programs having different APIs which are at least partially incompatible, comprising:

a. creating an operation object including at least one dataset at a first program using a predetermined integration API;

b. submitting the operation object to an integration server;

c. processing the operation object to create a further request object including said dataset, and forwarding the request object to a solution program;

d. processing the request object by the solution program to extract the dataset and forward the dataset for processing at a second program according to functionality associated the operation object.

7. The method of claim 6, further comprising:

e. the solution program forming a response object including a response dataset from the second program;

f. processing the response object by the integration server and forwarding the response dataset to the first program.

8. The method of claim 7, wherein step d further comprises transaction management including commits of the type including one of the group of asynchronous/immediate, synchronous/immediate, asynchronous/deferred, and synchronous/deferred commits.

9. The method of claim 6, wherein step a further comprises creating the operation object at client code into a well-formed XML document

10. The method of claim 9, wherein step a further comprises creating the operation object with an XML document including bound objects.

11. A system for operating transactions between programs having different APIs which are at least partially incompatible, comprising:

an integration server having a predetermined and fixed API;

a first application having associated client code operably configured to create operations consistent with said API;

a second application having solution code operably configured to process data from said operations consistent with said API.

12. The system of claim 11, wherein the integration server further comprises an integration administrator operable to define operations, configure the client code and solution code, and log the processing of operations.

13. The system of claim 11, wherein the fixed API comprises predetermined operation, connector, and resource classes.

14. The system of claim 13, wherein the first application comprises a listener comprising at least one of the group of a file server listener, an email server listener, a publish-subscribe listener, and a broadcast listener, said at least one listener operable to monitor for and convert data of pre-selected characteristics into integration objects.

15. A process for integrating application programs having application interfaces which are at least partially incompatible, comprising:

a. initializing an integration administrator;

b. defining operations and operation resources for transactions between a client and target application programs;

c. configuring an integration server to accept transactions from the client application program via client code and from the target application via a solution server code;

d. configuring the client code consistent with a client application interface and a predetermined integration server API, and solution server code consistent with a target application interface and the integration server API;

e. deploying the client code and solution server code.

16. The process of claim 15, further comprising the integration administrator testing the integration by generating a sample request and verifying that a correct response is received from the target application.

17. The process of claim 15, wherein the integration administrator is a program element of an integration server, and step b further comprises receiving a user input selecting a first selectable item associated with a first predefined set of security parameters, and step e further comprises automatically deploying security functionality with the client code and solution server code operable to process operation data according to the type of security associated with said predefined set of security parameters.

18. A process for providing single-user-action implementation of security, comprising:

a. initializing an integration administrator operable to define operations consistent with a predetermined integration server API including an operation class, the integration administrator comprising a user interface have at least one selectable item associated with a predefined set of security parameters;

b. receiving a single user input selecting a first selectable item associated with a first predefined set of security parameters; and

c. automatically deploying security functionality so said operations are created and processed according to the type of security associated with said predefined set of security parameters.

19. The process of claim 18, wherein the type of security is message authentication, and step c comprises automatically configuring client code to digitally sign each operation and at least one of an integration server and target solution code to authenticate the digitally signed operation based on the predefined set of security parameters.

20. The process of claim 18, wherein the type of security is encryption, and step c comprises automatically configuring client code to encrypt operation data and at least one of an integration server and target solution code to decrypt the operation data based on the predefined set of security parameters.