Enterprise Push Server

 

What It Does

In ICEfaces EE, the Enterprise Push Server (EPS) is built to manage single Ajax Push blocking connection(s) with the client browser and share it with any number of deployed ICEfaces applications and portlets, in both stand-alone and clustered deployments. The Enterprise Push Server delivers key additional features targeted at large-scale and high-availability enterprise deployments. Specifically, the Enterprise Push Server:

• Integrates with major open source and commercial application servers to provide high-scalability and fail-over support for clustered Ajax Push-enabled ICEfaces applications.
• Provides distributed management of Push blocking connection to any number of deployed ICEfaces applications and portlets in both a stand-alone and clustered environments.
• Designed to Load-balance for failover of blocking push connections.
• Supports Servlet 3.0 Asynchronous Request Processing (ARP) integration for thread-level scalability.

 

Application Deployments

Enterprise Push Server is required for deploying multiple Ajax Push applications to the same domain. It delivers push server capabilities and key features targeted at enterprise deployments in either stand-alone or cluster deployment environments.

 

Stand-alone Deployments

Enterprise Push Server fully supports stand-alone deployments of any number of ICEfaces applications that are Ajax Push enabled. It manages a single blocking connection per browser instance to one or more ICEfaces applications, while the ICEfaces Ajax Bridge shares that same single blocking connection to EPS with one or more ICEfaces application views. A basic stand-alone deployment utilizes an optional web server and JMS for inter-process communication as illustrated below.

 

 

 

Clustered Deployments

The Enterprise Push Server fully supports clustered deployments of any number of ICEfaces applications that use Ajax Push. Multiple servers coordinate to perform shared management of a single blocking connection per browser instance to one or more ICEfaces applications deployed to multiple nodes within the cluster. A basic clustered deployment utilizes standard web server load balancing with sticky sessions, and JMS for inter-process communication, as illustrated below.

 

 

 

High Availability

The Enterprise Push Server enables high-availability deployments based on session replication and fail over. Each deployed server will automatically follow sessions that migrate between nodes in the cluster. Failover of the Enterprise Push Server itself is also supported, so if one server fails, the sessions being managed there will be automatically redistributed between the other running servers.

 

Application Server Deployment Configuration

Fully-tested and documented deployment configurations are included for all major open source and commercial application servers, including:

Supported stand-alone environments:

• Tomcat 7/8
• JBoss EAP 6.3
• RedHat WildFly 8.2
• Oracle Glassfish v4
• Oracle WebLogic 12c
• IBM WebSphere AS 8.5
• Jetty 9

Supported cluster environments:

• Tomcat 7 / ActiveMQ 5
• Tomcat 8 / ActiveMQ 5
• WebSphere AS 8.5
• WebLogic 12c
• JBoss EAP 6.3

 

Asynchronous Request Processing

Supporting thread-scalable deployments of the Enterprise Push Server is achieved through integration of the Ajax Push mechanism with an ARP implementation. Enterprise Push Server supports the following ARP mechanisms.

ICEfaces EE:

• Servlet 3.0 ARP mechanisms

 

HTTP Server Integration

The Enterprise Push Server supports a range of commercial HTTP servers and connectors for clustered load balancing and fail over.

Supported Web servers include:

• Apache http Server 2.2
• IBM HTTP Server 7

Supported HTTP server connectors include:

• mod_proxy and sub modules (e.g. mod_proxy_balancer)
• WebLogic Server’s Web Server Plug-In for Apache HTTP Server 2.2
• WebSphere Application Server’s Plug-In for IBM HTTP Server 7