Running the Setup Program Separately from Installation
44 PATROL DashBoard User Guide
Running the Setup Program Separately from
Installation
If you need to change the setup parameters at some time after you have installed the
product, you can run the setup program again.
To run the setup script
■ on Windows: From the Windows Start menu, choose Programs => BMC Patrol =>
PATROL DashBoard => PATROL DashBoard Setup
.
■ on Unix: In an X-Window session, navigate to the PATROL DashBoard installation
directory (for example,
/opt/bmc/PATROL_DashBoard), and then issue the following
command:
Setup.sh
The setup script displays the Web Server Parameters window. Follow the instructions
for setup, starting with step 10 on page 32 and proceeding through step 15 on
page 35.
Configuring HTTPS for Your Operational
Environment
The PATROL DashBoard product and the PATROL DashBoard Corporate Edition
module each provide a turnkey HTTPS configuration that you can use for testing and
demonstration purposes. The turnkey configuration embeds a self-signed certificate
that is generated at installation. This self-signed certificate is valid for only 730 days
(2 years). Within that 730-day period, you must configure HTTPS for your
operational environment by following the instructions in this section.
PATROL DashBoard uses Tomcat as its Web server and servlet engine. The Tomcat
software is embedded in the product, installed along with PATROL DashBoard, and
configured by PATROL DashBoard setup. It was developed by the Apache Software
Foundation (http://www.apache.org
).
A keystore is a file where the public/private keypair and the HTTPS certificate are
stored. It is required when the HTTPS port is enabled. The keystore is protected with
a password. The default keystore password is dashboardkeypass, but you will change it
during the procedures described in this section. The keystore password and the
password of the keystore entry named tomcat must be the same.
