Professional Documents
Culture Documents
WOW Release Notes
WOW Release Notes
WOW Release Notes
5
Release Notes and Administration Manual
Contents
Introduction ..................................................................................................................................... 2
Major Changes in Version R2003 ................................................................................................. 3
Previous Enhancements and Fixes............................................................................................... 5
Enhancements and Fixes in this Version (R2003.3.1.5)............................................................ 10
Pre-Installation Planning .............................................................................................................. 11
Installation..................................................................................................................................... 13
Configuring Security Options ....................................................................................................... 18
Configuring Multiple OW_PMPATHs .......................................................................................... 21
Configuring Multiple Oracle Instances ........................................................................................ 22
Configuring Subscription Tools and Email.................................................................................. 23
Customizing the WOW Interface................................................................................................. 24
Browsing Unix Directories............................................................................................................ 25
Adding External Links................................................................................................................. 26
OpenWorks QC/QA Queries ....................................................................................................... 27
Changing Default Well Name Display......................................................................................... 28
WOW Documenter....................................................................................................................... 29
Integrating with CDA .................................................................................................................... 33
Referencing External Documents for SeisWorks 2D ................................................................. 35
Creating Live Trace Outlines...................................................................................................... 36
Using ZGF Backdrops.................................................................................................................. 39
Customizing Choice of Color Maps............................................................................................. 40
Customizing the Well, Field and Lease Modules ....................................................................... 41
Customizing the Key Facts Module ........................................................................................... 42
Customizing the Comparison Module......................................................................................... 43
OpenJournal Integration .............................................................................................................. 44
OpenExplorer GIS Integration ..................................................................................................... 45
ArcIMS Integration........................................................................................................................ 47
Viewing CGMs in WOW............................................................................................................... 48
Maintenance and Troubleshooting.............................................................................................. 49
Appendix 1: Typical wow.env File ...............................................................................................50
Appendix 2: Summary of Important Files.................................................................................... 53
Appendix 3: WOW Architecture...................................................................................................57
Appendix 4: Apache Installation Options .................................................................................... 58
Appendix 5: Background on the Devkit Shell lmksh ................................................................. 69
July 2004
Introduction
WOW provides dynamic access to E&P data over the company intranet. The product
addresses one of the biggest challenges facing the E&P business: making the right data
available to business users in time to facilitate decisions. Because subsurface
professionals spend too much time on non-productive data management tasks, WOW
allows users to quickly find, document, manage and QC vital project data:
Find data fast: rapid web-based browsing of projects - great for familiarizing users
with a new project area.
Find data easily: a uniform interface shelters users from the underlying applications,
databases and systems.
Cleanup project data: a raft of functions for managing the underlying data.
OpenWorks
SeisWorks
Z-MAP Plus
GeoProbe
VIP
OpenJournal
SEG-Y files
LAS files
WebApps is the shared architecture and software directory name for the following products: WOW (including GeoProbe
and VIP modules), Corporate Data Archiver (CDA), WOW for Geolog and WOW for GeoFrame.
Page 2 of 71
July 2004
Root is required for part of the install. The installation script builds a root.sh file with
the required Apache configuration commands. Installation cannot be completed
without the execution of this script by root.
The Apache password file, required for WOW security, is now moved to the
/etc/apache directory and also requires root to be updated. This considerably
tightens WOW security.
Since Apache is now started as root, the default HTTP port of 80 can be used, which
in turn means that no port need be specified in WOW URLs.
The actual Apache web root directory, /var/apache/htdocs, is not used by WOW.
Since this directory is owned by root, Landmark has implemented the static parts of
WOW as an alias to a non-root directory under the WOW installation:
<apache>/htdocs becomes <WOW>/htdocs, aliased to /wOW in the browser
(R2003.0 versions) or /wow (R2003.3 versions).
The R98 WOW directory contained a TclApps and an apache directory; it is now a
single flat structure referred to as $WOW_HOME, set to $OWHOME/WOW (R2003.0
versions) or $OWHOME/WebApps (R2003.3 versions).
In general the directory structure of WOW has been modified to look more like any
other Landmark application, with install, conf, bin, templates directories etc.
Page 3 of 71
July 2004
Level B or C security is now turned on by default during installation for the user doing the
install. See the Security section for more detail.
Simplified Installation Script
The WOW installation script $OWHOME/WebApps/install/WOWInstall now takes
command-line arguments as per standard Landmark applications, i.e. WOWInstall o
$OWHOME. The installation has been streamlined to ask fewer questions and complete
more activities, e.g. create Z-MAP Plus and OpenJournal directory links and turn on
security.
Rationalized style sheets / Dynamic framework
These changes will simplify the future enhancement of WOW, and make for a more robust
patch process.
Multiple OW_PMPATHs
The handling of multiple OW_PMPATHs has been made more generic. A simple custom
OW_PMPATH scenario is now the default, rather than CAI.
FlexLM Licensing / Source Code Compilation
R2003 WOW now uses regular FlexLM licensing. The browser simulates continuous
usage using the FlexLM linger function. Licenses are checked back in after 20 minutes of
browser inactivity. As part of this process, all Tcl source code in the procs and cgi-bin
directories is now compiled and is no longer viewable as plain text.
Improved Error Reporting
In the event of a WOW error occurring, the user now has access to the Apache error log
and the WOW environment through a link on the WOW top bar.
Page 4 of 71
July 2004
Page 5 of 71
July 2004
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
GIS: save pictures with world files for use in ArcView GIS
LAS: add LAS viewing module with curve graphs
OpenWorks: option to export multiple curves in LAS format
OpenWorks: compare 2D navigation
OpenWorks: new pick analysis matrix view
OpenWorks: new curve analysis matrix view
OpenWorks: compute and display velocities from time-depth tables
OpenWorks: extend cross-project search to picks by name / interpreter
OpenWorks: add a vertical section view to position log graph
OpenWorks: filter leases by quad/block, class, status, type
OpenWorks: filter wells by log curve name, curve source, pick interpreter
OpenWorks: filter curve comparisons by curve type, picks by interpreter
Push: add WOW documenter data
Version R2003.0.3
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Version R2003.0.3.1
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Page 6 of 71
July 2004
1.
2.
3.
4.
5.
Version R2003.3.1
General configuration changes: the WOW parent directory has been renamed from
wOW to WebApps. In addition, the WOW htdocs directory is now aliased to wow rather
than wOW, and the cgi-bin directory is now bin rather than cgi-bin-wow. The various
devkit shells have been replaced with a single integrated lmksh shell.
WOW R2003.3.1 is a point product release. WOW must be reinstalled.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
OpenWorks: added support for executing WOW QC/QA queries with variables
OpenWorks: editing/documenting of OpenWorks remarks columns in the browser
OpenWorks: module to match wells between projects with different UWI conventions
OpenWorks: add row counts to VC_ and R_ tables
OpenWorks: project comparison will now compare counts for well-related data types
OpenWorks: batch utility to do coordinate transformation on a file (#133205)
OpenWorks: project comparison will warn if CRS is different between projects
OpenExplorer: improved KRS handling with editing of metadata tables in the browser
OpenExplorer/OJ: allow linking of OpenJournal documents to the KRS
SeisWorks: option to save live trace outlines to shapefiles
SeisWorks: changed approach to handling multiple districts using cookies
SeisWorks: seismic info now shows bricking/compression parameters
SeisWorks: 3D horizon info shows horizon file size, owner, create and modify dates
SeisWorks: navigation info now shows project depth unit and datum
SeisWorks: 2D navigation info now shows 2D project total line length
SeisWorks: 2D horizon info now approximates %coverage using line counts
SeisWorks: documenter now defaults 2D horizon file owner from horizon header
SeisWorks: documenter now auto-populates horizon create date
General: Linux port
General: support for viewing CGMs added requires client configuration
General: quick view of DGN files in WOW (excluding text)
1.
2.
3.
4.
5.
Large ZMAP non-grid datasets can now be displayed without memory issues
Fixed error when viewing grids, pictures and datafiles with a '+' in the name
Fixed error when executing a stored OpenWorks query with more than one variable
SeisWorks seismic info no longer opens all volume extents
Fixed ZMAP to ArcView grid converter failure - requires ArcView3 feature (#150909)
Version R2003.3.1.1
1.
2.
3.
4.
5.
6.
Page 7 of 71
July 2004
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
OW: LAS export of selected curves was picking the wrong curves (#152838)
OW: Extra customizable well header attributes (#152389)
OW: Fixed incorrect well_table.dat.default (referenced log_crv_hdr)
OW: Fixed QC/QA query with variables bug where no text value entered
OW: Fixed errors with aperiodic and negative-valued curves (#153874/153880)
SW: Incorrect top navigation bar when viewing 2D master project files (#601453)
SW: Fixed unsupported BulkHrzRename/Delete functions
SW: Fixed inconsistencies and documentation for seis2png/seis2png2 (#154712/4)
SW: Fixed seismic display of 3dvs with a '+' in the name (#156285)
SW: Fixed 2D navigation save to only save specified line, not all (#156280)
SW: Fixed error in locating colormaps where COLOR_SOURCE1=project (#158714)
SW: Can display SEG-Y files > 2Gb, but not file attributes (#156891/153133)
ZM: Don't create .xml files unless user documents the MFD/ZGF (#157845/154350)
AV: Replaced corrupted ArcView extension file wow.avx (#153028)
AV: Changed storage of WOW GIS image backdrops to subdirectory (#157154)
OJ: OpenJournal browser was not detecting R2003 OJ projects
OJ: Fixed errors in OpenJournal search and links (#153134)
Other: Fixed stylesheet errors for Netscape 7
Other: fixed WOWInstall URL display error and permission check (#305984/158689)
Other: Improved WOW left frame cosmetics (#157878)
Version R2003.3.1.2
General integration changes: In this release the integration between WOW and
Corporate Data Archiver (CDA) is significantly improved, as described below.
1. WOW is now a prerequisite for CDA. The CDA web interfaces now check out a WOW
feature, rather than a CDAWEB feature. Clients with CDAWEB licenses will obtain a
WOW license for every CDAWEB license.
2. An Archives option has been added to the WOW left frame which will display the
CDA lite web interface, allowing users to browse archive data alongside live projects.
3. It is now possible to create control files and execute the archive creation from the
WOW OpenWorks and SeisWorks project summary pages, provided the site has a
CDARCHIVER license. This executes the same functions as the Unix archiver GUI
4. Thumbnails generated in a throwaway project called 'Stubs' are reused in the WOW
horizon and seismic documentation pages, simplifying the documentation process.
The large images are reused in the seismic and horizon detail pages.
5. It is now possible to create horizon and seismic lists in WOW, via a paginated GUI
which displays a user-modifiable number of objects at a time. These page views will
also reuse thumbnails from an existing Stubs project.
6. Horizon and seismic list-deletion command-line utilities are provided to delete all
objects in lists created using the above list builders.
7. A GeoProbe Information Manager module has been added, which provides
functionality for browsing, searching, documenting, cleaning up and archiving
GeoProbe project data. The archival component supports rich metadata extraction
both in the Archiver GUI and from within the WOW browser.
8. An ArcGIS .dll has been added, providing substantially the same functionality as the
current WOW ArcView extension. This allows users of ArcGIS to launch WOW/CDA
Page 8 of 71
July 2004
Version R2003.3.1.3
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
Page 9 of 71
July 2004
Version R2003.3.1.4
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Page 10 of 71
July 2004
Pre-Installation Planning
Minimum Requirements
The minimum requirement for the WOW server and for the WOW Documenter is:
Server Hardware: Sun Blade 100 or Pentium PC, 512Mb RAM, 100Mb free disk space
Operating System: Solaris 8 or Redhat Linux 7.2, patches as per R2003
Application Software: OpenWorks R2003.
Please note that WOW is a server-side application. There is no client-side (web browser)
installation or configuration:
Client Hardware: not restricted
Operating System: not restricted
Web Browser: version 5.5 and above of Internet Explorer and Netscape.
We assume the site has an internal network with PCs, installed web browsers, and a
mechanism for domain name lookup as described in point 4 below. See also Appendix 3
for a description of the product architecture.
Other Pre-installation Considerations
Important note: WOW stores SeisWorks project metadata in the OWSYS tablespace. On
R2003 upgrade, be sure to export this information BEFORE shutting down R98 Oracle.
The export and subsequent import in R2003 OWSYS is described in the Customizing
WOW Documenter section.
Before installing, you need to choose or confirm the following:
1. A system on which to run the Apache2server. Apache is a lightweight daemon
process that does not require a particularly powerful server.
2. Apache is usually, but not always, installed with the operating system.
If installed, directory /etc/apache (Solaris) or /etc/httpd (Linux) will exist. To
confirm that Apache is installed, type:
pkginfo | grep Apache
(Solaris)
rpm -qa | grep apache
(Linux)
There should be a number of Apache packages installed. If not found, please request
your System Administrator obtain and install it see Appendix 4 for more details.
Important note: The version of Apache shipped with Solaris lacks recent security
enhancements. Landmark strongly recommends upgrading Solaris Apache - see
Appendix 4 for more details.
3. We assume that Apache is NOT already running on the selected system and that the
default port 80 is available. If Apache is running, i.e. from a previous installation of
WOW, you must stop it before continuing (as root):
cd /etc/apache
(Solaris)
cd /etc/httpd/conf
(Linux)
cp httpd.conf httpd.conf.orig
2
This product includes software developed by the Apache Software Foundation (http://www.apache.org).
Page 11 of 71
July 2004
/usr/apache/bin/apachectl stop
/usr/sbin/apachectl stop
(Solaris)
(Linux)
Page 12 of 71
July 2004
Installation
The latest WOW point product release can be obtained on CD. The CD version is in
Landmark Release Manager (CD Installer) format under the product name WebApps, and
includes the Corporate Data Archiver.
Alternatively, the latest WOW point product release can be obtained from the Landmark ftp
server isite.lgc.com, directory /products/WOW/Releases as a compressed tar
file. Contact your customer support representative for isite login details. The current
patch level is R2003.3.1.5.
The overall installation process consists of installing the latest point product release, then
applying and subsequent patches, as described in this section.
Manual Method
Change directory to the CD install directory and execute the setup script:
cd /cdrom/cdrom0/install
./setup
Enter value for $OWHOME if requested. The Release Manager user interface will
appear. Choose Install for WebApps. Accept the default location of
$OWHOME/WebApps. Click on Start to extract the media.
After files are extracted, continue with the installation script as documented below.
Page 13 of 71
July 2004
WOW server hostname: the name of the system on which Apache will run: see preinstallation considerations. This is referred to as <hostname> hereafter.
WOW server full URL: if DNS is configured this will default successfully, if not, enter
http://<hostname>.
WOW user: defaults to the user name you are using to run the install script: see preinstallation considerations.
WOW users group: the default group of the user running Apache. Confirm the
default.
WOW_HOME: the location where you have extracted the WOW software, by default
$OWHOME/WebApps. Confirm the default value.
OWSYSSID: the default OpenWorks projects ORACLE_SID location in a multiinstance environment, defaults to ORACLE_SID if not set in the environment. Confirm
the default in single instance sites otherwise check with your data administrator.
Administrators email: this email address is used in error messages when Apache
has internal errors. Specify the system administrators email.
Email suffix: the part of your company email following the @, e.g. oilco.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 Unix
email is configured to work internally see the Notes on WOW email section and
check with your system administrator.
Security level: choose level B or C. See the Security section for more detail.
Review: check the options specified; exit and re-run if there are any errors.
Page 14 of 71
July 2004
Starts Apache
Creates an example password file, containing the installation user only (with
username as password) and further configures WOW for level B or C security. See
the Security section for more detail.
Copies the WOW default index.html to the Apache web root directory.
Location(s) for Z-MAP Plus browsing: you will be asked for zero, one or many
directories containing Z-MAP Plus data. If a single location is chosen, it will be linked
to $OWHOME/WebApps/htdocs/zmap_data. If you request multiple locations, these
will be linked into $OWHOME/WebApps/htdocs/zmap_data. In many sites these
data can be quite widely scattered, so WOW provides a convenient grouping
mechanism.
Location(s) for OpenJournal data browsing: you will be asked for zero, one or
many directories containing OpenJournal data. Details as above, using location
$OWHOME/WebApps/htdocs/openjournal_data
Location(s) for OpenExplorer data browsing: you will be asked for zero, one or
many directories containing shapefile data. Details as above, using location
$OWHOME/WebApps/htdocs/openexplorer_data
Location(s) for Other data browsing: you will be asked for zero, one or many
directories containing SEG-Y or LAS data. Details as above, using location
$OWHOME/WebApps/htdocs/other_data
Page 15 of 71
July 2004
A message will indicate complete installation. Try the final URL in the browser, i.e.
http://<hostname>.<domainname>. Once the license is installed (see next section)
WOW should be fully functional. See the Troubleshooting section if errors are
encountered.
At this point an option is provided to continue with Corporate Data Archiver installation.
See the CDA release notes for further details.
Notes on KRS Implementation
OpenExplorer knowledge reference system (KRS) documents can be loaded and viewed
through WOW. The (manual) steps described below are applicable if you use the KRS:
Name and value of KRS variable: KRS documents can be stored relative to an
environmental variable, which helps sharing documents between Unix and PC
filesystems. In $OWHOME/WebApps/conf/wow.env, specify the name of a KRS
environmental variable and its value, e.g. KRSDATA with value /data/krsdocs.
Location(s) for general links: for the KRS and in general it is often useful to allow
your Unix data disks to be viewed as part of the WOW system. Directories specified
(e.g. /data or /interp) can be linked into the web root /var/apache/htdocs.
This operation must be performed as root. NEVER use / as this is a security risk.
Page 16 of 71
July 2004
Patch history:
R2003.0.1.0 foundation release (April 2002)
R2003.0.1.1 patch, requires R2003.0.1 (May 2002)
R2003.0.2.0 point product release, includes R2003.0.1.1 (Jun 2002)
R2003.0.3.0 point product release, requires R2003.0.2 (July 2002)
R2003.0.3.1 patch release, requires R2003.0.3 (Oct 2002)
R2003.3.1.0 point product release, includes all previous versions (Jan 2003)
R2003.3.1.1 patch release, requires R2003.3.1.0 (May 2003)
R2003.3.1.2 patch release, includes R2003.3.1.0 (Aug 2003)
R2003.3.1.3 patch release, includes R2003.3.1.x (Dec 2003)
R2003.3.1.4 patch release, includes R2003.3.1.x (Apr 2004)
R2003.3.1.5 patch release, includes R2003.3.1.x (Jul 2004)
Page 17 of 71
July 2004
Page 18 of 71
July 2004
name or comment. Modifying this requires a degree of SQL knowledge; please contact
support if in doubt.
SeisWorks: the $OWHOME/WebApps/conf/restricted_plist.dat file lists the
names of any tight SeisWorks projects. They will appear in listings but will not be further
accessible.
Z-MAP Plus/OpenJournal: the
$OWHOME/WebApps/conf/restricted_dir_list.dat file lists the names of
any tight Unix directories. These will appear in listings but will not be further accessible.
The file already contains the main operating system directories such as / /usr /etc
/bin etc. It should also contain the web root, to prevent server-side browsing of restricted
directories.
Adding Users to the Apache Password File
Adding users requires root access for permission to edit files in /etc/apache.
Updating the password file from an existing source. A default password file is created
during installation with only the install user added. The format for the password file is
identical to that of a Solaris passwd file, except that only the first two fields (user and
encrypted password) are used. Apache uses the same crypt function as Unix, so one
method of adding users is:
ypcat passwd > /etc/apache/.wp
(Solaris)
ypcat passwd > /etc/httpd/conf/.wp
(Linux)
If you use this method, you should edit the file and delete users based on various criteria
such as group membership etc. Note that it is not considered secure to use the actual
/etc/passwd file itself.
For additional security, the password file name and location can be changed, and made
readable by the Apache server user only.
Updating the password file manually. You can also add new users manually using the
htpasswd facility, e.g. to add user demo, passwd demo:
/usr/apache/bin/htpasswd b /etc/apache/.wp demo demo
(Solaris)
/usr/bin/htpasswd b /etc/httpd/conf/.wp demo demo
(Linux)
Use the additional c flag when creating a new passwd file, or help for complete usage.
Important note: it is the site's responsibility to keep the password file up-to-date, e.g. by
scheduling a cron job to refresh it at regular intervals. If you uses NIS, it is possible to
authenticate directly using an optional Apache module - see Appendix 4 for details.
Changing Security Level between B and C
1. Modify the .htaccess file: Edit the $OWHOME/WebApps/cgi-bin/.htaccess file.
For level C security, comment the <FilesMatch></FilesMatch> lines. For level B
security, uncomment the <FilesMatch></FilesMatch> lines.
cd $OWHOME/WebApps/cgi-bin
vi .htaccess
# For level C security comment <FilesMatch></FilesMatch>
WOW R2003.3.1.5 Release Notes
Page 19 of 71
July 2004
#<FilesMatch (input|delete)\.cgi$>
AuthType basic
AuthName "WOW Unix" (a descriptive name for the authorization form)
AuthUserFile "/etc/apache/.wp"
Require valid-user
#</FilesMatch>
# For level B security uncomment <FilesMatch></FilesMatch>
<FilesMatch (input|delete)\.cgi$>
AuthType basic
AuthName "WOW Unix" (a descriptive name for the authorization form)
AuthUserFile "/etc/apache/.wp"
Require valid-user
</FilesMatch>
2. Update wow.env:
vi $OWHOME/WebApps/conf/wow.env and change SECURITY_LEVEL to B or C.
Protecting Static Documents
The WOW security model is largely aimed at preventing access to dynamic pages created
on the fly in WOW. This section explains how to protect certain static documents, e.g. an
OpenJournal project, which requires selective security. The restricted dir list mechanism
described for level 2 security provides blanket protection for certain directories, but even
legitimate users cannot get to these directories.
One possibility is to set up a custom .htaccess and password file for the specified
directory. Apache will then authenticate all access to static files in that directory. Notes that
this will have no effect on WOW dynamic pages, e.g. ZMAP browsing. To implement this:
1. Create a password file. Use the htpasswd utility to create a passwd file. The
example below creates a file called ojpasswd with user tight, passwd oj2001:
htpasswd bc /etc/apache/.ojpasswd tight oj2001
2. Create an .htaccess file. Create a file with contents as listed below:
AuthType basic
AuthName "Tight OJ Projects"
AuthUserFile "/etc/apache/.ojpasswd"
Require valid-user
3. Copy .htaccess to the required directory. Place the file into all directories that
require the same security policy.
4. Configure Apache to recognize the .htaccess file:
vi /etc/apache/httpd.conf
(Solaris)
vi /etc/httpd/conf/httpd.conf
(Linux)
Change AllowOverride from None to AuthConfig within the <Directory />
stanza (approx. line 390).
5. Restart Apache:
/usr/apache/bin/apachectl restart
/usr/sbin/apachectl restart
WOW R2003.3.1.5 Release Notes
Page 20 of 71
(Solaris)
(Linux)
July 2004
Alternatively, the WOW Apache owner can configure this file through the browser by
clicking on Admin on the WOW top bar.
Note the dependency on wow_distlist.dat (described in the next section).
All SeisWorks projects in a district must belong to the same Oracle instance.
Once configured, the district is set on a per-client basis by clicking on Change District/SID
on the WOW top bar. This sets a cookie that stores the instance name locally and
remembers it until changed by any user on the same client. This option will also change
the SID to match that required for the chosen district.
It is also important to set a valid default OW_PMPATH in the wow.env file in
$OWHOME/WebApps/conf - typically $OWHOME/conf.
Page 21 of 71
July 2004
Alternatively, the WOW Apache owner can configure this file through the browser by
clicking on Admin on the WOW top bar.
Once configured, the instance is set on a per-client basis by clicking on Change
District/SID on the WOW top bar. This sets a cookie that stores the instance name locally
and remembers it until changed by any user on the same client.
Alternative Options
Before configuring WOW for multiple instances, note that WOW supports without
configuration the specific cases where OpenExplorer Advanced Project Management
(APM) is configured, or where the remote project facility is used. Under these
circumstances the OWSYS tablespaces are either replicated by Oracle or manually.
WOW may run against either of the instances, and projects from the other will be visible
and can be accessed.
Note also that the following are also possible:
Install an Apache server per Oracle instance. Although this sounds inefficient, Apache
is a considerably lighter process than Oracle and does not add much overhead.
Page 22 of 71
July 2004
Page 23 of 71
July 2004
Alternatively, the WOW Apache owner can configure this file through the browser by
clicking on Admin on the WOW top bar.
Page 24 of 71
July 2004
files that are universally recognized by Web browsers, e.g. with extensions of .html,
.tif, .gif, .jpg etc. These are referred to as mime types.
If there are ASCII file types (e.g. .vel for velocity surveys) which you would like to be able
to view through WOW, then do the following:
cd $OWHOME/WebApps/conf
cp ascii_file_extensions.dat.default ascii_file_extensions.dat
vi ascii_file_extensions.dat
And add in file extensions as indicated.
A similar approach can be adopted for common mime types using the file
$OWHOME/WebApps/conf/web_file_extensions.dat.
Alternatively, the WOW Apache owner can configure these files through the browser by
clicking on Admin on the WOW top bar.
Important note: WOW is a server-side application, i.e. files are processed on the web
server and results (html or images) sent to the Web browser. This is the only way in which
files like MFDs, ZGFs, seismic and horizons can be displayed. Standard mime types
behave differently: they are supported directly by the browser and are therefore
downloaded and processed locally. This requires that files be addressable via a URL, i.e.
they must reside below the Web root. See Finalizing the Install for how to achieve this.
Exposing additional directories
The Z-MAP Plus, OpenJournal, OpenExplorer and Other Data modules run the same fileand directory-parsing function, which looks for a specific hard-coded start directory:
Z-MAP Plus: $OWHOME/WebApps/htdocs/zmap_data
OpenJournal: $OWHOME/WebApps/htdocs/openjournal_data
OpenExplorer: $OWHOME/WebApps/htdocs/openexplorer_data
Other Data: $OWHOME/WebApps/htdocs/other_data
If there is an obvious single start point for a data type, e.g. /oe_gisdat2 for
OpenExplorer, simply create a link to this location, e.g.
ln s /oe_gisdat2 $OWHOME/WebApps/htdocs/openexplorer_data
If there are multiple candidates, create the parent directory and then create links inside this
location to the multiple start directories, e.g.
mkdir $OWHOME/WebApps/htdocs/other_data
ln s /data/misc/vendors/segyfiles
Page 25 of 71
July 2004
$OWHOME/WebApps/htdocs/other_data
ln s /export/home/fred/lasdata $OWHOME/WebApps/htdocs/other_data
By simply creating and deleting links to data, directories may be exposed or hidden
rapidly. If the parent directory or link does not exist, an error message will be returned.
###############################################################################
# This file contains metadata for the other sources (links) page in WOW
# It consists of the following pipe-delimited fields:
#
Name: short name for the link
#
Description: longer descriptive name (up to approximately 255 chars)
#
URL: fully-specified URL, e.g. http://www.lgc.com
#
Logo (optional): name of logo image (place in $OWHOME/WebApps/htdocs/logos)
#
Category (optional, not yet supported): type of link, e.g. info vendor
#
# Do not edit the line below
Name Description URL Logo Category
#
# The Tag line allows html tags to be passed, e.g. uniform image height.
# Comment this line to allow images to display at their default sizes
Tag height=50
###############################################################################
CDA UK seismic and well data http://www.cdal.com cda_logo.jpg
DEAL Index of UKCS geotechnical data http://www.ukdeal.co.uk deal_logo.jpg
LIFT Promoting asset opportunities http://www.uklift.co.uk lift_logo.gif
DTI Released UK well/license/prod data http://www.og.dti.gov.uk dti_logo.gif
IndigoPool.com E-business portal for O&G http://www.indigopool.com ip_logo.gif
Landmark E&P software vendor http://www.lgc.com lmk_logo.gif
Alternatively, the WOW Apache owner can configure this file through the browser by
clicking on Admin on the WOW top bar.
Page 26 of 71
July 2004
The first line must contain REM title: this is displayed as the title in the browser.
The second line must contain REM dtype: this tells the browser what to create
the hyperlink to. Currently well, field, lease and seis (navigation) data types are
supported. Set dtype to some other value if not a simple well, field or lease query.
Page 27 of 71
July 2004
The first attribute selected must be the primary key for that data type, i.e. well_id,
field_id or lease_id. This first attribute then appears as a hypertext link in the browser.
To turn off this behavior, set dtype to some other value.
The advantage of this format is that files can be created and tested in standard SQL*Plus
the REM lines are treated as remarks and ignored, and the final / is the standard SQL
terminator. If a query parses and executes in SQL*Plus, it will execute in the browser.
An example QC/QA query is provided below:
REM title: Wells with 0 or null total depth
REM dtype: well
select
well_id ID,
well_uwi "UWI",
well_name_free "Common Well Name",
final_td "TD"
from
well_master
where
final_td is null
or
final_td = 0
order by
well_name_free
/
Page 28 of 71
July 2004
WOW Documenter
Running WOW Documenter
The WOW Documenter allows the user to store extra information about SeisWorks
interpretations. It provides a spreadsheet-style, multi-object interface to the same
functionality within the WOW Web interface. The WOW Documenter requires the user
have at least l_interp access to the associated OpenWorks project.
SeisWorks R2003.12 and above have adopted the WOW Documenter model. Use of the
WOW Unix GUI will therefore be phased out in a future release.
To run the WOW Documenter (kdoc):
prompt> source $OWHOME/WebApps/templates/dotlogin
prompt> kdoc
Alternatively, you can type the full path to the kdoc script, i.e.
prompt> $OWHOME/WebApps/bin/kdoc
For the R2003 version, kdoc is also a link in $OWHOME/bin, i.e. it can be run from any
OpenWorks xterm simply by typing kdoc. A sample launcher.dat entry is also
provided in $OWHOME/WebApps/templates/launcher.dat.extra.
The graphical user interface is illustrated below:
Page 29 of 71
July 2004
Many of the standard lists of values (LOVs) that appear in pop-up menus or list boxes
can be modified.
Modifying LOVs
The table below summarizes the LOVs under site control. Not all LOVs are editable, e.g.
lists of seismic, mapping and horizon files are determined in real time. These lists can be
modified by clicking on the modify lists of values link on each SeisWorks project summary
page. Note that changes made in this manner apply to the OpenWorks project with which
this SeisWorks project is associated and hence to all associated SeisWorks projects.
LOV name
Schema.Table.Key
Defaults
status
project.pimr_status.hrz_flt_status
hrzclass
project.pimr_hrz_class.hrz_class
polarity
project.pimr_polarity.polarity
phase
project.pimr_phase.phase
seisclass
project.pimr_seis_class.seis_class
application
project.pimr_application.application
interpstatus
owsys.pimr_interp_status.interp_status
pcompany
owsys.pimr_company.company
...
Optionally, three lmksh functions are provided to manage these LOVs. See Appendix 5
for further background on using the lmksh shell.
1. GetLOV <swproj> <lovtype>: returns a list of LOVs for the specified SeisWorks
project and LOV type
2. InsertIntoLOV <swproj> <lovtype> <value>: inserts a new value into the
LOV for the specified SeisWorks project LOV type
Page 30 of 71
July 2004
UK Normal
UK Reverse
SEG normal
SEG reverse
Changes are made to existing extensions. To modify the lists at the point at which the
datamodel extension is first created, you need to modify the file
create_pim_project_extension_custom.sql in
$OWHOME/WebApps/kdoc/sqlscripts. This requires SQL knowledge contact your
data administrator if in any doubt.
Modifying Column Titles
The labels given to each Documenter attribute are controlled by metadata stored in Oracle
column comments, and may be modified. Once the datamodel extension is created,
modification involves editing the appropriate SQL file then running the appropriate lmksh
function. For example, to change the project tab Quad/Block title to Area:
prompt> cd $OWHOME/WebApps/kdoc/sqlscripts
prompt> vi update_pim_owsys_comments.sql
- replace the string Quad/Block with Area
- save and exit
prompt> lmksh
lmksh{1}% UpdateOwsysExtension
For horizons and seismic edit update_pim_project_comments.sql and run the
lmksh function UpdateProjectExtension. To ensure consistency between existing
projects and those yet to be created, it is important to make the same changes in
create_pim_project_extension.sql. See the README in
$OWHOME/WebApps/kdoc/sqlscripts.
Removing the Documenter Tables
Internal lmksh procedures are provided should it be necessary to remove the WOW
Documenter tables within each project:
lmksh{1}% RemoveProjectExtension <owproj> (repeat for each project)
lmksh{2}% RemoveOwsysExtension
Page 31 of 71
July 2004
Page 32 of 71
July 2004
Thumbnails generated in the 'Stubs' projects will also appear in the horizon and seismic
documentation pages in WOW, making the process considerable easier.
WOW R2003.3.1.5 Release Notes
Page 33 of 71
July 2004
List-based Deletion
Command-line scripts are provided to delete lists of horizons and seismic created using
the WOW page view list builders.
Important note: these routines are inherently destructive. Make sure you have a current
project backup before executing.
To configure batch deletion scripts (one-off operation):
cd $OWHOME/WebApps/bin
ln s lmksh_wrapper HrzListDelete
ln s lmksh_wrapper SeisListDelete
To execute the deletion:
HrzListDelete <project> <listname>
SeisListDelete <project> <listname>
Page 34 of 71
July 2004
The file <masterproject>.docs can be generated via simple Unix commands and
then edited to add in the text references as appropriate, e.g.
ls *01.2v2_glb > <masterproject>.docs
Blank lines, lines beginning with # and lines with only one entry are safely skipped.
If the <masterproject>.docs file exists, the SeisWorks 2D seismic line selection page
will allow launching of the relevant line directly. The option to view the associated text file is
provided as a link below the seismic header table.
Page 35 of 71
July 2004
Zero-valued traces (real traces with zeros, as distinct from absent or null traces)
The algorithm therefore produces reasonable outlines in the majority of cases, but will not
always succeed.
Customizing the Algorithm
WOW aims to dynamically create Web pages or images on the fly, i.e. without resorting to
static, pre-created files. Seismic trace outlines present a real challenge in this regard. 3D
volumes containing many millions or traces may not complete within the patience
threshold of a typical user.
A batch mechanism is therefore provided to auto-generate the live trace outlines as png
images, ESRI shapefiles (3D only), ASCII coordinate files (3D only) or ZGF pictures (3D
only). Pre-generated png images in the project system directory will display by default in
WOW.
Options are provided to generate outlines in these formats for a single volume, all volumes
within a project or for all projects. These functions can be run within lmksh or linked to
lmksh_wrapper and run in an xterm, as described in Appendix 5.
To generate a single outline for 2D or 3D: use the lmksh proc seis2png, e.g.
lmksh{1}%
lmksh{2}%
lmksh{3}%
lmksh{4}%
outline
SeisSetUp
seis2png devnor 3 mig0801.3dv 25 15 50 50 800 40 tmp.png
seis2png devnor 3 mig0801.3dv 25 15 50 50 800 40 tmp.shp
seis2png devnor 3 mig0801.3dv 25 15 50 50 800 40 none tmp.zgf
Note that the output file extension determines the output type. Note also the different
syntax for ZGF file output. See the next section for a simpler mechanism for generating
outlines over all volumes in a project.
Page 36 of 71
July 2004
Arguments are:
<proj>
<2/3>
<seismic>
<stride>
<delta>
<lineinc>
<traceinc>
<xsize>
<padding>
<outfile>
An alternative 3D-only algorithm that does read every trace is currently under
development. Although it is considerably slower, it can handle internal holes within the
survey, non-contiguous pieces of seismic data, and decimated surveys. To test this
algorithm, use the lmksh proc seis2png2, with same arguments as seis2png:
lmksh{1}% seis2png2 devnor 3 mig0801.3dv 0 2 50 50 800 40 tmp.png
Generating Outlines for all Volumes in a Project
To generate outlines for all volumes for a project, use Do2DSeismaps or
Do3DSeismaps. This includes a clobber argument (3D only), allowing you to regenerate
all images (clobber) or only regenerate if the seismic has been modified since the last live
trace outline was created (noclobber). Note that an output file name need not be specified
as the png, ascii or zgf file is placed in the project sys directory with the following naming
convention:
png image: <sysdir>/<swproj>/<swproj>.<seismic>.png
ASCII file: <sysdir>/<swproj>/<swproj>.<seismic>.asc
ZGF file: <owprojdata>/<owproj>/<swproj>_outlines.zgf
(Each seismic volume produces a single picture within the ZGF file.)
Shapefile: <sysdir>/<proj>/<swproj>_outlines.shp
(Each seismic volume produces a single shape within the shapefile.)
Do2DSeismaps arguments are:
<proj>
SeisWorks project name
<traceinc> trace increment for symbol posting (default 100)
<xsize>
approximate image size, in pixels (default 500).
Page 37 of 71
July 2004
The utility takes as input a columnar ASCII file and computes/inserts latitude and longitude
for the specified column IDs containing the X and Y coordinates. The CRS information is
taken from the specified OpenWorks project. You will need to delete or insert a # before
any header lines in the ASCII line. The reverse ConvertFileLLtoXY can also be used.
Page 38 of 71
July 2004
Page 39 of 71
July 2004
The choice of which color maps to use can be modified for the installation in the wow.env
file, by adding COLOR_SOURCE1 and COLOR_SOURCE2 environmental variables, e.g.:
cd $OWHOME/WebApps/conf
vi wow.env
add line: COLOR_SOURCE1=PROJECT; export COLOR_SOURCE1
add line: COLOR_SOURCE2=DEFAULT; export COLOR_SOURCE2
COLOR_SOURCE1 applies to SeisWorks and has 3 options:
DEFAULT: a short hardcoded list. For horizons, the list is: rspectrum spectrum dipazim
blkwht whtblk. For seismic, the list is: blkwht whtblk blkwhtrd blkwhyel bluwhtbn
bluwhtrd grnwhtbn segfreq segphase segpolar segstg.
COLOR_SOURCE2 applies to SEG-Y, OpenWorks and Z-MAP Plus and has options of
DEFAULT or DIRECTORY as described above.
The recommended setting is DEFAULT as this produces the shortest selection lists and
therefore simpler user interfaces.
Page 40 of 71
July 2004
Similar configuration files are used to control the labels and multi-object display properties
for wells, fields and basins. These cannot be edited at present through the browser.
$OWHOME/WebApps/conf/well_tables.dat:
document null YES Documents YES n/a
keyfact null YES "Key Facts" YES n/a
Picks pick NO Picks n/a YES
Curves log_crv_hdr YES Curves n/a YES
Time-Depths time_depth_curve YES "Time Depths" n/a YES
Dir-Surveys dir_survey_hdr YES "Dir Surveys" n/a YES
Posn-Logs positional_log_hdr YES "Posn Logs" n/a YES
Synthetics synthetic_seismic YES Synthetics n/a NO
Lithology computed_lithology_hdr YES Lithology n/a NO
Casing casing NO Casing n/a NO
Cores well_core NO Cores n/a NO
Shows intrp_drilg_show NO Shows n/a NO
Tests well_test NO Tests n/a NO
Dipmeter dipmeter NO Dipmeter n/a NO
Paleo paleo NO Paleo n/a NO
Zone-Attributes strat_unit_intrp NO "Zone Attributes" n/a NO
Plugging plugging NO Plugging n/a NO
DST-RFTs dst_rft_gen NO "DST RFTs" n/a NO
Interests well_interest NO Interests n/a NO
Dates well_date NO Dates n/a NO
Alt-UWIs well_uwi_alt NO "Alt UWIs" n/a NO
Well-Study well_study NO "Well Study" n/a NO
Note-Pad well_note_pad NO "Note Pad" n/a NO
Remarks well_remark NO "Remarks" n/a NO
$OWHOME/WebApps/conf/field_tables.dat:
document null YES Documents YES n/a
keyfact null YES "Key Facts" YES n/a
interest field_prospect_interest NO Interests n/a YES
Page 41 of 71
July 2004
$OWHOME/WebApps/conf/field_keyfacts:
COL01
COL02
COL03
COL04
COL05
COL06
COL07
COL08
COL09
COL10
"Exp/Appraisal History" N 1
"Geology" N 2
"Geophysics" N 3
"Reservoir Engineering" N 4
"Facilities" N 5
"Economics" N 6
"Development Plans" N 7
"Data Availability" N 8
"Scout Info" N 9
"Other Comments" N 10
$OWHOME/WebApps/conf/lease_keyfacts:
COL01
COL02
COL03
COL04
COL05
COL06
COL07
COL08
COL09
COL10
"Exploration History" N 1
"License History" N 2
"Geology" N 3
"Geophysics" N 4
"Structure" N 5
"Plays" N 6
"Seismic" N 7
"Data Availability" N 8
"Scout Info" N 9
"Other Comments" N 10
$OWHOME/WebApps/conf/basin_keyfacts:
COL01
COL02
COL03
COL04
COL05
COL06
COL07
COL08
COL09
COL10
"Exploration History" N 1
"Play Summary" N 2
"Stratigraphy" N 3
"Reservoir" N 4
"Source" N 5
"Seal" N 6
"Structure" N 7
"Timing" N 8
"Scout Info" N 9
"Other Comments" N 10
Page 42 of 71
July 2004
Page 43 of 71
July 2004
OpenJournal Integration
Publishing OpenJournals
The Publish form in WOW is designed to allow the automatic sharing of OpenJournal
projects in a two-tier system of working vs. published OpenJournal projects. Rather than
copying the published OpenJournals to a new location, the publication takes place in situ
by creating a .auto_publish file in the project directory.
When the user clicks on the OpenJournal link, then View published OpenJournals, this
will automatically search the OpenJournal project tree and build a table of published
projects whenever it encounters the .auto_publish file. Note that this search starts in
the OpenJournal project directory, $OWHOME/WebApps/htdocs/openjournal_data,
within which are links to all parent directories of OpenJournal projects.
The .auto_publish file is a simple ASCII file, which may be edited outside of WOW
with any text editor. The format is illustrated below:
Title: OpenJournal Tutorial Project
Author: Andrew Greig
Date: 2001/08/14
Category: Support
Keywords: Landmark,OpenJournal,Badleys,support,tutorial
Description: This OpenJournal contains a description of how to
use the product. It includes a detailed description of the Image
drag&drop and text annotation functionality.
If you intend to create this file outside of WOW, then take note of the following points:
only the description may span multiple lines (must be last in the file).
OpenWorks/SeisWorks Integration
Any OpenJournal project linked into $OWHOME/WebApps/htdocs/openjournal_data
(see exposing additional directories) or a single subdirectory level below, will appear as a
hypertext link on the OpenWorks or SeisWorks project summary page in WOW, provided
its name begins with the name of the OpenWorks of SeisWorks project.
For example, if the SeisWorks project is named mc3d, an OpenJournal project named
mc3d_dataloading_history will automatically appear on the SeisWorks project
summary page. The name will be the internal OpenJournal title, rather than the project
(directory) name.
Page 44 of 71
July 2004
OpenWorks grids
Of the above, the most important are the raster types: OpenWorks and Z-MAPPlus grids
and SeisWorks horizons. There are alternative and better methods for viewing Z-MAPPlus
pictures and SeisWorks live trace outlines in ArcView.
In the relevant parts of WOW, select the Create GIS Image checkbox. This will save a .jpg
file and an associated world file with .jpgw extension, which provides ArcView with the
parameters required to geo-reference the image. The image can then be viewed in
ArcView as a theme, after loading the JPEG extension.
Important note: WOW will attempt to write images to
/oe_gisdat2/oegis/wow_images, or $OEGIS_DAT/wow_images. You should either
create an /oe_gisdat2 link on the WOW server, or add a definition of the OpenExplorer
OEGIS_DAT variable in wow.env, i.e.
cd $OWHOME/WebApps/conf
vi wow.env
add at end: OEGIS_DAT=/data/oe_data; export OEGIS_DAT
ArcGIS Integration
An ArcGIS .dll provides substantially the same functionality as the current WOW ArcView
extension described overleaf. This allows users of ArcGIS to launch WOW in context by
clicking on objects in shapefiles created by OpenExplorer. For further information, see
$OWHOME/WebApps/gis/arcgis.pdf.
Page 45 of 71
July 2004
With the exception of the WEB_BROWSER variable, the extension attempts to read these
from your environment. When you first try to access any functionality you will be prompted
to review these settings and edit them if appropriate (usually simply clicking OK will
suffice). Additionally these variables can be set in the operating system environment (e.g.
in a users .login file), or at any time within the ArcView session, by using the
Environment' option on the WOW menu.
Integrating with ArcView
Page 46 of 71
July 2004
ArcIMS Integration
The WOW GIS extension also provides functionality to prepare OpenExplorer-generated
shapefiles for use within ArcIMS, ESRIs web-based GIS server.
1. In an OpenExplorer GIS working view create themes from OpenWorks data (these
should contain a valid primary key, e.g. for a well, it is well_id).
2. Add hyperlink fields to your OpenExplorer themes using the Add ArcIMS Hyperlink option
on the WOW menu.
3. Setup your ArcIMS website in the normal way. You could use ESRI's View2AXL script
packaged with this extension to create an AXL file to use as a start point.
4. Enable hyperlinks on your ArcIMS themes by editing the ArcIMSparam.js file in
your ArcIMS website, change:
var useHyperLink=false to var useHyperLink=true.
5. Add hyperlink tags for each theme you wish to integrate, e.g.
hyperLinkLayers[0] = "Wells";
hyperLinkFields[0] = "WOW";
WOW R2003.3.1.5 Release Notes
Page 47 of 71
July 2004
Page 48 of 71
July 2004
On the WOW top bar, click on Show Error. This will display the last 40 lines of the
Apache error log, as well as the complete environment and WOW version number.
3. Capture this text and provide the output to your support representative for diagnosis.
Page 49 of 71
July 2004
Page 50 of 71
July 2004
Page 51 of 71
July 2004
# ZMAPPlus
if [ -d ${OWHOME}/ZMAPPlus ]; then
ZYCORHOME="${OWHOME}/ZMAPPlus"; export ZYCORHOME
fi
# set Tcl/Tk library locations
TCL_LIBRARY=${WOW_HOME}/tcltk/tcl8.3; export TCL_LIBRARY
TK_LIBRARY=${WOW_HOME}/tcltk/tk8.3; export TK_LIBRARY
# set LD_LIBRARY_PATH
LD_LIBRARY_PATH=${OWHOME}/lib:${OWHOME}/SeisWorks/lib:${WOW_HOME}/tcltk/lib
export LD_LIBRARY_PATH
#============================================================================
# Corporate Data Archiver environmentals
# Change value of all variables here
#---------------------------------------------------------------------------# Name of OW project to store Archive database records
ARCHIVE_OW_PROJECT=EMPTY; export ARCHIVE_OW_PROJECT
# Email address of the Archive administrator
ARCHIVE_ADMIN_EMAIL=${MAIL_TO}; export ARCHIVE_ADMIN_EMAIL
# Stub directory
ARCHIVE_STUB_DIR=/data1/archive_stub; export ARCHIVE_STUB_DIR
# Stub URL
ARCHIVE_STUB_URL=http://exprotech/wow/archive_stub; export ARCHIVE_STUB_URL
# Staging directory
ARCHIVE_STAGE_DIR=/data1/archive_stage; export ARCHIVE_STAGE_DIR
# Default tape device
ARCHIVE_TDEVICE=/dev/rmt/0n; export ARCHIVE_TDEVICE
# Tape device capacity in Mb
ARCHIVE_CAPACITY=40000; export ARCHIVE_CAPACITY
#============================================================================
# CDA post-installation optional variables
# Uncomment and change value of variables here as appropriate
#---------------------------------------------------------------------------# Archive in browser flag: ARCHIVE is the default, REQUEST means send email only
#ARCHIVE_BROWSER_FLAG=REQUEST; export ARCHIVE_BROWSER_FLAG
# Flag to print timestamps in archiver log file: 1=on 0=off (default)
#ARCHIVE_TIMESTAMPS=1; export ARCHIVE_TIMESTAMPS
# Default control file location for opening/saving (default is user HOME dir)
#ARCHIVE_CTL_LOC=${ARCHIVE_STUB_DIR}; export ARCHIVE_CTL_LOC
#============================================================================
# End of script
#============================================================================
Page 52 of 71
July 2004
Description
/etc/apache (Solaris):
/etc/httpd/conf (Linux):
httpd.conf
.wp
/usr/apache/bin (Solaris):
/usr/sbin (Linux):
apachectl
httpd
/usr/apache/bin (Solaris):
/usr/bin (Linux):
htpasswd
/var/apache/logs (Solaris):
/etc/httpd/logs (Linux):
access_log
error_log
/var/run (Solaris):
/etc/httpd/logs (Linux):
httpd.pid
$OWHOME/WebApps/bin
$OWHOME/WebApps/cgi-bin
$OWHOME/WebApps/dat/
sqlscripts:
$OWHOME/WebApps/gis:
wow.avx
$OWHOME/WebApps/install:
WOWInstall
Page 53 of 71
July 2004
$OWHOME/WebApps/htdocs:
WOW_README.change_server
logos:
openjournal_data:
zmap_data:
openexplorer_data:
other_data:
push_output:
$OWHOME/WebApps/conf:
lease_tables.dat
well_tables.dat
field_tables.dat
lease_keyfacts.dat
well_keyfacts.dat
field_keyfacts.dat
basin_keyfacts.dat
other_sources.dat
restricted_dir_list.dat
restricted_plist.dat
wow.env
wow_sidlist.dat
wow_distlist.dat
wow_menu.dat
ascii_file_extensions.dat
web_file_extensions.dat
well_comparison.dat
$OWHOME/WebApps/kdoc/
sqlscripts
create_pim_project_
extension_custom.sql
update_pim_owsys_comments
.sql
update_pim_project_comments
.sql
Page 54 of 71
July 2004
$OWHOME/WebApps/templates:
dotlmkrc
dotlogin
dotlogin2
dotprofile
launcher.dat.extra
dothtaccess
Page 55 of 71
July 2004
The diagrams below display these files and directories. Bold entries signify directories,
normal fonts represent files. Note that not all files are shown, only those that a WOW
administrator need be aware of.
$OWHOME/WebApps
bin
cgi-bin
*.cgi
*.tbc
dat
conf
sqlscripts
lmksh
rlmksh
lmksh_wrapper
avsh
avsh_wrapper
DoAll2DSeismaps.sh
DoAll3DSeismaps.sh
DoPush
kdoc
gis
install
wow.avx
htdocs
WebAppsInstall
wow.env
wow_sidlist.dat
wow_distlist.dat
restricted_plist.dat
restricted_dir_list.dat
well/field/lease_tables.dat
well/field/lease_keyfacts.dat
wow_links.dat
wow_menu.dat
ascii_file_extensions.dat
web_file_extensions.dat
well_comparison.dat
well_match.dat
/usr/apache
kdoc
templates
sqlscripts
dotlmkrc
dotlogin
dotprofile
dothtaccess
index.html
README.change_server
*.css
*.js
*.pdf
logos
openjournal_data
zmap_data
openexplorer_data
other_data
push_data
/etc
/var
/var/apache
bin
apache
run
logs
httpd
apachectl
htpasswd
httpd.conf
mime.types
.wp
httpd.pid
error_log
access_log
Page 56 of 71
push
July 2004
WOW Architecture
Web browser (thin client)
Any platform
Web server
Presentation logic
Business logic
Data integration
Data I/O
Unix
Apache
OpenWorks
devkit
OpenWorks
Oracle
OCI
OpenWorks
ZMAP Plus
devkit
ZMAP
mfd
zgf
SeisWorks
devkit
SeisWorks
horizons
seismic
projects
Other
api
Other
data
Data layer: WOW currently covers OpenWorks, SeisWorks, Z-MAP Plus and other data
types, including SEG-Y, OpenJournal etc.
Data I/O layer: This layer is comprised of the application devkits, which provide a safe
mechanism for reading/writing the data stores.
Data Integration Layer: This provides an integration layer on top of the diverse devkits to
allow consistent read/write of vendor data. WOW uses a number of devkit shells, which
are Tcl/Tk shells extended with the underlying devkit functions.
Business Logic Layer: This layer wrappers the lower-level extensions with business
logic, including error checking, lists of values, numerical computations etc. This provides a
consistent, modular, interface to the underlying data stores.
Presentation Layer: This layer executes the shell the web server in response to being
passed a URL by a web browser. It calls procedures from the business logic layer, and
formats output on the fly as html to send back to the browser.
Page 57 of 71
July 2004
All WOW configuration (with the exception below) is stored in a single file,
$OWHOME/WebApps/conf/wow.env.
The only static part of WOW that does not use wow.env, is contained in directory
$OWHOME/WebApps/htdocs. The files index.html and wow_css.js both
contain hardcoded URLs, which will need to be changed if server or port is changed.
Page 58 of 71
July 2004
Page 59 of 71
July 2004
Page 60 of 71
July 2004
Page 61 of 71
July 2004
Page 62 of 71
July 2004
vi wow.env
line 21: change WOW_HOME to /apps/ow/WebApps1
line 46: change WEBSERVER_URL to wow.oilco.com:8081
line 68: change APACHE_HOME to /usr/local/apache1
Change ORACLE_SID, OWSYSSID, OW_PMPATH and other variables as appropriate.
cd /usr/local/apache1/htdocs
cp index.html index.html.orig (if it exists)
cp $OWHOME/WebApps1/htdocs/index.html .
7. Repeat steps above as often as is required, e.g.:
Port: 80, Apache: default OS package, WOW: $OWHOME/WebApps
Port: 8081, Apache: /usr/local/apache1, WOW: $OWHOME/WebApps1
Port: 8082, Apache: /usr/local/apache2, WOW: $OWHOME/WebApps2
Port: 8083, Apache: /usr/local/apache3, WOW: $OWHOME/WebApps3
etc.
Installing Multiple Apache Servers Linux
1. Obtain the Apache binary distribution. Either download from
http://archive.apache.org/dist/httpd/binaries/linux/ , file apache_1.3.26-i686-whateverlinux22.tar.gz, or from isite.lgc.com, directory /products/WOW/apache.
2. Install Apache to a local disk (make sure it is writeable first):
gzip -dc apache_1.3.26-i686-whatever-linux22.tar.gz | tar xvf cd apache_1.3.26
./install-bindist.sh /usr/local/apache1
3. Configure Apache httpd.conf and make the following changes:
vi /usr/local/apache1/conf/httpd.conf
line 304: Port 8081
line 318: User <your WOW user>
line 319: Group <group of WOW user>
line 326: ServerAdmin <system administrators email>
line 648: change AllowOverride None to AllowOverride AuthConfig
line 612: insert line Alias /wow/ "/apps/ow/WebApps1/htdocs/"
line 654: add the following stanza:
ScriptAlias /bin/ "/apps/ow/WebApps1/cgi-bin/"
<Directory "/apps/ow/WebApps1/cgi-bin">
AllowOverride AuthConfig
Options None
Order allow,deny
Allow from all
</Directory>
4. Start Apache
/usr/local/apache1/bin/apachectl start
5. Duplicate the WOW software tree:
cd $OWHOME
mkdir WebApps1
Page 63 of 71
July 2004
cd WebApps
find . -depth -print | cpio -pdlmv ../WebApps1
6. Configure WOW:
Change all references from the default to the new port in files index.html and
wow_css.js, e.g. change wow.oilco.com to wow.oilco.com:8081 (2
locations in each)
cd $OWHOME/WebApps1/htdocs
vi $OWHOME/WebApps1/htdocs/index.html
vi $OWHOME/WebApps1/htdocs/wow_css.js
Update the wow.env file:
cd $OWHOME/WebApps1/conf
vi wow.env
line 21: change WOW_HOME to /apps/ow/WebApps1
line 46: change WEBSERVER_URL to wow.oilco.com:8081
line 68: change APACHE_HOME to /usr/local/apache1
Change ORACLE_SID, OWSYSSID, OW_PMPATH and other variables as appropriate.
7. cd /usr/local/apache1/htdocs
cp index.html index.html.orig (if it exists)
cp $OWHOME/WebApps1/htdocs/index.html .
8. Repeat steps above as often as is required, e.g.:
Port: 80, Apache: default OS package, WOW: $OWHOME/WebApps
Port: 8081, Apache: /usr/local/apache1, WOW: $OWHOME/WebApps1
Port: 8082, Apache: /usr/local/apache2, WOW: $OWHOME/WebApps2
Port: 8083, Apache: /usr/local/apache3, WOW: $OWHOME/WebApps3
etc.
Upgrading Apache to a Native Apache Version Solaris
WOW by default uses the version of Apache shipped with Solaris 8, which may need to be
updated. The Sun version of Apache is provided in package format, which distributes files
over multiple operating system directories. The native Apache version installs into a single
directory, by default /usr/local/apache. This section describes the steps required to
upgrade Apache. These steps will require root privileges:
1. Shutdown the current version of Apache:
/usr/apache/bin/apachectl stop
2. Download the Apache binary distribution into /tmp. Either download from
http://www.apache.org/dist/httpd/binaries/solaris/, file
apache_1.3.26-sun4u-sun-solaris2.280.tar.gz, or from
isite.lgc.com, directory /products/WebApps/apache.
3. Install Apache to a local disk using the install-bindist.sh script supplied:
cd /tmp
gzip -dc apache_1.3.26-sun4u-sun-sol2.280.tar.gz | tar xf cd apache_1.3.26
./install-bindist.sh /usr/local/apache
Page 64 of 71
July 2004
4. Configure Apache httpd.conf and make the changes listed below. It may be easier
to cut & paste from the original configuration file than to type in changes by hand. Line
numbers in brackets below are for the original file /etc/apache/httpd.conf.
vi /usr/local/apache/conf/httpd.conf
line 318 (320): User <your WOW user>
line 319 (321): Group <group of WOW user>
line 326 (328): ServerAdmin <system administrators email>
line 342 (344): ServerName <your server name>
line 612 (593): insert line Alias /wow/ "/your/OWHOME/WebApps/htdocs/"
line 654 (617): add the following stanza:
ScriptAlias /bin/ "/your/OWHOME/WebApps/cgi-bin/"
<Directory "/your/OWHOME/WebApps/cgi-bin">
AllowOverride AuthConfig
Options None
Order allow,deny
Allow from all
</Directory>
(replace the value /your/OWHOME with the value of $OWHOME).
5. Start Apache
/usr/local/apache/bin/apachectl start
6. Change permissions on the logs directory to enable viewing of the error_log for
diagnostic purposes by a non-root user. This is an optional step: some sites may not
wish non-root users to view the log files, although this will make WOW error diagnosis
more difficult.
chmod 755 /usr/local/apache/logs
7. Modify the Apache boot-time startup/shutdown scripts:
vi /etc/init.d/apache
line 8: APACHE_HOME=/usr/local/apache
line 9: CONF_FILE=/usr/local/apache/conf/httpd.conf
line 10: PIDFILE=/usr/local/apache/logs/httpd.pid
8. Update the value of APACHE_HOME in the wow.env file:
cd $OWHOME/WebApps/conf
vi wow.env
line 68: change APACHE_HOME to /usr/local/apache
9. Update the document root index.html file. Some sites will have previously
replaced the original Apaches start page /var/apache/htdocs/index.html with
an edited copy of $OWHOME/WebApps/htdocs/index.html. Others may use their
own index.html start page. In either event, copying the original file or files into the
new document root is required:
cp /var/apache/htdocs/index.html /usr/local/apache/htdocs
Page 65 of 71
July 2004
Page 66 of 71
July 2004
Page 67 of 71
July 2004
Page 68 of 71
July 2004
Practical Programming in Tcl and Tk (4th Edition), by Brent Welch, Jeffrey Hobbs &
Ken Jones, published by Prentice-Hall 2003, ISBN 0130385603
Tcl/Tk in a Nutshell, by Paul Raines & Jeff Tranter, OReilly 1999, ISBN 1565924339.
Running lmksh
To run lmksh you require a .lmkrc file in your home directory and to have sourced the
required environment:
prompt> cp $OWHOME/WebApps/templates/dotlmkrc ~/.lmkrc
(1-off)
(C-shell)
prompt> source $OWHOME/WebApps/templates/dotlogin*
prompt> . $OWHOME/WebApps/templates/dotprofile
(Bourne shell)
prompt> lmksh
lmksh{1}% OWSetup
(configures OpenWorks environment)
lmksh{2}% SeisSetUp
(configures SeisWorks environment)
lmksh{3}% info commands
(lists all available commands)
lmksh{4}% info commands sdl*
(lists commands beginning with sdl)
lmksh{5}% info procs
(lists all available procedures)
lmksh{6}% info args hrzinfo
(lists arguments for specified proc)
Alternatively, a wrapper script is provided and linked to $OWHOME/bin during installation:
prompt> rlmksh
Page 69 of 71
July 2004
Notes on .lmkrc: you will need to copy the .lmkrc into the home directory of every user
that wishes to run lmksh interactively:
prompt> cp $OWHOME/WebApps/templates/dotlmkrc $HOME/.lmkrc
Add or uncomment the commands OWSetup and SeisSetUp in .lmkrc so you do not
need to type these during every interactive session. Add or uncomment
SourceAllProcs to load all available commands.
The lmksh Commands
There are three classes of commands:
Tcl built-in commands: This is the core Tcl language. See the Tcl man pages or html
help at $OWHOME/WebApps/tcltk/htmldocs/tcltk.html for information on built-in
commands. To access the man pages:
prompt> source $OWHOME/WebApps/templates/dotlogin
prompt> man <cmd>
Extended commands: These are added to lmksh to provide scripted access to devkit
functions. The extended commands are usually low-level with little error trapping. Most
begin with sdl_ (SeisWorks), ow_ (OpenWorks), sil_ (MFD), zgf_ (ZGF), sgy_
(SEGY) and gen_ (LAS and others). To see the arguments for an extended command,
type the command name:
lmksh{7}% sdl_hrzinfo
Procedures: These are additional wrappers to the extended commands, including more
robust error trapping and other business logic to make the low-level commands more
useful. To see the arguments for any procedure:
lmksh{8}% info args hrzinfo
OpenWorks database access procedures usually start with a lowercase letter to denote
that they require an Oracle database connection to be established first, e.g.:
prompt> rlmksh
lmksh{9}% set lda [OWoralogon]
lmksh{10}% getWellLists TESTDATA
lmksh{11}% oralogoff $lda
Exposing lmksh Commands
It is sometimes more convenient to run lmksh procedures through a regular Bourne- or Cshell. A wrapper script is provided in $OWHOME/WebApps/bin for this purpose. To
expose any lmksh procedure on the command line, create a link as illustrated below:
prompt> cd $OWHOME/WebApps/bin
prompt> ln s lmksh_wrapper <proc>
The procedure can then be run on the command line, with any required parameters
passed through to the underlying lmksh.
Health Warning
WOW and CDA are largely read-only applications. But the underlying lmksh has
additional destructive options, e.g. the ability to create, rename and delete
SeisWorks horizons. Use of these options is entirely at your own risk, and you
should always ensure you have a current backup before proceeding.
Page 70 of 71
July 2004
Landmark/Asia Pacific
Landmark/EAME
Landmark/The Americas
Springfield Drive
Houston, TX 77042
Malaysia
England
U.S.A.
Tel: 60-3-2164-1121
Tel: 44-1372-868-600
Tel: 1-713-839-2000
Fax: 60-3-2164-1135
Fax: 44-1372-868-601
Fax: 1-713-839-2168
Email: apsupport@lgc.com
Email: eame_helpdesk@lgc.com
Email: support@lgc.com
Trademarks
Landmark, the Landmark logo, 3D Drill View, 3D Drill View KM, 3DVIEW, Active Field Surveillance, Active
Reservoir Surveillance, ARIES, Automate, BLITZ, BLITZPAK, CasingSeat, COMPASS, Contouring Assistant,
DataStar, DBPlot, Decision Suite, Decisionarium, DecisionDesktop, DecisionSpace, DepthTeam, DepthTeam
Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, DESKTOP-PVT, DESKTOP-VIP,
DEX, DFW, DIMS, Discovery, Drillability Suite, DrillModel, DrillVision, DSS, Dynamic Surveillance System,
EarthCube, EdgeCa$h, eLandmark, EPM, e-workspace, FastTrack, FZAP!, GeoDataLoad, GeoGraphix,
GeoGraphix Exploration System, GeoLink, GES, GESXplorer, GMAplus, GrandBasin, GRIDGENR, I2 Enterprise,
iDims, IsoMap, LandScape, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Make Great Decisions,
MathPack, Model Builder, MyLandmark, MyWorkspace, OpenBooks, OpenExplorer, OpenJournal, OpenSGM,
OpenTutor, OpenVision, OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView,
Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PRIZM, PROFILE, ProMAX, ProMAX 2D,
ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pStaX, QUICKDIF, RAVE, Real Freedom,
Reservoir Framework Builder, RESev, ResMap, RMS, SafeStart, SCAN, SeisCube, SeisMap, SeisModel,
SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, SigmaView, SpecDecomp, StrataMap, Stratamodel,
StratAmp, StrataSim, StratWorks, StressCheck, STRUCT, SynTool, SystemStart, T2B, TDQ, TERAS, Total
Drilling Performance, TOW/cs, TOW/cs The Oilfield Workstation, Trend Form Gridding, Turbo Synthetics, VIP,
VIP-COMP, VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIPPOLYMER, VIP-THERM, WavX, Web OpenWorks, Well Editor, Wellbase, Wellbore Planner, WELLCAT,
WELLPLAN, WellXchange, WOW, Xsection, ZAP!, Z-MAP Plus are trademarks, registered trademarks or service
marks of Landmark Graphics Corporation.
All other trademarks are the property of their respective owners.
Page 71 of 71
July 2004