Integrated trading platform architecture

• US 20050188378A1
• Filed: 05/21/2004
• Published: 08/25/2005
• Est. Priority Date: 06/06/2003
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Miller, Lawrence R., Lempenau, James A., Peterson, Andrew J., Le Gelebart, Marc, Shtivelman, Leonid, Deans, William T.
• Granted Patent: US 7,770,184 B2
• Time in Patent Office: Days
• US Class Current: 719/310
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: H04L 63/0869 for achieving mutual authentication cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A system and method that provides a JPeX client that opens up a socket on which it listens for connections from the local host. External applications on the desktop are able to connect to the server socket in the client and use XML to execute commands on the client.

Claims

1. An applet executing on a computer for interfacing with multiple client programs executing on the computer, the applet being initiated by a browser-based application executing on the computer, the applet comprising:

a socket server configured to perform actions comprising;

(1) establishing a server socket on a port,

(2) receiving a connection request via the port from at least one of the multiple client programs,

(3) opening a socket connection on a different port for communicating with the at least one of the multiple client programs in response to the received connection request,

(4) receiving a service request on the different port from the at least one of the multiple client programs after the socket connection is opened, and

(5) outputting the received service request as a passed-on service request;

a translation facade configured to perform actions comprising;

(1) receiving the passed-on service request outputted from the socket server,

(2) parsing the passed-on service request, thereby generating a parsed service request, if the passed-on service request complies with predetermined rules,

(3) rejecting the passed-on service request if the passed-on service request does not comply with the predetermined rules, and

(4) outputting the parsed service request if generated; and

a processing system configured to perform actions comprising;

(1) receiving the parsed service request from the translation facade and

(2) processing the parsed service request.

2. The applet according to claim 1, further comprising an authentication module configured to perform actions comprising authenticating the socket connection after the socket server opens the socket connection.

3. The applet according to claim 1, wherein at least one of the multiple client programs is a second applet that provides an interface between another browser-based application and the socket server.

4. The applet according to claim 3, wherein the service request has a string message format.

5. The applet according to claim 1, wherein at least one of the multiple client programs is a spreadsheet application.

6. The applet according to claim 1, wherein the socket server is configured to perform actions further comprising:

transmitting a handshake data message to the at least one of the multiple client programs after opening the socket connection; and

terminating the socket connection if a proper reply to the handshake data message is not received.

7. The applet according to claim 1, wherein the translation facade parses the passed-on service request into a SOAP Envelope structure.

8. A system for integrating programs executing on a computer, the system comprising:

multiple client programs each configured to perform actions comprising requesting data external to itself; and

an applet initiated by a browser-based application executing on the computer, the applet comprising;

a socket server configured to perform actions comprising;

(1) establishing a server socket on a port,

(2) receiving a connection request via the port from the at least one of the multiple client programs,

(3) opening a socket connection on a different port for communicating with the at least one of the multiple client programs in response to the received connection request,

(4) receiving a service request on the different port from the at least one of the multiple client programs after the socket connection is opened, and

(5) outputting the received service request as a passed-on service request;

a translation facade configured to perform actions comprising;

(1) receiving the passed-on service request outputted from the socket server,

(2) parsing the passed-on service request, thereby generating a parsed service request, if the passed-on service request complies with predetermined rules,

(3) rejecting the passed-on service request if the passed-on service request does not comply with the predetermined rules, and (4) outputting the parsed service request if generated; and

a processing system configured to perform actions comprising;

(1) receiving the parsed service request from the translation facade and

(2) processing the parsed service request.

9. The system for integrating programs according to claim 8, wherein the applet further comprises an authentication module configured to perform actions comprising authenticating the socket connection after the socket server opens the socket connection.

10. The system for integrating programs according to claim 8, wherein at least one of the multiple client programs is a second applet that provides an interface between another browser-based application and the socket server.

11. The system for integrating programs according to claim 10, wherein the service request has a string message format.

12. The system for integrating programs according to claim 8, wherein at least one of the multiple client programs is a spreadsheet application.

13. The system for integrating programs according to claim 8, wherein the socket server is configured to perform actions further comprising:

transmitting a handshake data message to the at least one of the multiple client programs after opening the socket connection; and

terminating the socket connection if a proper reply to the handshake data message is not received.

14. The system for integrating programs according to claim 8, wherein the translation facade parses the passed-on service request into a SOAP Envelope structure.

15. A method for use as an applet initiated by a browser-based application in a computer that interfaces with multiple client programs executing on the computer, the method comprising:

establishing a server socket on a port;

receiving a connection request via the port from at least one of the multiple client programs;

opening a socket connection on a different port for communicating with the at least one of the multiple client programs in response to receiving the connection request;

receiving a service request on the different port from the at least one of the multiple client programs after opening the socket connection;

parsing the received service request, thereby generating a parsed service request, if the received service request complies with predetermined rules;

rejecting the received service request if the received service request does not comply with the predetermined rules; and

processing the parsed service request.

16. The method according to claim 15, further comprising authenticating the socket connection after opening the socket connection.

17. The method according to claim 15, wherein at least one of the multiple client programs is a second applet that interfaces with another browser-based application.

18. The method according to claim 17, wherein the service request has a string message format.

19. The method according to claim 15, wherein at least one of the multiple client programs is a spreadsheet application.

20. The method according to claim 15, further comprising:

transmitting a handshake data message to the at least one of the multiple client programs after opening the socket connection; and

terminating the socket connection if a proper reply to the handshake data message is not received.

21. The method according to claim 15, wherein the parsed service request is in a SOAP Envelope structure.