Dynamic class mapping in messaging middleware

A server computer system, comprising:

• a processor;
• a non-transitory memory storing a business transaction mapping configuration file, where the business transaction mapping configuration file maps signatures comprising a client application identity, a business transaction type identity, and a business transaction service platform identity to an action, the action comprising one of executing a stubbed out function on a messaging middleware platform or performing a business transaction on a business transaction service platform;
• and
• a business transaction proxy application stored in the non-transitory memory that, when executed by the processor:
• receives a first client request from a client application executing on a remote computer system to perform a business transaction service, where the client request identifies the client application, identifies a business transaction type, and identifies a first business transaction service platform,
• in response to receiving the first client request, reads the business transaction mapping configuration file, where the business transaction proxy application reads the business transaction mapping configuration file each time it receives a different client request,
• based on reading the business transaction mapping configuration file, builds a first business transaction request,
• sends, by the business transaction proxy application, the first business transaction request to the first business transaction service platform identified in the client request via the messaging middleware platform,
• receives a second client request by the business transaction proxy application executing on the messaging middleware computer system from the client application executing on the remote computer system to perform the business transaction service, where the second client request identifies the client application, identifies the business transaction type, and identifies the first business transaction service platform,
• in response to receiving the second client request, reads the business transaction mapping configuration file by the business transaction proxy application,
• based on reading the business transaction mapping configuration file, builds a second business transaction request by the business transaction proxy application, and
• sends the second business transaction request to a second business transaction service platform based on a modified mapping in the business transaction mapping configuration file without rebooting the business transaction proxy application between reading the business transaction mapping configuration file in response to receiving the first client request, sending the first business transaction request to the first business transaction service platform, reading the business transaction mapping configuration file in response to receiving the second client request, and sending the second business transaction request to the second business transaction service platform and without rebooting the messaging middleware computer system.

A method of handling requests for service by client applications executing on remote computer systems, comprising:

• receiving a first client request by a business transaction proxy application executing on a messaging middleware computer system from a first client application executing on a remote computer system to perform a first business transaction, where the first client request identifies the first client application, identifies a first business transaction type, and identifies a first business transaction service platform;
• in response to receiving the first client request, reading a first version of a business transaction mapping configuration file by the business transaction proxy application, where the business transaction proxy application reads the business transaction mapping configuration file each time it receives a client request, where the business transaction mapping configuration file maps signatures comprising a client application identity, a business transaction type identity, and a business transaction service platform identity to an action, the action comprising one of executing a stubbed out function on the messaging middleware computer system and performing a business transaction on the business transaction service platform, and where the first version of the business transaction mapping configuration file comprises a mapping of the first client application identity, the first business transaction type identity, and the first business transaction service platform identity to the first business transaction of the first business transaction service platform;
• based on reading the first version of the business transaction mapping configuration file, building a first business transaction request by the business transaction proxy application that requests the first business transaction service platform to perform the first business transaction;
• sending by the business transaction proxy application the first business transaction request to the first business transaction service platform via the messaging middleware computer system;
• revising the first version of the business transaction mapping configuration file to a second version of the business transaction mapping configuration file that comprises a mapping of the first client application identity, the first business transaction type identity, and the first business transaction service platform identity to a second business transaction on a second business transaction service platform, the first business transaction and the second business transaction providing the same service;
• receiving a second client request by the business transaction proxy application from the first client application to perform the second business transaction, where the second client request identifies the first client application, identifies the first business transaction type, and identifies the first business transaction service platform;
• in response to receiving the second client request, reading the second version of the business transaction mapping configuration file by the business transaction proxy application;
• based on reading the second version of the business transaction mapping configuration file, building a second business transaction request by the business transaction proxy application that requests the second business transaction service platform to perform the second business transaction;
• and
• sending by the business transaction proxy application the second business transaction request to the second business transaction service platform via the messaging middleware computer system without rebooting the business transaction proxy application between reading the first version of the business transaction mapping configuration file, sending the first business transaction request to the first business transaction service platform, reading the second version of the business transaction mapping configuration file, and sending the second business transaction request to the second business transaction service platform.