Install guide

Configuring Subscription Tools and Email
The subscription tools allows users to request automatic notification by email in the event
that data are changed or added within a registered area of interest – by specified project,
geographic area or data type.
These tools allow users to establish, view and modify their subscriptions directly through
html forms. A series of cron jobs execute queries, which compose emails providing users
with a list of new/changed data from WOW.
To configure the subscription tools, you need to set up a cron job to run as the Apache
user. A default crontab is configured during installation, with contents in
$OWHOME/WebApps/install/wow_crontab. This can be added manually to other
users using the crontab command:
prompt> setenv EDITOR vi
prompt> crontab -e
0 4 * * 2-6 /your/OWHOME/WebApps/bin/DoAllSubscriptions Daily
0 4 * * 1 /your/OWHOME/WebApps/bin/DoAllSubscriptions Weekly
0 4 1 * * /your/OWHOME/WebApps/bin/DoAllSubscriptions Monthly
OpenWorks subscriptions are stored in the OWSYS schema in table wow_ow_push.
From version 5000.0.0.11, it is possible to execute ad hoc subscriptions which search for
changes over a specified number of days, rather than just daily, weekly or monthly. This
can be executed on the command-line or via cron using DoAdhocSubscription; or
interactively from the Subscriptions window in the WOW browser.
prompt> DoAdhocSubscription
Usage: DoAdhocSubscription owproj ?days? ?email?
?min_lat? ?max_lat? ?min_lon? ?max_lon?
?wells? ?logs? ?picks? ?checkshots?
?leases? ?fields? ?nav? ?seismic? ?horizons? ?faults? ?docs?
prompt> DoAdhocSubscription TEAPOT_DOME 3 [e-mail]
Processing ad hoc subscription request (3 days) for fred on
TEAPOT_DOME
Notes on WOW Email
The subscription module described above, as well as data error forms, requires access to
an SMTP (outgoing) mail server in order to correctly send email to relevant users. Prior to
version 5000.0.0.11 sendmail was also used in places for mail transport; this is no longer
supported.
The mail server is typically identified by a host alias of mailhost, i.e.:
prompt> nslookup mailhost
The mail server must be correctly identified to WebApps in the wow.env file in
$OWHOME/WebApps/conf, e.g.:
# Address of SMTP mail server (usually 'nslookup mailhost')
WOW_MAILSERVER=smtp.oilco.com; export WOW_MAILSERVER
WOW 5000.0.1.11 Release Notes Page 30 of 104 March 2014