Just a second...

Example: Simple solution

This solution uses a firewall to restrict incoming traffic and a load balancer to balance the traffic between multiple Diffusion™ servers.

Figure 1. A simple solution Traffic from external clients comes in from the internet through the firewall. The firewall blocks all traffic apart from that on port 80, it redirects the Diffusion traffic to port 8080. The load balancer balances the incoming traffic between the Diffusion servers available in the demilitarized zone. The Diffusion servers have connectors configured to receive the incoming traffic on port 8080. The connections coming in on this port are authenticated by an authentication handler. Authentication handler can be either local to the server or part of a control client. The authentication at this external-facing port is more strict than at the internal-facing ports. The Diffusion servers in the demilitarized zone have another connector configured on port 9090. This port is used for connections from components inside your network. These components can be the following: browsers accessing the console and internal clients.
  • Client applications can connect to Diffusion from the internet through a firewall.
  • The firewall protects the de-militarized zone (DMZ) from unwanted traffic. It allows connections on port 80 and redirects these connections to port 8080.
  • The load balancer balances the Diffusion connections between all the Diffusion servers in the DMZ . You can also use the load balancer to filter the URL space and to perform Secure Sockets Layer (SSL) offloading.
  • The Diffusion servers receive connections from external clients on port 8080. This port is protected by an authentication handler that performs strict authentication on the incoming connections. Authentication handlers can be local to the server or part of a control client.
  • The Diffusion servers receive connections from internal clients on another port, for example 9090. The authentication controls on this port are less strict because these connections come from within your network. Internal connections can come from any of the following components:
    • Browsers accessing the Diffusion console
    • Internal clients, such as control clients.