A Programming Legacy - http://remedylegacy.com

APLServerGroupFunctions is a client that connects to any Remedy server in your group via Remedy API, collects information on which servers are in the group
which Operations, and which Services are configured to run where, and then displays that information for you so you have a clear picture of who is in the group
and who is currently expected to do what.

This client will connect to 1 Remedy server on the specified TCP Port, it then gets your JMX port from your configuration and makes a connection to all of the
servers in the group via JMX on that port with the names you have each server talking to eachother with.  This means that the tool must be run from any machine
with both your TCP Port and your JMX port (default value is 61500) and must be able to resolve all of the machine names (as they know eachother).  So, depending
on your configuration, that could be your workstation, or might need to be a server in the server group, depending on your firewall configuration.

All command line parameters are optional and can be executed directly with a command line of

java -jar APLServerGroupFunctions.jar

If you don't wish to configure the properties file, or you want to allow for multiple and call each specifically on the command line, here is the full syntax

java -jar APLServerGroupFunctions.jar -x <server> -u <user> [-c <configFile> -p <password> -t tpcPort -v -h]
Required - only required in either config file or command line, but not both
-x:		This is the server to connect to
-u:		User used to connect to the servers
Optional
-c:		Config file to use, if undefined it looks at APLServerGroupFunctions.properties file
-p:		Password of the user being used to connect
-t:		TCPPort to connect to server, uses port mapper if undefined
-o:		File that you want the output to go to.  If undefined, it goes to APLServerGroupFunctions.log
-v:		Ignores all other inputs and provides Application and version information
-h:		Ignores all other inputs and provides this output

Version History
3.0 - April 9 2020
- Converted to using Log4j for logging
- Added an 'Operations' summary
- Added Services (Email Engine and Normalization Engine, as of this writing)
- Added notification for if you have an Operation globally disabled (Admin, Audit, Escalation)
2.0 - September 18 2015
- Added new config setting for output file, and defaulted it to APLServerGroupFunctions.log, if this is changed to blank, and no output file is specified, then the output goes to console
- Determined that the method I was using to determine parsing setup of the servgrp_board contents was flawed.  Did a bit more research and I believe I now have it done properly
- Added some 'config check' to notify you if your Approval Server, CMDB, and Business Rules Engine are not running on their proper server along with the Administration function
1.3 - September 17 2015
- Corrected problem with array index on server versions < 9.x
1.2 - September 17 2015
- Reconfigured the output a bit so that some errors go to the command line, while others go into the output file
1.1 - September 17 2015
- Added ability to pull the same functions from servers other than 9.x servers only
- Added new setting to properties file 'tcpPort'
1.0 - August 20 2015
- Provides what functions are on which server in a server group