12.2.4 Functions not supported in version 11

Application Server version 11 has functions that do not support migration from version 9. With a few exceptions, these functions can be used in V9 compatibility mode.

Organization of this subsection

(1) Non-supported web container functions
(2) Non-supported extended functionality
(3) Non-supported compatibility functionality

(1) Non-supported web container functions

(a) Request distribution by using the round-robin method

The proxy module built into the Web server of Application Server version 11 does not support request distribution (load balancer) by using the round-robin method, which was supported through Web server integration by using the conventional redirector.

To achieve request distribution by using the round-robin method, a load balancer or a Web server that has a load balancer function is separately required.

(b) Request distribution by using the POST data size

The proxy module built into the Web server of Application Server version 11 does not support request distribution by using the POST data size, which was supported through Web server integration by using the conventional redirector.

To achieve request distribution by using the POST data size, a load balancer that has that function or a Web server that has a load balancer function is separately required.

(c) Gateway specification functionality by the J2EE server

The NIO HTTP server of Application Server version 11 does not have the gateway specification functionality, which was provided by the conventional redirector and the in-process HTTP server.

If the URL of a gateway such as a load balancer or an SSL accelerator needs to be returned to the client as the URL to be added to the Location header when the URL is transferred, specify settings to return the URL of the appropriate gateway, for example, by rewriting the Location header by using the function of the load balancer or SSL accelerator.

(d) Error page customization function for each web container

The NIO HTTP server of Application Server version 11 does not have the error page customization function for each web container, which was provided by the conventional redirector and the in-process HTTP server.

If you want to return a user-specific error page corresponding to the error status code as a response, define it for each application by following the Servlet specifications, or configure Web server integration via the reverse proxy function of the Web server to customize the error page by using the Web server functionality.

(e) Function that limits HTTP-enabled methods

The NIO HTTP server of Application Server version 11 does not have the function that limits HTTP-enabled methods, which was provided by the conventional in-process HTTP server.

If you need to limit HTTP-enabled methods, configure Web server integration via the reverse proxy function of the Web server to limit HTTP-enabled methods by using the Web server functionality.

(f) Request distribution functionality that uses the redirector

The NIO HTTP server of Application Server version 11 does not have the request distribution functionality that uses the redirector, which was provided by the conventional in-process HTTP server.

If you need to redirect each URL, configure Web server integration via the reverse proxy function of the Web server to redirect URLs by using the Web server functionality.

To Page Top

(2) Non-supported extended functionality

Application Server version 11 does not support the EADs session failover functionality. This functionality cannot be used even in V9 compatibility mode.

To Page Top

(3) Non-supported compatibility functionality

The following compatibility functionality, which was retained in Application Server version 9 and earlier for compatibility with a previous version, cannot be used in Application Server version 11. The functionality cannot be used even in V9 compatibility mode.

Table 12‒2: Compatibility functionality that is no longer supported in Application Server version 11
Category	Functionality	Alternative functionality
Compatibility functionality	Basic mode	Use the J2EE server.
	Servlet engine mode (Web container server)	Use the J2EE server.
	Simple web server functionality	Use the NIO HTTP server functionality. For details, see the manual uCosminexus Application Server Web Container Functionality Guide.
	Subdirectory exclusive mode for EJB client application logs	Use the default subdirectory shared mode.
	Memory session failover functionality	Use the database session failover functionality. For details, see 6. Database session failover functionality in the uCosminexus Application Server Expansion Guide.
	Switching of multiple built execution environments	None
	Test function for J2EE applications	None
	Check of JSP source compliant with JSP 1.1 and JSP 1.2 specifications (cjjsp2java)	None
	V7 compatibility mode for logical server application management	None
Security management functionality	Inheritance of the login status by using the session failover functionality	Use the database session failover functionality. For details, see 6. Database session failover functionality in the uCosminexus Application Server Expansion Guide.
Command	Commands used by the Management Server (commands for compatibility with previous versions) `cmx_define_application` command `cmx_deploy_application` command `cmx_register_application` command `cmx_start_application` command `cmx_stop_application` command `cmx_undefine_application` command `cmx_undeploy_application` command `cmx_unregister_application` command `cmx_define_resource` command `cmx_deploy_resource` command `cmx_register_resource` command `cmx_start_resource` command `cmx_stop_resource` command `cmx_undefine_resource` command `cmx_undeploy_resource` command `cmx_unregister_resource` command `cmx_add_serverref` command `cmx_delete_serverref` command	Use commands of the J2EE server. For details, see 2. Commands Used with a J2EE Server in the uCosminexus Application Server Command Reference Guide.

To Page Top