US 7,603,431 B2
Secure transport gateway for message queuing and transport over an open network
Eric Campbell, Rye, N.H. (US); Robert F Hoffman, Baldwin, N.Y. (US); Robert Maloney, Jr., Massapequa Park, N.Y. (US); Maris N Lemanis, Smithtown, N.Y. (US); and Andrew Mintzer, Fort Salonga, N.Y. (US)
Assigned to Bottomline Technologies (de) Inc., Portsmouth, N.H. (US)
Filed on Mar. 12, 2005, as Appl. No. 11/81,033.
Application 11/081033 is a continuation in part of application No. 10/979045, filed on Nov. 01, 2004.
Application 10/979045 is a continuation in part of application No. 10/879233, filed on Jun. 29, 2004.
Application 10/879233 is a continuation in part of application No. 10/139596, filed on May 06, 2002.
Application 10/139596 is a continuation in part of application No. 10/041513, filed on Jan. 08, 2002, abandoned.
Prior Publication US 2005/0160098 A1, Jul. 21, 2005
Int. Cl. G06F 15/16 (2006.01)
U.S. Cl. 709—217  [709/218; 709/219] 2 Claims
OG exemplary drawing
 
1. A system for secure automated transfer of a binary object between a transfer client message queuing manager and a transfer server message queuing manager over the Internet, the transfer client message queuing manager operating in conjunction with a remote file transfer client, the system comprising:
a database storing file transfer parameters in association with identification of the remote file transfer client, the database comprising:
an event key table, the event key table comprising a plurality of records, each record associating an event with identification of the remote file transfer client, each event being identified by an event key value stored in an event key field; and
an event parameter table, the event parameter table comprising a plurality of records, each record associating an event parameter with the event key value, the event parameters comprising upload event parameters, the upload event parameters comprising:
an MQ Get parameter comprising data necessary for the transfer client to initiate an MQGET processing call to the transfer client message queuing manager and obtain a message in a queue identified in the processing call;
object destination parameters defining an MQ Put processing call to the transfer server message queuing manager and comprising an MQ Put parameter comprising all data necessary for the transfer application to initiate the MQ Put processing call to the transfer server, including a destination queue definition which provides for queuing the binary object within the defined queue for retrieval by a destination application, and
a processor executing a transfer application, the transfer application comprising a plurality of file transfer methods available to the remote file transfer client making method calls to the transfer application, the plurality of transfer methods comprising:
a log on method executed in response to receiving a log-on method call from the remote file transfer client, the log on method call comprising identification of the remote file transfer client, the log on method comprising:
assigning a session ID to a web services session with the remote transfer client; and
returning a response message to the transfer client, the response method comprising a session ID;
a retrieve active event keys method executed in response to the receiving a retrieve active event keys method call from the transfer client, the retrieve active event keys method call including the session ID, the retrieve active event keys method comprising:
obtaining, the identification of the remote transfer client associated with the session ID included in the method call;
obtaining, from the event key table, the event key value associated with the identification of the remote transfer client; and
providing a response message to the transfer client, the response message including the event key value associated with identification of the remote transfer client;
a read event method executed in response to receiving a read event method call from the remote transfer client, the read event method call comprising the session ID and the event key value; the read event method comprising:
retrieving the event parameters associated with the event key value included in the method call from the event parameter table, and
returning a response message to the transfer client, the response message comprising the MQ Get Parameter and the MQ Put Parameter;
an upload method operated in response to receiving an upload method call from the remote file transfer client, the upload method call comprising the session ID, a file name, and the binary object, the upload method comprising;
generating an object ID to associated with the binary object;
returning a response to the remote transfer client, the response comprising the object ID; and
storing the binary object in a binary storage; and
a destination method operated in response to receiving a destination method call from the transfer client, the destination method call comprising the session ID, the object ID, and the MQPUT parameter, the destination ID method comprises executing the MQ Put processing call to the transfer server message queuing manager, the processing call delivering the binary object associated with the object ID from the binary storage to the transfer server method queuing manager in conjunction with the destination queue definition.