Command Center monitoring

The Command Center is a web-based user interface to SA. Use the SA Client to access the Command Center.

SA users connect to the Command Center component through an Apache HTTPS Proxy (installed by the HPE BSA Installer with the Command Center component).

Command Center ports

Monitoring processes for the Command Center

Command Center logs

Command Center ports

The HTTPS Proxy uses port 443 (HTTPS) and port 80 and directs connections to the Command Center component, which uses port 1031 (the Web Services port).

Monitoring processes for the Command Center

On Linux, execute the command on the server running the Command Center component:

# ps -eaf | grep -v grep | grep java | grep occ

Running this command should produce output similar to the following output:

occ  17373  1  6  19:46  ?  00:02:35  /opt/opsware/j2sdk1.4.2_10/bin/

java -server -Xms256m -Xmx384m -XX:NewRatio=3 -Docc.home=/opt/opsware/occ -Docc.cfg.dir=/etc/opt/opsware/occ -Dopsware.deploy.urls=,/opt/opsware/occ/deploy/ -Djboss.server.name=occ -Djboss.server.home.dir=/opt/opsware/occ/occ -Djboss.server.

To monitor the Command Center component, you can also set up an automatic monitoring process to send a URL query (using tools such as Wget) to the Command Center URL. If the Command Center component returns its login page, it indicates that both the Apache HTTPS Proxy and Command Center processes are functioning normally.

Command Center logs

The Command Center does not generate its own logs. The Command Center uses the JBoss server, which writes to the following log files:

/var/log/opsware/occ/server.log*

/var/log/opsware/httpsProxy/*log*

Conditions to monitor in the logs:

java.net.ConnectionException

java.net.SocketException

java.lang.NullPointerException