| US 7,483,994 B1 | ||
| System and method for creating a standard envelope structure | ||
| Michael Clifford Stephens, Stillwater, Minn. (US); and Rae Dean M. Walby, New Hope, Minn. (US) | ||
| Assigned to Ameriprise Financial, Inc., Minneapolis, Minn. (US) | ||
| Filed on Jun. 08, 2005, as Appl. No. 11/160,094. | ||
| Claims priority of provisional application 60/624377, filed on Nov. 01, 2004. | ||
| Int. Cl. G06F 15/16 (2006.01); G06F 7/00 (2006.01) | ||
| U.S. Cl. 709—230 [709/204; 709/228; 707/103 R; 707/1] | 50 Claims |

| 1. A method for creating an envelope structure with defined data blocks within a request-response messaging pattern, said
method including:
creating a first request message within a first programming language;
creating a request mark-up language envelope from said first request message by:
creating a transaction block for maintaining transport protocol parameters;
maintaining said transport protocol parameters within said transaction block during component message processing;
creating a state block for maintaining an application specific process control identifier;
maintaining said application specific process control identifier within said state block during said component message processing;
creating a routing block for maintaining a response message return path;
maintaining said response message return path within said routing block during said component message processing;
creating an accounting block for maintaining processing costs to be charged to a requester;
maintaining said processing costs within said accounting block during said component message processing;
creating a logging block for maintaining an audit trail provided to said requestor;
maintaining said audit trail within said logging block during said component message processing;
creating a trace block for maintaining error information;
maintaining said error information within said trace block during said component message processing;
creating a security block for maintaining a security token designating authentication of said requester; and
maintaining said security token designating authentication within said security block during said component message processing;
converting said request mark-up language envelope to a second request message within a second programming language;
processing said second request message;
creating a first response message within said second programming language, wherein said first response message is based upon
results of said processing of said second request message;
creating a response mark-up language envelope from said first response message;
converting said response mark-up language envelope to a second response message within said first programming language; and,
processing said second response message.
|