A proxy server such as a load balancer may be used with Calem to enforce security policy or to distribute load among Calem application servers. Some configuration changes are necessary for Calem to work with a proxy server.
1. Calem URL by HTTPs
If your proxy server is to terminate SSL and Calem is accessed with plain HTTP, one needs to tell Calem to always use HTTPs by adding the following line to your Calem_Home/server/conf/calem.custom.php.
2. Calem URL by Proxy
Calem uses internally configured URLs sometimes for reports and presentation. One needs to define both URLs to use with the proxy server by adding the following two lines to your calem.custom.php (replace the internal IP and external URL by your service configuratiton).
//Internall URL for report generation $_CALEM_dist['calem_full_uri_np']= 'http://10.211.55.3/index.php'; //External URL for report/image rendering $_CALEM_dist['calem_full_uri']= 'https://acme.calemeam.com/index.php';
3. Health Check
The proxy server should use HTTP "HEAD" request to check the status of Calem. For instance, a proxy server does health check of Calem every 5 seconds by sending an HTTP "HEAD" request to http://192.168.31.235 (replace the IP with that of your own Calem app server).
If HTTP "HEAD" request is not available to do health check and one has to use HTTP "GET" to check Calem, one should use the following URL: http://192.168.31.235/status (replace the IP with that of your own Calem app server).
Doing health check by HTTP "GET" at Calem login URL such as http://192.168.31.235 will cause Calem app server to process the request and is not recommended.
- Add the configuration to your "calem.custom.php" to enable it.
- How to Deploy Calem with High Availability and Performance
- How to Integrate with Calem
- How to Use Deployment Tool to Manage Multiple Calem Services
- How to Customize Access Control and Profiles in Calem
- User Guide and Admin Guide (customer account required)
- Calem Enterprise Training Site
- Calem Enterprise Blogs
- Calem Enterprise demo