APL LB Monitor is used to monitor the availability of either a Remedy AR System server or a Remedy Mid-Tier instance. Use this tool in conjunction with a load balancer’s health check feature to route traffic to responsive servers.
Monitoring just a Remedy server’s TCP port or the Mid-Tier’s web server port is an indication that a process is allowing TCP connections however such a connection does not ensure that the system is responsive in a way that is useful to users or integrated systems. Many Remedy admins have experienced situations where the Remedy server is up and technically running but is “hung” and not processing responses to connected clients, often leading to timeout errors. APL Load Balancer Monitor (APL LBM) goes beyond just a process allowing TCP connections and “works” the Remedy server to make sure the system is in a useful state.
2.0 – November 24th, 2020
- The tool has been updated to be able to be run with the Apache RunProc wrapper instead of previous capability
- Capability was added to allow for notification when the port is taken up or down
1.3 – January 26th, 2019
- Updated the code, documentation and config to allow for a user on Linux to start the tool in the way they want
- Modified the default logging in the config.properties to not log AR Exceptions to the log as they are already being handled in the code
- Put it so that the JAR doesn’t bundle the api again so that the api version can be managed independently of the tool version
1.2 – December 15th, 2018
- Converted to using Log4J services so that people not using the wrapper have the ability to configure the size/max number of log files
1.1 – June 12th, 2017
- Fixed problem with the services inability to find the config file
1.0 – June 10th, 2017
- Initial Release