Browse Prior Art Database

High Performance Cross-Process Synchronous EJB Call Disclosure Number: IPCOM000199673D
Publication Date: 2010-Sep-14
Document File: 1 page(s) / 43K

Publishing Venue

The Prior Art Database


Enable low-latency connections to improve performance of local system application server calls from within low-level programming languages. Application processes running outside of the application server process must use a separate web services stack or include a Java Virtual Machine runtime (JVM) and use IIOP in 'local mode' from a Java program, to call an EJB which is deployed in WebSphere Application Server for z/OS.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 99% of the total text.

Page 1 of 1

High Performance Cross-Process Synchronous EJB Call

With the invention summary above, the invention works as follows:

     In an existing or new application an application programmer desires to make a web services call with very low overhead. First step, the EJB must be extended to allow the EJB to receive requests through the optimized pipeline. The EJB will implement an execute() method/routine which accepts a byte array input and returns a byte array output.

Next, the EJB is deployed on the WebSphere Application Server.

     Then, the application environment (program) registers a connection with the target WAS server using a "Register" API. This will establish connection attributes and bind the caller's process (address space) to the target Websphere Application Server group (cell).

Finally, an inbound connection is used with an optimized "Invoke" API call.

     First, This results in the invocation of a "non-address space switch" Program Call, or PC, routine to change the application environment into supervisor/protected state and a non-User memory key and establish the optimized environment in the local process.

     Next, an "address space-switch" PC routine is used to switch to the Websphere server environment's process and route the request into the EJB container where the applications execute() method is driven.

     On return, the execute() method populates the byte array for output and unwinds back to the caller in the external process.


[This page contains 1 picture or other...