boom Administration

Starting and Stopping the boom server

On Unix systems:

The boom server runs as daemon and is managed by the init scripts. To start or stop the server manually, enter the following command:

   /etc/init.d/boom_srv start | stop | status

On Windows systems:

The boom server runs as Windows service and is managed by the service control.

Checking the boom server process

On Unix systems:

To check the boom server process, enter the following command:

   # ps -eo args| grep BOOMSERVER
		    java -DBOOMSERVERPROC -Xmx512M -Dfile.encoding=UTF8
		    -Dsun.net.inetaddr.ttl=300 -Djava.awt.headless=true -jar boom_server.jar
	    

The parameters limit the Java process heap to 512MB memory (Xmx) and restrict the TTL of the Java internal DNS cache to
300 seconds. For production systems the Java heap size should be increased e.g. to 2GB: -Xmx2048MB. The startup parameters can be changed in the </opt/boom/server>/boom_srv startup script.

To check the status of the boom server, enter the following command:

   /etc/init.d/boom_srv status

boom server configuration file

The boom server configuration file contains setup information for the server. The file is located in:

<boom_server_installdir>/boom.props

Configuration parameters:

boom database configuration files

The boom server allows you to configure one single database for fault management and performance data or to configure a separate database only for performance data.

The boom database configuration file db.props contains information which is necessary for the connection to the database. All fault management data are written to this database. The file is located in:

<boom_server_installdir>/db.props

<boom_server_installdir>/db_perf.props

boom server logfiles

Starting and Stopping the boom agent

On Unix systems:

The boom agent runs as a java process and is managed by the init scripts. To start, restart or stop the agent manually, enter the following command:

   /etc/init.d/boom_agt start | restart | stop | status

On Windows systems:

The boom agent runs as Windows service and is managed by the service control.

Checking the boom agent process

On Unix systems:

To check the boom agent process, enter the following command:

   # ps -eo args| grep BOOMAGENT
		    java -DBOOMAGENTPROC -jar boom_agent.jar
	    

To check the status of the boom agent, enter the following command:

   /etc/init.d/boom_agt status

boom agent configuration file

The install script creates the boom agent configuration file automatically. It contains setup information for the agent. The file is located in:

<boom_agent_installdir>/conf/agent.conf

boom agent logfiles

boom agent configuration on cluster nodes (unix/linux)

Cluster nodes might have additional virtual network interfaces and virtual names.

The boom server - agent communication is name based, but also checks the originating IP addresses.

Depending on OS and Cluster software, the communication from agent to server might use a virtual interface, leading to an address update on the server side

Failover might cause confusion in the IP resolution if both cluster nodes are having agents

For cluster nodes set the following flags in the agent.conf

		SHARED_IP=true		#indicates that multiple agents might share one address
		FIXED_IP =true		#skip IP detection on agent and bind connection to the configured address
		FIXED_NAME=true		#skip hostname detection on agent and report configured name to server
		AGENT_HOST=abc.domain.com
		AGENT_IP=10.168.10.199
		CLUSTER_NODES=list of boom servers	#e.g. netage-boo01, netage-boom02, netage-boomvirtual
							all cluster nodes (physical and virtual) to which the 
					  		agent connects
		

boom agents connecting to a clustered boom server environment

boom agents connecting to a boom server which runs in a cluster environment have to set the following parameter in the agent.conf file

		CLUSTER_NODES=list of boom servers	#e.g. netage-boo01, netage-boom02, netage-boomvirtual
							all cluster nodes (physical and virtual) to which the 
					  		agent connects
		

boom agent configuration in a SUN Solaris Global Zone

In a SUN Solaris global zone only the agent PID must be used to control the agent (e.g. stop agent). Please proceed the following steps to configure PID-only agent control:

1. Stop the agent: /etc/init.d/boom_agt stop
2. Set the variable PID_ONLY in the /opt/boom/agent/boom_agt control file:
PID_ONLY=true
3. Start the agent: /etc/init.d/boom_agt

For the GUI administration please see GUI settings