WOW Software 5000.0.1.11 Release Notes and Administration Manual Contents Third Party Applications ................................................................................................................. 2 International Trade Compliance .................................................................................................... 3 Introduction .....................................................................................................................................
Third Party Applications Halliburton uses various third-party applications in the development of its software. Halliburton acknowledges that certain third party code has been bundled with, or embedded in, its software. The licensors of this third party code, and the terms and conditions of their respective licenses, may be found at the following locations: $OWHOME/docs/third_party.pdf $OWHOME/WebApps/tcltk/license.terms WOW is part of Halliburton’s WebApps technology framework.
International Trade Compliance This application is manufactured or designed using U.S. origin technology and is therefore subject to the export control laws of the United States. Any use or further disposition of such items is subject to U.S. law. Exports from the United States and any re-export thereafter may require a formal export license authorization from the government. If there are doubts about the requirements of the applicable law, it is recommended that the buyer obtain qualified legal advice.
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 information available to business users in time to facilitate decisions.
Enhancements and Fixes Version 5000.0.1.11 Important note: WOW 5000.0.1.11 is an update, which does not require re-installation of the WebApps software tree. See Patching the Installation for patch location and installation instructions. WebApps 5000.0.1.11 is compatible with OpenWorks 5000.8.3.01 and above. 1. OpenWorks/SeisWorks: change default project listing to display project hierarchy rather than just PDBs by default. For SeisWorks-mode projects change default grouping to be per project.
Version 5000.0.1.10 WOW 5000.0.1.10 is an update, which does not require re-installation of the WebApps software tree. This update is compatible with OpenWorks 5000.8.3.01 and above. 1. Shapefiles: also copy .prj file if it exists when creating shapefiles from ZGF files in OpenWorks project directories (defect 919765). 2. SeisLTO3D: add seismic line/trace to ASCII output option (defect 912486). 3. PickReport: fixed error running on projects with over 15 characters in their name (defect 920331). 4.
Version 5000.0.1.8 WOW 5000.0.1.8 is an update, which does not require re-installation of the WebApps software tree. This update is compatible with OpenWorks 5000.8.0.0 and above. 1. General: new dark color scheme used by default, original light scheme still available. 2. OpenWorks: added new cross-district OpenWorks project data map to display data counts, remarks, CRS, measurement system and other information for all projects in the WOW instance. 3.
Version 5000.0.1.7 WOW 5000.0.1.7 is an update, which does not require re-installation of the WebApps software tree. This update is compatible with OpenWorks 5000.8.0.0 and above. 1. QC/QA: provide option to save results for all projects to a single table when running in cross-project mode (defect 900846). 2. Shapefiles: allow user to specify top or bottom hole location for OpenWorks well shapefiles (defect 899015). 3. Shapefiles: copy project-specific .
3. OpenWorks: added additional queries to check for well header denormalization issues for spud/completion dates and formation at TD. 4. OpenWorks: added additional attributes to well location page (country, state, county, on/offshore flag) and to the real-time monitoring curves report (increment, depth units and mode). 5. OpenWorks: fixed issue when displaying well coordinates for IPs with a geographically-projected PDB (defect 886789). 6.
Version 5000.0.1.3 WOW 5000.0.1.3 is an update, which does not require re-installation of the WebApps software tree. This update is compatible with OpenWorks 5000.8.0.0 and above. 1. QC/QA: clearly annotate certain queries that are only applicable on project databases, e.g. orphan vector detection queries (defect 875442). 2. Subscriptions: trap login failure if the executing user does not have access to a particular instance (defect 875555). 3.
Version 5000.0.1.1 WOW 5000.0.1.1 is an update, which does not require re-installation of the WebApps software tree. This update is compatible with OpenWorks 5000.0.3.0 and above. 1. Added support for Oracle 11 with OpenWorks 5000.0.3.5. 2. Added optional district support for Z-MAP Plus, Other Data, GeoProbe and VIP modules, i.e. restrict displayed data based on current district selection (defect 856038). 3. Added support for GeoProbe V2 ascii/binary horizon file formats (defect 850103). 4.
6. Added a Well Status page displaying well symbols, launched from the OpenWorks Project Summary page. 7. Added a Well Location page, launched from the Well Summary page (defect 853278). 8. Added option to the “Lat/Lon ⇔ XY Calculator” to support conversion to and from WGS84 (defect 850172). 9. Automatically display ZGF picture thumbnails, if generated by CDA ZgfThumbs, when browsing OpenWorks project external data ZGF directory (defect 849517). 10.
Known Problems The addition of attributes to the Live Trace Outline shapefile dbf output (version 5000.0.1.8, defect 904045/6) means that preexisting shapefiles cannot be appended, they must be recreated. When running the SeisLTO GUI over multiple volumes, check that ‘Overwrite’ is set to ‘Yes’. For command-line versions of this module, specify the ‘clobber’ flag. When running through the WOW browser, the error ow_seismic_lto.
Pre-Installation Planning Minimum Requirements The minimum requirement for the WOW server is: Server Hardware: Intel Pentium IA32 or X86_64 processor, 2 GB RAM, 4 GB swap, 200 MB disk space for software installation. Server Operating System: Red Hat Enterprise Linux 4 or 5. Server Application Software: Apache version 2, OpenWorks R5000.0.3.x. Important note: WOW does not work with SELinux. SELinux must be disabled. Note that WOW is a server-side application.
6. The domain name for the site. This will default correctly during installation if the site uses DNS to allow the resolving of domain names. To test this, type: nslookup in a Linux xterm or at the DOS command prompt. The value returned by the Linux domainname command is not the correct domain name. If nslookup returns an error, you will need to determine whether the host name is visible across the site network. To do this, type ping from a DOS prompt on a PC.
Installation The latest WOW point product release can be obtained by electronic delivery using the Landmark Software Manager (requires PeopleSoft login and password). The downloadable setup.tar.gz file is listed under the product name WebApps, and includes WOW, Corporate Data Archiver, and Project Administrator. Alternatively, the media can be obtained on DVD. The release requires re-installation (new sites) or upgrade (existing sites) of the WebApps software, as described below.
• Continue through the installation wizard, accepting license terms and confirming OWHOME and WOW_HOME locations. After the files are extracted, continue with the WebAppsInstall installation script as documented below. Important note: the WebApps post installation script can be re-run if required, i.e. without rerunning the InstallAnywhere installer: cd $OWHOME/WebApps/install .
• Apache administrator’s email: this email address is used in error messages when Apache has internal errors. Specify the system administrator’s email. • Company email suffix: the part of your company email addresses following the @ symbol, e.g. shell.com • Data administrator’s email: a comma-separated list of email addresses for the data administrators, to whom error form output will be sent. The forms will only work if email is configured to work internally – see the Notes on WOW email section.
• Creates an example password file in the Apache configuration directory, containing the installation user only (with same 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. • Copies the WOW favicon.ico to the Apache web root directory. Run $OWHOME/WebApps/install/root.sh as root before continuing.
Configuring Districts Support for districts – collections of project data typically based on geographic or business unit criteria – is provided by OpenWorks in R5000. No additional configuration is required within WOW. Districts are listed in the OpenWorks configuration directory $OW_CONF_DIR (typically $OWHOME/conf) district.dat file. The district is set on a per-client basis by clicking on ‘Change District/SID’ on the WOW top bar.
5000.0.1.5 – update compatible with OpenWorks 5000.8.0.0 (June 2012) 5000.0.1.6 – update compatible with OpenWorks 5000.8.0.0 (September 2012) 5000.0.1.7 – update compatible with OpenWorks 5000.8.0.0 (December 2012) 5000.0.1.8 – update compatible with OpenWorks 5000.8.0.0 (March 2013) 5000.0.1.9 – update compatible with OpenWorks 5000.8.3.01 (June 2013) 5000.0.1.10 – update compatible with OpenWorks 5000.8.3.01 (September 2013) 5000.0.1.11 – update compatible with OpenWorks 5000.8.3.
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 Z-MAP Plus, GeoProbe, VIP, ProMAX or AssetJournal, read the Configuring Other Landmark Applications section. WOW 5000.0.1.
Configuring Security Options This section applies to the WOW browser client only. All WOW command-line and GUI utilities obeys identical Oracle and Linux file permissions as any other OpenWorks or SeisWorks utility. All WOW operations are actually executed by the WOW Apache user. Security levels as described below only emulate end user access. To perform a particular operation in WOW, both the WOW Apache user and the end user must have legitimate access.
Adding Users to the Apache Password File A default password file is created during installation with only the install user added. Adding additional users requires root access for permission to edit the password file /etc/httpd/conf/.wp. Updating the password file using ypcat. The format for the password file is identical to that of a Linux passwd file, except that only the first two fields (user and encrypted password) are used.
2. Update wow.env: prompt> 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 AssetJournal project, which requires selective security.
Configuring Other Landmark Applications Z-MAP Plus / Other Data Unlike OpenWorks and SeisWorks which have strong project management, Z-MAP Plus and some other data can be widely scattered in different locations. WOW needs to know where to look for these data. The methodology employed is to maintain a list of parent directories in configuration files in $OWHOME/WebApps/conf. For Z-MAP Plus, the directories specified are simply start points for directory browsing, i.e. no project structure is assumed.
prompt> cd $OWHOME/WebApps/conf prompt> cp ascii_file_extensions.dat.default ascii_file_extensions.dat prompt> vi ascii_file_extensions.dat And add in file extensions as required. A similar approach can be adopted for common mime types using the file $OWHOME/WebApps/conf/web_file_extensions.dat. Members of the WOW_ADMIN_GROUP can configure both these files through the browser by clicking on ‘Admin’ on the WOW top bar.
prompt> cd $OWHOME/WebApps/conf prompt> cp vip_projdirs.dat.default vip_projdirs.dat prompt> vi vip_projdirs.dat …add parent directories of VIP VBDs, e.g.: ######################################################################### # # This file contains a list of project directories for VIP.
AssetJournal AssetJournal projects contain web documents (using standard mime types such as html text and images) which are supported directly by the browser. This requires that files be addressable via a URL, i.e. they must reside below the Web root. Location(s) for AssetJournal browsing: In some sites these data can be quite widely scattered, so WOW provides a convenient grouping mechanism. The parent location for AssetJournal is $OWHOME/WebApps/htdocs/ assetjournal_data.
Configuring Subscription Tools and Email The subscription tools allows users to request automatic notification by email in the event that data are changed or added within a registered area of interest – by specified project, geographic area or data type. These tools allow users to establish, view and modify their subscriptions directly through html forms. A series of cron jobs execute queries, which compose emails providing users with a list of new/changed data from WOW.
To test WOW email on the command-line, use the testEmail utility: prompt> testEmail Usage: testEmail Set WOW_DEBUG=1 for additional diagnostic information. prompt> testEmail plain fred@oilco.com 'sendEmail plain' completed in 8 seconds. Check fred@oilco.com inbox; most likely email has been delivered. prompt> testEmail html fred@oilco.com 'sendEmail html' completed in 8 seconds. Check fred@oilco.com inbox; most likely email has been delivered.
Customizing the WOW Interface Although WOW will install and run ‘out of the box’, it is designed to form part of a larger subsurface E&P portal. For example, the portal would cover project databases via WOW, other internal databases, links to electronic document management systems, external links etc. WOW behaves identically 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.
Up to version 5000.0.1.10 the default OpenWorks project listing is of project databases (PDBs). Since version 5000.0.1.11 this changes to a hierarchy mode which displays interpretation projects (IPs) beneath their associated PDB. For SeisWorks-mode survey listings, the default has changed from listing surveys in IPs by survey type, to by project. These defaults may be changed by setting environmental variables WOW_OW_LISTING, WOW_SW_LISTING and WOW_SW_GROUPING in the wow.
Adding a ‘Custom’ Intro Page If a file wow_custom.html exists in $OWHOME/WebApps/htdocs, a link to this page will appear on the WOW front page. This can be used to add site-specific content. prompt> cd $OWHOME/WebApps/htdocs prompt> cp wow_custom.html.default wow_custom.html Edit wow_custom.html in any HTML authoring tool and add your desired content. Changing Default Well Name Display By default WOW displays wells using the common well name attribute WELL_NAME_FREE.
Important note: this functionality is deprecated and will be removed in a future release. To implement, add the environmental variable WOW2003_URL to wow.env, e.g.: prompt> cd $OWHOME/WebApps/conf prompt> vi wow.
Accessing WOW pages from other applications District Redirects Most WOW pages can be accessed directly using an HTTP GET, i.e. a full URL with arguments. To see what this URL look like, place the cursor over any link in WOW, use the right mouse button and select option ‘Open Link in New Window’. The URL will be displayed in the address bar of the new window. In the examples below, http://wow.oilco.com is an illustrative main WOW URL, (environmental variable WOW_URL in wow.
Configuring KRS OpenWorks knowledge reference system (KRS) documents can be loaded and viewed through WOW. The document types supported are ‘Hardcopy’, which is a reference to a physical location, and ‘Web link’, which is any URL beginning with http://. Note that WOW itself can be used a source of both dynamic URLs to any related WOW page, or as a server to ‘publish’ a directory of static documents beneath WOW’s Web root.
OpenWorks QC/QA Queries The QC/QA module allows the storage and execution of SQL queries against OpenWorks projects. 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 can be 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.
To turn on the display of the SQL in WOW, set the WOW_SHOW_SQL environmental variable to 1 (on) in $OWHOME/WebApps/conf/wow.env. The default is 0 (off): # Show SQL in QC/QA module: 1=on 0=off WOW_SHOW_SQL=1; export WOW_SHOW_SQL An example QC/QA query is provided below: REM title: Wells with 0 or null total depth REM dtype: well REM description: This query checks for wells with TD.
Command-Line Utilities OpenWorks and SeisWorks project data management changes significantly in R5000. WOW provides a number of command-line utilities to assist users in understanding the new approach. These allow listing of districts, projects, surveys, lines, seismic, and horizons. First source the WebApps environment before running any command-line utilities: (if C-shell) prompt> source $OWHOME/WebApps/templates/wow.login prompt> . $OWHOME/WebApps/templates/wow.
Utility prjlist: list ‘projects’ names only, i.e. 3D surveys and OpenWorks projects containing 2D lines, with external storage defined. The convention is to list 3D surveys as /, with project databases capitalized and interpretation projects in lowercase, e.g.: prompt> prjlist SWDEVKIT SWDEVKIT/devnor SWDEVKIT/devnor2 SWDEVKIT/hew3d01 SWDEVKIT/pwt devnor2_ip/devnor2 devnor_ip/devnor goliath2d minkit2d minkit_ip pwt_ip/pwt Utility plist: list ‘projects’, i.e.
Utility linelist: lists 2D lines for the specified OpenWorks project or external storage directory, e.g.
Important note: handing spaces in arguments: If arguments have spaces, for example survey name, it is necessary to both quote and use braces, e.g. prompt> seislist SWDEVKIT 3D "{devnor survey 2}" Utility ow_prj_sql: runs SQL*Plus for the specified OpenWorks project. This is similar to the OpenWorks ow_prj_access script, except that the project password is not printed to the screen, but is used to connect directly to Oracle.
Utility lasexport: utility to export LAS files for a single well. Usage: lasexport owproj uwi ?dir? ?curveList? ?top? ?base? e.g.
The WOW GUI The WOW GUI provides a single interface to launching most of the WOW graphical user interfaces and other command-line utilities. In an OpenWorks xterm, set the WebApps environment first, then run wowgui: prompt> source $OWHOME/WebApps/templates/wow.login (if C shell) prompt> . $OWHOME/WebApps/templates/wow.
• Checkshot report (CheckshotReport) • Generic coordinate converter (CrsConvert) • Generic MD-TVD converter (TvdConvert) • ZGF to shapefile conversion GUI (Zgf2Shape) • ZGF picture thumbnail creation GUI (ZgfThumbs: requires CDA license) • WOW browser, WebApps and Tcl xterms • Commands owlist plist seislist hrzlist linelist surveylist. WOW 5000.0.1.
Coordinate Conversion WOW has historically had a single-point ‘Lat/Lon ⇔ XY Calculator’ which converts coordinates within the context of the OpenWorks project, i.e. between projected and geographic coordinates using the project’s CRS. Version 5000.0.1.0 added the option to use WGS84 as the geographic coordinate system, allowing for datum shifting. New in version 5000.0.1.
Utility fileCrsConvert: command-line file-based multiple-point conversion between any two cartographic reference systems (projected or geographic). The utility takes as input a columnar ASCII file, column IDs for the coordinates to convert, and source/target CRS IDs. Converted coordinates are inserted at the beginning of each line in the output file. Any header lines in the files will be ignored if prefixed with a # symbol.
MD/TVD Conversion New in version 5000.0.1.6 is a generic conversion utility that will convert an ASCII file of well-related measured depth (MD) data to true vertical depth (TVD), also including subsea true vertical depth (TVDSS) and X/Y absolute and relative coordinates for each point. The reverse operation is also possible, i.e. from TVD to MD.
The TvdConvert GUI is illustrated below. TvdConvert may also be launched from the wowgui interface. WOW 5000.0.1.
Integrating with Google Earth This module provides the ability to create Google Earth format .kmz files from OpenWorks projects. These .kmz files are in fact zip files containing the .kml file with spatial information, and associated .png files for well, line and survey icons. Coverage includes well locations, position logs, 2D lines, 3D surveys and OpenWorks project extents based on well data.
prompt> ow2kml Usage: ow2kml owproj ?fileout? ?wellListID? ?posLogFlag? ?timeSpanFlag? ?surveyListID? ?lineListID? OpenWorks project name Full path to output .
Creating OpenWorks WGS84 Shapefiles in Batch WOW interactively produces WGS84 geographic shapefiles of wells, position logs, 2D lines and 3D surveys from the OpenWorks Project Summary page. This process can optionally be run on the command-line of from a graphical user interface. Important note: this module converts project X/Y coordinates into lat/long using the WGS84 geodetic datum, which may differ from the project geodetic datum.
prompt> ow2shp Usage: ow2shp owproj ?shpdir? ?suffix? ?wellListID? ?posLogFlag? ?lineListID? ?survListID? ?botHoleFlag? OpenWorks project name Full path to output shapefile directory Optional suffix to include in shapefile name well list ID: -1 = all wells (default), 0 = no wells 1 = include position logs (default), 0 = exclude position logs 2D line list ID: -1 = all lines (default), 0 = no lines 3D survey list ID:
The directory override allows all shapefiles to be written to a single location, rather than the default $WOW_DATA_DIR/wow_shapes/ directory. To create navigation shapefiles for a single project/survey, use navShape with usage: navShape owproj survey gtype ?lineinc? ?traceinc? ?shapetype? ?shp? e.g. navShape SWDEVKIT devnor 3D Use survey All3D to process all surveys in the project. An alternative way to create navigation shapefiles is to use the NavShape graphical user interface, illustrated below.
Creating Horizon Images in Batch WOW interactively produces images of horizons, one at a time, for use as backdrops in GIS applications. This process can optionally be run in batch to produce images for all horizons in a specified project.
Creating ‘Live Trace’ Outlines The Default ‘Live Trace’ Algorithm The default algorithm is designed to display the actual extent of 2D or 3D seismic traces, rather than 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 exist within the rectangular project limits.
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) optional output zgf file (default none) optional output ZGF picture name (default none) Note that the output file extension determines the output type. Note also the different syntax for ZGF file output.
default is noclobber, i.e.
Important note: specifying –a slow to invoke the seisLTOexact algorithm will take considerably longer and is not recommended. Rather, use the default fast algorithm, then selectively use the slow algorithm where the default does not give a satisfactory output. Using the SeisLTO GUI An alternative way to execute the live trace outline utilities is to use the SeisLTO graphical user interface, illustrated below.
Updating Seismic and Horizon Statistics The seismic data set table in OpenWorks includes attributes for trace count, coverage %, number of extents and total volume size. These are currently not maintained by SeisWorks, but provide useful metadata to the user and data manager if loaded correctly. For 3dv and 3dh volumes, trace count is stored and can be read directly. For bri and cmp volumes, reading traces is required to obtain a valid trace count.
Seismic Polygon Clipping The seismic polygon clipping a utility takes as input a 3D seismic volume, trims it to one or more polygon shapes within the specified mapping polygon set in OpenWorks, and writes a new seismic volume as output. This may be used for example to cut out some complex lease shape from a larger survey. Additional notes: • Polygons may be INCLUSIVE or EXCLUSIVE, i.e.
WOW 5000.0.1.
Using ZGF Backdrops The SeisWorks navigation, live trace outline and horizon map displays can be enhanced through the use of ZGF backdrops. This allows the maps to include wells, fields, leases, bathymetry, coastlines, shipping lanes etc. – whatever is in the specified ZGF picture. ZGFs are ideal for cultural backdrops, in that they are the OpenWorks standard neutral backdrop culture format. They are widely used across applications and can be created in SeisWorks, StratWorks, Z-MAP Plus and WOW.
prompt> ls -ltr /tmp/out* -rw-rw-r-- 1 bruce users 1140 Aug 10 11:56 /tmp/outline3d_lgb36_arc.shx -rw-rw-r-- 1 bruce users 12308 Aug 10 11:56 /tmp/outline3d_lgb36_arc.shp -rw-rw-r-- 1 bruce users 2501 Aug 10 11:56 /tmp/outline3d_lgb36_arc.dbf To produce geo-referenced images rather than shapefiles, use utility zgfImage.
Integrating with ESRI GIS Saving GIS Image Backdrops ArcView and GIS is aimed predominantly at vector data. It is however possible to load raster images as backdrops to cultural information in GIS. WOW images can be exported in an ArcView-compatible format for a number of data types: • OpenWorks grids • Z-MAPPlus grids and pictures • SeisWorks horizon, navigation and live trace outlines Of the above, the most important are the raster types: OpenWorks and Z-MAPPlus grids and SeisWorks horizons.
Customizing Choice of Color Maps WOW utilizes SeisWorks color maps (.
Viewing CGMs in WOW There are two different methods of implementation: client-side plugin or server-side conversion, with advantages and disadvantages for both methods. A number of vendors provide functionality in this area, e.g. SDI (http://www.sdicgm.com) and Zeh (http://www.zeh.com). Others are mentioned below. Important note: By default, WOW implements a converter from SDI (http://www.sdicgm.com). No further configuration should be required for simple viewing.
Integrating with CDA Corporate Data Archiver (CDA) can be used to generate ‘throwaway’ stubs which include image thumbnails for re-use within WOW. These options are provided for OpenWorks, SeisWorks, GeoProbe, ProMAX and VIP projects. This functionality is designed to facilitate a project cleanup operation, e.g. deleting empty horizons. Note that a CDARCHIVER license is required in order to run CDA.
Additional Customization Options Customizing the Well, Field and Lease Modules The lease module allows the editing of lease commitments, interests and remarks. Editing can be turned off for sites that prefer read-only execution. Also, descriptive names can be changed to take into account global differences, e.g. ‘Lessee’ has meaning in the Gulf of Mexico, whereas ‘Block interests’ might be more applicable in the North Sea. The file $OWHOME/WebApps/conf/lease_tables.
Customizing the ‘Key Facts’ Module The ‘key facts’ module allows users to ‘add a note’ against projects, wells, fields, leases, basins, seismic and 3D surveys. These notes are a collection of up to 10 long remarks, each up to 2000 characters in length, associated with an individual well, field or lease. The ‘key facts’ are implemented in the OpenWorks KRS (knowledge reference system) model. The attributes that may be edited are controlled on a site-wide basis by the following configuration files.
COL02 COL03 COL04 COL05 COL06 COL07 COL08 COL09 COL10 "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 $OWHOME/WebApps/conf/seismic_keyfacts: COL01 COL02 COL03 COL04 COL05 COL06 "Data Source" N 1 "Acquisition Info" N 2 "Processing Info" N 3 "Data Loading Info" N 4 "Related Seismic" N 5 "Other Comments" N 6 $OWHOME/WebApps/conf/survey_keyfacts: COL01 COL02 COL03 COL04 COL05 COL06 COL07 COL08 "Interp Status"
Customizing the Well Match Module The well match modules computes, then stores, a reference between a well in one project and a well in another project. Well matching is typically relevant where wells have different UWIs in different projects. Well matches are stored in the WELL_UWI_ALT table in both projects. There may be multiple matches for the same UWI against many UWI types. For example, API:1001423276841000 may match NPD:12/13-14a and also CORP:012/13014s1.
Maintenance and Troubleshooting Apache Apache is a freeware web server developed by the Apache Software Foundation (http://www.apache.org). Apache is the most widely used web server on the Web. It has excellent performance, is lightweight, stable, and very reliable. It should require almost no maintenance from a system administration perspective. Apache must be started by root.
Appendix 1: Example wow.env File #============================================================================ # Name: # wow.
WOW_ADMIN_EMAIL="bruce"; export WOW_ADMIN_EMAIL # Default email suffix (e.g. exprodat.com) WOW_EMAIL_SUFFIX=exprodat.
APACHE_HOME=/etc/httpd; export APACHE_HOME # Web root (should not need to change) WEB_ROOT=${WOW_HOME}/htdocs; export WEB_ROOT # URL to web server cgi-bin directories (should not need to change) WOW_CGI=${WOW_URL}/bin; export WOW_CGI # SeisWorks if [ -d ${OWHOME}/SeisWorks ]; then SEISHOME="${OWHOME}/SeisWorks"; export SEISHOME fi # set Tcl/Tk library locations TCL_LIBRARY=${WOW_HOME}/tcltk/lib/tcl8.4; export TCL_LIBRARY TK_LIBRARY=${WOW_HOME}/tcltk/lib/tk8.
Appendix 2: Summary of Important Files The following table summarizes the main files used by WOW and Apache. File/Directory Description /etc/httpd/conf: httpd.conf Main apache configuration file .
$OWHOME/WebApps/conf: wow.env Main WOW configuration file – see appendix 1 webapps_version.dat WebApps version information wow_menu.dat Customize WOW left frame menu zmap_projdirs.dat Lists of parent directories for ZMAP data other_projdirs.dat Lists of parent directories for ‘Other’ data gp_projdirs.dat Lists of parent directories of GeoProbe projects vip_projdirs.dat Lists of parent directories of VIP projects promax_data_homes.dat Lists of PROMAX_DATA_HOME locations restricted_dir_list.
Appendix 3: WOW Architecture The fundamental concept behind WOW is dynamic access to data. This means that the majority of content is generated on the fly programmatically by reading the underlying databases, formatting and then sending results to a Web browser. WOW is a server-side application. There are no client-side dependencies, i.e. plug-ins to be downloaded or installed, considerably simplifying maintenance.
Appendix 4: Apache Installation Options Introduction This section discusses options for customizing the Apache installation, such as using an existing Apache server, changing server name or port, running multiple instances, using alternative authentication methods etc. When planning any non-default installation or customization of WOW, administrators should be aware of the critical configuration files for Apache and for WOW. Most changes, e.g.
Using an existing Apache server during install By default, WOW installation requires a system with Apache installed but not configured or running. Sites may wish to install WOW and rather use an existing Apache, e.g. the server shipped with PowerExplorer. To do so, run WebAppsInstall (or WOWInstall directly) with an additional –n flag to skip Apache configuration during installation, as illustrated below. In this example the server is http://wow.oilco.
Changing the Apache server during install Sites may need to install WOW on a different system from which the Apache server will eventually run. For example, WOW may need to be installed on an application server containing the OpenWorks tree, which may be exported read-only to the intended Apache server. To achieve this, provide the hostname for the preferred Apache server rather than the default during installation. Do NOT run root.sh on the installation system.
1. Edit the Apache configuration file to change the value of User/Group: prompt> vi /etc/httpd/conf/httpd.conf change User and Group to the new user’s credentials. 2. Edit the WOW configuration file to change the value of APACHE_USER: vi $OWHOME/WebApps/conf/wow.env change APACHE_USER to new username change HOME to match the home directory of the APACHE_USER. 3.
# WOW Alias /wow/ "/apps/ow/WebApps2/htdocs/" line 645: Add lines: #WOW ScriptAlias /bin/ "/apps/ow/WebApps2/cgi-bin/" AllowOverride AuthConfig Options None Order allow,deny Allow from all line 945: Insert line ErrorDocument 500 "/wow/error.html" 4. Start Apache (as root if port is less than 80): /usr/local/apache2/bin/apachectl start 5. Duplicate the WOW software tree: cd $OWHOME mkdir WebApps2 cd WebApps find . -depth -print | cpio -pdlmv ../WebApps2 6.
Building the Apache Server from Source Building Apache from source is an alternative where a binary distribution is not available or is unsuitable for any reason. In this example, a new Apache binary distribution is compiled and installed into /usr/local/apache2. See the previous section for instructions on required WOW changes to Apache httpd.conf. 1. Download the Apache source from http://httpd.apache.org/download.cgi. Look for the latest stable 2.0.x version (RHEL 4) or 2.2.x (RHEL 5), e.g. httpd-2.0.64.
Using External NIS Password Authentication (RHEL 5 only) The mod_auth_pam.so method described above is for Apache 2.0 on RHEL 4 and will not work with Apache 2.2 on RHEL 5. Note that mod_auth_pam is no longer supported or developed: see http://pam.sourceforge.net/mod_auth_pam. On RHEL 5 with Apache 2.2, using mod_authnz_external.so with pwauth may provide an alternative method for NIS authentication. For installation details see $OWHOME/WebApps/dso/external.README and external.tar.gz.
Moving the Apache Web Root (read-only $OWHOME) WOW by default creates a Web alias from /wow/ to $OWHOME/WebApps/htdocs, which is referred to as the Web Root. This location on disk contains static files, directories and links that are customizable on a site-by-site basis. If your site requires that the $OWHOME directory be entirely read-only, then the Web Root can be moved as described below: 1. Change the Apache alias: vi /etc/httpd/conf/httpd.conf.
Appendix 5: Background on the Devkit Shells Introduction The ‘WebApps’ products WOW, Corporate Data Archiver and Project Administrator all run Tcl/Tk shells, extended with OpenWorks devkit functions. This provides a powerful yet simple mechanism for extracting information from these project data sources for display in a table, graphical user interface or Web page. The main devkit shell lmksh integrates the OpenWorks, SeisWorks, Z-MAPPlus and ZGF devkits with other api’s providing coverage of e.g.
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/wow.lmkrc $HOME/.lmkrc Add or uncomment the commands OWSetup 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.
Appendix 6: WOW Functionality Checklist OpenWorks Multi-Project • • • • • • • summarize projects, reporting main data type counts across multiple projects search for objects (wells/fields/leases/lines/surveys) across multiple projects apply a standard or user defined QC/QA query across multiple projects compare 2 projects, reporting differences in attributes for the main data types match wells between projects that have a different UWI scheme show project create info with CRS info for all projects subscrib
Fields, Lease & Basins • • • • • • • • • display field headers, interests and boundary display/launch/add field documents display/add extended field documentation in the key facts module display lease headers, interests and remarks display/add lease documents display/add extended lease documentation in the key facts module display basin headers display/add basin documents display/add extended basin documentation in the key facts module Documents • • • • • • display all KRS documents display document head
Admin • • • • • • • • • display tables in Oracle project schema with table/column descriptions display VC tables list with data counts display individual VC table list of values display R_ tables list with data counts display individual R_ table list of values display stratigraphic column headers display surfaces and units for an individual stratigraphic column display users with project access rights and interpreter count display interpreters for an individual project user QC/QA • • • • • show customisa
Horizons • • • • • • • • display horizon headers display horizons with optional CDA-generated thumbnails display horizon statistics (% coverage) display horizon basemap images export horizon GIS image display/export horizon values display 2D line vs.
• • display and request publishing of shared AssetJournal projects link AssetJournal project to an OpenWorks object as a KRS document Other Data • • • • • • • • • • • • • • • • display common ASCII file formats (e.g. .dat, .txt) display common web file formats (e.g. .gif, .jpg, .
• • • • • • display fault file headers with drilldown to data values display well file headers with drilldown to marker/curve headers display colormaps with drilldown to RGB values and images display state file headers with drilldown to objects referenced in state files document volume, surface, horizon, point, fault, well, colormaps or lease objects display all project documentation • • • • • • • • • • • • display all VBD file attributes display VDB summary info with case headers plus CDA thumbnails if
Parameter Tables • • show table headers with types drill down to show table header plus data OPFs • • • • • list OPFs drill down to show OPF attributes drill down to OPF attribute details view 2D cross plot of OPF attributes view OPF tabular data Miscellaneous • • • • • • • • • • • • save results to Excel on PC or Linux file (all modules) report data errors context-sensitive (all modules) change SeisWorks/OpenWorks district/instance in multi-district sites display WOW Apache error log plus environment
Appendix 7: WOW Documenter Attributes Migration to R5000 Seismic Attributes PIM_SEIS_INFO 3D Upgrade Path 2D Upgrade Path PROJECT None None SEISMIC None None TIME_DEPTH None POLARITY Copy into SEISMIC_DATA_SET field PHASE Copy into SEISMIC_DATA_SET field SEIS_CLASS Copy into SEISMIC_DATA_SET attribute SEISMIC_CLASS None Copy into each SEISMIC_DATA_SET entries associated with the proclev. Copy into each SEISMIC_DATA_SET entries associated with the proclev.
Copy into SEISMIC_DATA_SET attribute TOTAL_SIZE TOTAL_SIZE None Values didn't apply to 2D in pim REMARKS Copy into SEISMIC_DATA_SET attribute PROCESSED_DATE Added to SEISMIC_DATA_SET_REMARK Type = SW_GENERAL Added to SEISMIC_DATA_SET_REMARK Type = SW_GENERAL Added to SEISMIC_DATA_SET_REMARK Type = SW_GENERAL Added to SEISMIC_DATA_SET_REMARK Type = EBCDIC_HDR Added to SEISMIC_DATA_SET_REMARK Type = BINARY_HDR Added to SEISMIC_DATA_SET_REMARK Type = SW_GENERAL Added to SEISMIC_DATA_SET_REMARK Type = SW_G
RECOMP_MAX MEAN None None None Not relevant None Mean in new model will be computed as part of upgrade from the data. Percent coverage value in new model will be computed as part of upgrade from the data.
Structure of Remark Data For each PIM_SEIS_INFO record associated with a 3D project, three remark records will be created that are associated with the SEISMIC_DATA_SET instance in OW. A SEISMIC_DATA_SET_REMARK ‘long remark’ of type SW_GENERAL will contain the fields in the WOW model that don't map to the OW R5000 model directly including the contents of the remark field.
Contacting Landmark Customer Support Landmark software operates Technical Assistance Centers (TACs) in Australia, the United Kingdom, and the United States. Additional support is also provided through local support offices around the world. Support via Web Portal Support information is always available on the Landmark Customer Support internet page. You can also submit a support request directly to Landmark Customer Support though the Landmark Customer Support Portal: http://css.lgc.
Regional Offices For contact information for regional offices, see the Contact Support page located at: http://css.lgc.com/InfoCenter/index?page=contact§ion=contact If problems cannot be resolved at the regional level, an escalation team is called to resolve your incidents quickly. WOW 5000.0.1.
© 2014 Halliburton All Rights Reserved Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Halliburton. Unauthorized reproduction or distribution of this documentation, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under law.
