WOW Release Notes

8/20/2019 WOW Release Notes

1/71

WOW R2003.3.1.5Release Notes and Administration Manual

ContentsIntroduction..................................................................................................................................... 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

July 2004 Part No. 159509 R2003

Appendix 5: Background on the Devkit Shell ‘lmksh’ .................................................................69


2/71

Introduction

WOW provides dynamic access to E&P data over the company intranet. The productaddresses one of the biggest challenges facing the E&P business: making the right dataavailable to business users in time to facilitate decisions. Because subsurfaceprofessionals 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 userswith a new project area.

• Find data easily: a uniform interface shelters users from the underlying applications,databases and systems.

• Capture knowledge: allow users to document projects, providing context to enhancethe content.

• Cleanup project data: a raft of functions for managing the underlying data.

WOW is part of Landmark’s WebApps1 technology framework. It is a 'thin client'application, which means that the majority of content is generated dynamically on the Webserver by reading the underlying databases, formatting and then sending results to theWeb browser. This means also that there are no client-side dependencies, i.e. plug-ins tobe downloaded or installed, considerably simplifying maintenance.

WOW coverage is considerable and expanding in both depth and breadth:

• OpenWorks

• SeisWorks

• Z-MAP Plus

• GeoProbe

• VIP

• OpenJournal

• SEG-Y files

• LAS files

• OpenExplorer (ArcView) shapefiles and DBF files

• Archives (from Corporate Data Archiver - licensed separately)

• Geolog® (licensed separately)

•

GeoFrame

®

(licenses separately)

1 WebApps is the shared architecture and software directory name for the following products: WOW (including GeoProbeand VIP modules), Corporate Data Archiver (CDA), WOW for Geolog and WOW for GeoFrame.® Geolog is a registered trademark of Paradigm Geotechnology B.V.

WOW R2003.3.1.5 Release Notes Page 2 of 71 July 2004

® GeoFrame is a registered trademark of Schlumberger.


3/71

Major Changes in Version R2003

A number of configuration changes have been made to WOW for the R2003 release.These are summarized below:

Use of Native Apache

Apache version 1.3 is now distributed as an optional package with the Solaris 8 operatingsystem. Consequently, WOW is no longer distributed with its own version of Apache, withthe following implications:

• 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 completedwithout 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, whichin turn means that no port need be specified in WOW URLs.

• The actual Apache cgi-bin directory, /var/apache/cgi-bin, is not used by WOW.

Since this directory is owned by root, Landmark has implemented the dynamic partsof WOW as an alias to a non-root directory under the WOW installation:/cgi-bin becomes /cgi-bin, aliased to /cgi-bin-wow in thebrowser (R2003.0 versions) or /bin (R2003.3 versions).

• 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 ofWOW as an alias to a non-root directory under the WOW installation:

/htdocs becomes /htdocs, aliased to /wOW in the browser(R2003.0 versions) or /wow (R2003.3 versions).

Restructuring of WOW Directories

The Apache change has enabled an overall simplification and rationalization of the WOWdirectory tree, with the following changes:

• The R98 WOW directory contained a TclApps and an apache directory; it is now asingle flat structure referred to as $WOW_HOME, set to $OWHOME/WOW (R2003.0versions) or $OWHOME/WebApps (R2003.3 versions).

• In general the directory structure of WOW has been modified to look more like anyother Landmark application, with install, conf, bin, templates directories etc.

• All configuration files have been centralized in a new $WOW_HOME/conf directory.

These files have all been made more consistent to support future Web-basedmodification. The most significant change is that the old /cgi-bin/server_env file has been replaced by $OWHOME/WebApps/conf/wow.env .



4/71


5/71

Previous Enhancements and Fixes

Version R2003.0.1

1. OpenWorks: added a navigation bar, similar to the SeisWorks module2. OpenWorks: new summarize option to display data counts across all projects

3. OpenWorks: new option to run QC/QA queries across projects4. OpenWorks: 5 new QC/QA queries5. OpenWorks: truncate QC/QA results to 500 rows per query6. OpenWorks: only display projects a user has access to if level C security7. OpenWorks: added well lease name/number to well header and comparison8. OpenWorks: added elevation type and value to comparison9. OpenWorks: added field interests and lease status/type to filter options10. OpenWorks: added axes to checkshot, wavelet and synthetic graphs11. SeisWorks: horizon count on summary page corrected12. Documenter: extended documenter remarks to 2000 chars13. Documenter: added create and update user and date to all Documenter tables14. General: added file filter, sort and save to all directory-parsing modules15. Z-MAP Plus: display first 500 points of large DATA files16. SEG-Y: added axis labels and decimate/interpolate options

Enhancement #132498: modified crontab to run at 4am on days 2-6Enhancement #132800: allow sort, filter and save on OpenWorks external file listingsEnhancement #601120, 304814: increased documenter comments from 80 to 2000 charsEnhancement #601147: added support for hyperlinks in seismic documentationEnhancement #304809: scripts provided to move kdoc data between projectsEnhancement #304826: save MFD/ZGF contents to file/ExcelEnhancement #128370: save query results to file/ExcelDefect #133596: push for seismic does workDefect #132823: fixed ‘error in linediv’ messageDefect #130222: ZMAP dependencies on SeisWorks plist.dat removed

Defect #121936: Tcl script error with APM fixedDefect #133138: ZMAP data files with no points now display OKDefect #132456: improved documentation importing grids to ArcViewDefect #129005: prevent browsing above ZMAP/OJ start locationDefect #128920: browsing directories with ‘+’ in directory path now OKDefect #305035: checkshot label changeDefect #133596: push for seismic navigation works

Version R2003.0.1.1

Defect #135965: Push email points to wrong URLDefect #136165: KDoc OWSYS copy sqlscript missingDefect #136168: Incorrect URL sent from Push email

Defect #137632: Cannot compare projects without manage access to bothDefect #137990: ArcView extension points to wrong URLDefect not reported: ZMAP->ArcView grid export fixed

Version R2003.0.2

1. GIS: add ArcView shapefile viewer module2. GIS: view/save shapefile coordinates and database



6/71

3. GIS: save pictures with world files for use in ArcView GIS4. LAS: add LAS viewing module with curve graphs5. OpenWorks: option to export multiple curves in LAS format6. OpenWorks: compare 2D navigation7. OpenWorks: new pick analysis ‘matrix’ view8. OpenWorks: new curve analysis ‘matrix’ view

9. OpenWorks: compute and display velocities from time-depth tables10. OpenWorks: extend cross-project search to picks by name / interpreter11. OpenWorks: add a vertical section view to position log graph12. OpenWorks: filter leases by quad/block, class, status, type13. OpenWorks: filter wells by log curve name, curve source, pick interpreter14. OpenWorks: filter curve comparisons by curve type, picks by interpreter15. Push: add WOW documenter data

Version R2003.0.3

1. OpenWorks: Coverage of TDQ models plus external binary data2. OpenWorks: Ability to compare projects across SIDs3. OpenWorks: QC/QA query results can be saved/download to Excel

4. OpenWorks: QC/QA queries now support seismic navigation queries5. OpenWorks: Allow change of default well name display, e.g. UWI or CWN6. SeisWorks: New workflow for 2D seismic handling7. SeisWorks: Coverage of mapping (dts) files8. SeisWorks: Export horizons to table/Excel with specified decimation9. SeisWorks: Export seismic navigation to table/Excel with specified decimation10. SeisWorks: Export single seismic trace to table/Excel11. SeisWorks: New layout for accessing seismic/horizon documenter records12. SeisWorks: Allow adding/deleting of Documenter R table entries through the browser13. SeisWorks: Allow choice of short, project or directory color maps lists14. Push: support for SeisWorks horizons and seismic15. OpenExplorer: View and browse contents of .par files in Shapefile module16. OpenExplorer: View contents and drill down into .apr file contents17. OpenExplorer: allow editing of KRS document name, comments and hyperlink18. General: New customizable left frame options for OE and Other Data

Version R2003.0.3.1

1. OpenWorks: added general support for multiple Oracle instances2. OpenWorks: added optional filter of wells by pick name3. OpenWorks: display tolerances in comparison results (#130055)4. OpenWorks: option to save project counts summary page (#136085)5. SeisWorks: live trace outlines now write ZGF to1st OW_PROJ_DATA dir (#131112)6. SeisWorks: for 3D, optional rigorous command-line live trace outlines (#133197)7. SeisWorks: for 2D, added line navigation detail drilldown

8. SeisWorks: for 2D, list lines which have interpreted a specified horizon9. SeisWorks: for 2D, display a line/proclev matrix for the master project10. SeisWorks: for 3D, added line name to seismic image preview11. SeisWorks: simple support for viewing .cd file headers (#142005)12. SeisWorks: added tabular editing of horizon/seismic documenter records13. SeisWorks: ability to set up bulk horizon rename/delete actions14. Z-MAPPlus: added XML-based MFD/ZGF documenting through the browser15. General: Allow editing of all WOW configuration files through the browser



7/71

1. Trapped bug when the push_output directory does not exist2. Trapped bug when KDoc OWSYS extension not created3. Fixed general pointset display error4. Fix to allow very large velocity models to be viewed5. Fix to script Do3DSeismaps generating live trace outlines (#143709)

Version R2003.3.1

General configuration changes: the WOW parent directory has been renamed fromwOW to WebApps. In addition, the WOW htdocs directory is now aliased to ‘wow’ ratherthan ‘wOW’, and the cgi-bin directory is now ‘bin’ rather than ‘cgi-bin-wow’. The variousdevkit shells have been replaced with a single integrated lmksh shell.

WOW R2003.3.1 is a point product release. WOW must be reinstalled.

1. OpenWorks: added support for executing WOW QC/QA queries with variables2. OpenWorks: editing/documenting of OpenWorks remarks columns in the browser3. OpenWorks: module to match wells between projects with different UWI conventions

4. OpenWorks: add row counts to VC_ and R_ tables5. OpenWorks: project comparison will now compare counts for well-related data types6. OpenWorks: batch utility to do coordinate transformation on a file (#133205)7. OpenWorks: project comparison will warn if CRS is different between projects8. OpenExplorer: improved KRS handling with editing of metadata tables in the browser9. OpenExplorer/OJ: allow linking of OpenJournal documents to the KRS10. SeisWorks: option to save live trace outlines to shapefiles11. SeisWorks: changed approach to handling multiple ‘districts’ using cookies12. SeisWorks: seismic info now shows bricking/compression parameters13. SeisWorks: 3D horizon info shows horizon file size, owner, create and modify dates14. SeisWorks: navigation info now shows project depth unit and datum15. SeisWorks: 2D navigation info now shows 2D project total line length16. SeisWorks: 2D horizon info now approximates %coverage using line counts17. SeisWorks: documenter now defaults 2D horizon file owner from horizon header18. SeisWorks: documenter now auto-populates horizon create date19. General: Linux port20. General: support for viewing CGMs added – requires client configuration21. General: quick view of DGN files in WOW (excluding text)

1. Large ZMAP non-grid datasets can now be displayed without memory issues2. Fixed error when viewing grids, pictures and datafiles with a '+' in the name3. Fixed error when executing a stored OpenWorks query with more than one variable4. SeisWorks seismic info no longer opens all volume extents5. Fixed ZMAP to ArcView grid converter failure - requires ArcView3 feature (#150909)

Version R2003.3.1.1

1. OW: added extra attributes to KRS document detail display2. OW: support for non-float32 log storage and TVDSS logs (#149557)3. SW: added sorting of 2D seismic lines4. SW: added option to reference external text file for each 2v2 file (#156392)5. AV: functionality to convert ZMAP to ArcInfo grid formats moved into WOW6. Other: Added file for implementing NIS passwd authentication



8/71

1. OW: LAS export of selected curves was picking the wrong curves (#152838)2. OW: Extra customizable well header attributes (#152389)3. OW: Fixed incorrect well_table.dat.default (referenced log_crv_hdr)4. OW: Fixed QC/QA query with variables bug where no text value entered5. OW: Fixed errors with aperiodic and negative-valued curves (#153874/153880)6. SW: Incorrect top navigation bar when viewing 2D master project files (#601453)

7. SW: Fixed unsupported BulkHrzRename/Delete functions8. SW: Fixed inconsistencies and documentation for seis2png/seis2png2 (#154712/4)9. SW: Fixed seismic display of 3dvs with a '+' in the name (#156285)10. SW: Fixed 2D navigation save to only save specified line, not all (#156280)11. SW: Fixed error in locating colormaps where COLOR_SOURCE1=project (#158714)12. SW: Can display SEG-Y files > 2Gb, but not file attributes (#156891/153133)13. ZM: Don't create .xml files unless user documents the MFD/ZGF (#157845/154350)14. AV: Replaced corrupted ArcView extension file wow.avx (#153028)15. AV: Changed storage of WOW GIS image backdrops to subdirectory (#157154)16. OJ: OpenJournal browser was not detecting R2003 OJ projects17. OJ: Fixed errors in OpenJournal search and links (#153134)18. Other: Fixed stylesheet errors for Netscape 719. Other: fixed WOWInstall URL display error and permission check (#305984/158689)

20. Other: Improved WOW left frame cosmetics (#157878)

Version R2003.3.1.2

General integration changes: In this release the integration between WOW andCorporate 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 WOWfeature, rather than a CDAWEB feature. Clients with CDAWEB licenses will obtain aWOW license for every CDAWEB license.

2. An ‘Archives’ option has been added to the WOW left frame which will display theCDA ‘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 theWOW OpenWorks and SeisWorks project summary pages, provided the site has aCDARCHIVER license. This executes the same functions as the Unix ‘archiver’ GUI

4. Thumbnails generated in a throwaway project called 'Stubs' are reused in the WOWhorizon 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 GUIwhich displays a user-modifiable number of objects at a time. These ‘page’ views willalso reuse thumbnails from an existing ‘Stubs’ project.

6. Horizon and seismic list-deletion command-line utilities are provided to delete allobjects in lists created using the above list builders.

7. A GeoProbe Information Manager module has been added, which providesfunctionality for browsing, searching, documenting, cleaning up and archivingGeoProbe project data. The archival component supports rich metadata extractionboth in the Archiver GUI and from within the WOW browser.

8. An ArcGIS .dll has been added, providing substantially the same functionality as thecurrent WOW ArcView extension. This allows users of ArcGIS to launch WOW/CDA



9/71

in context by clicking on objects in shapefiles created by OpenExplorer and CDA. See$OWHOME/WebApps/gis/arcgis.pdf for further information.

Other enhancements and bug fixes:

1. OW: fixed error in comparison saving well list to project 2 (#159311)

2. OW: added pick observation number to pick export page (#160600)3. OW: show correct TD table used on pick export page (#160601)4. OW: Add UTM zone to CRS info display5. SW: fixed ‘no data found’ error in SeisWorks subscription module (#162020)6. SW: Increased SeisWorks trace length limit from 4001 to 7001 samples7. SW: fixed 2D live trace outlines: was highlighting the wrong line in yellow8. SW: Improved performance on SeisWorks multi-horizon documentation page9. SW: added caching of 2D seismic file names to speed up 2D proclev listings10. Other: Improvements to ASCII viewers to show all data, and to download/save11. Other: Increase length of ASCII files displayed in WOW to 1000 lines (#161549)12. Other: LAS viewer option to view raw data and to download/save file13. Other: Standardized date formats as YYYY-MM-DD, e.g. 2003-07-23

Version R2003.3.1.3

1. Changed SeisWorks project details table to display in right frame2. Added option to sort/save SeisWorks project details table3. Allow 3D volumes with master grid mismatches to process4. Added support for displaying 3D traces (crosslines)5. Added project name to SeisWorks live trace outline shapefile6. Added option to seismic detail popup to change seismic7. Added option to ZGF viewer popup to change picture8. Added option to MFD viewer popup to change file9. Added original coordinates/CRS to OpenWorks 3D survey report10. Added option to display all OpenWorks 3D surveys in a table11. Added link from SeisWorks 3D navigation page to OW survey page

1. Fixed SeisWorks timeslice image creation failure2. Fixed SeisWorks time slice label and added line/trace axis labels3. Fixed seismic trace annotation bug when internal X = line4. Flipped seismic images color mapping to match SeisWorks5. Removed hyperlinks from WOW SeisWorks project summary if count=06. Fixed SeisWorks documenter error when using apostrophes7. Added SeisWorks documenter field length checking8. Fixed error in saving OpenWorks QC/QA results for > 500 rows9. Fixed saving OpenWorks QC/QA query results with variables10. Fixed hyperlink from OW pick/curve matrixes to multi-well detail11. Added warning if pick/curve matrixes > 256 columns (Excel limit)

12. Changed OpenWorks well comparison to handle null poslog offsets13. Remove most dependencies on knowing OWSYS/OWSYSP passwords14. Fixed OpenWorks velocity model error on small TDQ models15. Detect ZGF pictures with 0 XY coordinates and scale16. Fixed ArcGIS extension incorrect hyperlink17. Fixed GeoProbe pointset processing error18. Fixed SEGY file viewer showing zero file size



10/71

Version R2003.3.1.4

1. GeoProbe: Added support for viewing GeoProbe 'Pictures' directory2. SW: Added generate stub link on seismic/horizon 'page' views3. SW: Added ability to drill down into subdirectories on SeisWorks files page4. SW: Added support for jpg/png images in SeisWorks files page

5. SW: Allow Apache user to delete subscriptions for deleted projects (#170392)6. OW: Added display of well dipmeter data (#172540)7. OW: Added CRS name to OpenWorks project create info table8. OW: Moved OW project create info to main frame; added sort/save options9. OW/SW: Added default display of OpenJournal docs on OW/SW summary pages10. Other: CGM file display changes.

1. GeoProbe: Changed volume count to only list .vol files2. GeoProbe: Handle volumes with corrupt real-world coordinates3. GeoProbe: fix for >2Gb volumes4. OW: Fixed form error in well log curve comparison5. OW: Fixed error in poslog comparison when not present in both projects6. OW: Removed dependencies on owsysp password (#162136)

7. SW: Added underscores to live trace outline shapefile (dbf) titles8. SW: Changed navigation GIS image from png to jpg (#160693)9. OJ: Fixed OpenJournal search bug if space after text string10. ZM: Fixed error displaying grid images from read-only MFDs11. ZM/OJ/GeoProbe/Other/CDA: tightened security on level C file access

Enhancements and Fixes in this Version (R2003.3.1.5)

WOW R2003.3.1.5 is a patch release. It requires WOW R2003.3.1 to be installed first.

Bug fixes and enhancements:

1. Added support for browsing VIP data covering these VDB data types per case:case headersplot classes with graphs of variables vs. time with observed data where presentinitialization variables with maps of variables per layerrecurrent variables with maps of variables per layer per timestepternary diagrams of initial and recurrent variableslists of grids, timesteps and perforations with start/end flow type.

2. OW: Added original XY locations to OW project comparison3. OW: Added save 2D line list following OW project comparison4. OW: Extend cross-project well search to also search the well remark5. OW: Fixed error in saving results of OW well header comparison6. OW: Fixed parsedir error displaying very small files7. OW: Fix error adding KRS documents with apostrophe in name/comment

8. OJ: Automatic OJ link on OW/SW summary pages now handles exact match



11/71

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 amechanism 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. OnR2003 upgrade, be sure to export this information BEFORE shutting down R98 Oracle.The export and subsequent import in R2003 OWSYS is described in the CustomizingWOW 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 daemonprocess 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. Toconfirm 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 requestyour System Administrator obtain and install it – see Appendix 4 for more details.Important note: The version of Apache shipped with Solaris lacks recent securityenhancements. 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 thedefault port 80 is available. If Apache is running, i.e. from a previous installation ofWOW, 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).

http://www.apache.org/http://www.apache.org/


12/71

/usr/apache/bin/apachectl stop (Solaris) /usr/sbin/apachectl stop (Linux)

4. An install location, typically $OWHOME/WebApps, but may be any NFS-exportedfilesystem, e.g. /apps/WebApps.

5. A user who will run the Apache server. This should be a user with read-writeaccess to most of the OpenWorks and SeisWorks projects – typically a dataloader or administrator. Do NOT use root ororacle for security reasons. Youshould run the install script as this user, from within a Landmark environment. Thismay require temporarily opening up of permissions on the following directories:$OWHOME$OWHOME/bin

$OWHOME/revisions

6. The domain name for the site. This will default correctly during installation if the siteuses DNS to allow the resolving of domain names. To test this, type: nslookup in a Unix xterm or at the DOS command prompt. The value returned bythe Unix domainname command is not the correct domain name. If nslookup

returns an error, you will need to determine whether the host name is visible acrossthe site network. To do this, type ping from a DOS prompt on a PC. If

the host is recognized, use the host name with no domain specified; if not, use the fullIP address obtained from the local /etc/hosts file or from NIS using the Unixcommand ypcat hosts | grep .

7. Root access IS now required to execute the root.sh script for Apache configuration.

8. See Appendix 4 if you require anything other than a single standard Apache rootinstallation. Appendix 4 addresses options for changing the Apache server and port,obtaining the Apache package, and installing multiple Apache instances.

Licensing

In WOW version R2003 and above, regular FlexLM licensing is used with a feature nameof ‘WOW’. The product simulates a typical user session using the FlexLM ‘linger’ function.Whenever a user clicks on a link in WOW, the license is refreshed for a further 20 minutes.The license is checked back in after 20 minutes of inactivity.

See your R2003 installation instructions and Release Notes for how to install licenses,and/or email [email protected] to obtain a valid license key.

You should install licenses BEFORE installing WOW, as the installation script checks out aWOW license feature.


mailto:[email protected]?subject=wOW%20license%20requestmailto:[email protected]?subject=wOW%20license%20request


13/71

Installation

The latest WOW point product release can be obtained on CD. The CD version is inLandmark Release Manager (CD Installer) format under the product name WebApps, andincludes the Corporate Data Archiver.

Alternatively, the latest WOW point product release can be obtained from the Landmark ftpserver isite.lgc.com, directory /products/WOW/Releases as a compressed tarfile. 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, thenapplying and subsequent patches, as described in this section.

Manual Method

• Login to the chosen server as the chosen user.

•

Source the Landmark environment if not done by default:source $OWHOME/templates/.lgclogin

• Create and cd to the installation location ($WOW_HOME):mkdir $OWHOME/WebAppscd $OWHOME/WebApps

• Untar the media: gzip –dc /loc/WebApps_2003.3.1.0_release.tar.gz | tar xvf –

• Run the installation script: cd install

./WOWInstall –o $OWHOME

CD Installer Method (WebApps)

• Login to the chosen server as the chosen user.

• Insert the WOW CD into the server CD drive

• 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 willappear. 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.

Stage 1 – Installation Parameters

The installation script prompts for the following parameters:



14/71

• WOW server hostname: the name of the system on which Apache will run: see pre-installation considerations. This is referred to as hereafter.

• WOW server full URL: if DNS is configured this will default successfully, if not, enterhttp://.

• WOW user: defaults to the user name you are using to run the install script: see pre-installation considerations.

• WOW user’s group: the default group of the user running Apache. Confirm thedefault.

• WOW_HOME: the location where you have extracted the WOW software, by default$OWHOME/WebApps. Confirm the default value.

• ORACLE_HOME: the ORACLE_HOME location, default taken from the environment.Confirm the default value.

• ORACLE_SID: the ORACLE_SID location, default taken from the environment.

Confirm the default value.

• OWSYSSID: the default OpenWorks projects ORACLE_SID location in a multi-instance environment, defaults to ORACLE_SID if not set in the environment. Confirmthe default in single instance sites – otherwise check with your data administrator.

• OW_PMPATH: the default configuration directory for OpenWorks and SeisWorksprojects, default is $OWHOME/conf if not set in the environment. It is important to set

this to a sensible default if the site uses multiple OW_PMPATHs.

• LM_LICENSE_FILE: the location of the OpenWorks license file, defaults to$OWHOME/lam/license.dat if not set in the environment.

• Administrator’s email: this email address is used in error messages when Apachehas internal errors. Specify the system administrator’s 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 dataadministrators, to whom error form output will be sent. The forms will only work if Unixemail is configured to work internally – see the Notes on WOW email section andcheck 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.

During this stage the $OWHOME/WebApps/conf/wow.env file is created containing allthe variables required by WOW. This is the single most important configuration file forWOW; see Appendix 1 for an example and Appendix 2 for a list of all configuration files.



15/71

Stage 2 – Configuring WOW Shells/Documenter

During this stage the installation script modifies environmental variables in the WOW tree,loads the WOW Documenter (kdoc) OWSYS extension and runs tests on the main WOWshell (lmksh). See Appendix 5 for further background on the devkit shells.

Stage 3 – Configuring Apache

The installation of Apache must be run as root. This step will create a ‘root.sh’ file for

execution as root in a separate xterm. We assume that the selected system is NOTalready running Apache and that the default port of 80 is available.

The root.sh script does the following:

• Creates the Apache configuration file httpd.conf in/etc/apache (Solaris) or /etc/httpd/conf (Linux).

• Starts Apache

• Creates an example password file, containing the installation user only (withusername as password) and further configures WOW for level B or C security. Seethe Security section for more detail.

• Copies the WOW default index.html to the Apache web root directory.

Run $OWHOME/WebApps/install/root.sh as root before continuing. You should get

a message indicating that Apache has been started successfully.

To check the installation, run netscape or other Unix browser, typing in the indicatedURL, e.g. http://. . This should display an Apache

message saying ‘It Worked!’. To test PC connectivity, try the same URL in a PC browser.

Stage 4 – Finalizing the Install

• Location(s) for Z-MAP Plus browsing: you will be asked for zero, one or manydirectories containing Z-MAP Plus data. If a single location is chosen, it will be linkedto $OWHOME/WebApps/htdocs/zmap_data . If you request multiple locations, thesewill be linked into $OWHOME/WebApps/htdocs/zmap_data . In many sites these

data can be quite widely scattered, so WOW provides a convenient groupingmechanism.

• Location(s) for OpenJournal data browsing: you will be asked for zero, one ormany 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 ormany 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 manydirectories containing SEG-Y or LAS data. Details as above, using location$OWHOME/WebApps/htdocs/other_data


16/71

• Location of ‘Subscription’ directory: specify a location where the results ofsubscription requests will be written. This is any directory with ~100Mb free diskspace. The directory will be created if it does not exist and linked to$OWHOME/WebApps/htdocs/push_output . It also creates a sample crontab file in$OWHOME/WebApps/install/wow_crontab . See the Subscription section later inthis document.

A message will indicate complete installation. Try the final URL in the browser, i.e.http://. . Once the license is installed (see next section)

WOW should be fully functional. See the Troubleshooting section if errors areencountered.

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 viewedthrough 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 anenvironmental variable, which helps sharing documents between Unix and PCfilesystems. In $OWHOME/WebApps/conf/wow.env , specify the name of a KRSenvironmental 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 allowyour 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.

Patching the Installation

WOW patches are designed as simple compatible additions or replacements of existingfiles in the software directories. Patches are provided as a series of compressed tar files,available from the Landmark ftp server isite.lgc.com, directory/products/WOW/Supported_Patches . Contact your customer support representativefor isite login details. The current patch level is R2003.3.1.5.

Since R2003.3.1, a new ‘rolling patch’ has been introduced. The objective is to fix bugswith days and update a continuous ‘rolling patch’, so customers do not have to waitmonths for the next official patch. This patch is on isite, directory/products/WOW/Rolling_Patch .

To install a patch, copy it to your install location, typically $OWHOME/WebApps. See theassociated README for detailed installation instructions.

Current patch level can be obtained by clicking on ‘About’ on the WOW browser interface.



17/71

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)

This is the end of the compulsory installation process.

To modify the default security sections or to add additional users, read the Security section.

If the site uses multiple OW_PMPATHs, read also the OW_PMPATH section.

If the site has multiple Oracle instances, read the Multiple Oracle Instances section.

If the site has WOW Documenter (‘kdoc’) records from R98, see the Customizing WOWDocumenter section.



18/71

Configuring Security Options

This discussion applies to the WOW browser client only. The Unix Documenter GUI obeysidentical Unix file permissions as SeisWorks, HrzUtil or any other SeisWorks utility.

There are a number of different options for implementing security in WOW, from universal

read-only access to enforcement of access rights, as if the user was trying to access theactual Unix project. Specified ‘tight’ projects can be restricted entirely. In the currentrelease, the application is largely read-only. The default is therefore a generally openapproach, but with all write-back options requiring authentication (level B).

Security Levels

Level A – Universal read-only with named exclusions: Any user that can login toany system over the company network can access all OpenWorks, SeisWorks andZ-MAP Plus data, read-only, except for named exclusions. Nobody can see namedexclusions, which protects sensitive data. The main advantage of level A security is that itis a low-maintenance approach, but it does require a company to have an open approachto sharing technical data. The main disadvantage is that even legitimate users cannotaccess restricted projects. Also, access to all write-back functionality (e.g. list creation,WOW Documenter and Subscriptions) is denied under Level A security.

Level C – Full emulation: As above, but users are required to login at all times. Theauthenticated username is then used to validate access at an individual project level,exactly as if the user is logging on to a Unix workstation in the site. This is as secure as theunderlying applications, but at the expense of extra administration to maintain thepassword file. Extra administration is also required to grant casual users access (e.g.Team Leaders, Drillers etc.). To access WOW, casual browsers will need to:• have Unix accounts• be added to Oracle as external users• be granted browser access to required OpenWorks projects

• be granted read-write access to required SeisWorks project directories (SeisWorksdoes not support read-only execution)

• be granted read-only access to required Z-MAP Plus directories and files.

Level B – Full emulation, but on a subset of functionality: An intermediate option, thisprovides full emulation but only on the write-back modules (e.g. creating well lists,adding/deleting KRS documents, adding/updating SeisWorks documentation). Universalbrowsing is thus encouraged without having to provide a password, but as soon as anattempt is made to write back to the database (e.g. loading a KRS document), the user isprompted for a login and password. This is the default security level.

Important note: To enjoy the full functionality of WOW, Level B or above security isstrongly recommended.

Configuring Security Level A

Access is restricted to projects and directories by modifying files in the$OWHOME/WebApps/conf directory as described below.


OpenWorks: modify the OW_PROJ_WHERE_CLAUSE in$OWHOME/WebApps/conf/wow.env to restrict projects to those that have a particular


19/71

name or comment. Modifying this requires a degree of SQL knowledge; please contactsupport 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 furtheraccessible.

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 createdduring installation with only the install user added. The format for the password file isidentical to that of a Solaris passwd file, except that only the first two fields (user andencrypted 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 criteriasuch 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 thehtpasswd 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. byscheduling a cron job to refresh it at regular intervals. If you uses NIS, it is possible toauthenticate 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 lines. For level Bsecurity, uncomment the lines.cd $OWHOME/WebApps/cgi-binvi .htaccess


# For level C security comment


20/71

#

AuthType basic

AuthName "WOW Unix" (a descriptive name for the authorization form) AuthUserFile "/etc/apache/.wp"

Require valid-user#

# For level B security uncomment

AuthType basic

AuthName "WOW Unix" (a descriptive name for the authorization form)AuthUserFile "/etc/apache/.wp"Require valid-user

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 createdon the fly in WOW. This section explains how to protect certain static documents, e.g. anOpenJournal project, which requires selective security. The restricted dir list mechanismdescribed for level 2 security provides blanket protection for certain directories, but evenlegitimate 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 thatthis 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 basicAuthName "Tight OJ Projects"

AuthUserFile "/etc/apache/.ojpasswd"Require valid-user

3. Copy .htaccess to the required directory. Place the file into all directories thatrequire 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 toAuthConfig within the ”

stanza (approx. line 390).


5. Restart Apache: /usr/apache/bin/apachectl restart (Solaris) /usr/sbin/apachectl restart (Linux)


21/71

Configuring Multiple OW_PMPATHs

Many Landmark sites, in particular those with large numbers of SeisWorks projects,subset their SeisWorks configuration files using multiple OW_PMPATHs. EachOW_PMPATH contains a unique plist.dat, dir.dat and lgcenv.cf.

The most common scenario is to have a number of conf_xxx subdirectories under$OWHOME in parallel to the default Landmark $OWHOME/conf directory, e.g. conf_sns,conf_nns, conf_wos etc. Or a completely new directory may be created, e.g./data/conf with subdirectories of sns, cns, wos etc.

Some companies use a site-specific customized environment called Common ApplicationInterface (CAI). Although supported on a site-by-site basis on existing installations,Landmark is no longer offering CAI to new sites. WOW installations can however beconfigured in CAI environments.

In both custom OW_PMPATH and CAI situations, it must be possible to uniquely identifythe names and locations for the OW_PMPATH directories. These should be added to the

wow_distlist.dat file in

$OWHOME/WebApps/conf.

cd $OWHOME/WebApps/confcp wow_distlist.dat.default wow_distlist.datvi wow_distlist.dat

######################################################################## This file contains a list of SeisWorks districts. It comprises:# - district# - associated OW_PMPATH location# - a common name for the district# - associated OWSYSSID#

# You MUST ensure that all OWSYSSIDs referenced are in wow_sidlist.dat#######################################################################d1 /data3/bruce/conf_d1 "District D1" owproddr /data3/bruce/conf_dr "GOM Regional" owexplordx /data3/bruce/conf_dx "GOM Deepwater" owexplorall /data3/bruce/conf_all "Composite" owprod

Alternatively, the WOW Apache owner can configure this file through the browser byclicking 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 changethe 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.



22/71

Configuring Multiple Oracle Instances

Dynamic support for multiple Oracle instances (ORACLE_SID/OWSYSSID) isincorporated with WOW since release R2003.0.3.1. This enables users to browse data inmultiple instances, and to carry out cross-project comparisons between instances.

The Instance Configuration File

To enable multiple instance functionality, edit$OWHOME/WebApps/conf/wow_sidlist.dat and list entries of ORACLE_SIDscontaining OpenWorks projects. Ensure that all entries are also in the Oracletnsnames.ora file, located in $TNS_ADMIN or$ORACLE_HOME/network/admin .

cd $OWHOME/WebApps/confcp wow_sidlist.dat.default wow_sidlist.dat

vi wow_sidlist.dat

###############################################################################

# This file contains a list of Oracle SIDs available for project comparison# Note: SIDs referenced below MUST be added to the tnsnames.ora file# in $TNS_ADMIN or $ORACLE_HOME/network/admin###############################################################################owden “Denver (local)”owcal Calgaryowabz Aberdeen#owstv Stavanger (offline)owhst Houston


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 locallyand ‘remembers’ it until changed by any user on the same client.

Alternative Options

Before configuring WOW for multiple instances, note that WOW supports withoutconfiguration the specific cases where OpenExplorer Advanced Project Management(APM) is configured, or where the ‘remote project’ facility is used. Under thesecircumstances 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 visibleand can be accessed.

Note also that the following are also possible:

• Install an Apache server per Oracle instance. Although this sounds inefficient, Apacheis a considerably ‘lighter’ process than Oracle and does not add much overhead.

• The $OWHOME/WebApps/conf/wow.env variable for ORACLE_SID and/or

OWSYSSID variable can be changed if necessary, to point to another instance. Onlyone instance can be browsed at a time by this method.



23/71

Configuring Subscription Tools and Email

The subscription or ‘push’ tools allow users to request automatic notification by email in theevent that data are changed or added within a registered area of interest – by specifiedproject, geographic area or data type.

These tools allow users to establish, view and modify their subscriptions directly throughhtml forms. A series of cron jobs execute queries, which compose emails providing userswith 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 Apacheuser. 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:

setenv EDITOR vi

crontab -e0 4 * * 2-6 /your/OWHOME/WebApps/bin/DoPush Daily

0 4 * * 1 /your/OWHOME/WebApps/bin/DoPush Weekly

0 4 1 * * /your/OWHOME/WebApps/bin/DoPush Monthly

Notes on WOW Email

The subscription module described above, as well as the data error and feedback forms,rely on Unix email to be configured. Many sites are configured such that mail sent fromUnix will go to the recipient’s in-house PC email system. Few allow external emailconnections.

To test whether your site is configured for internal Unix->PC email, type:

nslookup mailhost

If this command returns an error, WOW cannot send mail to your PC email account. If itreturns a valid IP address for the mailhost, try a test email as follows:

/usr/lib/sendmail –i -tTo: Subject: Test Email

This is a test email sent by WOW

The email should appear in your PC email within a few minutes.

If internal Unix->PC email is not configured, you do have the option of selecting a pureUnix email address (same as Unix account name) as the email recipient duringinstallation, but this is not recommended.



24/71

Customizing the WOW Interface

Although WOW will install and run ‘out of the box’, it is designed to form part of a largersubsurface E&P portal. For example, the portal would cover project databases via WOW,other internal databases, links to EDMS systems, external links etc. WOW behavesidentically to any other Web site that contains a combination of static and dynamic content.

This means that WOW URLs can be called from or embedded in any other Web page.

Knowledge of html and Web authoring is required to create Web pages that invoke WOWcomponents. The static pages that provide the default WOW interface reside in$OWHOME/WebApps/htdocs. Landmark recommends that you do NOT modify thesefiles. Rather, create a new Web page that calls the relevant WOW file or dynamic URLdirectly.

The ‘home page’ for the Apache installation is /var/apache/htdocs/index.html (Solaris) or /var/www/html/index.html (Linux). This file is replaced with the WOW

home page on installation, but any client-provided page may be used. In this case, the fullWOW URL is http://./wow/ , with the trailing slash required by

Apache.

To revert to the simpler URL http://. without the ‘/wow/’ (if the Apache server is not used other than by WOW), replace the default Apache index.html filewith the WOW index.html (as root):cd /var/apache/htdocs (Solaris) cd /var/www/html (Linux) cp index.html index.html.orig

cp $OWHOME/WebApps/htdocs/index.html .

The WOW left frame menu is partly customizable. This allows site administrators to addlinks below the WOW links, by modifying a simple configuration file. See$OWHOME/WebApps/conf/wow_menu.dat for details.

cd $OWHOME/WebApps/conf

cp wow_menu.dat.default wow_menu.datvi wow_menu.dat

################################################################################ This file contains metadata for adding links to the WOW left frame# It consists of the following tab-delimited fields:# Name: short name for the link, e.g. "Landmark Graphics"# URL: fully-specified URL, e.g. http://www.lgc.com# Note: use double quotes for entries with a space in the name###############################################################################"Landmark Graphics" http://wow.lgc.com

"E&P Home Page" http://www.oilco.com/eandp




25/71

Browsing Unix Directories

Recognizing specific file types

The Z-MAP Plus, OpenJournal, OpenExplorer and ‘Other Data’ modules run the same file-and directory-parsing function. The function is hard-coded to recognize certain file types,

e.g. MFDs and ZGFs, as well as certain structures, e.g. OpenJournal projects. There arealso two special categories for files of the following types:

• files that are composed only of ASCII characters

• 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 ableto view through WOW, then do the following:cd $OWHOME/WebApps/conf

cp ascii_file_extensions.dat.default ascii_file_extensions.datvi 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 byclicking on ‘Admin’ on the WOW top bar.

Important note: WOW is a server-side application, i.e. files are processed on the webserver and results (html or images) sent to the Web browser. This is the only way in whichfiles like MFDs, ZGFs, seismic and horizons can be displayed. Standard mime typesbehave differently: they are supported directly by the browser and are thereforedownloaded 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 file-and directory-parsing function, which looks for a specific hard-coded start directory:

Z-MAP Plus: $OWHOME/WebApps/htdocs/zmap_dataOpenJournal: $OWHOME/WebApps/htdocs/openjournal_dataOpenExplorer: $OWHOME/WebApps/htdocs/openexplorer_dataOther 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 thislocation to the multiple start directories, e.g.mkdir $OWHOME/WebApps/htdocs/other_data

ln –s /data/misc/vendors/segyfiles



26/71

$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 hiddenrapidly. If the parent directory or link does not exist, an error message will be returned.

Adding External ‘Links’

The ‘Links’ button allows a site to rapidly integrate other intranet or Internet data,information and knowledge sources within WOW. Essentially this provides a mechanismfor adding hypertext links to a web page without needing to update static html – the pageis generated dynamically from a simple configuration file. Links can also be searched,sorted and saved to Excel.

The configuration file is $OWHOME/WebApps/conf/wow_links.dat . This contains one

link per line with four space-delimited fields (see example below).

Important note: the format of this file has changed from pipe-delimited to space delimited.

• Name: a descriptive name for the information source, e.g. DEAL

• Description: a full description of the source

• URL: the full hypertext link to the information source

• Icon: an optional logo file, which if specified should exist in$OWHOME/WebApps/htdocs/logos

################################################################################ 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 belowName 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 sizesTag height=50###############################################################################CDA “UK seismic and well data” http://www.cdal.com cda_logo.jpgDEAL “Index of UKCS geotechnical data” http://www.ukdeal.co.uk deal_logo.jpgLIFT “Promoting asset opportunities” http://www.uklift.co.uk lift_logo.gifDTI “Released UK well/license/prod data” http://www.og.dti.gov.uk dti_logo.gifIndigoPool.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




27/71

OpenWorks QC/QA Queries

The QC/QA module allows the storage and execution of SQL queries against OpenWorksprojects. It differs from the stored queries in OpenWorks in that queries are ‘global’, i.e.they are stored once without needing to be copied between projects. Multiple queries canbe run sequentially against a single project, or a single query can be run across multiple

projects. The objective is to run a series of queries that provide a project health check, e.g.wells without KB, wells without TD etc.

Important note: The QC/QA logic as expressed in these queries may not apply to allsites, or made need modification based on local conditions. These queries are not meantto be universally applicable and infallible. Although a standard suite is provided as listedbelow, these may be copied to a site-specific version and edited. Editing the queries asprovided is not recommended, as edits will be overwritten by subsequent updates.

A suite of standard queries is provided.• Fields with 0 or null XY/LatLongs• Leases with blank names• Pick counts• Project data counts• Seismic surveys• Well checkshots with suspicious datums• Well curves > TD• Well curves with decimal/percent issues• Well curves with min/max values outside left/right scales• Well curves with possible duplication• Well curves with suspicious min/max values• Well curves with unknown units• Well list counts• Well picks > TD• Well picks with possible duplication

• Wells with 0 or null Lat/Longs• Wells with 0 or null XYs• Wells with 0 or null datum• Wells with 0 or null datum and pick/crv/log/poslogs• Wells with 0 or null total depth• Wells with blank common well names• Wells with directional survey but no poslog• Wells with poslog / TD mismatch• Wells with unknown status or symbol.

Queries can be edited or added to this list by copying a .sql file to the$OWHOME/WebApps/dat/sqlscripts directory. Files should follow a certain format toexecute properly within the browser:

Important points to note:

• 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 createthe hyperlink to. Currently well, field, lease and seis (navigation) data types aresupported. Set dtype to some other value if not a simple well, field or lease query.


28/71


29/71

WOW Documenter

Running WOW Documenter

The WOW Documenter allows the user to store extra information about SeisWorksinterpretations. It provides a spreadsheet-style, multi-object interface to the same

functionality within the WOW Web interface. The WOW Documenter requires the userhave at least ‘l_interp’ access to the associated OpenWorks project.

SeisWorks R2003.12 and above have adopted the WOW Documenter model. Use of theWOW 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 anyOpenWorks xterm simply by typing kdoc. A sample launcher.dat entry is alsoprovided in $OWHOME/WebApps/templates/launcher.dat.extra .

The graphical user interface is illustrated below:



30/71


31/71

3. DeleteFromLOV : deletes a value from the LOV

for the specified SeisWorks project LOV type

Example:

prompt> rlmksh

lmksh{1}% OWSetup; SeisSetUplmksh{2}% set lda [OWoralogon]lmksh{3}% GetLOV colt polarity

{SEG normal} {SEG reversed} UNKNOWNlmksh{4}% InsertIntoLOV colt polarity “UK Normal”lmksh{5}% InsertIntoLOV colt polarity “UK Reverse”

lmksh{6}% DeleteFromLOV colt polarity “SEG normal”lmksh{7}% DeleteFromLOV colt polarity “SEG reverse”

lmksh{8}% oralogoff $ldalmksh{9}% exit

Changes are made to existing extensions. To modify the lists at the point at which thedatamodel 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 Oraclecolumn comments, and may be modified. Once the datamodel extension is created,modification involves editing the appropriate SQL file then running the appropriate lmkshfunction. 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> lmkshlmksh{1}% UpdateOwsysExtension

For horizons and seismic edit update_pim_project_comments.sql and run thelmksh function UpdateProjectExtension. To ensure consistency between existing

projects and those yet to be created, it is important to make the same changes increate_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 WOWDocumenter tables within each project:

lmksh{1}% RemoveProjectExtension (repeat for each project)lmksh{2}% RemoveOwsysExtension



32/71

Moving Records Between OpenWorks Projects

If the SeisWorks-OpenWorks project association changes, i.e. if the SeisWorks project ismoved between two overlapping OpenWorks projects, then the WOW Documenterrecords pertaining to that SeisWorks project need to be transferred from the old to the newOpenWorks project as follows:

prompt> cd $OWHOME/WebApps/kdoc/sqlscriptsprompt> sqlplus /@$ORACLE_SID @kdoc_swproj_transfer

Important note: run this SQL script as a user that has MANAGE access to bothOpenWorks projects.

Moving Records Between OWSYS Tables

Clients with existing WOW Documenter data under R98.x may wish to import the projectrecords that are stored in the OWSYS tablespace, as described below.

1. Make a copy of the R98 owsys.pim_prj_info tablesqlplus owsys/owsys@create table temp_pim_prj_info as select * from pim_prj_info;exit

2. Export the R98 OWSYS Documenter tablesexp owsys/owsys@ file=kdoc.dmptables=temp_pim_prj_info,pimr_company,pimr_interp_statusgrants=n Check that records are exported and that the import terminates successfully.

3. Delete the automatically created records from the R2003 OWSYSsqlplus owsys/owsys@

delete from pim_prj_info;delete from pimr_company;delete from pimr_interp_status;exit

4. Import data into the R2003 OWSYSimp owsys/owsys@ file=kdoc.dmp full=y ignore=y Check that records are imported and that the import terminates successfully.

5. Copy data from temp_pim_prj_info to pim_prj_infocd $OWHOME/WebApps/kdoc/sqlscripts sqlplus owsys/owsys@ @kdoc_owsys_copy

6. Drop the temporary table after checking resultsdrop table temp_pim_prj_info;

Important note: Execute this process before loading new data to the Documenter tables.



33/71

Integrating with CDA

Corporate Data Archiver (CDA) can be used to generate ‘throwaway’ stubs which produceimage thumbnails for re-use within WOW. These options are provided for OpenWorks,SeisWorks and GeoProbe projects. This functionality is designed to facilitate a projectcleanup operation, e.g. deleting empty horizons and intermediate processing seismic

volumes. Note that a CDARCHIVE license is required in order to exercise this option.

The option to generate, regenerate or view an existing archive stub is provided on theOpenWorks and SeisWorks project summary pages. Clicking this link brings up a CDAcontrol file editor. Once created, the stub can be previewed directly. Use an archive projectname of ‘Stubs’ to create thumbnails in a fixed location, for re-use in the WOW horizonand seismic list builders.

Important note: for sites not wishing to allow archive generation through the browser, addthe following line to $OWHOME/WebApps/conf/wow.env :ARCHIVE_BROWSER_FLAG=REQUEST; export ARCHIVE_BROWSER_FLAG

This will replace the link to generate archive with a link to request archive generation,which sends email to the CDA administrator.

The SeisWorks horizon and seismic list builders are accessible from the ‘page’ links on theSeisWorks project summary page. They allow browsing horizons and seismic a page at atime, drilling down to view details or selecting objects to save or append a list.

The web interface is illustrated below:

Thumbnails generated in the 'Stubs' projects will also appear in the horizon and seismicdocumentation pages in WOW, making the process considerable easier.



34/71

List-based Deletion

Command-line scripts are provided to delete lists of horizons and seismic created usingthe 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 HrzListDeleteln –s lmksh_wrapper SeisListDelete

To execute the deletion:HrzListDelete SeisListDelete



35/71

Referencing External Documents for SeisWorks 2D

The WOW Documenter model allows attributes and comments to be added against the‘proclev’, rather than against an individual seismic line 2v2 file. Therefore all lines thatshare the same proclev, e.g. mig080001, share the same documentation. In somecircumstances however it may be preferable to reference a unique document for every line

that has a certain processing level. For example, there may be a vendor-providedacquisition and processing report containing velocity data for each 2v2 file.

The OpenExplorer KRS document reference also cannot be used to store a documentrelated to a non-OpenWorks object such as a SeisWorks 2v2 file.

To overcome these limitations, WOW provides a simple mechanism to allow the display ofplain text files on a per-2v2 basis. To enable this, create a file .docs inside the 2D master project system directory. This file should contain a simple lookup listbetween 2v2 file name and external documentation file name, e.g.:

#

# File .docs

# File contains a list of 2v2 name vs. external text file.

# Place this file in the master project system directory.

#

CAGC-001-UA7A_________mig00000101.2v2_glb /fullpathto/CAGC01U7.filt.Veritas.01.txt



CAGC-001-UA10_________mig00000101.2v2_glb /fullpathto/CAGC01U10.filt.Veritas.01.txt

CAGC-001-UA10_________mig00000101.2v2_glb /fullpathto/CAGC01U11.filt.Veritas.01.txt

The file .docs can be generated via simple Unix commands andthen edited to add in the text references as appropriate, e.g.ls *01.2v2_glb > .docs

Blank lines, lines beginning with ‘#’ and lines with only one entry are safely skipped.

If the .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 isprovided as a link below the seismic header table.



36/71

Creating ‘Live Trace’ Outlines

The ‘Live Trace’ Algorithm

The algorithm is designed to display the actual extent of 2D or 3D seismic traces, ratherthan the navigation extents. In the 2D case, the output shows exactly which lines or parts

thereof have the specified processed level.

In the 3D case, the output attempts to show the exact shape or outline where traces existwithin the rectangular project limits. The 3D algorithm operates by walking clockwisearound the outside of the survey, until it returns to the starting point. The algorithm doesnot read every trace, which makes it considerably faster, but it consequently cannot handlethe following scenarios:

• Internal holes within the survey

• Non-contiguous pieces of seismic data

•

Surveys where e.g. every 2nd line or trace is loaded

• 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 notalways succeed.

Customizing the Algorithm

WOW aims to dynamically create Web pages or images on the fly, i.e. without resorting tostatic, pre-created files. Seismic trace outlines present a real challenge in this regard. 3Dvolumes containing many millions or traces may not complete within the patiencethreshold of a typical user.

A batch mechanism is therefore provided to auto-generate the live trace outlines as pngimages, ESRI shapefiles (3D only), ASCII coordinate files (3D only) or ZGF pictures (3Donly). Pre-generated png images in the project system directory will display by default inWOW.

Options are provided to generate outlines in these formats for a single volume, all volumeswithin 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}% SeisSetUp lmksh{2}% seis2png devnor 3 mig0801.3dv 25 15 50 50 800 40 tmp.png

lmksh{3}% seis2png devnor 3 mig0801.3dv 25 15 50 50 800 40 tmp.shp

lmksh{4}% seis2png devnor 3 mig0801.3dv 25 15 50 50 800 40 none tmp.zgf

outline

Note that the output file extension determines the output type. Note also the differentsyntax for ZGF file output. See the next section for a simpler mechanism for generatingoutlines over all volumes in a project.



37/71

Arguments are:

SeisWorks project name

2 for 2D, 3 for 3D

seismic file name or proclev, e.g. mig0801.3dv or mig080001

look-ahead factor (default 25 traces – 3D only) thinning distance (default 10 traces – 3D only)

line increment for symbol posting (default 100 – 3D only)

trace increment for symbol posting (default 100)

approximate image size, in pixels (default 500)

padding around image, in pixels (default 40)

output image file name (default stdout).

An alternative 3D-only algorithm that does read every trace is currently underdevelopment. Although it is considerably slower, it can handle internal holes within thesurvey, non-contiguous pieces of seismic data, and decimated surveys. To test thisalgorithm, 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 orDo3DSeismaps. This includes a ‘clobber’ argument (3D only), allowing you to regenerateall images (clobber) or only regenerate if the seismic has been modified since the last livetrace outline was created (noclobber). Note that an output file name need not be specifiedas the png, ascii or zgf file is placed in the project sys directory with the following namingconvention:

png image: //..png

ASCII file: //..asc

ZGF file: //_outlines.zgf

(Each seismic volume produces a single picture within the ZGF file.)

Shapefile: //_outlines.shp(Each seismic volume produces a single shape within the shapefile.)

Do2DSeismaps arguments are:



approximate image size, in pixels (default 500).



38/71

Do3DSeismaps arguments are:


png, asc, zgf or shp

default is ‘noclobber’, i.e. only regenerate if the seismic has changed

look-ahead factor for 3D (default 25 traces)

thinning distance for 3D (default 10 traces) line increment for symbol posting (default 100 – ignored for 2D)


approximate image size, in pixels (default 500).

Examples:

lmksh{1}% Do3DSeismaps devnor png (generates default png pictures) lmksh{1}% Do3DSeismaps devnor png clobber 25 10 50 50 800

(overwrite the defaults with new parameters).

Generating Outlines for all Projects

Finally, to generate outlines for all 2D or 3D projects, the scripts$OWHOME/WebApps/bin/ DoAll2DSeismaps.sh and DoAll3DSeismaps.sh will

run on the command line with options as shown below. For 3D, specify the –c flag to‘clobber’; skip it for ‘noclobber’.

prompt> DoAll2DSeismaps.sh -t -x

prompt> DoAll3DSeismaps.sh –c –f –s -d -l - t -x

Computing Lat/Long Outlines

To convert the ASCII live trace outlines from XY to Lat/Long coordinates, you can run ageneral purpose command-line conversion on an ASCII file as follows:ConvertFileXYtoLL

The utility takes as input a columnar ASCII file and computes/inserts latitude and longitudefor the specified column IDs containing the X and Y coordinates. The CRS information istaken from the specified OpenWorks project. You will need to delete or insert a ‘#’ beforeany header lines in the ASCII line. The reverse ConvertFileLLtoXY can also be used.



39/71

Using ZGF Backdrops

The SeisWorks navigation, live trace outline and horizon map displays can be enhancedthrough the use of ZGF cultural backdrops. This allows the maps to include wells, fields,leases, bathymetry, coastlines, shipping lanes etc. – whatever is in the specified ZGFpicture.

ZGFs are ideal for cultural backdrops, in that they are the Landmark standard neutralbackdrop culture format. They are widely used across applications and can be created inSeisWorks, StratWorks, Z-MAP Plus and via the Map Data Manager.

There is however no accepted default naming convention or even location for these files –they are often, but not universally, stored in the ZGF subdirectory of the OW_PROJ_DATAdirectory of the associated OpenWorks project.

WOW therefore needs to provide a flexible, customizable way of specifying which ZGFand picture to use for which SeisWorks project. Three locations are searched in order,from most specific to most general:

1. WOW first looks for a file named .wow_backdrop in the SeisWorks system directory.This is a simple ASCII text file containing two lines: the fully-pathed ZGF file name andthe picture name, e.g./data/seisworks/d0/colt/culture.zgfGOM culture basemap

This allows any ZGF and any picture to be used, irrespective of file location.

2. If there is no .wow_backdrop file in the SeisWorks system directory, the next searchis for a file in the SeisWorks system directory named wow_backdrop.zgf. The first

picture from this file is displayed.

3. If there is neither a .wow_backdrop nor a wow_backdrop.zgf file in the

SeisWorks project system directory, the OW_PROJ_DATA ZGF associatedOpenWorks project directories are searched in order for a wow_backdrop.zgf file.

Again, the first picture from this file is used.

The advantage of option 3 above is that a single ZGF can be used as backdrop to allSeisWorks projects associated with a single OpenWorks project. Options 2 and 1 allow forincreasingly more restrictive choices.

Important note: Unix filesystem links are all that is required to ‘expose’ a culturalbackdrop. For example, if you already have existing ZGF files with arbitrary names:cd //ZGF

ln –s wow_backdrop.zgf

Note also that the batch generation of seismic live trace outlines, using script

WOW Release Notes

Documents

Transcript of WOW Release Notes