Hitachi

uCosminexus Application Server Maintenance and Migration Guide


12.2.1 NIO HTTP server functionality

Application Server version 11 has enhanced support for new functionality that mainly handles the asynchronous processing of web applications, such as asynchronous servlets of Servlet 3.0, asynchronous I/O APIs of Servlet 3.1, and WebSocket 1.0. Accordingly, the Web server integration functionality using the redirector and the in-process HTTP server functionality, which required conventional synchronous processing, were updated, and the NIO HTTP server functionality, which is the in-process HTTP server functionality newly implemented by using Java NIO technology, was installed.

The new functionality of Application Server version 11 requires non-blocking I/O of the NIO HTTP server functionality. For this reason, the conventional redirector functionality and in-process HTTP server functionality cannot be used. Requests to web applications on the J2EE server are unified to use HTTP communication by the NIO HTTP server functionality when going through the Web server or when directly accessing the J2EE server.

For this reason, you need to revise the system design supporting the redirector functionality and the in-process HTTP server functionality to a design supporting the NIO HTTP server.

For details, see 12.4 Migration guide for system design.

Figure 12‒1:  When migrating the Web server integration configuration that uses the redirector to Application Server version 11

[Figure]

Figure 12‒2:  When migrating the in-process HTTP server configuration to Application Server version 11

[Figure]