Storix Software SBAdmin Web Interface Installation Guide - Manual (Page 3)

Storix System Backup Administrator 3 Web Interface Installation Guide
Copyright © 2014 Storix, Inc.
Storix is a registered trademark of Storix, Inc in the USA. SBAdmin is a trademark of Storix, Inc in the USA and other countries
Configuring and starting the web server
During the initial installation of the software, you will be asked if you want to configure the SBAdmin Web Interface. If you
choose not to configure the web interface at that time, you can go back at any time and launch the program to configure and
start the web server. You must be logged on as the “root” user to configure and start the web interface. From a terminal on
your Administrator system type “stconfigweb” and answer the questions that follow. This will set the options for the web
server, configure the web server to start automatically on reboot, and start the web server. At the end of the process you will
be given the Uniform Resource Locator (URL) used by your browser to access the web interface.
Here is an overview of the questions that will be asked during the configuration process:
Enter the network port number you would like the SBAdmin webserver to use
[8080] =>
This is the port number the web server will be listening on. We have specified the port 8080 by default as this is an alternate
http port specified by the Internet Corporation for Assigned Names and Numbers (ICANN). When you enter the server
hostname or IP address as part of the URL, you will need to append this port number to the end preceded by a colon. For
example, if your administrator's IP address is 192.168.1.100, the hostname is mickey and you use the default port number of
8080, the URL will be https://mickey:8080 or https://192.168.1.100:8080. If you do not already have a web server running on
the Administrator, you may use the ICANN designated port 443 for https. If you choose port 443, you will not need to append
the port number to the URL of the web server address.
Location of the SSL certificate [/opt/storix/samples/sbaweb.pem] =>
The SBAdmin Web Interface uses Secure Socket Layer (SSL) to ensure the passwords and data are sent securely. SSL
requires the use of a secure certificate. There are two acceptable types of SSL certificates: certificates signed by a
Certificate Authority (CA) and self-signed certificates. We have included a self signed certificate as a default. If you have
your own certificate you would like to use, enter the full path to the .pem file. If you do not have a signed certificate, you can
use the default certificate. NOTE: If you use the self-signed certificate, you will see a warning message from your web
browsers stating that the signing authority is unrecognized. This does not mean the site is unsecured. It is intended to inform
users that the signing authority (Storix,Inc.) is not recognized as an official signing authority.
You may now access the SBAdmin web interface at https://adminhost:8080 , where adminhost is the
hostname of the local administrator system.
Web server customization
After the web server has been configured and started, the following file will contain the settings necessary to run the lighttpd
web server used for the web interface.
/storix/config/sthttpd.conf
(assuming /storix is your data directory)
Settings in this file have been verified for use with the SBAdmin Web Interface. However, you may have a need to change
the configuration of the web server so that it may be used in your environment. Any changes should be applied to the
/storix/config/sthttpd.conf file.
NOTE: This configuration file will be overwritten upon running stconfigweb, but will be retained when updating SBAdmin
software.
NOTE: If you choose to modify these settings it may affect the performance and usability of the SBAdmin web interface.
You may also want to review documentation provided at http://lighttpd.net.
One common customization you may choose to make is to enable is SSL version 2 by adding the following line to the
configuration file:
ssl.use-sslv2 = “enable”
For the settings to take effect, you will need to restart the web server. Depending on the operating system running the web
server you will need to run one of the following commands: