IMS transaction messages metamodel

Claim 3

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

Claim 4

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.

Claim 5

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

Claim 6

The method of claim 1 wherein the metamodel data of the transaction manager includes control data, state data, and user data.

Claim 7

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 second language in a form for a transaction manager running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in the 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 the response to the application request from the server, to convert the response to the application request from the second language running on the server to the first language of the first application program running on the client; and e) wherein the 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 second language running on the server as a target language, and (ii) convert the response to the application request from the second language running on the 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 from a metamodel data repository, including transaction manager metadata corresponding to the transaction manager; 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.

Claim 8

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 second language in a form for a transaction manager running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in the 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 the response to the application request from the server, to convert the response to the application request from the second language running on the server to the first language of the first application program running on the client; and e) wherein the 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 second language running on the server as a target language, and (ii) convert the response to the application request from the second language running on the 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 from a metamodel data repository, including transaction manager metadata corresponding to the transaction manager; 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.

Claim 9

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

Claim 10

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

Claim 11

The system of claim 6 wherein the transaction manager metadata includes control data, state data, and user data.

Claim 12

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, wherein: a) the client having an end user application, and being configured and controlled 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 second language in a form for a transaction manager running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in the second language with a second application program and the transaction manager 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 the response to the application request from the server, to convert the response to the application request from the second language running on the server to the first language of the first application program running on the client; and e) wherein the 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 second language running on the application server as a target language, and (ii) convert the response to the application request from the second 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 the transaction manager, from the metamodel data repository; and invoking the retrieved, populated connector metamodels; and 3) converting the source language to the target language.

Claim 13

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, wherein: a) the client having an end user application, and being configured and controlled 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 second language in a form for a transaction manager running on the server; c) the server being configured and controlled to receive the converted application request from the connector and process the application request in the second language with a second application program and the transaction manager 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 the response to the application request from the server, to convert the response to the application request from the second language running on the server to the first language of the first application program running on the client; and e) wherein the 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 second language running on the application server as a target language, and (ii) convert the response to the application request from the second 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 the transaction manager, from the metamodel data repository; and invoking the retrieved, populated connector metamodels; and 3) converting the source language to the target language.

Claim 14

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

Claim 15

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

Claim 16

The system of claim 10 wherein the metamodel data of the transaction manager includes control data, state data, and user data.

Claim 17

A program product comprising a computer-readable storage medium having invocation metamodel data, application domain interface metamodel data, language metamodel data, and transaction manager metamodel data, said transaction manager metamodel data including control data, state data, and user data; computer instructions for building a metamodel data repository of source and target language metamodel data; and computer instructions to build a connector for: 1) retrieving connector metamodel of respective source and target languages from a metamodel data repository; 2) populating the connector metamodel with metamodel data from the metamodel data repository for each of the respective source and target languages; and 3) invoking the retrieved, populated connector metamodel and converting the source language to the target language.

Claim 18

A program product comprising a computer-readable storage medium having invocation metamodel data, application domain interface metamodel data, language metamodel data, and transaction manager metamodel data, said transaction manager metamodel data including control data, state data, and user data; computer instructions for building a metamodel data repository of source and target language metamodel data; and computer instructions to build a connector for: 1) retrieving connector metamodel of respective source and target languages from a metamodel data repository; 2) populating the connector metamodel with metamodel data from the metamodel data repository for each of the respective source and target languages; and 3) invoking the retrieved, populated connector metamodel and converting the source language to the target language.

Claim 19

The program product of claim 14 wherein the metamodel data in the repository comprises invocation metamodel data, application domain interface metamodel data, transaction manager metamodel data, and type descriptor metamodel data.