International Business Machines Corporation

Other

Gopalakrishnan P

Hariharan N Venkitachalam

Jithesh Moothoor

Nageswararao Venkata Gokavarapu

Madhu B Ananthapadmanabh

Parameswaran Selvam

Tomohiro Taguchi

Kishor S Kulkarni

Sreejith Nalamvathukkal

Systems and methods for sharing transactional context between Java and traditional language applications are disclosed. In embodiments, a method comprises: receiving, by a computing device, a transaction request to execute a program, wherein the program comprises non-Java program components and Java program components; executing, by a transaction middleware of the computing device, the non-Java program components; contacting, by the transaction middleware, a resource manager server and registering with the resource manager server using global transaction ID data; transferring, by the transaction middleware of the computing device, the Java program components to a transaction coordinator of the computing device, along with thread ID data and the global transaction ID data; and storing, by the transaction coordinator, the thread ID data and global transaction ID data in a recoverable transaction log store.

Sharing transaction contexts in an optimized colocation of java and non-java language applications

An approach is provided for providing transactional operations in an event-driven polyglot language runtime environment. Native functionalities of a transaction processing system are exposed as interfaces to multiple languages and frameworks in the runtime environment. The transactional operations are called from modules. The transaction processing system is integrated with the modules. A prepare operation is sent to a resource manager (RM) via a resolution thread. For a committed transaction outcome of the resolution thread, the commit is logged, an indication of the commit is sent to the RM, the commit is performed, a completion indication of the commit is sent, and a forget operation is logged. For a rollback transaction outcome of the resolution thread, the rollback is logged, an indication of the rollback is sent to the RM, the rollback is performed, a completion indication of the rollback is sent, and the forget operation is logged.

Integrating transaction processing system interfaces with event-driven polyglot runtime modules

A first request to a first thread-based server from a first thread-based client is detected. The first request is derived by the first thread-based client in response to a first call from a first user program running on process-based middleware. The first request is intercepted from a communication pathway. The first request is converted to a merged request. The merged request is intended for a merged thread-based server of the thread-based middleware. The merged request is sent to the merged thread-based server.

Efficient usage of resources in multiple middleware environments

An approach is provided for providing transactional operations in an event-driven polyglot language runtime environment. Native functionalities of a transaction processing system are exposed as interfaces to multiple languages and frameworks in the event-driven polyglot language runtime environment. Application programming interfaces (APIs) are generated for the event-driven polyglot language runtime environment. Via the APIs, the transactional operations are called from modules within the event-driven polyglot language runtime environment. Based on the native functionalities of the transaction processing system being exposed and the transactional operations being called from the modules within the event-driven polyglot language runtime environment via the APIs, the transaction processing system is integrated with the modules within the event-driven polyglot language runtime environment.

The present disclosure relates to techniques for discovering and exposing middleware applications as service endpoints through a universal connector in a middleware-agnostic fashion that does not require additional coding. In one embodiment, a back-end middleware system identifies a set of middleware applications that operate on an input/output (I/O) data area. Next, the back-end middleware system generates a set of discovery artifacts describing the middleware applications and the I/O data area. A discovery client sends a discovery request to a the back-end middleware system, which sends structured information from the discovery artifacts in response. Based on the structured information, the discovery client creates a REST model for the set of middleware applications, mapper artifacts that map REST operations to the middleware applications, and transformer artifacts that indicate how to convert data between Javascript-object-notation (JSON) format and format that is compatible with the I/O data area.

Discovery and exposure of transactional middleware server-based applications as consumable service endpoints

A processor receives a request to perform a transaction, wherein each activity of the transaction is respectively associated with an application server process. The processor creates an entry in a mapping file, which includes at least information regarding the transaction, one or more resource managers to perform activities of the transaction, and the resources managed by the one or more resource managers. In response to detection of a failure of a resource manager of the one or more resource managers, the processor receives a notification from a call-back function of an XA specification switch of the resource manager associated with the failure. The processor identifies an application server process associated with the failure of the resource manager, and sends an event to terminate the application server process associated with the failure of the resource manager.

Growing community of inventors

Bengaluru, India

Gopalakrishnan P