Troubleshooting the installation
The following questions may help you resolve problems about installing the BladeLogic Dashboard.
- Which versions of BMC Server Automation support the BladeLogic Dashboard?
- Which versions of BMC BladeLogic Decision Support for Server Automation support the BladeLogic Dashboard?
- Are any environment variables required for installation?
- During installation, a message says, "The NSH Script BSA Dashboard Script/Job BSA Dashboard Job already exists." What does that mean?
- How can I use an existing Tomcat instead of the one bundled in BSA Dashboard.zip?
- Are there any restrictions on using Tomcat?
- After installing, I try to start the dashboard and a message says, "Warning: Unable to start Tomcat. Please run startup.bat from directory ./Tomcat/bin." What does that mean?
- I see warnings when running the configure_dashboard.nsh script. Should I be concerned?
- What do the following messages mean?
- If the report for BMC Decision Support for Server Automation fails to install as part of a normal installation, can I install it manually?
- What happens if the Dashboard NSH Script job throws errors like "ORA-00942: table or view does not exist?"
Which versions of BMC Server Automation support the BladeLogic Dashboard?
BladeLogic Dashboard is compatible with BMC Server Automation version 8.2 and later.
If you are running BMC Server Automation 8.2.x, 8.3.0, or 8.3.1, some additional steps are required to enable the BladeLogic Dashboard. See Getting-started-with-the-BladeLogic-Dashboard for details.
Which versions of BMC BladeLogic Decision Support for Server Automation support the BladeLogic Dashboard?
BladeLogic Dashboard is compatible with BMC BladeLogic Decision Support for Server Automation version 8.2 and later.
What is the footprint of this application?
The size of the extracted zip files is approximately 11 MB.
Are any environment variables required for installation?
The Java Development Kit (JDK) version 1.6 or later must be installed, and the JAVA_HOME environment variable must specify a valid directory. Typically, installing the JDK sets the JAVA_HOME variable. However, if it is not set, run one of the following commands to set the variable:
- (Linux) export JAVA_HOME=<path_to_JDK_directory>
- (Windows) set JAVA_HOME=<path_to_JDK_directory>
During installation, a message says, "The NSH Script BSA Dashboard Script/Job BSA Dashboard Job already exists." What does that mean?
You have probably already installed the dashboard. To perform a fresh installation, delete the BSA Dashboard Script and the BSA Dashboard Job and run the installation again.
How can I use an existing Tomcat instead of the one bundled in BSA Dashboard.zip?
When running the configure_dashboard.nsh script, use the -no_tomcat flag as the first argument. Running the configure_dashboard.nsh script generates a webapp/dashboard folder. Copy the dashboard folder to the webapp directory for the existing tomcat server. Then restart the existing tomcat server.
Are there any restrictions on using Tomcat?
If you are using your own version of Apache Tomcat rather than installing Tomcat with the rest of the dashboard, ensure that you are using Tomcat 6 or 7. Currently version 8 is not supported.
If Tomcat is running as a Windows server, it cannot run as the LocalSystem user. It must be running as a real user, and that user must have write access to the Tomcat\webapps\dashboard folder.
After installing, I try to start the dashboard and a message says, "Warning: Unable to start Tomcat. Please run startup.bat from directory ./Tomcat/bin." What does that mean?
A problem occurred when starting Tomcat. To start Tomcat:
- Cd to ./Tomcat/bin. The /Tomcat directory is in the directory where you extracted the contents of the BSA_Dashboard.zip file or in the installation directory for your existing Tomcat server.
- Run one of the following commands:
- (Linux) startup.sh
- (Windows) startup.bat
I see warnings when running the configure_dashboard.nsh script. Should I be concerned?
When running the configure_dashboard.nsh script, you can ignore the following warnings:
- org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled. - org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
What do the following messages mean?
If you see the following messages, the configure_dashboard.nsh script cannot access the home environment variable for BMC BladeLogic Decision Support for Server Automation. Restart the RSCD agent on the BMC BladeLogic Decision Support for Server Automation server.
- /shared/ConfigurationManagement: Remote host is unknown
- /portal/deployment: Remote host is unknown
- /shared/ConfigurationManagement/libs: Remote host is unknown
If the report for BMC Decision Support for Server Automation fails to install as part of a normal installation, can I install it manually?
Use the following procedure to install the BMC Decision Support for Server Automation report.
- Log onto the BMC Decision Support for Server Automation server.
Copy one of the following files from the location where you installed BladeLogic Dashboard to <BDSSA_location>/bin. <BDSSA_location> is the location where you installed BMC Decision Support for Server Automation.
Version of BMC Server Automation
File to copy
Version 8.5
import_value_dashboard_8_5.nsh
Versions earlier than 8.5
import_value_dashboard.nsh
- Copy value_dashboard.jar from the location where you installed BladeLogic Dashboard to <BDSSA_location>/lib.
- Open a command line and start Network Shell.
- Execute the dashboard.nsh script (either import_value_dashboard_8_5.nsh or import_value_dashboard.nsh).
What happens if the Dashboard NSH Script job throws errors like "ORA-00942: table or view does not exist?"
You might see errors in the Job Run log like java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist for tables like db_size, table_sizing. This indicates the BMC Decision Support for Server Automation data warehouse user was not granted the proper permission when you were configuring the Value Dashboard.