Servlet Container Configuration
A number of container options are available to deploy CAS. The WAR Overlay guide
describes how to build and deploy CAS.
How Do I Choose?
There are is a wide range of servlet containers and servers on the menu. The selection criteria is outlined below:
- Choose a technology that you are most familiar with and have the skills and patience to troubleshoot, tune and scale for the win.
- Choose a technology that does not force your CAS configuration to be tied to any individual
servers/nodes in the cluster, as this will present auto-scaling issues and manual effort.
- Choose a technology that works well with your network and firewall configuration and is performant and reliable enough based on your network topology.
- Choose a technology that shows promising results under your expected load, having run performance and stress tests.
- Choose a technology that does not depend on outside processes, systems and manual work as much as possible, is self-reliant and self contained.
Production Quality
All servlet containers presented here, embedded or otherwise, aim to be production ready. This means
that CAS ships with useful defaults out of the box that
may be overridden, if necessary and by default, CAS configures everything for you from development to production
in today’s platforms. In terms of their production quality, there is almost no
difference between using an embedded container vs. an external one.
Unless there are specific, technical and reasonable objections, choosing an
embedded servlet container is almost always the better choice.
Actuator Endpoints
The following endpoints are provided:
The following settings and properties are available from the CAS configuration catalog:
The configuration settings listed below are tagged as Required in the CAS configuration metadata. This flag indicates that the presence of the setting may be needed to activate or affect the behavior of the CAS feature and generally should be reviewed, possibly owned and adjusted. If the setting is assigned a default value, you do not need to strictly put the setting in your copy of the configuration, but should review it nonetheless to make sure it matches your deployment expectations.
The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This
flag indicates that the presence of the setting
is not immediately necessary in the end-user CAS configuration, because a default value is assigned or
the activation of the feature is not conditionally controlled by the setting value. You should only include this field in your
configuration if you need to modify the default value.
The following settings and properties are available from the CAS configuration catalog:
The configuration settings listed below are tagged as Required in the CAS configuration metadata. This flag indicates that the presence of the setting may be needed to activate or affect the behavior of the CAS feature and generally should be reviewed, possibly owned and adjusted. If the setting is assigned a default value, you do not need to strictly put the setting in your copy of the configuration, but should review it nonetheless to make sure it matches your deployment expectations.
The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This
flag indicates that the presence of the setting
is not immediately necessary in the end-user CAS configuration, because a default value is assigned or
the activation of the feature is not conditionally controlled by the setting value. You should only include this field in your
configuration if you need to modify the default value.
The following settings and properties are available from the CAS configuration catalog:
The configuration settings listed below are tagged as Required in the CAS configuration metadata. This flag indicates that the presence of the setting may be needed to activate or affect the behavior of the CAS feature and generally should be reviewed, possibly owned and adjusted. If the setting is assigned a default value, you do not need to strictly put the setting in your copy of the configuration, but should review it nonetheless to make sure it matches your deployment expectations.
The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This
flag indicates that the presence of the setting
is not immediately necessary in the end-user CAS configuration, because a default value is assigned or
the activation of the feature is not conditionally controlled by the setting value. You should only include this field in your
configuration if you need to modify the default value.
Embedded
Please see this guide.
External
Please see this guide
Docker
You may also be interested to deploy CAS via Docker.
See this guide for more info.
System Service
CAS can be easily started as Unix/Linux services using either init.d
or systemd
. To learn
more, please visit this guide.