# Disclaimer: 
# This information are provided "AS IS" without warranty of any kind, either expressed or implied. 
# The entire risk arising out of the use or performance of the script and documentation remains with you. 
# Furthermore, Worldline or the author shall not be liable for any damages you may sustain by using this information, 
# whether direct, indirect, special, incidental or consequential, including, without limitation, damages for loss of business profits,
# business interruption, loss of business information or other pecuniary loss even if it has been advised of the possibility of such damages.
# Read all the implementation and usage notes thoroughly.


The following lists boom Utility examples suitable for boom Server running on Linux (Red Hat 8.x) exclusively. 

Divided up into these categories:
- boom Action based
	boomAGTSTAT (supplies boom agent status details displayed self-explanatory: "Version... Started... PID..., etc., TotalReceivedIndications..., etc.")

- boom REST API based (Note: requires usage related SSL configuration)
	boomSRVSTAT (supplies boom server status details displayed self-explanatory: "Active... Closed... FreeMemPct... #Top 10 Agents ... #Top 10 Policies ...")
	boomINDISEXP (export all attributes of filtered boom indications into comma separated output file)
	boomINDIGET (supplies all attributes of 1 dedicated boom indication comma separated)
	boomIIDGET (supplies boom's indication ID based on filter terms)

- boom CLI based (Note: requires usage related CLI configuration)
	boomCMD (executes any OS, boom Agent-Action command or script at boom agent system)
	boomUPLD (uploads file to any directory at boom agent system)
	boomDNLD (downloads file from any directory at boom agent system)


I. Providing SSL configuration (needed for hidden SSL password decryption internally):
- semi-automatic proceeding (name and password of any boom's administration user required)
1. execute script boom_prov_enc.sh passing parameters >><boom user> <boom user-password> [<boom server HTTPS-port>]<<

- manually proceeding (name and password of any boom's administration user required)
1. execute whole line beginning with "p=..." of config file boom_env_ssl.cnf inside Shell
2. execute line beginning with "##RHEL 8 ..." starting with "echo <BOOM_USR-password> | openssl ..." inside same Shell
3. open configuration file boom_env_ssl.cnf
4. provide setting of variable >>SRV_URL<<
5. provide setting of variable >>SRV_PORT<<
6. provide setting of variable >>BOOM_USR<<
7. provide setting of variable >>Penc<< enclosed in double quotes with output of step "2."
8. save and exit configuration file boom_env_ssl.cnf


II. Providing CLI configuration (needed for boom Server CLI connection by saved login credentials):
- proceeding in case only /opt/boom/server/srv/cli/boom_cli.cfg does not exist (name and password of a decidated boom administration user required)
1. cd /opt/boom/server/srv/cli
1. java -jar boom_cli.jar -u <user> -p <password> -fs boom_cli.cfg


