Method for facilitating transactions between thin-clients and message format service (MFS)-based information management system (IMS) applications

• US 8,640,144 B2
• Filed: 07/08/2008
• Issued: 01/28/2014
• Est. Priority Date: 09/16/2002
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Dinh, Thu-Tram T., Ho, Shyh-Mei F., Hung, Jenny ChengYin, Yo, Kevin Yu Chang
• Primary Examiner(s): Sough, H S
• Assistant Examiner(s): RONI, SYED A
• Application Number:
  US12/169,486
• Publication Number:
  US 20080271049A1
• Time in Patent Office: 2,030 Days
• Field of Search: None
• US Class Current: 719/313
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/84 Mapping; Conversion
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues

Abstract

A method is disclosed for facilitating conversational and non-conversational transactions between thin-clients and MFS-based IMS applications. The method includes storing conversation attributes associated with a conversational transaction between a thin-client and an MFS-based IMS application, the conversation attributes comprising connection information and conversation-specific information. Next, one or more transaction messages from the thin-client are preprocessed based on a transaction message type. The stored conversation attributes are updated in response changes in the conversation attributes caused by the one or more transaction messages. Then, a conversation output message is formatted for the thin-client. The method may include a security module authenticating a user, a connection module establishing a connection with an MFS-based IMS application, a state module preserving and maintaining conversation attributes, and a control module processing a transaction message having one or more transaction message types.

Claims

1. A programmed method for facilitating transactions between thin-clients and Message Format Service (MFS)-based Information Management System (IMS) applications, the programmed method comprising the process steps of:

storing, by use of a processor, conversation attributes associated with a conversational transaction between a thin-client and an MFS-based IMS application, the conversation attributes comprising a message input descriptor (MID), a message output descriptor (MOD), and a table;

establishing a connection for the conversational transaction between the MFS-based IMS application on a mainframe and a web server;

determining if a request from the thin-client requires interaction with the MFS-based IMS application based on a transaction message type, wherein security information message types, function key message types, paging message types, conversational commands, and format command message types do not require interaction with the MFS-based IMS application;

in response to the request requiring interaction with the MFS-based IMS application, transmitting a conversation input message to the MFS-based IMS application and formatting a conversation output message for the thin-client from the MFS-based IMS application according to the conversation attributes, wherein formatting comprises combining (XML) Extended Markup Language Metadata Interchange (XMI) information for a computing device executing the thin-client with XML Stylesheet (XSL) information to generate HyperText Markup Language (HTML) data suitable for display on the thin-client and sends the HTML data to the thin-client; and

in response to the request not requiring interaction with the MFS-based IMS application, responding to the request from the web server.

2. The programmed method of claim 1 further comprising selectively transmitting the conversation input message to the MFS-based IMS application based on a transaction message type and the conversation attributes.

3. The programmed method of claim 2 wherein the conversation input message is transmitted through an MFS adapter that mediates conversational transactions and the conversation output message is received from the MFS adapter.

4. The programmed method of claim 1 wherein the XMI information is associated with the MFS-based IMS application and the XSL information is user configurable.

5. The programmed method of claim 1, the process steps further comprise:

preprocessing one or more transaction messages from the thin-client based on a transaction message type; and

updating the stored conversation attributes in response to a change in the conversation attributes caused by the one or more transaction messages, wherein the one or more transaction messages comprise a conversation command and preprocessing comprises selectively modifying connection information in response to the conversation command.

6. The programmed method of claim 5 wherein the one or more transaction messages comprise a paging command and preprocessing comprises selectively modifying the conversation output message based on pagination information associated with conversation-specific information.

7. A non-transitory computer-readable storage medium tangibly storing computer instructions for facilitating transactions between thin-clients and Message Format Service (MFS)-based Information Management System (IMS) applications, wherein the computer instructions when executed by a computer perform the process steps of:

storing conversation attributes associated with a conversational transaction between a thin-client and an MFS-based IMS application, the conversation attributes comprising a message input descriptor (MID), a message output descriptor (MOD), and a table;

establishing a connection for the conversational transaction between the MFS-based IMS application on a mainframe and a web server;

determining if a request from the thin-client requires interaction with the MFS-based IMS application based on a transaction message type, wherein security information message types, function key message types, paging message types, conversational commands, and format command message types do not require interaction with the MFS-based IMS application;

in response to the request requiring interaction with the MFS-based IMS application, transmitting a conversation input message to the MFS-based IMS application and formatting a conversation output message for the thin-client from the MFS-based IMS application according to the conversation attributes, wherein formatting comprises combining (XML) Extended Markup Language Metadata Interchange (XMI) information for a computing device executing the thin-client with XML Stylesheet (XSL) information to generate HyperText Markup Language (HTML) data suitable for display on the thin-client and sends the HTML data to the thin-client; and

in response to the request not requiring interaction with the MFS-based IMS application, responding to the request from the web server.

8. The computer-readable storage medium of claim 7 wherein the process steps further comprising selectively transmitting the conversation input message to the MFS-based IMS application based on a transaction message type and the conversation attributes.

9. The computer-readable storage medium of claim 8 wherein the conversation input message is transmitted through an MFS adapter that mediates conversational transactions and the conversation output message is received from the MFS adapter.

10. The computer-readable storage medium of claim 7 wherein the XMI information is associated with the MFS-based IMS application and the XSL information is user configurable.

11. The computer-readable storage medium of claim 7, the process steps further comprising:

preprocessing one or more transaction messages from the thin-client based on a transaction message type; and

updating the stored conversation attributes in response to a change in the conversation attributes caused by the one or more transaction messages, wherein the one or more transaction messages comprise a conversation command and preprocessing comprises selectively modifying connection information in response to the conversation command.

12. The computer-readable storage medium of claim 11 wherein the one or more transaction messages comprise a paging command and preprocessing comprises selectively modifying the conversation output message based on pagination information associated with conversation-specific information.