CICS BMS (Basic Message Service) meta model

• US 20020042849A1
• Filed: 05/04/2001
• Published: 04/11/2002
• Est. Priority Date: 08/08/2000
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Ho, Shyh-Mei F., Sheats, Benjamin Johnson, Krasun, Andrzej McColl
• Granted Patent: US 7,559,066 B2
• Time in Patent Office: Days
• US Class Current: 719/329
• CPC Class Codes: G06F 2209/509 Offload
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

A method of and a system for processing a transaction on an end user application and an application server. This is accomplished by initiating the transaction on the end user application in a first language (such as a markup language) with a first application program (such as a Web browser), and transmitting the transaction to the server and converting the transaction from the first language of the first end user application to a language running on the application server, processing the transaction on the application server, and transmitting the transaction from the application server back to the end user application, and converting the transaction from the language running on the application server to the language of the end user application. The end user application and the application server have at least one connector between them, and the steps of (i) converting the transaction from the language of the end user application (as a source language) to the language running on the application server (as a target language), and (ii) converting the transaction from the language running on the application server (as a source language) to the language of the end user application (as a target language), each include the steps of invoking connector metamodels of the respective source and target languages, populating the connector metamodels with metamodel data of each of the respective source and target languages, and converting the source language to the target language.

Claims

1. A method of processing an application request on an end user application and an application server including a mapping support language comprising the steps of:

a) initiating the application request on the end user application in a first language with a first application program;

b) transmitting the application request to the server and converting the application request from the first language of the first end user application to a form for the mapping support language running on the application server;

c) processing said application request on the application server;

d) transmitting a response to the application request from the application server to the end user application, and converting the response to the application request from the mapping support language running on the application server to the first language of the first end user application; and

e) wherein the end user application and the application server have at least one connector therebetween, and the steps of (i) converting the application request from the first language of the first end user application as a source language to the language running on the application server as a target language, and (ii) converting a response to the application request from the language running on the application server as a source language to the first language of the first end user application as a target language, each comprise the steps of;

1) invoking connector metamodels of respective source language and target mapping support language;

2) populating the connector metamodels with metamodel data of each of the respective source language and target mapping support language, the metamodel data of the target mapping support language including a map, a mapset, and a mapfield; and

3) converting the source language to the mapping support language.

2. The method of claim 1 wherein the end user application is a web browser.

3. The method of claim 2 wherein the end user application is connected to the application server through a web server, and the web server comprises a connector.

4. The method of claim 1 wherein the metamodel comprises invocation metamodel data, application domain interface metamodel data, transaction message metamodel data, and type descriptor metamodel data.

5. A transaction processing system comprising a client, a server, and at least one connector therebetween,

a) the client having an end user application, and being controlled and configured to initiate an application request with the server in a first language with a first application program and to transmit the application request to the server;

b) the connector being configured and controlled to receive the application request from the client, convert the application request from the first language of the first end user application running on the client to a language and a mapping support language running on the server;

c) the server being configured and controlled to receive the converted application request from the connector and processing the said application request in a second language with a second application program residing on the server, and to thereafter transmit a response to the application request through the connector back to the first application program on the client;

d) the connector being configured and controlled to receive a response to the application request from the server, to convert a response to the application request from the language running on the application server to the first language of the first application program running on the client; and

e) wherein connector between the client and the server is configured and controlled to (i) convert the application request from the first language of the client application on the client as a source language to the language running on the application server as a target language, and (ii) convert the response to the application request from the language running on the application server as a source language to the first language of the client application running on the client as a target language, each by a method comprising the steps of;

1) retrieving connector metamodels of respective source and target languages and target mapping support language from a metamodel data repository, said mapping support language metadata including a map, a mapset, and a mapfield;

2) populating the connector metamodels with metamodel data from the metamodel data repository for each of the respective source and target languages; and

3) invoking the retrieved, populated connector metamodels and converting the source language to the target language.

6. The system of claim 5 wherein the end user application is a web browser.

7. The system of claim 6 wherein the end user application is connected to the application server through a web server, and the web server comprises an connector.

8. A transaction processing system configured and controlled to interact with a client application, and comprising a server, and at least one connector between the server and the client application, where the client has an end user application, and is controlled and configured to initiate an application request with the server in a first language with a first application program and to transmit the application request to the server, wherein:

a) the connector being configured and controlled to receive an application request from the client, convert the application request from the first language of the first end user application running on the client to a language running on the server;

b) the server being configured and controlled to receive the converted application request from the connector and process the said application request in a second language with a second application program and a target mapping support language residing on the server, and to thereafter transmit a response to the application request through the connector back to the first application program on the client;

c) the connector being configured and controlled to receive the application request from the server, to convert a response to the application request from the language running on the application server to the first language of the first application program running on the client; and

d) wherein connector between the client and the server is configured and controlled to (i) convert the application request from the first language of the client application on the client as a source language to the language running on the application server as a target language, and (ii) convert the response to the application request from the language running on the application server as a source language to the first language of the client application running on the client as a target language, each by a method comprising the steps of;

1) retrieving connector metamodel data of respective source and target languages from a metamodel data repository;

2) populating the connector metamodels with metamodel data of each of the respective source and target languages and target mapping support language, from the metamodel data repository, said target mapping support language metadata including a map, a mapset, and a mapfield; and

invoking the retrieved, populated connector metamodels; and

3) converting the source language to the target language.

9. The system of claim 8 wherein the end user application is a web browser.

10. The system of claim 9 wherein the end user application is connected to the application server through a web server, and the web server comprises an connector.

11. A program product comprising a storage medium having invocation metamodel data, application domain interface metamodel data, language metamodel data, and mapping support language metamodel data, said mapping support language metamodel data including a map, a mapset, and a mapfield;

and computer instructions for building a metamodel data repository of source and target language metamodel data.

12. The program product of claim 11 wherein the metamodel data in the repository comprises invocation metamodel data, application domain interface metamodel data, mapping support language metamodel data, and type descriptor metamodel data.