Page Comparison

The instructions below describe an optional configuration for deploying uPortal.

There are a plethora of reasons why you may need or desire to run Apache HTTP Server in front of uPortal:

• Your single sign on implementation requires use of an apache module (e.g. Pubcookie)
• You wish to load balance multiple instances of Tomcat and don't have existing load balancing technology
• You prefer to offload SSL to Apache HTTP Server

It is important to consider a proper value for the address attribute in the AJP connector described above. If you don't specify the address attribute on a Connector, Tomcat will bind to the default value of 0.0.0.0, which is a special address that translates to ALL bound IP addresses for the host. It is not uncommon to have multiple IP addresses bound to the host running your uPortal/Tomcat instance, and if you don't specify the specific IP address to listen on, you may open up the AJP connector unintentionally on one of those addresses.

A good choice to use for the AJP connector is localhost, 127.0.0.1 as long as you run Apache on the same host you run Tomcat. If you run Apache and Tomcat on separate hosts, an ideal IP address to bind your AJP Connector is one that is on a private network or otherwise behind a firewall that would only allow the separate host running Apache to connect and forbid all others.