Install guide

• Apache administrator’s email: this email address is used in error messages when
Apache has internal errors. Specify the system administrator’s email.
• Company email suffix: the part of your company email addresses following the @
symbol, e.g. shell.com
• Data administrator’s email: a comma-separated list of email addresses for the data
administrators, to whom error form output will be sent. The forms will only work if email
is configured to work internally – see the Notes on WOW email
section.
• SMTP mail server: address of the mail server used for outgoing SMTP email. This
can usually be found by typing nslookup mailhost, e.g. mailhost.shell.com.
If not present it will default to host name.
• Security level (B or C): Level B provides universal read without authentication, but
authenticates any write actions. Level C authenticates all access. See the Security
section for more detail.
• Parent directory for WebApps exports: enter a parent directory for WOW to use for
subscription output, exported shapefiles, geo-referenced images, ZGFs, LAS files etc.
• Review: check the options specified; and re-run if there are any errors.
Important note: the OpenWorks configuration directory setting $
OW_CONF_DIR will be
included automatically in the wow.env file, if set within the environment of the installer.
During this stage the $OWHOME/WebApps/conf/wow.env file is created containing all
the variables required by WOW. This is the single most important configuration file for
WOW; see Appendix 1 for an example and Appendix 2
for a list of all configuration files.
During this stage the installation script also modifies environmental variables and URLs in
the WOW tree, and creates links for various devkit shell utilities. See Appendix 5
for further
background on the devkit shells.
Stage 2 – Apache Configuration
Important note: see Appendix 4
for non-default installation options, including bypassing
this Apache configuration step, i.e. if wanting to use an existing Apache server.
The installation of Apache must be run as root. This step configures the main Apache
configuration file httpd.conf, then creates a ‘root.sh’ file for execution as root in a
separate xterm. The selected system may not already running Apache and the default port
of 80 must be available.
The root.sh script does the following:
• Copies httpd.conf into the Apache configuration directory /etc/httpd/conf.
• Starts Apache
WOW 5000.0.1.11 Release Notes Page 18 of 104 March 2014