iwellfile™ software version 5000.1.10.0 installation...

iWellFile™ Software Version 5000.1.10.0 Installation Guide

© 2012 Halliburton

March 2012

© 2012HalliburtonAll Rights Reserved

This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of:

Halliburton | Landmark Software & Services2107 CityWest Blvd, Building 2, Houston, Texas 77042-3051, USA

P.O. Box 42806, Houston, Texas 77242, USAPhone:713-839-2000, FAX: 713-839-2015Internet: www.halliburton.com/landmark

Trademarks3D Drill View, 3D Drill View KM, 3D Surveillance, 3DFS, 3DView, Active Field Surveillance, Active Reservoir Surveillance, Adaptive Mesh Refining, ADC, Advanced Data Transfer, Analysis Model Layering, ARIES, ARIES DecisionSuite, Asset Data Mining, Asset Decision Solutions, Asset Development Center, Asset Development Centre, Asset Journal, Asset Performance, AssetConnect, AssetConnect Enterprise, AssetConnect Enterprise Express, AssetConnect Expert, AssetDirector, AssetJournal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, AssetOptimizer, AssetPlanner, AssetPredictor, AssetSolver, AssetSolver Online, AssetView, AssetView 2D, AssetView 3D, BLITZPAK, CasingLife, CasingSeat, CDS Connect, Channel Trim, COMPASS, Contract Generation, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot, Decision Management System, DecisionSpace, DecisionSpace 3D Drill View, DecisionSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace Atomic Meshing, DecisionSpace Desktop, DecisionSpace Nexus, DecisionSpace Reservoir, DecisionSuite, Deeper Knowledge. Broader Understanding., Depth Team, Depth Team Explorer, Depth Team Express, Depth Team Extreme, Depth Team Interpreter, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery 3D, Discovery Asset, Discovery Framebuilder, Discovery PowerStation, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth-Model, Drillworks, Drillworks ConnectML, Drillworks Predict, DSS, Dynamic GeoModeling, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, EDM AutoSync, EDT, eLandmark, Engineer's Data Model, Engineer's Desktop, Engineer's Link, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, ezTracker2D, FastTrack, Field Scenario Planner, FieldPlan, For Production, FrameBuilder, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, GeoLink, Geometric Kernel, GeoProbe, GeoProbe GF DataServer, GeoSmith, GES, GES97, GESXplorer, GMAplus, GMI Imager, Grid3D, GRIDGENR, H. Clean, Handheld Field Operator, HHFO, High Science Simplified, Horizon Generation, I2 Enterprise, iDIMS, Infrastructure, Iso Core, IsoMap, iWellFile, KnowledgeSource, Landmark (as a service), Landmark (as software), Landmark Decision Center, Landmark Logo and Design, Landscape, Large Model, Lattix, LeaseMap, LithoTect, LogEdit, LogM, LogPrep, Make Great Decisions, MathPack, MDS Connect, MicroTopology, MIMIC, MIMIC+, Model Builder, NETool, Nexus (as a service), Nexus (as software), Nexus View, Object MP, OpenBooks, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWire Client, OpenWire Server, OpenWorks, OpenWorks Development Kit, OpenWorks Production, OpenWorks Well File, PAL, Parallel-VIP, Parametric Modeling, Permedia, PetroBank, PetroBank Explorer, PetroBank Master Data Store, PetroStor, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family, Power Interpretation, PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, PowerModel, PowerView, PrecisionTarget, Presgraf, PressWorks, PRIZM, Production, Production Asset Manager, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D, ProMax 3D, ProMAX 3DPSDM, ProMAX 4D, ProMAX Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+, QUICKDIF, Quickwell, Quickwell+, Quiklog, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real Time Surveillance, Real-time View, Reference Data Manager, Reservoir, Reservoir Framework Builder, RESev, ResMap, RTOC, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio, SimResults, SimResults+, SimResults+3D, SIVA+, SLAM, SmartFlow, smartSECTION, smartSTRAT, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel, StrataSim, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SurfNet, SynTool, System Start for Servers, SystemStart, SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, T-Grid, The Engineer's DeskTop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, TracPlanner Xpress, Trend Form Gridding, Trimmed Grid, Turbo Synthetics, Unconventional Essentials, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Well Cost, Well H. Clean, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WellDirect, WELLPLAN, WellSolver, WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!, ZetaAnalytics, and Z-MAP Plus are trademarks, registered trademarks, or service marks of Halliburton.

All other trademarks, service marks and product or service names are the trademarks or names of their respective owners.

NoteThe information contained in this document is subject to change without notice and should not be construed as a commitment by Halliburton. Halliburton assumes no responsibility for any error that may appear in this manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore, this statement may not apply to you.

Third Party Licenses and AttributionsHalliburton 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 location:

PathNameInInstallationDir/Third_Party.pdf

DisclaimerThe programs and documentation may provide links to external web sites and access to content, products, and services from third parties. Halliburton is not responsible for the availability of, or any content provided on, third party web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Halliburton is not responsible for: (a) the quality of third party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Halliburton is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

iWellFile™ Software Installation Guide

5000.1.10.0 i

Contents

About this Manual .......................................................................................................... 1Overview............................................................................................................................. 1How To Use This Manual................................................................................................... 2Platform Notes .................................................................................................................... 3

Web Server Operating System Support ....................................................................... 3Browser Support .......................................................................................................... 3EDM™ Database Systems on Oracle .......................................................................... 3

What’s in this Manual......................................................................................................... 4

Before You Install ........................................................................................................... 5Product Dependencies: Checklist ................................................................................ 5

Engineer’s Desktop 5000.1.10.0 ............................................................................ 5ODBC Data Source Connection ............................................................................ 5Internet Information Services (IIS) and Windows Components ........................... 6Acrobat Reader ...................................................................................................... 7Oracle Client (on Oracle systems only) ................................................................. 7

Load Balancing on Windows 2003 .............................................................................. 8

Installation .......................................................................................................................... 9Installing iWellFile™ Software in a 32-Bit Environment .................................................. 10

Installing with Previous Versions ................................................................................ 105000.1.10 Update Installation Procedure ..................................................................... 105000.1.1 Installation Procedure ................................................................................... 12

Installing iWellFile™ Software in a 64-Bit Environment .................................................. 18Installing with Previous Versions ................................................................................ 18Install the Engineer’s Desktop in a 64-Bit Environment ............................................. 18Install iWellFile on a Windows 2008 Server (64-bit) .................................................. 19

Install IIS 7.0 With ASP.NET Support .................................................................. 19Create an Application Pool .................................................................................... 225000.1.10 Update Installation Procedure ............................................................... 24Configure iWellFile Application Pool ................................................................... 25Configure iWellFile ............................................................................................... 27

Configuring iWellFile™ software ...................................................................................... 28Important—If You Are Using a SQL Server Database ............................................... 28Register ASP.NET with IIS (Windows 2003 (32-Bit) Environment ONLY) ............. 29Configure IIS (Windows 2003 (32-Bit) Environment ONLY) ................................... 31Register .CVS, .LOG and MSC MIME Types ............................................................ 34Run the Materialized Views Database Script .............................................................. 36Set Internet Explorer Security Options ........................................................................ 37


ii 5000.1.10

Generate KPIs Asynchronously using the Analytical Service ..................................... 40Launching iWellFile™ software......................................................................................... 42

iWellFile software Web Page Components ................................................................. 43Toolbar ................................................................................................................... 44Selection Controls .................................................................................................. 45

Configure Windows Authentication..................................................................... 51Overview............................................................................................................................. 51Create an iWellFile™ Software Users Group .................................................................... 52Grant Privileges to User Rights Assignment ...................................................................... 54Grant Permissions to Various Folders ................................................................................ 56Configure IIS ...................................................................................................................... 57

Windows 2003 Server .................................................................................................. 57Windows 2008 Server .................................................................................................. 57

Configure Web.Config File ................................................................................................ 59Redirect PROFILE™ Software Log File............................................................................ 60Configure EDM™ Database............................................................................................... 61

Configure the Environmental Variable ........................................................................ 61Configure SQL Server and Oracle to Use Windows Authentication .......................... 62

Window Authentication for SQL Server ............................................................... 62Window Authentication for Oracle ........................................................................ 63

Configure a DSN when using a SQL Server Database....................................................... 64Create a SQL Server Authentication DSN .................................................................. 64Configure the SQL Server Authentication DSN in iWellFile™ software ................... 65

Set System DSN Credentials for SQL Server" ...................................................... 65Set up Users for Windows Authentication ......................................................................... 66

Create Windows Users in EDM™ Database for SQL Server ..................................... 66Create Windows Users in EDM™ Database for Oracle .............................................. 67

Step 1 - Create Users in Oracle .............................................................................. 67Step 2 - Create Users in EDM™ Administration .................................................. 68

Configure Internet Explorer on the Client Machine ........................................................... 70

Customize the User Interface .................................................................................. 71Overview............................................................................................................................. 71Administration Page ........................................................................................................... 75

Announcements ........................................................................................................... 75To search Announcements: .................................................................................... 76To view all Announcements: ................................................................................. 76To add an Announcement: ..................................................................................... 76To edit an Announcement: ..................................................................................... 77To delete an Announcement: ................................................................................ 77

Daily Operations Report Summary .............................................................................. 77iWellFile Control ......................................................................................................... 78

Application Status area .......................................................................................... 78


5000.1.10 iii

Report Generator Service ....................................................................................... 79Application Logs ................................................................................................... 80

Profiling ....................................................................................................................... 81To begin Profiling Data: ........................................................................................ 81

Data Generation Login ................................................................................................. 82Generate KPIs Asynchronously using the Analytical Service ............................... 82

Launch in Context Support ................................................................................................. 84Guest Login......................................................................................................................... 86Layout Configuration.......................................................................................................... 88iWellFile™ software Configuration File ............................................................................ 90

Applying changes to iWellFile Software ..................................................................... 91ODBC Data Source Name Selection .................................................................... 91Application Settings Tag ....................................................................................... 92Session State Settings ............................................................................................ 98

iWellFile Service Registry Settings .................................................................................... 99Well Operations Tab Configuration ................................................................................... 100

Applying changes to iWellFile software ..................................................................... 100Configuring Data Fields and Layout ..................................................................... 101

Lessons Learned Screens Customization-iWellFile ........................................................... 104Purpose of Document ................................................................................................... 104Details of Configuration files ...................................................................................... 104SearchCriteriaSelectorConfig.xml ............................................................................... 104SearchResultConfig.xml .............................................................................................. 104LessonLearned_Details.xml ........................................................................................ 105Location of Configuration files .................................................................................... 105How to Configure ....................................................................................................... 106

SearchCriteriaSelectorConfig.xml ......................................................................... 106SearchResultConfig.xml ........................................................................................ 108Adding a new CD_LESSON attribute on screen (attribute that is not present in aspx page) ...................................................................................................................... 111Adding a new Child attribute on screen. ................................................................ 112

..................................................................................................................................... 112Well Operations Tab Display Selection Configuration ...................................................... 113

Configuration Displays ................................................................................................ 114Highlight Tight Group Name ....................................................................................... 115Display Attribute Name ............................................................................................... 116Calendar Incident Icon Configuration ........................................................................ 116Well Operations Summary Field Security ................................................................... 118

Key Performance Indicators Tabs Configuration ............................................................... 120Macros ......................................................................................................................... 121Syntax .......................................................................................................................... 121Parameters .................................................................................................................... 122Adding a Field to the Performance Tab ....................................................................... 123KPI Security Level Support ........................................................................................ 125

Report Customization File .................................................................................................. 127Chart Configuration ........................................................................................................... 128


iv 5000.1.10

iWellFile™ Software Initialization Configurations............................................................ 130Log File Locations Configuration....................................................................................... 131Configure Default Filter on Startup .................................................................................... 132Configure the iWellFile Style Sheet ................................................................................... 133

Applying changes to iWellFile software: .................................................................... 133Themes................................................................................................................................ 136Restarting the iWellFile™ software Service ...................................................................... 137Text Labels and Internationalization .................................................................................. 138

Applying changes to iWellFile software: .................................................................... 138

Uninstall Procedures .................................................................................................... 141iWellFile™ software 5000.1.10.0 Uninstall ....................................................................... 141

Troubleshooting .............................................................................................................. 143iWellFile Software Security Tokens ............................................................................ 143iWellFile.log Errors ..................................................................................................... 144Cannot see the Administration options in iWellFile Software .................................... 145ERROR [HYC00] [Oracle][ODBC]Optional feature not implemented ...................... 145Multiple EDM Report windows stay after a report is generated ................................. 145iWellFile™ Software Server cannot process your request error ................................. 146Internet Explorer "Connect to" Dialog appears when using iWellFile ........................ 146iWellFile™ Software External Components (Analysis, Output Reports, COMPASS Plots, Schematics) do not work .............................................................................................. 147"Page Not Found" error occurs when accessing Log files ........................................... 147No report was generated error ...................................................................................... 148Schematics, Wall Plots and Reports may not work ..................................................... 148Login.aspx Text Displayed When Launching iWellFile Software .............................. 149Reports, Wellbore Schematics, PROFILE™Software Wall Plots Not Responding ... 150PROFILE Software Wall Plots Will Not Generate to JPG Format ............................. 150iWellFile™ Software Does Not Respond .................................................................... 150iWellFile™ Software Windows and Help Cannot be Accessed .................................. 151HTTP 403.9 Error ........................................................................................................ 151EDM™ Database Login Error When Using Oracle ODBC Database ........................ 151Oracle ODBC Data Source .......................................................................................... 152Oracle Login Error ....................................................................................................... 152Restarting iWellFile ..................................................................................................... 152Log File Generation ..................................................................................................... 153Changing Regional Settings ......................................................................................... 153Popups Blocked or Runtime Error Displayed .............................................................. 153Windows 2003 Server—Windows\System32 Path/Environment Variable Corruption 154Using FileMon and RegMon to Troubleshoot ............................................................. 155

Appendix A......................................................................................................................... 157


5000.1.10 v

Configuring iWellFile™ Software to Support Both Windows Authenticated and EDM User Credentials .......................................................................................................................... 157

Appendix B......................................................................................................................... 165Language Codes.................................................................................................................. 165

Appendix C......................................................................................................................... 173

Installation Checklists ................................................................................................. 175Install iWellFile 5000.1.1 Checklist ................................................................................... 176

Prerequisites Checklist ................................................................................................. 176Install iWellFile 5000.1.1 Checklist ............................................................................ 177

iWellFile 5000.1.10 Software 32-Bit Installation Checklist............................................... 178Prerequisites Checklist ................................................................................................. 178

iWellFile Software 64-Bit Installation Checklist................................................................ 180Install Engineer’s Desktop 64-Bit Checklist ............................................................... 180Prerequisites Checklist ................................................................................................. 181Install IIS 7.0 With ASP.NET Support Checklist ........................................................ 182Create Application Pool Checklist ............................................................................... 182Install iWellFile 5000.1.10 Checklist .......................................................................... 182Configure iWellFile Application Pool Checklist ......................................................... 183

Configure iWellFile Checklist ............................................................................................ 184Configure Windows Authentication ................................................................................... 185

Create iWellFile User Group ....................................................................................... 185Grant Privileges to User Rights Assignment ............................................................... 185Grant iWellFile Group Permissions to Various Folders .............................................. 185Configure IIS ............................................................................................................... 186

Windows 2003 Server ........................................................................................... 186Windows 2008 Server ........................................................................................... 186

Configure Web.Config File ......................................................................................... 186Redirect PROFILE™ Software Log File ..................................................................... 187Configure EDM Database ............................................................................................ 187Configure SQL Server and Oracle to Use Windows Authentication .......................... 187

SQL Server ............................................................................................................ 187Oracle Server ......................................................................................................... 187

Configure a DSN when using a SQL Server Database ................................................ 188Create a SQL Server Authentication DSN ............................................................ 188Configure the SQL Server Authentication DSN in iWellFile™ software ............. 188


vi 5000.1.10

About this Manual iWellFile™ Software Installation Guide

5000.1.10.0 Overview 1

About this Manual

Overview

The information in this manual is applicable to the iWellFile™ software on the Engineer’s Data Model™ (EDM™) database.

iWellFile™ software is Landmark’s latest product to be integrated on the Engineer’s Desktop™ software. iWellFile™ software is a Web-based application that provides users with intranet access to well operations, reports, current activity, key performance indicators, wellbore schematics, and analysis. All this information is available from the EDM™ database. This database is the shared data model for Drilling, Completions, and Production and Economics applications.

This manual is designed for system administrators or others who are responsible for installing and setting up the iWellFile™ software server.

Starting with Release 5000.1, all Landmark software is available on a server for customers to download, using the Landmark Software Manager. See the Landmark Software Manager online Help for details.

iWellFile™ Software Installation Guide About this Manual

2 How To Use This Manual 5000.1.10.0

How To Use This Manual

Before you use the procedures in this manual the following software products and certain third-party applications must be installed: EDM™, Data Analyzer™, COMPASS™, PROFILE™ and EDM™ Report Manager. The installation of these products are covered in the following manuals:

• EDM™ Software Installation Guide (EDM_Install.pdf)

• EDT™ Drilling Software Installation Guide (EDT_Drilling_Install.pdf)

Once these applications have been installed, the iWellFile™ software can be installed using the procedures outlined in this manual.

About this Manual iWellFile™ Software Installation Guide

5000.1.10.0 Platform Notes 3

Platform Notes

The iWellFile™ Software Version 5000.1.10 Release Notes document outlines necessary information about new features and known problems specific for the 5000.1.10 release. This document is available in PDF format (iWellFileRelease Notes.pdf).

Web Server Operating System Support

iWellFile™ software is certified using Internet Information Server 5.0 and 6.0 on a Windows 2003 Server machine, and Internet Information Server 7.0 on a Windows 2008 Server machine.

Browser Support

This release supports the use of Internet Explorer 6.0 or a newer version. Netscape Navigator and other browsers are not supported.

Certain components of the software require the use of “popup” windows. Therefore, popups must be enabled for full functionality of iWellFile™ software.

EDM™ Database Systems on Oracle

For EDM database systems implemented on an Oracle system included on an iWellFile™ web server, Oracle Client software is required.

iWellFile™ Software Installation Guide About this Manual

4 What’s in this Manual 5000.1.10.0

What’s in this Manual

This manual contains the following chapters:

“Before You Install” on page 5—This chapter reviews the prerequisites and implementation plan for the installation.

“Installation” on page 9—This chapter provides detailed instructions for the installation on both 32-bit and 64-bit systems.

“Configure Windows Authentication” on page 51—This chapter shows how to configure the software to use Windows Authentication.

“Customize the User Interface” on page 71—This chapter outlines customization of the iWellFile™ software user interface. This information is additionally available in the on-line help.

“Uninstall Procedures” on page 141—This chapter contains the uninstall procedures.

“Troubleshooting” on page 143—This chapter contains solutions to various errors and problems that may occur during the installation.

“Appendix A” on page 157—This chapter contains an option (at the time of login) for users to login either using windows credential or EDM™ login-password.

“Appendix B” on page 165—This chapter contains a listing of language codes used to internationalize iWellFile™ software.

“Appendix C” on page 173- This chapter contains contact information for Landmark Technical Assistance Centers and Regional Support Offices around the world.

“Installation Checklists” on page 175- This chapter contains checklists that can printed and used as a guide in tracking or troubleshooting the installation process.

Before You Install iWellFile™ Software Installation Guide

5000.1.10.0 5

Before You Install

Prior to installing iWellFile™ software, review the following sections.

Product Dependencies: Checklist

The installation has dependencies on the order of installation. The following checklist outlines the steps that must take place prior to installing. In some cases the installation will fail to continue if these dependencies are not met.

Engineer’s Desktop 5000.1.10.0

You must have the Engineer’s Desktop™ software version 5000.1.10.0 installed using either the standalone or server installation option.

Access to the following applications affect functionality available in iWellFile software:

• Data Analyzer™ software- If this is not available, the Analysis page will not be available.

• PROFILE™ software - If this is not available, the Schematics tab will also not be available.

• COMPASS™ software - If this is not available, the directional plots will not be available.

• EDM™ Report Manager - If this is not available, the Output Reports will not be available.

ODBC Data Source Connection

Configure an ODBC Data Source connection to the EDM™ database. iWellFile software now allows the administrator configure a list of

ENGINEER’S DESKTOP™ 5000.1.10.0 SUITE MUST BE INSTALLED BEFORE YOU USE iWELLFILE™ 5000.1.10SOFTWARE

iWellfile™ 5000.1.10.0 software uses a number of EDT™ Applications and components that were updated in EDT 5000.1.10.0. You cannot login to iWellFile™ 5000.1.10.0 software unless EDT 5000.1.10.0 is installed (EDM database version 09.04.07.107).

iWellFile™ Software Installation Guide Before You Install

6 5000.1.10.0

restricted EDM database ODBC DSN connections, to control the EDM databases the application can connect to.

iWellFile™ software also supports the use of EDM™ database users with read-only access. Landmark further recommends the use of read-only user accounts for non-EDM application users.

For more information see “ODBC Data Source Name Selection ” on page 91.

Internet Information Services (IIS) and Windows Components

You must Install Internet Information Services (IIS), 6.0 or greater and a number of other Window components prior to running the iWellFile software installation. Each of these components can be installed through the Add and Remove Programs > Add/Remove Windows Components dialog.

For Windows 2003 Server, the following Windows components are also required:

Select a component and click the Details button to select the sub-components.

Application Server Components:

• Application Server Console

• ASP.NET

• Internet Information Services (IIS)

Internet Information Services Manager Components:

• Common Files

• Internet Information Services Manager

• World Wide Web Service

World Wide Web Service Components:

• Active Server Pages

• Server Side Includes

• World Wide Web Service

Before You Install iWellFile™ Software Installation Guide

5000.1.10.0 7

Acrobat Reader

Adobe Acrobat Reader is required on the Client machine to use components of iWellFile™ software.

Oracle Client (on Oracle systems only)

For EDM™ systems implemented on an Oracle system including on iWellFile software web server, Oracle Client software is required.

Adobe Acrobat Reader

Landmark supports Adobe Acrobat Reader version 7.09 and above only, for use with iWellFile software.

IMPORTANT: iWellFile software Web Server Should Not Be Used as an Applications Server

Landmark strongly recommends that the iWellFile software web server NOT be used as an Engineer’s Desktop™ application server (for example, Citrix Server).

iWellFile™ Software Installation Guide Before You Install

8 5000.1.10.0

Load Balancing on Windows 2003

To increase performance in a multi-user environment, Network Load Balancing could be implemented for iWellFile software. Details about how to configure this environment are outlined in a White Paper that can be found at http://www.west-wind.com/presentations/loadbalancing/networkloadbalancingwindows2003.asp 1

1. Strahl, Rick. 2003. Web Farming with the Network Load Balancing Service in Windows 2003. West Wind Technologies White Paper. http://www.west-wind.com/presentations/loadbalancing/networkloadbalancingwindows2003.asp (accessed May 5, 2008)

Installation iWellFile™ Software Installation Guide

5000.1.10.0 9

Installation

This chapter instructs the user on the preparation, installation, and launch of the iWellFile™ software application. The following stages are discussed:

• “Installing iWellFile™ Software in a 32-Bit Environment” on page 10

The iWellFile software installation stage involves installation of pre-requisites and the iWellFile software and configuration of the IIS web server.

• “Installing iWellFile™ Software in a 64-Bit Environment” on page 18

This section outlines the installation of iWellFile in a 64-bit environment.

• “Configuring iWellFile™ software” on page 28

After installing, some manual configurations must be performed on the iWellFile Server, as well as on machines accessing iWellFile from Internet Explorer.

• “Launching iWellFile™ software” on page 42

Once the installation stages have been completed the iWellFile software site is ready to be accessed from a browser.

To help track the installation process, checklists are available for printing at the end of this manual. See“Installation Checklists” on page 175.

iWellFile™ Software Installation Guide Installation

10 Installing iWellFile™ Software in a 32-Bit Environment 5000.1.10.0

Installing iWellFile™ Software in a 32-Bit Environment

This section describes the installation procedure for iWellFile software in a 32-bit environment using Windows 2003 Server. The installation creates a web site on the server that is accessible to users through a web browser.

To install iWellFile software in a 64-bit environment, see “Install the Engineer’s Desktop in a 64-Bit Environment” on page 18.

The iWellFile™ software is delivered via Electronic Delivery System using the Landmark Software Manager tool. iWellFile 5000.1.10 version is an update release, so you can install the iWellFile 5000.1.10 version only if iWellFile 5000.1.0 or higher has already been installed and configured on your machine.

Installing with Previous Versions

iWellFile 5000.1.10.0 must be installed on a system that already has 5000.1.0 (or later) installed. If a version previous to 5000.1.0 exists on your machine, uninstall it and then install version 5000.1.1.

To install iWellFile from scratch, see “5000.1.1 Installation Procedure” on page 12.

5000.1.10 Update Installation Procedure

Prior to running the iWellFile 5000.1.10.0 update, ensure the iWellFile 5000.1.1 installation and configuration has been successfully completed. (See “5000.1.1 Installation Procedure” on page 12.)

1. Double-click on the Setup.exe file, or run it from the Start > Run command in Windows (e.g., C:\Setup.exe).

IMPORTANT: Pre-requisites

A number of applications must be installed prior to beginning the iWellFile software installation process. See “Before You Install” on page 5 for information on these pre-requisites.


5000.1.10.0 Installing iWellFile™ Software in a 32-Bit Environment 11

Click OK on the confirmation box that appears.

2. Click Setup on the next dialog.

3. When all the files are unzipped a command window opens. Press any key to continue.

The installation detects the location of the existing iWellFile program and asks for confirmation that it found the correct path with the following question:

The default path is: <path>. Would you like to change this path (Y/N).

4. Verify the location of the currently installed iWellFile program, and then perform one of the following:

• If the suggested path is the correct installation location of the existing iWellFile program, press “N” and then Enter to continue.

• If the existing iWellFile installation is in another location, press “Y” When prompted, enter the enter the path with no trailing backslashes.

5. The installation continues until completion. When finished, press any key to close the installation.

If you are installing in a 32-bit environment for the first time, you must now perform manual configuration steps (described in “Configuring iWellFile™ software” on page 28).

If you are updating a previous version o f iWellFile 5000.1.x that was installed in Windows authentication mode, then go to “Configure



Windows Authentication” on page 51 to perform customization of privileges.

Otherwise, go to “Launching iWellFile™ software” on page 42 to begin using the application.

This completes the installation of iWellFile software version 5000.1.10 for Windows 2003 Server.

5000.1.1 Installation Procedure

The following installation procedure is included if you need to install the 5000.1.1 required iWellFile version before you install version 5000.1.10.0.

Remember, you must have versions 5000.1.0 (or later) installed before you attempt to install 5000.1.10.0.


2. The Installation program checks the system for Internet Information Server (IIS). If IIS is not installed, the installation will notify you. Problems may occur if IIS is not installed prior to running the installation (see step on page 6).

ENGINEER’S DESKTOP 5000.1.10.0 MUST BE INSTALLED BEFORE YOU USE IWELLFILE 5000.1.10.0

iWellfile 5000.1.10.0 uses a number of EDT™ Applications and components that were updated in EDT 5000.1.10.0. You cannot login to iWellFile 5000.1.10.0 unless EDT 5000.1.10.0 is installed (EDM database version 09.03.06.067).

IMPORTANT: Installation Notes

The installer MUST be logged in with local administrator privileges; otherwise, programs will fail to install properly.

ALL open programs should be closed prior to the commencement of the installation, including the Windows Office Toolbar.



The InstallShield Wizard opens and displays the Welcome window.

3. Click Next to begin the installation.

The Customer Information window appears.

Enter your user name and organization, then click Next.

The Setup Type window appears.



Select an installation type:

• Complete—By default, iWellFile software is installed in the C:\inetpub\wwwroot\iWellFile_5000.1.1 directory. To accept that location, click Complete, and then click Next to continue.

• Custom—If you wish to change the location where the software is installed, select Custom, then click Next. In the dialog that appears, click the Change... button to browse directories. Specify the desired location. Then click Next to continue.

Note:

If iWellFile software is installed on a drive other than that which contains the Engineer’s Desktop™ software, then the local Network Service group must have read access to the whole drive on which it is located.



The Virtual Directory window appears.

This is the name of the website directory used to launch the application. The default, iWellFile_5000.1.1, may be changed.

Using the default name, when running iWellFile™ software from Internet Explorer, the following address would be entered: http://<servername>/iWellFile_5000.1.0/login.aspx.

4. Click Next to continue.

HTTP Address

When having trouble connecting to the iWellFile software server using the http web address, try replacing the server name with the IP address of the server (e.g., http://132.134.52.12/iWellFile_5000.1.0/login.aspx).



The Ready to Install the Program window appears.

5. Click Install to continue.

The Wizard will begin copying files. This may take a few minutes.



When copying is complete, the InstallShield Wizard Complete window appears.

6. Click Finish to exit from the Wizard.

This completes the installation of iWellFile software.

If you are installing in a 32-bit environment, return to “5000.1.10 Update Installation Procedure” on page 10).

If you are installing in a 64-bit environment, return to “Installing iWellFile™ Software in a 64-Bit Environment” on page 18).

IMPORTANT: Reboot is required.

You must reboot after installing iWellFile™ software.

Oracle Data Provider (ODP).

Some administrators may wish to use Oracle Data Provider for .NET 2.0. 10.2.0.2.20, instead of Window ODBC for the database connections. In this case, ODP can be downloaded from Oracle’s website and configured in iWellFile software’s web.config file.

For more information see “ODBC Data Source Name Selection ” on page 91.



Installing iWellFile™ Software in a 64-Bit Environment

This section describes the installation procedure for iWellFile software in a 64-bit environment using Windows 2008 Server. The installation creates a web site on the server that is accessible to users through a web browser.

The iWellFile™ software is delivered via Electronic Delivery System using the Landmark Software Manager tool. iWellFile 5000.1.10 version is an update release, so you can install the iWellFile 5000.1.10 version only if iWellFile 5000.1.0 or higher has already been installed and configured on your machine.

Installing with Previous Versions

iWellFile 5000.1.10 must be installed on a system that already has 5000.1.0 (or later) installed. If a version previous to 5000.1.0 exists on your machine, uninstall it and then install version 5000.1.1.

To install iWellFile from scratch, see “5000.1.1 Installation Procedure” on page 12

Install the Engineer’s Desktop in a 64-Bit Environment

Prior to installing iWellFile software in a 64-bit environment, the Engineer’s Desktop 5000.1.10 must be installed in the same environment.

Check the System Requirements in the Engineer’s Desktop™ Software Version 5000.1.10 Release Notes (EDT_Drilling_SummaryReleaseNotes.pdf).

Perform the following steps when installing on Windows 64 bit.

1. Log in as the Administrator.

IMPORTANT: Pre-requisites

A number of applications must be installed prior to beginning the iWellFile software installation process. See “Before You Install” on page 5 for information on these pre-requisites.



2. Disable hardware-based DEP (Data Execution Prevention) in BIOS, if machine has hardware-based DEP.

3. Set Software-based DEP to "Turn on DEP for essential Windows programs and services only" as stated in the Release Notes.

4. Disable User Account Control.

5. If the machine uses SMS (Software Management Service), then unplug the network cable as SMS conflicts with EDT installations.

6. Follow the instructions found in the Engineer’s Desktop™ Software Version 5000.1.10 Release Notes (EDT_Drilling_SummaryReleaseNotes.pdf) sections:

• Before You Install

• Installation: 64-Bit Operating Systems

It is important to follow these instructions for a successful installation.

Install iWellFile on a Windows 2008 Server (64-bit)

The following steps must be carried out in the following order, to correctly install iWellFile software on a Windows 2008 Server 64-bit machine.

• Install IIS 7.0 with ASP.NET Support (see page 19)

• Create an Application Pool (see page 22)

• Install iWellFile 5000.1.10 (see page 24)

• Configure iWellFile Application Pool (see page 25)

• Configure iWellFile (see page 27)

Install IIS 7.0 With ASP.NET Support

Install IIS 7.0 with ASP.NET support if not already installed on the server. Follow these steps to do so:

1. Select All Programs > Administrative Tools > Server Manager.



2. Select Role Summary > Add Roles to open the “Add Roles Wizard”.

3. Press Next. On the next screen, select Web Server (IIS).



4. The following dialog box opens. Click the Add Required Features button.

5. Click the Next button on the main wizard screen.

6. Click Next again.



7. Click Next again. On the next screen check the Application Development box. Do not uncheck any defaults.

8. Click Next.

9. On the next screen click Install. Once installation is complete click Close.

Create an Application Pool

1. Open IIS Manager, and go to Application Pools.



2. Right click on Application Pools and select Add Application Pool.

3. Create a new application pool, giving it any name. Choose .NET Framework version v.2.0.50727 and Managed Pipeline Mode Classic.



4. Once the application pool is created, right click on it and choose Advanced Settings. Set Enable 32-bit Applications flag as True.

5000.1.10 Update Installation Procedure

Prior to running the iWellFile 5000.1.10 update, ensure the iWellFile 5000.1.1 installation and configuration has been successfully completed. (See “5000.1.1 Installation Procedure” on page 12.)


Click OK on the confirmation box that appears.



2. Click Setup on the next dialog.

3. When all the files are unzipped a command window opens. Press any key to continue.

The installation detects the location of the existing iWellFile program and asks for confirmation that it found the correct path with the following question:

The default path is: <path>. Would you like to change this path (Y/N).

4. Verify the location of the currently installed iWellFile program, and then perform one of the following:

• If the suggested path is the correct installation location of the existing iWellFile program, press “N” and then Enter to continue.

• If the existing iWellFile installation is in another location, press “Y” When prompted, enter the enter the path with no trailing backslashes.

5. The installation continues until completion. When finished, press any key to close the installation.

This concludes the iWellFile 5000.1.10 installation.

Configure iWellFile Application Pool

1. Open IIS Manager, and go to Default web site.

2. Find the iWellFile application in the list of applications under Default web site.



3. Right click on iWellFile application and open the Advanced Settings.

4. Set the Application Pool as the one created in a previous step.



5. Grant Full access to local ‘Users’ group on iWellFile installation folder, e.g., C:\inetpub\wwwroot\iWellFile_5000.1.1.0.

6. Perform an IISReset, and start the LGC iWellFile Service.

Configure iWellFile

1. Use the configuration steps outlined in section “Configuring iWellFile™ software” on page 28; ignoring the following subsections:

• Register ASP.NET with IIS

• Configure IIS

This completes the installation of iWellFile software version 5000.1.10 for Windows 2008 Server (64-bit).

ENGINEER’S DESKTOP 5000.1.10 MUST BE INSTALLED BEFORE YOU USE IWELLFILE 5000.1.10

iWellfile 5000.1.10 uses a number of EDT™ Applications and components that were updated in EDT 5000.1.10. You cannot login to iWellFile 5000.1.10 unless EDT 5000.1.10 is installed (EDM database version 09.03.06.067).


28 Configuring iWellFile™ software 5000.1.10.0

Configuring iWellFile™ software

The following manual configurations must be performed in order for iWellFile software to operate correctly.

• Configure KPIs for SQL

• Register ASP.NET with IIS (Windows 2003 Server 32-bit ONLY)

• Configure IIS (Windows 2003 Server (32-bit) ONLY)

• Register .CVS, .LOG and MSC MIME Types

• Run the Materialized Views Database Script

• Set Internet Explorer Security Options

• Generate KPIs Asynchronously using the Analytical Service

Each of these steps are outlined below.

Important—If You Are Using a SQL Server Database

If you are using a SQL Server database, the standard Key Performance Indicator (KPI) configuration file need to be adjusted.

In the kpi.xml, dashboardkpi.xml, and multiplewellskpi.xml files:

• comment out all inline comments that say “Oracle Version...”,

• and uncomment the SQL Server version sections.


5000.1.10.0 Configuring iWellFile™ software 29

These files are located in the iWellFile™ software install directory, under the Config\Custom\KPI folder.

Register ASP.NET with IIS (Windows 2003 (32-Bit) Environment ONLY)

If ASP.NET is not registered with IIS, the web pages will display as text.

1. To register ASP.NET with IIS, run the following command from Windows Start > Run command.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

2. Verify that ASP.NET Version 2.0.50727 is configured. The following steps show how to verify the correct version is configured.

a. Open the Computer Management console from Start > Programs > Administrative Tools > Computer Management.

b. Navigate to Services & Application > Internet Information Services (IIS) Manager > Web Sites > Default Web Site > iWellFile 5000.1.1 instance.

Custom Configuration Folder

iWellFile software now ships with two folders for configuration files. The Landmark folder contains the default configuration of iWellFile software and the Custom folder contains configurations that are customized by administrators.

Configurations made in the Custom folder override configurations made in the Landmark folder.

Future installs of iWellFile software will not overwrite configurations made to files located in the Custom folder.



c. Right-click on the iWellFile 5000.1.1 instance and select Properties from the menu that appears.

d. Select the ASP.NET tab and confirm that version 2.0.50727 appears in the dialog.

3. Click OK.

ASP.NET Version Note:

iWellFile™ software 5000.1.1 does not support previous versions of ASP.NET. If version 1.1.4322 appears by default when the tab is opened, change it to 2.0.50727.



Configure IIS (Windows 2003 (32-Bit) Environment ONLY)

These steps enable the iWellFile™ software application to run correctly.

1. From the Computer Management console, select the Web Service Extensions folder.

2. Verify that the ASP.NET v 2.0.50727 web service extension on the right is set to Allowed. This enables any ASP.NET application in IIS.

Windows 2003 Server has added a new item to this list called Application Pools. The Application Pools are isolated areas that a web application runs in. By default, a web application runs in the Default Application Pool. This step creates a new Application Pool, where iWellFile will run exclusively, creating the following two effects:

• it allows the iWellFile™ software to execute,

• and it isolates the application from other processes, thereby allowing more configuration and better handling.

3. Right-click on Application Pools and select New > Application Pool from the menu that appears.



The Add New Application Pool dialog appears.

4. Enter iWellFileAppPool in the Application pool ID field.

5. Select the Use existing application pool as template option and select DefaultAppPool in the Application pool name picklist.

6. Click OK.



7. The new Application Pool—iWellFileAppPool—appears in the tree.

Next, configure the application to take advantage of the iWellFileAppPool.

8. Expand Web Sites > Default Web Site.

9. Right-click on iWellFile_5000.1.1 and select Properties from the menu that appears.

The iWellFile_5000.1.1 Properties dialog appears.



10. Select iWellFileAppPool in the Application pool picklist.

Register .CVS, .LOG and MSC MIME Types

By default, IIS is not configured to serve the .LOG, .CSV and .MSC (Event Viewer file) files to client machine. This causes a “Page not found” error when trying to access Log files in the iWellFile™ software Administration page. To configure IIS to serve .LOG, .CSV and .MSC files:



1. From the iWellFile_5000.1.1 Properties dialog, select HTTP Headers tab and click on MIME Types button.

2. Click New and add the extension .LOG and enter TXT in the MIME type field.

3. Click OK.

4. Repeat step 2 to add .CSV and .MSC extensions and assign them a TXT MIME type.

5. Click OK to close the MIME Types dialog.

6. Click OK to close the iWellFile 5000.1.1 Properties dialog.



7. Reset the IIS service. Follow the menu path, Start > Run. Enter iisreset and click OK.

Run the Materialized Views Database Script

This step must be performed on all EDM™ databases that will be accessed by the application.

The Materialized View scripts create views, which pre-cache EDM data that the application displays. These views:

• minimize the EDM database response times to the application requests,

• and reduce the net load time the application places on the EDM database server.

The SQL Server and Oracle version of these scripts are located in the installation directory, SQLScripts folder (e.g., C:\Inetpub\wwwroot\iWellFile_5000.1.1\SQLScripts).

Ensure the user has rights to create a MATERIALIZED VIEW.

If running SQL Server

1. Login to a SQL Server tool as EDMADMIN.

2. Run the MATERIALIZED VIEWS_MSDE.SQL script.

If running Oracle

1. Create a tablespace called, IWF_MVIEWS.

2. Login to SQL Plus as the Administrator.

SQL Database Note

The SQL Server Management Studio Express installed with the EDM database can be used to run this script. To do this:

Double-click on the MATERALIZED VIEWS_MSDE.SQL file and login to the EDM5000 SQL instance as EDMADMIN.

Select the EDM database and click Execute in the toolbar.



3. Run the following command to give the EDMADMIN user appropriate permissions to the IWF_MVIEWS tablespace:

Alter user edmadmin quota unlimited on iwf_mviews;

4. Login to SQL Plus as EDMADMIN.

5. Run the IWELLFILE_PACKAGE_ORACLE.PKS script also found in the SQLScripts directory.

6. Run the MATERIALIZED VIEWS_ORACLE.SQL script.

Set Internet Explorer Security Options

Trusted sites must be entered for Internet Explorer to recognize the application. This must be preformed on all machines that will be accessing the application from Internet Explorer.

1. In the Internet Explorer application, select Tools > Internet Options....

The Internet Options dialog appears.


You must reboot the Server after completing the configuration steps outlined above.



2. Select the Security tab, and click the Sites button.

The Trusted Sites dialog appears.

3. Enter the iWellFile™ software server’s name or IP address in the Add this Web Site to the zone field (e.g. CalTest14W2K3 or 132.32.72.116).

4. Click the Add button to add this site to the list. Do NOT select the Require server verification (https:) for all sites in this zone.

5. Enter the website http address (e.g. http://<server name>/iWellFile_5000.1.1/login.aspx) in the Add this Web Site to the zone field.

Adding iWellFile’s Server Name:

Adding the Server Name or IP address, helps to avoid security issues on the client machine, such as popup blocker, Java Scrip blocker, etc.

HTTP Address

When having trouble connecting to the web server using the http web address, try replacing the server name with the IP address of the server (e.g., http://132.134.52.12/iWellFile_5000.1.1/login.aspx).



6. Click the Add button to add this site. Do NOT select the Require server verification (https:) for all sites in this zone.

7. Click OK to accept the changes and return to the Internet Options dialog.

8. Select the Advanced tab.

9. Scroll down to the bottom of the list of settings and select Enable Integrated Windows Authentication (requires restart) option.

10. Click OK to accept the changes and close the Internet Options dialog.

11. Close all Internet Explorer windows.



Generate KPIs Asynchronously using the Analytical Service

Any appropriate configured Database DSN (Database Source Name) can use the Analytical Service to calculate the KPI's asynchronously. Only one DSN should be selected, as the default and this is the only one that can have KPI's pre-cached.

When to Set System DSN Credentials

If the KPI component displays the following message then the DSN must be configured.

How to Set System DSN Credentials

1. Launch iWellFile™ software from any machine.

2. Login as the iWellFile software Administrator privilege.

3. Click the Administration link and select Data Generation Login from the menu that appears.

iWellFile Administrator Login

Be sure the iWellFile software Administrator account has the iWellFile.Adminstration token granted in the EDM™ Administration Utility. By default, all accounts have this token revoked.



4. In the form that appears, select the DSN Name for the EDM™ database, which will use the Analytical Service to calculate the KPI's asynchronously.

5. Select the Default DSN checkbox.

6. Enter the database credentials: User and Password.

7. Click the Save button.

8. Reset the IIS service. Follow the menu path, Start > Run. Enter iisreset and click OK.

If iWellFile 5000.1.x was installed in Windows authentication mode, then go to “Configure Windows Authentication” on page 51 to perform customization of privileges.

Otherwise, go to “Launching iWellFile™ software” on page 42 to begin using the application.


42 Launching iWellFile™ software 5000.1.10.0

Launching iWellFile™ software

Once iWellFile software has been installed on the server, the PC has been rebooted and licenses have been made available, the application is ready for use.

To launch iWellFile software from a networked machine:

1. Open a browser window (e.g., Internet Explorer).

Licensing Checks

Verify that the license file (Licence.dat) is readable by the local Windows Users Group.

Verify that a UNC path is not used to access the license file. Use the port number and machine name instead (e.g., instead of the UNC path \\License\Landmark\LAM\License.dat use 2013@License).


5000.1.10.0 Launching iWellFile™ software 43

2. Enter the web site address in the Address bar. This is the address configured during the installation (e.g., http://<server name>/iWellFile_5000.1.1/login.aspx).

5. The login window appears in the browser. Login to the EDM™ database ODBC Data Source.

iWellFile software Web Page Components

The iWellFile software web page contains a Toolbar, a Selection Control Bar and a number of tabs containing Well Operations information for a selected viewing date.

HTTP Address

When having trouble connecting to the web server using the http web address, try replacing the server name with the IP address of the server (e.g., http://132.134.52.12/iWellFile_5000.1.1/login.aspx).

The following steps also resolve this problem.

1. On the iWellFile™ software server, open command prompt.

2. Locate and then change to the directory that contains the Adsutil.vbs file. By

default, this directory is C:\Inetpub\Adminscripts.

3. Execute the following in command prompt.

cscript adsutil.vbs set w3svc/NTAuthenticationProviders “NTLM”

4. Execute the following in command prompt to verify that the

NTAuthenticationProviders metabase property is set to NTLM.

cscript adsutil.vbs get w3svc/NTAuthenticationProviders

The following text should be returned:

NTAuthenticationProviders : (STRING) “NTLM”

Popups in Internet Explorer

Popups must be enabled to have full functionality in iWellFile software. If popups are disabled many parts of iWellFile software will fail to launch including on-line help, Data Analyzer™ software Query results and Output Reports.



Toolbar

The toolbar is used to navigate the various pages and components of iWellFile™ software.

The following pages are available from the toolbar:

• Dashboard - The Dashboard page provides users with quick access to high-level summary information based on a selected region of interest.

• Multiple Well - The Multiple Well page provides users with access to Well Operations data for all wells located in a selected region.

• Single Well - The Single Well page provides users with access to current and historical Well Operations data for selected well.

• Rig Operations - The Rig Operations Page provides users with status information for the active and historical Rig activity.

• Analysis - The Analysis page enables users to view Well Operations data in graphs or tables generated from Data Analyzer™ software.

• Lesson Learned - The Lessons Learned page allows users to record planning or operations experience and learnings.

• Well Initialization - The Well Initialization page allows users to create and initialize a Well in the EDM™ database

• Reports Page - The Reports page allows users to view output reports from OpenWells® software and may chose reports from a date, well name, event, report type, rig name, or rig number.



The following components are also available from the toolbar:

• Administration - The Administration option allows iWellFile software administrators to control and configure the application from the browser window. This option is only visible to System Administration users who have been granted access to the iWellFile.Administration application security token.

• My iWellFile- The My iWellFile link opens a dialog, which is used to configure the user’s default display settings for iWellFile software.

• Announcements - The Announcements button ( )allows managers to publish messages to iWellFile™ software users.

• Help - The Help link opens the iWellFile software online Help system.

• About iWellFile - The About iWellFile link opens the About dialog, which displays release, current user, and licensing information on the iWellFile software session. In addition, the iWellFile software release notes can be launched from this dialog.

• Logout - The Logout link logs the user out of iWellFile software, making a license available

Selection Controls

Selection controls are available above the toolbar. These controls are used to view Well Operations information in iWellFile software for the selected Well, Event, Datum and Unit System. The bar also allows the user to apply filters to the Wells picklist. Different controls appear on the bar depending on the pages selected.

Well Filter Option

The Well Filter option is available on a number of pages including Dashboard, Multiple Wells, Single Well, Rig Operations, Lessons Learned and Reports pages.

• Well Filter Checkbox - When the Well Filter checkbox is activated (checked), the Well Filter picklist becomes available and Well filters can be applied to the data on the page. When this checkbox is activated, the Well Filter picklist appears and the Location picklists are not available.



• Well Filters Picklist - The Well Filters picklist appears when the Well Filter checkbox is selected. This picklist displays filters that have been created in the following Engineer's Desktop™ drilling and completion software, such as OpenWells®, PROFILE™ or COMPASS™. When a filter is selected it is applied to the Well selection picklist in the Single Well page. For the Dashboard and Multi Wells pages and active filters reduces content presenting in the various displays. Well Filters are stored on the web server and are globally available to all users.

Use the Upload ( ) button to load filters contained on the local computer to the global list available from iWellFile™ software. Filters that are uploaded are available to all users. Filters can only be uploaded by users who have been granted access to the iWellFile.Upload token.

Use the Create Well Filters ( ) button to create new filter.

Location Picklist Options

The Location Picklists are available on a number of pages including Dashboard, Multiple Wells, Single Well, Rig Operations, Lessons Learned and Reports pages.

• Location Picklists - Three location picklists appear in the Selection Control Bar. By default, these locations are Block, District and Country. This picklists are customizable using My iWellFile. They may be labelled as Block, District, Country, Division, Region, or State/Prov etc. The user may also select other location fields to filter data. These picklists are used to define Sites by location. Data for the defined Sites is displayed on the page.

The Location picklists are not available when the Well Filter checkbox is selected.

Note:

The iWellFile software Administrator can remove Well Filters by deleting the filter file (.QRY extension) from the filters directory found in the iWellFile software installation directory on the web server.



Dashboard and Multiple Well Pages:

The Section Control Bar in the Dashboard and Multiple Wells pages contains the following features.

• Current Date Selector - Use the Current Date selection area to set the date for the information that is displayed on the Dashboard and Multiple Wells pages.

Single Well Page

The section controls in the Single Well page contains the following features.

• Well - The Well picklist is used to select the Well, whose data is displayed on the Single Well page. The selections appearing in the Event, Datum and Design picklists are determined by the selected Well.

• Event - The Event picklist is used to select the Event whose operations data is displayed on the Single Well page. The selections appearing in the Event picklist are determined by the selected Well.

• Reference Datum Elevation - The Reference Datum Elevation picklist is used to select the Reference Datum Level (RDL) of the data displayed on the Single Well page. This picklist allows the user to change the downhole depths viewing datum 'on the fly' within the application. The Datum is automatically set to the Well's default datum when a Well is selected.

• Design - The Design picklist is used to select the Design, whose data is to be displayed on the Single Well page. The selections appearing in the picklist are determined by the selected Well. Actual, Planned and Prototype designs are available. Actual Designs are selected by default.



Rig Operations Page

The section controls in the Rig Operations page contains the following features.

• Contractor - The Contractor picklist is used to filter the Contractor whose data is displayed on the Rig Operations page. If no filter is required, select "All".

• Rig Attribute - The Rig Attribute picklist is used to select the attribute of the Rig in which the Rig data is displayed on the Rig Operations page. A number of attributes are available to select from including: ALL, Is Offshore, Rig Name, Rig Number, Rig Owner and Rig Type.

• Attribute Name - The Attribute Name picklist displays the available values for the Rig Attribute selected. For example, if the Rig Attribute 'Rig Name' has been selected, then the Attribute Value will display all Rig Names belonging to the selected Contractor.

• Start Date and End Date - The Start Date and End Date fields are used to define a date range to retrieve Rig Operations information. All Rigs active within the date range are displayed on the Rig Operations page.

Analysis Page

The Section Control Bar in the Analysis page contains the following features.

• Pane Layout - The Pane Layout picklist is used to define the layout of the graphs and tables displayed on the Analysis page. The choices are 1x2, 2x1, 2x2, and 3x2.

• Query - The Query picklist is used to select a Data Analyzer™ software query to run against the EDM™ database. Only queries set with the iWellFile™ software attribute in Data Analyzer software query properties are displayed.

• Graph and Table Option Buttons - The Graph ( ) and Table ( ) options appear for queries that can be displayed as either a graph or table. These options are used to select the type of output generated. Queries that do not contain graphs will not have the graph option available.



• Modify Parameters Link - The Modify Parameters link appears when a query is selected that requires additional information to run the query. Click this link to open the Parameters dialog.

• Generate Button - The Generate ( ) button is used to generate the results for the selected Data Analyzer software query. The output appears in the currently selected pane.

• Regenerate - The Regenerate button is used to refresh the results of a Data Analyzer software query.

Lessons Learned Page

The section controls in the Lessons Learned page contains the following features.

• Search Criteria - The Search Criteria area is used to define the parameters by which the Lessons Learned search is performed. The following options are available:

• Canned Selection - define the search criteria by a specific Well or All Wells and by Lesson Type, Contractor, Rig Type, Region and/or Report Type

• Free Text Search - use free flow text to search the following Lessons memo fields: Summary, Comments, Keywords, Lesson Description, Comments Discussion

• Fixed Field Search - define the search criteria by selecting the Lesson's Author and/or Owner from the picklists

• Well - define the search criteria by selecting a specific Well from the picklist

Well Initialization Page

The Section Control Bar in the Well Initialization page contains the following features.

• Template Picklist - The Template picklist allows users to select a predefined template of a Well Initialization. These templates expedite the initialization of a Well.

• Create Template - The Create Template button ( ) opens a new Well Initialization Template window.



• Edit Template - The Edit Template button ( ) opens the Well Initialization Template window of the currently selected template.

• Apply Template - The Apply Template button ( ) opens a new Well Initialization Template window.

Reports Page

The Section Control Bar in the Reports page contains the Well Filter option and Locations picklists.

• Search Criteria - The following search criteria is available and can be used on their own or in combination with each other: Start and End Date (returns reports that fall on or between the Start and End dates); Well; Event; Report Type; Rig associated with the report; and Cached Reports or All reports.

Configure Windows Authentication iWellFile™ Software Installation Guide

5000.1.10.0 Overview 51

Configure Windows Authentication

Overview

The iWellFile™ software Server can be configured to use Windows Authentication when logging into the EDM™ database. The following steps must be performed to activate the Windows Authentication option.

• Create an iWellFile software Users Group

• Grant Permissions to User Rights Assignment

• Grant Privileges to Various Folders

• Configure IIS

• Configure Web.Config file

• Redirect PROFILE™ software log file to iWellFile\Output Folder

• Configure EDM Database to Use Windows Authentication

• Configure a Non-Windows Authentication DSN

• Set up iWellFile software for Windows Authentication

• Configure Internet Explorer on the Client machine

Each of these steps are outlined below.

iWellFile™ Software Installation Guide Configure Windows Authentication

52 Create an iWellFile™ Software Users Group 5000.1.10.0

Create an iWellFile™ Software Users Group

1. On the Domain Controller,

• Create a Domain Group called iWellFile Users.

• Add all domain users that will be accessing the iWellFile software must be added to the Domain Group: iWellFile Users.

2. On the iWellFile software server, create a local group called iWellFile Group.

a. To create the new group, select Start > Programs > Administrative Tools > Computer Management.

b. Expand the Local Users and Groups item and select the Groups item.

c. Right-click on Groups and select New Group from the menu that appears.

d. The New Group dialog appears.

e. Enter iWellFile Group in the Group name field.

f. Enter a description of the new group (e.g., iWellFile User's Local Group).

g. Click the Add button.

h. Add the Domain Group, iWellFile Users, to the Local Group.

i. Add the local Network Service, Authenticated Users user to the local group.


5000.1.10.0 Create an iWellFile™ Software Users Group 53

j. Click Create to create the new group.

k. Click Close to close the New Group dialog.


54 Grant Privileges to User Rights Assignment 5000.1.10.0

Grant Privileges to User Rights Assignment

User the following method to grant user right assignment on the iWellFile™ software server.

• Grant the Debug program privilege to the local group iWellFile Group (created in “Create an iWellFile™ Software Users Group” on page 52).

1. Open the Local Security Settings from Start > Programs > Administrative Tools > Local Security Policy.

2. Select Local Policies > User Right Assignment.

3. Right-click on the Debug Program privilege and select Properties from the menu that appears.

4. The Debug Program Properties dialog appears.

5. Click the Add User or Group button.

6. Click the Locations... button.

7. Select the name of the local machine from the list and click OK.

8. Click the Object Types button, select Groups and click OK.


5000.1.10.0 Grant Privileges to User Rights Assignment 55

9. Enter iWellFile Group, in the Enter the object names to select text box.

10. Click OK.

11. iWellFile Group appears in the properties dialog.

12. Click OK.


56 Grant Permissions to Various Folders 5000.1.10.0

Grant Permissions to Various Folders

The following table outlines all folder permissions that must be granted for the specified user/group on the iWellFile™ software server.

Folder/File User/Group Permissions

iWellFile software Installation folder (e.g., C:\Inetpub\wwwroot\iWellFile_5000.1.1

iWellFile Group Read

Write

Execute

Windows Vista and 7 Users folder iWellFile Group Full Control

• Create a folder Landmark\Cache on drive where iWellFile software is installed.

• Create a folder Landmark\Cache on drive where EDT software is installed.


Write

Modify

EDT installation folder (e.g., C:\Landmark\EDT_5000.1)


Write

Execute


5000.1.10.0 Configure IIS 57

Configure IIS

Windows 2003 Server

1. From the Windows desktop, follow the menu path Start > Programs > Administration Tools > Internet Information Services (IIS) Manager.

2. Navigate to the iWellFile_5000.1.1 Web application under Web Sites.

3. Right-click on the node and select Properties from the menu that appears. The iWellFile 5000.1.1 Properties dialog appears.

4. Select the Directory Security tab.

5. In the 'Authentication & Access Control' area click the Edit button. The Authentication Methods dialog appears.

6. If using Oracle, select the Integrated Windows Authentication option. If using SQL Server, select Basic authentication.

7. Deselect all other options including: Enable anonymous access, Digest authentication for Windows domain servers and .NET Passport authentication.

Windows 2008 Server

1. Open the Internet Information Services (IIS) Manager.

2. Navigate to the iWellFile virtual folder in the Explorer tree on the left.

3. Double-click on the Authentication icon in the toolbar.

4. Right-click on the ASP.NET Impersonation and select Enable.

5. If using SQL Server, right-click on Basic Authentication and select Enable.

6. If using Oracle, right-click on Windows Authentication and select Enable.


58 Configure IIS 5000.1.10.0

7. Right-click on the remaining options and select Disable, including: Enable anonymous access, Digest authentication for Windows domain servers and .NET Passport authentication.

5000.1.10.0 Configure Web.Config File 59

Configure Web.Config File

1. Open the web.config file (e.g., C:\Inetpub\wwwroot\iWellFile_5000.1.1).

2. Comment out the authentication mode =None entry

3. Comment in the authentication mode =Windows and identity impersonate=true entries.

See example below:

Comment out entry:



Comment in entries:

<authentication mode="Windows" />

<identity impersonate=”true” />


60 Redirect PROFILE™ Software Log File 5000.1.10.0

Redirect PROFILE™ Software Log File

The PROFILE software log file must be redirected to the iWellFile™ software Output folder.

1. Open the Windows Registry.

2. Edit (or add) the following registry key to direct the PROFILE software log file (i.e., NGProfile.log) to the application output folder. If the String Value Log File does not exist create it.

Registry Path: HKEY_LOCAL_MACHINE\Software\Landmark Graphics Corporation\EDT\5000.1\Profile

String Value: Log File

Log File Data String: C:\Inetput\wwwroot\iWellFile_5000.1.1\Output\NGProfile.log


5000.1.10.0 Configure EDM™ Database 61

Configure EDM™ Database

The EDM Database must be configured to use Windows Authentication.

Configure the Environmental Variable

Windows Authentication is disabled in the Engineer's Desktop™ software by default. To enable Windows Authentication the following Windows Environmental Variable must be added to Windows.

1. Open the Environment Variable dialog. Once way to open this dialog is through Control Panel > System Properties > Advanced tab > Environment Variables button.

2. Click the New button in the System variable area.

3. Enter the Variable name: LGC_EDM_REMOTE_OS_AUTHENT.

4. There are two possible entries for the Variable value field:

• FALSE - will hide the Windows Authentication checkbox in the EDM database Login dialog for applicable Engineer's Desktop software products.

• TRUE - will show the Windows Authentication checkbox in the EDM database Login dialog for applicable Engineer's Desktop applications.

5. Click OK to add the variable.

6. Click OK to close the System Properties dialog.


62 Configure EDM™ Database 5000.1.10.0

Configure SQL Server and Oracle to Use Windows Authentication

Windows Authentication is configured differently for SQL Server and Oracle. The following topics outline the steps to implement Windows Authentication for use with the Engineer's Desktop software products.

Window Authentication for SQL Server

The EDM™ database’s Data Source Name must be configured to use Window Authentication.

1. Launch the ODBC Data Source Administrator.

The ODBC Data Source Administrator dialog appears.

2. Select the System DSN tab.

3. Select the EDM database Data Source Name (e.g., EDM 5000.1 Single User Db) and click the Configure button.

4. The Microsoft SQL Server DSN Configuration wizard appears.

5. Click Next.

6. Select the With Integrated Windows authentication option and click Next.

7. Select the Change the default database to: checkbox and select the EDM database file (the name of the .MDF file).

8. Click Next.

9. Click Finish and click the Test Data Source... button to test the connection.

10. If the connection is successful click OK for each of the open dialogs. If the test fails try configuring the Data Source again.

Note: On 64-bit machines, you still need to select 32-bit drivers for EDT software.

On 64-bit machines, you need to go to a different location than in the past to launch the ODBC Administration dialog. Do not use the? Control Panel> Administrative Tools> Data Sources (ODBC)—instead, browse for and launch the ODBCAD32.EXE from the WINDOWS\SYSWOW64 folder.? ? \Windows\SysWOW64\odbcad32.exe


5000.1.10.0 Configure EDM™ Database 63

Window Authentication for Oracle

The EDM database's Data Source Name must be configured to use Window Authentication.




3. Select the EDM™ database Data Source Name (e.g., EDM 5000.1 Single User Db) and click the Configure button.

The Oracle ODBC Driver Configuration wizard appears.

4. Remove the user name from the User ID field. This field must be blank.

5. Click OK.



Shortcut Method:

From the Start > Run dialog enter odbcad32 and click OK.


64 Configure a DSN when using a SQL Server Database 5000.1.10.0

Configure a DSN when using a SQL Server Database

When using Windows Authentication to login to the SQL Server EDM™ database, some features do not work properly. This occurs because iWellFile™ software needs a Non-Windows Authentication SQL Server connection to access these components. To fix this issue another DSN must be created and configured for use by iWellFile software. The following section outlines the steps to create and configure the new DSN.

Create a SQL Server Authentication DSN




3. Click the Add... button.

4. Select the SQL Native Client driver and click Finish.

The Create a New Data Source to SQL Server dialog appears (e.g., EDM 5000.1 Non-WA Db).

5. Enter a name for the DSN and select the SQL Server instance where the database resides (e.g., CALTEST14W2K3\EDM5000).

6. Click Next.

7. Select the With SQL Server authentication using a login ID and password entered by the user option.

8. Select the Connect to SQL Server to obtain default settings for the additional configuration options checkbox.




5000.1.10.0 Configure a DSN when using a SQL Server Database 65

9. Enter the Login ID and Password for the SQL Server.

10. Click Next.

11. Select the Change the default database to: checkbox and select the EDM database (this is the name of the mdf file e.g., edm).

12. Click Next.

13. Click Finish.

Configure the SQL Server Authentication DSN in iWellFile™ software

1. Open the web.config file (e.g., C:\Inetput\wwwroot\iWellFile_5000.1.1).

2. Add the following to the web.config file, using the SQL Server Authentication DSN:

<add key="PrivilegeDsn" value="PUT-DSN-NAME-HERE"/>

For example, using the DSN EDM 5000.1 Non-WA Db the key would read as follows:

<add key="PrivilegeDsn" value="EDM 5000.1 Non-WA Db"/>

3. Reset IIS to apply the changes. Follow the menu path, Start > Run. Enter iisreset and click OK.

Set System DSN Credentials for SQL Server"

Perform the procedure outlined in “How to Set System DSN Credentials” on page 40 for both the Windows Authenticated DSN and the SQL Server Authenticated DSN created on “Create a SQL Server Authentication DSN” on page 64.

Both the Windows Authenticated DSN and the SQL Server Authenticated DSN must be entered for “Generate KPIs Asynchronously using the Analytical Service” on page 40. Check Default DSN the Windows Authenticated DSN as the Default DSN.


66 Set up Users for Windows Authentication 5000.1.10.0

Set up Users for Windows Authentication

Windows Authentication users are added differently for SQL Server and Oracle. The following topics outline the steps to add Windows Authentication users for the Engineer's Desktop™ software products.

Create Windows Users in EDM™ Database for SQL Server

Use the EDM Administration utility to create new Users that will log in with Windows Authentication.

1. Launch the EDM Administration Utility and login to the SQL Server DSN connection created in “Configure a DSN when using a SQL Server Database” on page 64 (e.g., EDM 5000.1 Non-WA Db).

2. Select the Users node in the EDM Security node of the Administration tree and follow the menu path, File > New > User

The Create New User dialog appears.

3. Enter the Domain name and user name separated by a \ in the Name field. For example, for the user JSmith in the LANDMARK domain enter LANDMARK\JSmith.

Important!

Only a DBA user can create new users. For information on granting DBA privileges for a user contact your Database System Administrator. A default account 'edmadmin' is provided for the SQL Server database.

Shortcut Methods:

Use the keyboard shortcut Ctrl+Shift+U, or right-click on the Users node, EDM Security node of the Administration tree and select New User... from the menu that appears.

Note:

User names cannot contain apostrophes ( ' ).


5000.1.10.0 Set up Users for Windows Authentication 67

4. Assign the user to a group using the Group drop-down menu. The Group drop-down menu displays the Group name and Security Level. A user can only belong to one Group.

5. Select a Security Level using the drop-down menu. The user's security level will determine the user's access to data entry fields and Output Reports.

6. To use Windows Authentication when logging into the database, activate the External User checkbox.

7. Click OK to save the new user.

The new user will appear under the Users node.

Create Windows Users in EDM™ Database for Oracle

The creation of Windows Users in the EDM database for Oracle is described in the following two procedures.

Step 1 - Create Users in Oracle

1. Logon to Oracle as DBA.

C>sqlplus username/password@tnsname as sysdba

2. Display the Oracle System Flag "remote_os_authent"

sql>show parameters remote_os_authent

3. This system flag should be set to TRUE. If it is set to FALSE change the parameter to TRUE.

sql>alter system set remote_os_authent=TRUE scope=spfile;

4. Display Prefix parameters

sql>show parameters os_authent_prefix

Note:

The password for the newly created user defaults to the user name. (e.g., User Name=drilling; Password=drilling). Password must be at least 8 characters.


68 Set up Users for Windows Authentication 5000.1.10.0

5. Parameter os_authent_prefix can be set to either an empty or non-empty string.

a. If it is empty enter:

sql> alter system set os_authent_prefix='' scope=spfile;

b. If it is not empty enter:

sql> alter system set os_authent_prefix=\<prefix string goes here> scope=spfile;

6. The Oracle default is "OPS$". Enter a prefix string, for example:

sql>alter system set os_authent_prefix=’EDM$’ scope=spfile;

7. Oracle uses the prefix to narrow down its focus in matching users' name that start with the prefix.

8. Restart the database.

sql>shutdown

sql>startup

Step 2 - Create Users in EDM™ Administration

The EDM Administration utility automatically detects when a user is connected to an Oracle database and changes the Create New User dialog appropriately.

1. To create a new user, select the Users node in the EDM Security node of the Administration tree and follow the menu path: File > New > User.

The Oracle version of the Create New User dialog box appears.

Shortcut Methods:

Use the keyboard shortcut: Ctrl+Shift+U, or right-click on the Users node, EDM Security node of the Administration tree and select New User... from the menu that appears.


5000.1.10.0 Set up Users for Windows Authentication 69

2. Enter the Oracle username in the Name field including the prefix if applicable (e.g., DOMAIN\jsmith or with a prefix EDM$LANDMARK\jsmith).

3. Set SQLNET.ORA file.

a. Open the SQLNET.ORA file with Notepad and set authentication to use the following: SQLNET.AUTHENTICATION_SERVICES= (NONE)

b. Save the file and close Notepad.

4. Assign the user to a group using the picklist in the Group field. A user can only belong to one Group.

5. Select a Security Level using the drop-down menu. The user's security level will determine the user's access to data entry fields and Output Reports.

6. Enter the TempTablespace and DatabaseTablespace names. By default the tablespace is EDMSPC.

7. Activate the External User checkbox.

8. Click OK.

The new user will appear under the Users node.

Note:

User names cannot contain apostrophes ( ' ).


You must reboot after configuring iWellFile™ software, before you can go live.


70 Configure Internet Explorer on the Client Machine 5000.1.10.0

Configure Internet Explorer on the Client Machine

Internet Explorer must be configured on the Client machine to avoid the Connect to dialog from appearing every time you change pages in iWellFile™ software.

1. From the Internet Explorer window, follow the menu path Tools > Internet Options.


3. Verify that the Enable Integrated Windows Authentication setting is selected.

4. Click OK to close the Internet Options dialog.

5. Close all your Internet Explorer windows before trying iWellFile software again.

Customize the User Interface iWellFile™ Software Installation Guide

5000.1.10.0 Overview 71

Customize the User Interface

Overview

The iWellFile™ software contains a number of configuration files that allow customers to customize the user interface area of the application. These configuration files are located in the website directory on the iWellFile software web server.

Starting in release 5000.1.1 some configuration files ship with two folders.

• Landmark - The Landmark folder contains the default configuration of the application.

• Custom - The Custom folder contains configurations that are customized by administrators.

Configurations made in the Custom folder override configurations made in the Landmark folder. Future installs of iWellFile software will not overwrite configurations made to files located in the Custom folder.

The following configuration options are available:

• Administration Page - This page allows System Administrators allows to control and configure the application from the browser window. For more information see “Administration Page” on page 75.

• Launch in Context Support - This feature allows administrators to configure external launch of the iWellFile software in context using available command line parameters. For more information see “Launch in Context Support” on page 84.

• Guest Login - This features enables administrators to configure a guest account, which can be restricted. For more information see “Guest Login” on page 86.

• iWellFile Layout Configuration -The Single Well, Multiple Wells, and Dashboard pages can be configured by editing the

iWellFile™ Software Installation Guide Customize the User Interface

72 Overview 5000.1.10.0

page's ASPX file. For more information see “Layout Configuration” on page 88.

• iWellFile Configuration File - This file is used to configure ODBC Data Source Name Selection, Application Settings Tags and Session Timeout. For more information see “iWellFile™ software Configuration File” on page 90.

• Well Operations Tab - Configure the fields displayed and layout of the Well Operations Tabs of the Multiple Wells and Dashboard pages. For more information see “Well Operations Tab Configuration” on page 100.

• Well Operations Display Selection Configuration File - This file is used to configure Configuration Displays, Highlight Tight Group Name, Display Attribute Name, Calendar Incident Icon Configuration and Well Operations Summary Field Security. For more information see “Well Operations Tab Display Selection Configuration” on page 113.

• Lessons Learned - This document describes the XML configuration files that control the GUI of Lesson Learned module of iWellFile application. For more information, see page “Lessons Learned Screens Customization-iWellFile” on page 104.

• Key Performance Indicators - Customize Key Performance Indicators calculated and displayed in the Performance Tabs of the Single Well, Multiple Wells, and Dashboard pages. For more information see “Key Performance Indicators Tabs Configuration” on page 120.

• Report Customization File - This file allows administrators to configure the report links displayed in the Well Operations tabs. For more information see “Report Customization File” on page 127.

• Chart Configuration - Customize Charts appearing in the Dashboard, Multiple Wells and Single Well pages. For more information see “Chart Configuration ” on page 128.

• Well Initialization Configurations - Configure the sections of the four well initialization windows. For more information see “iWellFile™ Software Initialization Configurations” on page 130.

• Log File Location Configuration - Allows administrators to define the path where iWellFile software should look for log files


5000.1.10.0 Overview 73

on the Administration page > iWellFile Control. For more information see “Log File Locations Configuration” on page 131.


74 Overview 5000.1.10.0

• Configuring Default Filter on Startup - Customize filter to user preference and to reduce the number of wells displayed. For more information see “Configure Default Filter on Startup” on page 132.

• Style Sheets - Change the look and feel of the iWellFile™ software (e.g. fonts, colors, spacing). For more information see “Configure the iWellFile Style Sheet” on page 133.

• Themes - select one of the iWellFile software themes or build your own style sheets. For more information see “Themes” on page 136.

• Text Labels and Internationalization - Rename field name labels and configure iWellFile software to display in a different language. For more information see “Text Labels and Internationalization” on page 138.

Applying changes to iWellFile software:

Once iWellFile software configuration files have been modified, you must reboot the server for the changes to take effect. Configuration of Style Sheets requires that the web page be refreshed to implement changes; you need not reboot.


5000.1.10.0 Administration Page 75

Administration Page

The Administration option allows iWellFile™ software administrators to control and configure the application from the browser window. The following pages are available from the Administration link.

• Announcements - add, edit and delete Announcements (page 75);

• Daily Operations Report Summary - view a summary of report for the Well, Event and Rigs sent over the past week (page 77);

• iWellFile Control - manage the iWellFile software instance without having to log onto the web server (page 78);

• Profiling - view and record time iWellFile software is spending on loading each panel on the various pages (page 81);

• Data Generation Login - define a DSN that will generate KPIs asynchronously using the Analytical Service (page 82).

The Administration link is only visible to System Administration users who have been granted access to the iWellFile.Administration application security token.

Announcements

Announcements allow administrators to publish messages to iWellFile software users. These messages automatically appear each time a user logs into the application or when the button is selected in the toolbar.

The Announcements page displays a listing of existing announcements. From this page a user can add, edit, delete announcements.

The List of Announcements can be filtered based on the date range the announcement is active and the Author.

Note:

If pop-ups have been disabled Announcements will not appear. This functionality requires the use of pop-up windows.


76 Administration Page 5000.1.10.0

To search Announcements:

1. Select a Date using the button.

2. Select an individual Author or ALL authors.

3. Click the Search button.

4. A list of all Announcements, active on the selected date and for the selected Author (or all authors) appears.

To view all Announcements:

1. Leave the Date field blank, and select All from the Authors picklist.

To add an Announcement:

1. From the Administrations drop-down menu in the iWellFile™ software toolbar, select the Announcements menu item.

2. Select the button to open the Add/Edit Announcements window.

3. To define the date the announcement begins to appear, click the button to select the Announcement Date.

4. To define the date the last day the announcement appears, click the button to select the Expiry Date.

-or-

To define the number of days the announcement will appear in the application from the Announcement Date, select a value from 1 - 10 from the Duration picklist.

5. Enter a concise description of the announcement in the Title field.

6. Enter the announcement text in the Description field.

Pop-up Reminder:

If pop-ups have been disabled the Add/Edit Announcements window will not appear. This functionality requires the use of pop-up windows.



7. Click the Save button to save changes.

8. Click the Close button to close the window.

9. The announcement appears each time a user logs into iWellFile™ software starting on the Announcement date and ending on either the Expiry date or when the duration has been exceeded.

To edit an Announcement:

1. Click on the announcement title. The Add/Edit Announcements window opens.

2. Enter the announcement.

3. Click the Save button to save changes.

4. Click the Close button to close the window.

To delete an Announcement:

1. Click on the announcement's Delete link.

2. A dialog appears, confirming the deletion of the announcement. Click OK to delete the announcement or click Cancel to cancel the deletion operation.

Daily Operations Report Summary

iWellFile software Daily Operations Report Summary allows the administrator to view a summary of report for the Well, Event and Rigs sent over the past week.

• If a report has been generated for a given day then a link to the Daily Drilling Report is displayed.

Pop-up Reminder:

If pop-ups have been disabled the Add/Edit Announcements window will not appear. This functionality requires the use of pop-up windows.



• If no report exists for the day (but the Event was active on that day) then the cell is displayed as orange with the message NR (No Report Present).

• If the Event was not active then the cell of the corresponding days is empty and shown as green.

iWellFile Control

The iWellFile Control page allows administrators to manage the iWellFile™ software instance without having to log onto the web server. This page includes the application service controller, the report generation service controller and a list of application logs.

Application Status area

Use this area within the iWellFile Controls to determine the number of users connected to iWellFile software and to Run, Pause and Stop the application which may provide information regarding issues such as memory leak. This feature also allows the administrator to pause the application which will prevent new sessions from being accepted; or stop the application which will abort existing sessions (allowing for maintenance).

Any user who tries to login while iWellFile software is paused or stopped, receives a message that the web site is in maintenance. Only the administration user is allowed to login in when iWellFile software is paused or stopped.

Click the button to start the application.

Click the button to pause the application. Currently logged in users can continue to use the application. Any user who tries to login receives



a message that the web site is under maintenance. Pausing the application may be useful when the administrator wants to limit the load on the application.

Click the button to stop the application. All sessions are terminated and a message appears notifying the user that the application is under maintenance. Any user who tries to login receives a message that the web site is under maintenance. Stopping the application may be useful when the administrator is testing or changing the application.

Report Generator Service

The Report Generator Service informs the administrator of the status of the report generator as it generates reports for users.

The Report Generator Status gives the current stat of the Report Generator Service (i.e., Running... or Stopped...).

Click the button to view a listing of jobs currently in the queue. This button must be clicked to view changes in the Job Queue Status.

Click the button to stop the current report generation service and send all items in queue to a new report generation process.

Select the Clear All Jobs checkbox and click the Refresh or Restart buttons to cancel all queued reports.

The Maximum Reports field defines the number of reports generated prior to the report generator services restarting. The application shuts down the report generator process once the maximum report count is



reached. This is a preventive measure for potential problems with the Report Generator Service (e.g., memory leaks).

The Memory Consumed field displays the amount of memory used by the Report Generator. This value is useful in diagnosing potential problems with the Report Generator Service (e.g., memory leaks).

Application Logs

iWellFile Logs area allows administrators to view various log files maintained by the application. These log files are useful for troubleshooting problems that may be occurring with the application. The log files reside on the web server which may not always be accessible. This feature provides simple access.

• Click the log file link to access the current log file.

• Click on the Archive button to add the current log file to the Archive.

The log file archive, located on the iWellFile™ software server in the Inetpub\wwwroot\iWellFile_5000.1\Logs folder, contain a folder for each log type. Log files are named by the date and time they were archived. For example, a log file archived on November 24, 2006 at 10:11 am would be named 20061124101121iWellFile.log.

When the Archive button is clicked, the log file link is disabled. This link will become available again once a new log file is created. A disabled log file links indicates that no log file exists.



The following logs files are available:

- iWellFile log- iWellFile Report System Front End- Report System .NET Code- Report System Java Code- Wellbore Schematics and Well Plots- Compass Plots Log 1- Compass Plots Log 2- Event Viewer- Session Log- Reports Log

Profiling

The Profiling page enables administrator to view and record time the application is spending on loading each panel on the various pages. The Profiling feature captures the SQL being executed and the time the application is taking to execute the SQL.

To begin Profiling Data:

1. From the Administrations drop-down menu in the iWellFile™ software toolbar, select the Profiling menu item.

The Profiling window opens.

2. Click the Start Profiling button to begin recording SQL actions. As the application is used the SQL information is collected.

3. Click the Refresh button to load the data collected in the Profiling window. This button must be clicked each time you want to update the information gathered.

- The execution time of each panel is detailed in the first section. - The Page SQLs - Consolidated area displays a list of all SQL

run on the page and the time it took to run each SQL. This list can be sorted by clicking on the column header. The Page Section column details the page and pane affected by the SQL.

- The Page SQLs - Detailed area displays a list of each SQL run and the file the SQL in located in.



4. Click on the SQL link to view the details of the SQL.

5. To save the recorded information use the browsers File > Save As command.

Data Generation Login

Generate KPIs Asynchronously using the Analytical Service

Any appropriate configured Database DSN (Database Source Name) can use the Analytical Service to calculate the KPI's asynchronously. Only one DSN should be selected as the default and this is the only one that can have KPIs pre-cached.

When to Set System DSN Credentials

If the KPI component displays the following message then the DSN(s) have to be configured.



How to Set System DSN Credentials

1. Log in to the application with Administrator privileges.

2. From the Administrations drop-down menu in the iWellFile™ software toolbar, select the Data Generation Login menu item.

3. Enter the System Credentials. If the DSN is the default then make sure to check the Default DSN check box.

4. Click Save.

5. After entering System Credentials to all of the DSNs, IIS must be reset by running “iisreset” at the command line.


84 Launch in Context Support 5000.1.10.0

Launch in Context Support

iWellFile™ software supports a command line interface which enables administrators to configure external launch of the application in context using available command line parameters like Well ID, Well Common Name, API No, Event ID, Page etc.

This feature enables administrators to integrate iWellFile software with other web sites thus enabling their users to view the well information directly without requiring them to login to the application and manually navigate to their chosen area.

• The name of target page to launch the application in context is ‘LaunchInContext.aspx’.

• The following parameters can be passed to the application:

• DSN, UID & PWD information is used to login into the application. If this information is not passed the guest login information (defined in web.config) is used.

DSN (ODBC DSN Name on web server)

UID (EDM User ID)

Pwd (EDM User Password)

• Well name can be passed using any of the three parameters WellId, WellCName or APINo.

WellId (EDM Well Identifier – CD_WELL.well_id)

WellCName (Well Common Name – CD_WELL.well_common_name)

APINo (Well API Number – CD_WELL.api_number)

• Page to open on start up can be passed using Page parameter. If no page is set, the page shown is the last visited page.

Page (Page Code :‘DB’ – Dashboard, ‘MW’- Multiple Well, ‘SW’- Single Well, ‘AS’- Analysis)


5000.1.10.0 Launch in Context Support 85

• Event ID can be passed using the Eventid parameter. If this is not passed then the most recent/last seen Event of the Well is shown.

EventId (Event Identifier – DM_EVENT.event_id)

• Current date can be passed using Date parameter. If date is not passed, then the last date of the Event is shown.

Date (Display Date)

Examples:

http://<Server>/iWellFile_5000.1/LaunchInContext.aspx?UID=edm&PWD=edm&DSN=dsname&WELLID=0xzsefeyydg&Page=SW&Date=12/01/2006&Eventid=gdxw63

http://<Server>/iWellFile_5000.1/LaunchInContext.aspx?UID=edm&PWD=edm&DSN=dsname&WELLID=0xzsefeyydg&Page=SW

http://<Server>/iWellFile_5000.1/LaunchInContext.aspx?WELLID=0xzsefeyydg&Eventid=gdxw63

http://<Server>/iWellFile_5000.1/LaunchInContext.aspx?WELLID=0xzsefeyydg


86 Guest Login 5000.1.10.0

Guest Login

The Guest Login functionality enables administrators to configure a guest account, which can be restricted. Guest Login is configured in the Web.config file located on the iWellFile™ server (e.g., C:\Inetpub\wwwroot\iWellFile).

The Web.config file is not stored in a Custom folder and therefore will be overwritten by a new installation of iWellFile software. Prior to upgrading to a newer version of iWellFile software, verify that these customized files have been backed up.

Required Knowledge: Knowledge of XML is required to configure this file.

The configuration file can be edited using any standard text editor (e.g., Wordpad).

Save a backup copy of the original Web.config file prior to making any changes.

To configure the guest login:

1. Obtain a user name and password from the EDM™ database Administrator, which will be used for the guest login. This account should be configured by the EDM database System Administrator with the appropriate limited privileges to the EDM database. In the following steps the username "guest" and password "landmark" are used.

2. Open the iWellFile software configuration file, Web.config.

3. Scroll down the file to the end of the appSettings tag, where the guest_username key is located.

4. Define the following parameter keys for the guest login information:

IIS Reset.

Once the configuration file has been modified, the IIS Service must be restarted on the web server for the changes to take effect.


5000.1.10.0 Guest Login 87

a. Enter the user account name for the EDM™ database guest user account. In this example, the user is edm.

<add key="guest_username" value="guest" />

b. Enter the user password for the EDM database guest user account. In this example the password is landmark.

<add key="guest_password" value="landmark" />

c. Enter the Data Source Name for the database that the guest login will use. In this example, the Data Source is EDM Single User Db.

<add key="guest_DSN" value="EDM Single User Db" />

5. Save and close the Web.config file.

6. Enter the iWellFile™ software site address followed by guest.aspx. For example http:\\Landmark\iWellFile\guest.aspx

7. The guest user is automatically logged into iWellFile software using the parameters set above (i.e., user edm, password landmark and DSN EDM Single User Db).


88 Layout Configuration 5000.1.10.0

Layout Configuration

The Single Well, Multiple Wells, and Dashboard pages can be configured by editing the page's ASPX file. Layout for each of these pages is contained within the configuration files (SingleWell.aspx, MultipleWells.aspx, and Dashboard.aspx), located on the web server in the iWellFile™ software website directory (e.g., C:\Inetpub\wwwroot\iWellFile). The configuration file is used to define the layout of the tabs appearing in the application.

Required Knowledge: Knowledge of HTML is required to configure this file.


Save a backup copy of the original default.aspx file prior to making any changes.

The SingleWell.aspx, MultipleWells.aspx, and Dashboard.aspx files organize tabs using HTML tables. Tabs can be reorganized and hidden by editing this file.

The following example illustrates the removal of the Rig Count/Safety Incident panel on the Dashboard page.

1. Save a backup copy of the Dashboard.aspx prior to making any changes.

2. Open the Dashboard.aspx file using a text editor such as Microsoft® Notepad.

Backup ASPX Files!

The ASPX files are not stored in a Custom folder and therefore will be overwritten by a new installation of iWellFile software. Prior to upgrading to a newer version of iWellFile software, verify that these customized files have been backed up.

IIS Reset

Once the iWellFile configuration file has been modified, the IIS Service must be restarted on the web server for the changes to take effect.

5000.1.10.0 Layout Configuration 89

3. Navigate to the location of the Rig Count HTML row:



<td valign="top" align="left" width="32%" height="100%">

<iFRAME id="RigCount" SRC="RigCountContainer.aspx" scrolling="no" width="100%" height="100%"

frameborder="no" marginheight="0" marginwidth="0" vspace="0" hspace="0"></iFRAME>

</td>



4. Delete or comment out the row using the  tags.

5. Save the file.

6. Refresh the iWellFile™ software page.

Note:

There is no row listed in this file for Safety Incident. The Safety Incident tab is part of the same row, which displays the Rig Count. For this reason both tabs are removed when the row is removed from the .ASPX file.


90 iWellFile™ software Configuration File 5000.1.10.0

iWellFile™ software Configuration File

The iWellFile software configuration file (Web.config) is located on the web server in the virtual directory where the application has been installed (e.g., C:\Inetpub\wwwroot\iWellFile).

The iWellFile software configuration file is used to store the application configuration settings (such as applications settings, session timeout, Company Logo's etc.). It operates much like a traditional Windows INI file. Settings are stored in the configuration file in an XML-based format. Each setting has a start tag and an end tag that delimit the setting value.

The Web.config file is not stored in a Custom folder and therefore will be overwritten by a new installation of iWellFile software. Prior to upgrading to a newer version of iWellFile software, verify that these customized files have been backed up.


The configuration file can be edited using any standard text editor (e.g., Microsoft® Wordpad).

Save a backup copy of the original Web.config file prior to making any changes.

IIS Reset



5000.1.10.0 iWellFile™ software Configuration File 91

Applying changes to iWellFile Software

Once the iWellFile software configuration file has been modified, the IIS Service must be restarted on the web server for the changes to take effect.

This topic outlines the following features defined in the web.config file.

• ODBC Data Source Name Selection • Application Settings Tags• Session Timeout

ODBC Data Source Name Selection

The web.config file contains a new 'DSNList' XML parameter. This parameter enables the iWellFile™ software Administrator to control the EDM™ databases, the application can connect to by configuring a restricted list of EDM database ODBC DSN selections.

If no DSN is added in <DSNList> all the DSNs configured on the web server machine will appear on the login page. For each type of provider there is a different syntax. If no provider is given, it will consider it an ODBC connection.

Syntax:

<DSNList>

-- ODBC CONNECTION SYNTAX--

<DSN Provider="odbc" Server="LandmarkApps" Database="edm"><![CDATA[EDM 5000.1Single User Db]]></DSN>

OR

<DSN><![CDATA[EDM 5000.1 Single User Db]]></DSN>

-- SQLCLIENT CONNECTION SYNTAX. (FOR SQL SERVER ONLY).--

<DSN Provider="sqlclient" Server="LandmarkApps" Database="edm"><![CDATA[EDM 5000.1Single User Db]]></DSN>

-- SQLCLIENT CONNECTION SYNTAX. (FOR ORACLE ONLY).--



<DSN Provider="odp" Server="Oracle_service_name" Database="Oracle_service_name"><![CDATA[EDM 5000.1 Single User Db]]></DSN>

-- SQLCLIENT CONNECTION SYNTAX. (FOR ORACLE ONLY).--

<DSN Provider="oracleclient" Server="Oracle_service_name" Database="Oracle_service_name"><![CDATA[EDM 5000.1 Single User Db]]></DSN>

</DSNList>

Application Settings Tag

The appSettings tag contains the following application configuration keys:

General Settings

CompanyLogo.url - This key defines the logo file that appears in the upper left corner of the application. By default, the Landmark logo is displayed. Supported image formats: BMP, JPG, GIF.

Data Analyzer™ software Graph Width and Height - The keys DataAnalyzer.GraphWidth and DataAnalyzer.GraphHeight, define the height and width of graphs (in pixels) displayed in the Data Analyzer software query window.

Data Analyzer Datum - The DataAnalyzer.Datum key defines the datum type used to display depth reference values selected and displayed in the Data Analyzer software query window. There are two supported values that can be defined by this key:

• System - This setting forces Data Analyzer software to return depth values relative to the system datum elevation. The System datum is the absolute zero height or depth for the project. It is the depth from which all wellbore depths are measured. Typically the default System datum is Mean Sea Level.

Oracle Connection Note.

In the case of ODP or OracleClient the Server and Database should be set to the Oracle_service_name and not to the machine name and database name.

• Default- this setting forces Data Analyzer software to return depth values relative to the default well datum elevation configured in Well Properties for each well.

Analysis Layout Graphs - The Analysis Layout Graph Width and Height keys define the width and heights of the Analysis windows when the defined pane option is selected.

Short Date Format - The key DateFormat enables the iWellFile™ software administrator to adjust the date format to meet the requirement of the company or region. This configuration overrides the web server's Regional settings date format. This custom date format functionality affects iWellFile software web server page outputs only (e.g. Well Operations displays, Key Performance Indicators). Outputs generated from iWellFile using external modules are not affected by this change (e.g. PROFILE™ software Wallplot Composer plots, Data Analyzer™ software queries, OpenWells® software output reports).

<add key="DateFormat" value="dd-MMM-yy" /> 

Restricted Field Format - The RestricedFieldFormat key is used to define whether a restricted field will be hidden or grayed out.

Log Debug Message - The LogDebugMessage key is used to add additional content to the log file.

Report Service Settings

Report Generator Days To Keep Report - The ReportService.DaysToKeepReport key defines the number of days a report will be kept in the cache prior to being deleted.

Report Service Maximum Reports - The ReportService.MaxReports key defines the number of reports generated before the Report Generator instance restarts. By default, this value is set to 10 reports.

Report Service Cache Path - The ReportService.CachePath key defines the location of the cached reports.

Daily Drilling Report Path - The DailyDrillingReportPath key defines the path were the OpenWells® software Daily Drilling reports are located.

PROFILE Schematics Cache Expiry - The Schematics.CacheExpiry setting defines the number of days PROFILE™ software generated



schematic image files are kept on the web server before they are deleted.

Output Files Cache Expiry - The OutputFiles.CacheExpiry setting defines the number of days Output files (except PROFILE software Schematics) are kept on the web server before they are deleted.

Compass Graph Output Settings

COMPASS Graph Quality Page - The key Compass.GraphQualityPage defines the size of the COMPASS™ software graph image generated on the Single Well page.

COMPASS Graph Quality Popup - The key Compass.GraphQualityPage defines the size of the COMPASS software graph image generated on the popup page.

Graph Curve Color - The Graph.CurveColor key allows the user to control the curve colors for the following xy graphs:

• xyCostVDaysDashboard• xyCostVDaysMultipleWells• xyDepthVCostDashboard• xyDepthVCostMultipleWells• xyDepthVDaysDashboard• xyDepthVDaysMultipleWells

COMPASS Graph Width Popup - The key Compass.GraphWidthPopup defines the width of graphs (in pixels) displayed in the COMPASS™ software Wellpath graphs.

COMPASS Graph Height Popup - The key Compass.GraphHeightPopup defines the height of graphs (in pixels) displayed in the COMPASS software Wellpath graphs.

COMPASS Graph Format - The key Compass.GraphFormat defines the file format of the COMPASS software Wellpath graphs. By default, this value is set to PNG.

Popup Graph Width - The key Popup.GraphWidth defines the width of graphs (in pixels) displayed in iWellFile™ software.

Popup Graph Height - The key Popup.GraphHeight defines the height of graphs (in pixels) displayed in iWellFile software.



Login Date - The Login.Date key defines the report selection date that configures which Daily Reports appear when an Event and date are selected in the Single Well page. This key can be set to "today" or "yesterday".

Guest Account Configuration

Guest Name and Password - The guest_username key defines the EDM™ database login username for users using the iWellFile software Guest Login option. The guest_password key defines the EDM login password for users using the iWellFile software Guest Login option.

Guest Data Source Name - The guest_DSN key defines the EDM database being used by users using the iWellFile software Guest Login option.

iWellFile Tracing - The key iWellFile.Tracing enables the iWellFile software to record errors to a log file. To log application errors, set this key value to TRUE.

Well Filter Default - The key WellFilter.Default defines the default Well Filter that is used when no filter has been selected.

Access to iWellFile main pages

My iWellFile Setting - The MyiWellFileSetting key allows administrator to hide pages and Production graphs as required. Setting the value of the key to False will hide the specified page or graphs on the iWellFile™ software site. The following MyiWellFileSetting keys are available.

• MyiWellFileSetting.ShowDashBoard - show/hide the Dashboard page

• MyiWellFileSetting.ShowMultipleWell - show/hide the Multiple Wells page

• MyiWellFileSetting.ShowSingleWell - show/hide the Single Well page

• MyiWellFileSetting.ShowAnalysis - show/hide the Analysis page

• MyiWellFileSetting.ShowLessonsLearned - show/hide the Lessons Learned page

• MyiWellFileSetting.ShowAdministration - show/hide the Administration page



• MyiWellFileSetting.ShowRigOperation - show/hide the Rig Operations page

• MyiWellFileSetting.DefaultUnitSet - define the default Unit Set

• MyiWellFileSetting.DefaultBarGraphFormat - define graphs as stacked or unstacked

iWellFile software Depth Graphs

Graph MD vs Cost vs Days Events - The Graph.MDvsCostvsDays.Events key allows administrator define the Event Types for which the MD vs Cost vs Days graphs will appear.

Dashboard Page

Dashboard Calendar Show Report Indicators - The Dashboard.Calendar.ShowReportIndicators key turns the * denoting data present on a day on and off. This key could be set to false to improve performance.

Show and Hide Panels - The following panels can be shown or hidden in the Dashboard page:

• Dashboard.ShowProductionGraphs• Dashboard.ShowRigSummaryPlots• Dashboard.ShowMonthlyCumCostGraphs• Dashboard.ShowKPISection• Dashboard.ShowCommonWellGraphs• Dashboard.ShowGraphs.CostvsDays• Dashboard.ShowGraphs.MDvsCost• Dashboard.ShowGraphs.RigActivity• Dashboard.ShowGraphs.Operations• Dashboard.ShowGraphs.SafetyIncidents• Dashboard.ShowGraphs.SISummary• Dashboard.ShowGraphs.MonthlyCumlativeCost

Multi Wells Page

Multiple Wells Calendar Show Report Indicators - The MultipleWells.Calendar.ShowReportIndicators key turns the * denoting data present on a day on and off. This key could be set to false to improve performance.

Show and Hide Panels - The following panels can be shown or hidden in the Multi Wells page:



• MultipleWells.ShowMultiWellsSection• MultipleWells.ShowPerformanceSection• MultipleWells.ShowMDvDaysGraphSection• MultipleWells.ShowGraphs.MDvsDays• MultipleWells.ShowGraphs.CostvsDays• MultipleWells.ShowGraphs.MDvsCost

Single Wells Page

The following panels can be shown or hidden in the Single Wells page:

• SingleWell.ShowGraphs.MDvsDays• SingleWell.ShowGraphs.CostvsDays• SingleWell.ShowGraphs.MDvsCost

Rig Operations Page

The following keys can be used to configure the Rig Operations page.

Rig Color - defines the color code for each Event type displayed in the Rig Operations page.

MultipleRigEventColor - defines the color code for multiple Events.

UnknownRigEventColor - defines the color code for unknown Events.

NoRigEventActiveColor - defines the color code when no Event exists.

RigOperations.RigStartDate - defines the field used to define the Rig Start Date.

RigOperations.RigEndDate - defines the field used to define the Rig End Date.

Licensing Pool

RigOperations.RigEndDate - The iWellFile.LicensePoolSize key defines the size of License Pool. "0" means no licensing pooling.



Session State Settings

After 20 minutes of inactivity, iWellFile™ software displays the following dialog and automatically logs out the user. This setting can be changed by the iWellFile software Administrator. Click OK on this dialog and the Logged out page appears with a link to login again.


5000.1.10.0 iWellFile Service Registry Settings 99

iWellFile Service Registry Settings

iWellFile™ software installs services to generate Report/Schematics/Wallplots/COMPASS plot and Data Analyzer plot. Registry keys at (HKEY_LOCAL_MACHINE\SOFTWARE\Landmark Graphics Corporation\EDT\5000.1\iWellFile) can be modified to change the default setting of this services. Following are the keys to configure the services.

Registry Key Name Description

BatFilePath Path of the Executable file, which the service invokes to complete the request.

IdleTimeout IdleShutdown key determines the number of minutes the service must be idle before automatically shutting down. By default, this vale is set to 20 minutes.

LogDebugMessage The LogDebugMessage key is used to add additional content to the log file. Value can be 0 or 1 (i.e. true or false).

LogFolder Defines the location of the Log File.

Port The Port key determines the TCP port used by the application.

RequestTimeout RequestTimeOut Key determines the number of minutes a request can take to complete. It is helpful in cases when a process hangs for unknown reasons.

MaxInstances The MaxInstances key enables administrators to run multiple instances of the service on servers with multiple CPUs.Landmark recommends a maximum of 1 instance per CPU.


100 Well Operations Tab Configuration 5000.1.10.0

Well Operations Tab Configuration

The Well Operations Tab configuration files (WellOperations.ascx, WellOperationsMultipleWells.ascx, and WellOperationsDashboard.ascx) are located on the web server, in the iWellFile™ software website “Controls” directory (e.g., C:\Inetpub\wwwroot\iWellFile\Controls).

Each page may be customized; and, the pages may be customized differently if required. The configuration files can be edited to add or remove fields appearing in the Well Operations tab.

The WellOperations.ascx, WellOperationsMultipleWells.ascx, and WellOperationsDashboard.ascx files are not stored in a Custom folder and therefore will be overwritten by a new installation of iWellFile software. Prior to upgrading to a newer version of iWellFile™ software, verify that these customized files have been backed up.

Required Knowledge: Knowledge of C#.NET, SQL, and HTML is required to configure this file.


Save a backup copy of the original WellOperations.aspx file prior to making any changes.

Applying changes to iWellFile software

The Well Operations configuration files define the data fields and layout of the Well Operations data table.

There are now three independent KPI tabs in Dashboard, Multiple Wells, and Single Well page:

• Dashboard: DashboardKPI.xml• Multiple Wells: MultipleWellsKPI.xml

IIS Reset.



5000.1.10.0 Well Operations Tab Configuration 101

• Single Well: SingleWellKPI.xml

Each KPI area is independent; the pages can be customized differently so they are appropriate to each page.

Configuring Data Fields and Layout

Adding a Field

Adding a new field to the Well Operations tab is implemented in two steps: Define and Call the Data Field in the Database, and Add the New Field to the Table

The following example shows how to add the field CD_Well.well_legal_name to the Standard Well Operations tab:

Define and Call the Data Field in the Database

The following code identifies the new data and extracts it from the database for each Well Operation listed in the View All Well Operations dialog. This code should be placed within the <script language="C#" runat="server"> </Script> tag. The comments within this code define the function of the line.

protected override DataTable GetStandardDisplayData (int PageNumber,out int TotalNoOfRecords)

{

// Call the base class function

DataTable table = base. GetStandardDisplayData (PageNumber,out TotalNoOfRecords);

// Add the extra column to it.

table.Columns.Add("well_legal_name",typeof(string));

// Calculate the value of column added for each row.

foreach(DataRow row in table.Rows)

{

string sql =

"SELECT well_legal_name " +

"FROM CD_WELL " +


102 Well Operations Tab Configuration 5000.1.10.0

"WHERE well_id = '" + row["well_id"] + "'";

DataTable dataTable = DataAccess.ExecuteQuery(sql).Tables[0];

if(dataTable.Rows.Count > 0)

{

row["well_legal_name "] = dataTable.Rows[0]["remarks"];

}

else

{

row["well_legal_name "] = "no data";

}

}

return table;

}

Add the New Field to the Table

Once the data has been called from the database (see above), you can display it within the Well Operations table. The following example adds the data to a new row within the Well Operations table. The data can also be added as a column in an existing row.

<tr>

<td colspan=2 class="WellOperationsDetailLabel" style="PADDING-LEFT: 10px"><%# GetLabel("CD_WELL", "well_legal_name", false) %>

</td>

<td colspan=12 class="WellOperationsDetailData"><%# GetValue("CD_WELL", "well_legal_name", Container.DataItem) %>

</td>

</tr>


5000.1.10.0 Well Operations Tab Configuration 103

Removing a Field

To remove a field in a Well Operations tab:

Select the Table Row (i.e., from the field's <tr> tag to its closing tag </tr>) for the field and press the Delete key on the keyboard.


104 Lessons Learned Screens Customization-iWellFile 5000.1.10.0

Lessons Learned Screens Customization-iWellFile

Purpose of Document

This document describes the XML configuration files that control the GUI of Lesson Learned module of iWellFile application. Using these XMLs files admin can change the layout that is suitable to use.

Details of Configuration files

There are 3 configuration files each dedicated to different section of lesson learned screens.

1. SearchCriteriaSelectorConfig.xml2. SearchResultConfig.xml3. LessonLearned_Details.xml

These files are present at location mentioned on page 90.

SearchCriteriaSelectorConfig.xml

This is meant for configuring the filter section of lessons search screen.

SearchResultConfig.xml

This is meant for the configuring the results section of lessons search screen.


5000.1.10.0 Lessons Learned Screens Customization-iWellFile 105

LessonLearned_Details.xml

This is meant for configuring the Add/Edit lesson details screen.

Location of Configuration files

Configuration files are present in following folders.



<iwellfile folder>\Config\Landmark\LessonLearned\ - Contains the default configuration provided by Landmark.

<iwellfile folder>\Config\Custom\LessonLearned\- Customer can put their customized configuration here. Configuration here overrides the default configuration.

How to Configure

Config files can be edited in any text editor, however use of an XML editor will make the things easier. All the screen shots in this document are using XML editors.

It is advisable not to directly edit the files in “Config\Landmark\LessonLearned\” location; instead copy the config file(s) into custom config files location “Config\Custom\LessonLearned\” and do editing in custom location. File(s) in custom location overrides the Landmark location file(s).

SearchCriteriaSelectorConfig.xml

This config file declares the CD_LESSON attributes that are to be displayed in search criteria.

This configuration file has 3 sections one for each type of search options (Canned, Free text and Fixed).



Each section again has 6 child tags <Filter>, that again encompasses the information about the filter attribute. <Filter> tag has following sub tags.

<AttributeName> - Put the name of any CD_LESSON attribute here. For example if Well_Type is to be used for filtering criteria, put Well_Type.

<DisplayName> - By default IWellFile will pick the name of Attribute from metadata defined in EDM. Howeever in cases where this is to be changed the new name can be put inside this tag. Leave it blank in case no overriding of metadata name is required.

<Visible> - It has Y/N values. If it is set to N the filter field will not be displayed e.g. if only 4 out of total 6 are set as Visible then only 4 filters will be shown in search criterion. If there are more than 6 <Filter> tags having Visible =Y then only first 6 will be displayed.



SearchResultConfig.xml

This config file declares the CD_LESSON attributes that are to be displayed in search result grid.

#1

<SearchResults> - section in Config files encompasses the list of <Column> tags. <Column> tag consists of information about the attributes to be displayed in search grid.

<AttributeName> - Put the name of any CD_LESSON attribute here. For example if Well_Type is to be displayed in searh results put Well_Type here.

<DisplayName> - By default IWellFile will pick the name of Attribute from metadata defined in EDM. Howeever in cases where this is to be changed the new name can be put inside this tag. Leave it blank in case no overriding of metadata name is required.



<Type> - Attribute type i.e. string, number, date, datetime.

<Visible> - It can be Y/N. If it is set to N the filter field will not be displayed .

<Width> - In case a specific width is to be given to a column. put numbers only in this tag. Use blank for automatic option.

<AttachLink> - Valid values are Y/N. Y means this text in this column will be a hyperlink that opens Add/Edit lesson details window.

#2

<AddEditLinkedPage> defines the name of the page that is to be opened when hyperlink in search results grid is clicked.

LessonLearned_Details.xml

This config file declares the CD_LESSON and child tables attributes that are to be placed on Add/Edit Lesson details screen. Using this attributes can be added/removed from the screen.

On screen position of input boxes cannot be changed by this config file. For this editing in AddEditLessons.aspx page is required. A person with good HTML knowledge can change position of attributes fields from the screen.

This configuration file has multiple sections. The main section <CDLessonAttributes> is meant for CD_LESSON table attributes while other sections belong to the child tables of CD_LESSON.



All major sections tag have a list of <Control> sub tags. Each <Control> sub tag is meant for a attribute of table.

The structure of Control tag is as below.



Visible - Valid values are true/false. False means field will not be visible on screen.

Disable - Valid values are true/false. True means the field is disabled on screen.

Read-only – Makes the field on screen as readonly.

isRequiredField – Valid values are Y/N. Y means it will become mandatory.

Following tags are used for seizing he field on screen.

<LabelTextWidth> - Width of Label of input field.

<ControlWidth> - Width assigned to place the control. Complementary to LabelTextWidth.

<ControlSize> - Width of input area. Integer value only.

<ControlHeight> - Height of input area. Integer value only.

Following tags describe the attribute and table.

<BussinessName> - Table Name

<AttributeName> - Table Name

ChildSections

The sections under ChildSection are meant for Child tables of CD_Lesson. Each section has a property “visible” that should be used to hide/display the child table section on screen.

Child section also have the <Control> tags very simier to as explained earlier.

Adding a new CD_LESSON attribute on screen (attribute that is not present in aspx page)

This can be accomplished in 2 steps.

1. Add the field on AddEditLessons.aspx page using following syntex. Good knowledge of HTML will in deciding where the field should be placed.



<uc1:genericinputcontrol

id="date_lesson" - This should be the attribute name as in database

runat="server"

BusinessName="CD_LESSON"

AttributeName="date_lesson"> - This should be the attribute name as in database

</uc1:genericinputcontrol>

2. Add a control tag under <CDLessonAttributes>.

Adding a new Child attribute on screen.

This can be accomplished in 1 step only.

1. Add a control tag under <ChildTableTag e.g. LessonDisscusions , LessonBiblography etc.>.


5000.1.10.0 Well Operations Tab Display Selection Configuration 113

Well Operations Tab Display Selection Configuration

The Well Operations Tab Selection Display configuration file (WellOperationsDisplaySelector.xml) allows administrators to configure Well Operations displays available in the Current View picklist on the Well Operations tab.

This file is located on the web server, in the iWellFile™ software website “Config” directory (e.g., C:\Inetpub\wwwroot\iWellFile\Config\Landmark).

The Landmark folder stores the default settings shipped with the application. When customizing the Well Operations tab selection display, be sure to store the customized version of the WellOperationsDisplaySelector.xml in the Custom folder.


Future installs of iWellFile™ software will not overwrite configurations made to files located in the Custom folder.

Required Knowledge: Knowledge of SQL, and HTML is required to configure this file.

The configuration file can be edited using any standard text editor (e.g., Microsoft® Wordpad).

This topic outlines the following features defined in the Well Operations Display configuration file.

• Configuration Displays• Highlight Tight Group Name• Display Attribute Name• Calendar Incident Icon Configuration• Well Operations Summary Field Security

IIS Reset.



114 Well Operations Tab Display Selection Configuration 5000.1.10.0

Configuration Displays

By default iWellFile™ software contains the following five configurable displays:

• Standard Summary • One Day Operations Summary• 'X' Day Operations Summary• Worldwide Operations Summary• Detailed Daily Operations Summary

<Configuration> Tag

To remove any display from the picklist shown on the Dashboard and Multiple Wells pages remove the corresponding <Configuration> tag. To add a new display add a new <Configuration> tag with proper attributes values as explained below.

<ConfigureLink> Tag

The following tags are used in the configuration. Each display details are enclosed in a parent tag <ConfigureLink>. This tag has the following attributes and Child tags.

Attributes of <ConfigureLink>

• value="OneDayOprSummary" - A unique value given to each display.

• name="One Day Operations Summary" - The name displayed in the Current View picklist.

• File="WellXDailyOperations.ascx" - The display control file name.

• ShowXDaysDropDownSelectionList="N" - Defines if the Number of Reports per Well picklist is displayed.

• XPickListValueRange ="" - Defines the range of Days available in the Number of Reports per Well picklist.

For example,

<ConfigureLink value="OneDayOprSummary"

name="One Day Operations Summary"

File="WellDailyOperations.ascx"

ShowXDaysDropDownSelectionList="N"



XPickListValueRange="">

Child Tags of <ConfigureLink>

• <sql></sql> - SQL to call the list of wells and their attributes to be shown in display. This can be changed when required to display extra fields (also requires a change in ascx file).

• <AllowedBusinessUnit></AllowedBusinessUnit> - Restricts the Business Units (Companies) displayed.

• To allow all Business Units to be displayed use the following:

<BU PolicyID="*" CustomerName="*" />

• To allow select Business Units to be displayed, enter their PolicyID (CD_POLICY.policy_id) as shown below:

<BU PolicyID="4AqbCVvwh0"><![CDATA[HDCS Cement]]></BU>

<BU PolicyID="5ZG7nTJUwh"><![CDATA[FOOTHILLS COMPLETIONS LTD.]]></BU>

<BU PolicyID="gQfDMo2M90"><![CDATA[CHINOOK RESOURCES LTD]]></BU>

<BU PolicyID="K5KP3GLdoQ"><![CDATA[FULL FEATURE OIL & GAS CO.]]></BU>

Highlight Tight Group Name

The <tightGroupSectionGroup> tag is used to highlight the Tight Group name in the Worldwide Operations Summary Display.

Add the name of tight group and unique identifier of Tight Groups to be highlighted in the list as shown below.

<add key="TG001" value="TIGHT" />

<add key="T0001" value="SUPER TIGHT" />

<add key="TG003" value="NORTH RIDGE" />

Display Attribute Name

The <DisplayAttributeNames> tag is used to override Labels stored in the EDM Data Dictionary. If a particular BusinessObject.Attribute is not found in the WellOperationsDisplaySelector.xml file, then the name of attribute will be taken from Data Dictionary. In the following example the rig_name, rig_type, and event_name fields will have the labels Name, Type and Event respectively.

<DisplayAttributeName>

<BusinessObject name="CD_RIG">

<Attribute name="Rig_Name">Name of Rig</Attribute>

<Attribute name="Rig_Type">Type of Rig</Attribute>

</BusinessObject>

<BusinessObject name="DM_DAILY">

<Attribute name="Event_Name">Name of Event</Attribute>

</BusinessObject>

</DisplayAttributeName >

Calendar Incident Icon Configuration

The Well Operations displays and the Single Well Calendar display are both configured to display an incident ( ) icon whenever a safety incident is reported in the OpenWells® software Daily Operations form. These safety incident icons can be disabled through the WellOperationsDisplaySelector.xml file. Additionally, the criteria for displaying Incidents can be changed using customized SQL to select the incidents from the EDM™ database.

The following example outlines the configuration of the Calendar Incident Icon.

<DisplaySecurityIncident>





<key ID="DisplaySafetyIncidentIcon">true</key>

<!-- Define the SQL to define the Criteria of displaying safety incident icon in calender.

**SQL should always return DATE. Icon will be displayed in calender for all the dates returned by SQL.**

SQL Query Macros:

- ->

<key ID="DisplaySafetyIncidentSQLQuery">

<![CDATA[SELECT DISTINCT DM_REPORT_JOURNAL.date_report Saftey_Incident_Dt

FROM DM_REPORT_JOURNAL, DM_DAILY, DM_SAFETY_INCIDENT

WHERE DM_REPORT_JOURNAL.well_id ${CURRENT_WELL}

AND DM_REPORT_JOURNAL.event_id ${CURRENT_EVENT}

AND DM_REPORT_JOURNAL.date_report >= ${START_DATE}

AND DM_REPORT_JOURNAL.date_report < ${END_DATE}

AND DM_REPORT_JOURNAL.report_journal_id = DM_DAILY.report_journal_id

AND DM_DAILY.well_id = DM_SAFETY_INCIDENT.well_id

MACRO DESCRIPTION

${START_DATE} The first day of month selected in Calendar

${END_DATE} The last day of month selected in Calendar

${CURRENT_WELL} The well_id list (after page filter application)

${CURRENT_EVENT}

The Event_id (in case of single well page). For other page it returns "All events i.e. '%'".



AND DM_DAILY.event_id = DM_SAFETY_INCIDENT.event_id

AND DM_DAILY.daily_id = DM_SAFETY_INCIDENT.daily_id]]>

</key>

</DisplaySecurityIncident>

Well Operations Summary Field Security

The Well Operations display supports Data Dictionary field security. The iWellFile Administrator is able to configure custom displays to hide field labels and data to which the user does not have access in OpenWells® software. This architecture uses the user's security level to compare against Data Dictionary security level. When the user's level is less than the field level, no data displays.

Syntax:

<Security>

<BusinessObject name="NAME OF BUSINESS OBJECT">

<Attribute name="ATTRIBUTE NAME">Security Level</Attribute>

</BusinessObject>

</Security>

If security level is not explicitly set for a BusinessObjects.Attribute the default is Zero.

Example:

<Security>

<BusinessObject name="CD_RIG">

<Attribute name="Rig_Name">5</Attribute>

<Attribute name="Rig_Type">3</Attribute>

</BusinessObject>

<BusinessObject name="DM_DAILY">


120 Key Performance Indicators Tabs Configuration 5000.1.10.0

Key Performance Indicators Tabs Configuration

The Key Performance Indicators (KPI) configuration files (KPI.xml, MultipleKPI.xml, and DashboardKPI.xml) are located on the web server, in the iWellFile™ software website “config” directory (e.g., C:\Inetpub\wwwroot\iWellFile_5000.1.1\config\Landmark\KPI).

The Landmark folder stores the default settings shipped with the application. When customizing KPI's, be sure to store the customized version of the XML files in the Config\Custom\KPI folder.



These XML configuration files are used to define calculated operations performance metrics appearing in the Performance Tabs of iWellFile software.

Required Knowledge: Knowledge of SQL and XML is required to configure this file.

Each configuration file can be edited using any standard text editor (e.g., Wordpad).

Important—If You Are Using Oracle: If you are using an Oracle database, you must view the kpi.xml, dashboardkpi.xml, and multiplewellskpi.xml and search for the inline comments that say “SQL Server Version...”. Comment out the SQL Server version, and uncomment the Oracle version. This must be done because by default, Oracle has been commented out in favor of SQL Server.

This topic outlines the following features defined in the KPI configuration files.

IIS Reset



5000.1.10.0 Key Performance Indicators Tabs Configuration 121

Macros

The following macros have been configured for the KPI configuration files:

Syntax

The Syntax used to define a KPI appearing in a Performance tab appears as follows:

<kpi name="KPI DISPLAY NAME" class-name="MEASUREMENT CLASS NAME (optional)">

<sql>

<![CDATA[

SQL QUERY (must return a single numeric value or null)

]]>

</sql>

</kpi>

Macro Description

${TODAY} The selected date in the Calendar tab.

${TOMORROW} The day after the selected date in the Calendar tab.

${START_OF_YEAR} January 1st of the selected year in the Calendar tab.

${DATUM} The value of the currently selected datum reference - can be used only in Single Well KPIs.

${CURRENT_WELL} The well_id of the currently selected well - can be used only in Single Well KPIs.

${CURRENT_EVENT} The event_id of the currently selected event - can be used only in Single Well KPIs.

${FILTER} The current Well Filter as a SQL condition supports Company, Project, Site and Well filters - can only be used in Multiple Well and Dashboard KPIs.

All KPIs must include:

Tables CD_PROJECT, CD_SITE, CD_POLICY and CD_WELL in FROM clause instead of just CD_WELL

Following conditions in WHERE clause

AND CD_PROJECT.POLICY_ID = CD_POLICY.POLICY_ID

AND CD_SITE.PROJECT_ID = CD_PROJECT.PROJECT_ID

AND CD_WELL.SITE_ID = CD_SITE.SITE_ID

Note: Macro ${WELL_FILTER} is still supported, and no change is required in existing KPI SQL if this macro is used. Use of macro ${FILTER} is optional.



Parameters

The KPI DISPLAY NAME parameter defines the label displayed with the performance measure. Enter the KPI's label that will appear in the application. For example, <kpi name="Active Wells">.

The MEASUREMENT CLASS NAME parameter defines the unit measurement class appropriate for the performance metric. iWellFile™ software uses this unit class name to display a unit label after the performance metric value. This parameter should be set for numeric values. Enter the class to define the unit of measurement for the KPI after the label. For example, <kpi name="Daily MD Progress"class-name="CLASS_depth">.

A listing of Measurement classes is found at the beginning of each KPI configuration files.

In addition, the KPIs now contain user configuration options and the KPI xml definitions have the following optional properties:

• lockBlocks - Defines the count of days (starting backward from current day) for which pre-caching should take place. If set to 0 no pre-caching occurs. For example, <lockblocks>3</lockblocks>.

• refreshInterval - Defines the duration in minutes after which KPI Cache expires – will override the web config property per KPI. For example, <refreshInterval>5</refreshInterval>.

• isAsync="true" - Defines whether KPI calculation should be done asynchronously. Default of all KPIs is true if this property is left out. For example, <isAsync>true</isAsync>.



Adding a Field to the Performance Tab

The following two examples illustrate how to add a new KPI to the Performance tab.

Example 1

The following example adds the Safety Incidents (last 30 days) KPI to the Performance Tab, which displays the number of safety incidents reported in the last 30 days.

<kpi name="Safety Incidents (last 30 days)">

<sql>

<![CDATA[

SELECT count(*)

FROM DM_DAILY, CD_WELL, DM_SAFETY_INCIDENT

WHERE

DM_DAILY.date_report >= ${TODAY} - 30 AND

DM_DAILY.date_report < ${TOMORROW} AND

DM_DAILY.well_id = CD_WELL.well_id AND

DM_DAILY.well_id = DM_SAFETY_INCIDENT.well_id AND

DM_DAILY.event_id = DM_SAFETY_INCIDENT.event_id AND

DM_DAILY.daily_id = DM_SAFETY_INCIDENT.daily_id AND

${WELL_FILTER}

]]>

</sql>

</kpi>



Once the web server has been restarted the Safety Incident (last 30 days) field appears. In this example the KPI was added at the top of the Performance Tab.

Example 2

The following example adds the Daily Progress field to the Performance Tab, which displays the measured depth progress for the currently selected day.

<kpi name="Daily Progress" class-name="CLASS_depth">

<sql><![CDATA[

SELECT SUM(progress) FROM DM_DAILY, CD_WELL

WHERE

DM_DAILY.date_report >= ${TODAY} AND

DM_DAILY.date_report < ${TOMORROW} AND

DM_DAILY.well_id = CD_WELL.well_id AND

$(WELL_FILTER)

]]>

</sql>



</kpi>

Once the web server has been restarted the Daily Progress field appears. In this example the field was added at the top of the Performance Tab.

KPI Security Level Support

The KPI configuration files include a Security Level feature. This feature provides the iWellFile™ Administrator with the ability to control access to KPI results returned from iWellFile software. The optional ‘SecurityLevel’ parameter enables the administrator to specify the minimum security level required to display the KPI to the user.

The KPI security level is compared against the user’s security level. If the user's security level is less than that set for the KPI, the KPI result is not displayed. If the user does have sufficient permission, the KPI result is displayed. By default, all Landmark standard KPIs have been configured with security level set to 1 so that all results are available. These values can be adjusted as required.

The following example shows the security setting for the Single Well Page 'Days from Spud' KPI:

<kpi name="Days from Spud" class-name="CLASS_days" SecurityLevel="1">


5000.1.10.0 Report Customization File 127

Report Customization File

The Report Customization file (ReportCustomization.xml) is used to Report links available in the follow areas:

• the Well Operations tabs on the Dashboard and Multiple Wells pages,

• the 24 Hrs Summary tab on the Multiple Wells page,

• the Rig Operations page

• and the Daily Operations Reports summary Tab on the Administration page.

This file is located on the web server in the iWellFile™ software installation directory “config” folder (e.g., C:\Inetpub\wwwroot\iWellFile\config\Landmark).

The Landmark folder stores the default settings shipped with the application. When customizing report links, be sure to store the customized version of the ReportCustomization.xml in the Config\Custom folder.



Instructions for editing the ReportCustomization.xml file is contained within the file.


IIS Reset



128 Chart Configuration 5000.1.10.0

Chart Configuration

The Charts Configuration file (ChartsConfig.xml) is used to configure charts appearing on the Dashboard, Multiple Wells and Single Well pages. This file is located on the web server in the iWellFile™ software installation directory Charts folder (e.g., C:\Inetpub\wwwroot\iWellFile\config\Landmark\Charts).

The Landmark folder stores the default settings shipped with the application. When customizing Charts, be sure to store the customized version of the ChartsConfig.xml in the Config\Custom\Charts folder.



The XML file defines the following attributes of charts.

• Size (e.g. height, width etc.)• Style (e.g. Line, Bar etc)• SQL that pulls the data.• Column name that should be plotted against X axis.• Column name(s) that should be plotted against Y axis. More than

one column can be chosen.• Support of 2Y axis. • DataSeries column name. Also provided is the facility to form the

groups for unique value of dataseries column. Only one Dataseries column can be defined.

• Choice of Colors to be used in plotting charts.• Chart Title Name.• Axis Label Name (can also defined as a Macro, to get the value at

run time)

Instructions for editing the CartsConfig.xml file are contained within the file.



5000.1.10.0 Chart Configuration 129


IIS Reset



130 iWellFile™ Software Initialization Configurations 5000.1.10.0

iWellFile™ Software Initialization Configurations

The Well Initialization configuration files (Event_Details.xml, Location_Details.xml, Well_Details.xml and WellBore_Details.xml) are used to configure the sections of the four well initialization windows.

These files are located on the web server in the installation directory Config folder (e.g., C:\Inetpub\wwwroot\iWellFile\Config\Landmark).

The Landmark folder stores the default settings shipped with the application. When customizing Well Initialization windows, be sure to store the customized version of the XML file in the Custom\Well Initialization folder.



Instructions for editing these files are contained within the file.



Important: The following properties should not be changed in the XML file:

• isDynamic="Y"• <BusinessName>• <AttributeName>• <Type>

IIS Reset



5000.1.10.0 Log File Locations Configuration 131

Log File Locations Configuration

The Log File location configuration file (LogfilesLocation.xml) is used to add new log files to the Administration page > iWellFile Control > iWellFile Logs. As of release 5000.1.1, log files predefined by the installation can no longer be changed.

The LogfilesLocation.xml is located on the web server, in the iWellFile™ software website “config” directory (e.g., C:\Inetpub\wwwroot\iWellFile\config\Landmark).

The Landmark folder stores the default settings shipped with the application. When customizing the XML, be sure to store the customized version of the file in the Config\Custom folder.




Each configuration file can be edited using any standard text editor (e.g., Microsoft® Wordpad).

Save a backup copy of the original LogfilesLocation.xml file prior to making any changes.

Instructions for adding log files are contained within the LogfilesLocation.xml file.

IIS Reset


132 Configure Default Filter on Startup 5000.1.10.0

Configure Default Filter on Startup

Clients using OpenWells® software may have thousands or tens of thousands of wells in their EDM™ database data store. OpenWells software and iWellFile™ software support a common filtering architecture to enable Well lists to be filtered according to user preference and also to reduce the number of wells displayed.

These filters are saved as QRY files which are cached on each user's machine for OpenWells software and on the web server for iWellFile software. To prevent first time users from experiencing a performance problem the very first time they run iWellFile software, the administrator can configure a default Well Filter which would be used on start up where the user did not have a cookie for iWellFile software previously saved on their PC.

The default Well Filter can be used to reduce the number of Wells displayed the first time they log into the system. Once logged in, they can set up filtering to their personal requirements. This preference would be saved to the cookie when they log off of the system. Once the cookie exists, the default filter would not be applied.

1. To assign a default filter, the .QRY file must be placed in the iWellFile\Filters folder on the web server, for example,

C:\Inetpub\wwwroot\iWellFile\filters\Great Guns Wells.qry.

2. Then, the administrator must edit the web.config file located in the iWellFile software install directory and adjust the Wellist.Filter key parameter with the name of the default filter (query) file, for example,

<add key="WellFilter.Default" value="Great Guns Wells.qry" /> 

3. After saving the change to the web.config file, IISRESET must be run on the web server for it to take effect. Once configured, new users will have the configured filter set by default the first time they run iWellFile software.


5000.1.10.0 Configure the iWellFile Style Sheet 133

Configure the iWellFile Style Sheet

The iWellFile™ software style sheet (iWellFile.css) is located on the web server in the website “css” directory (e.g., C:\Inetpub\wwwroot\iWellFile\css).

The CSS files are not stored in a Custom folder and therefore will be overwritten by a new installation of iWellFile software. Prior to upgrading to a newer version of iWellFile software, verify that these customized files have been backed up.

The Style Sheet file can be edited using any standard text editor (e.g., Wordpad).


The Web Page must be refreshed to implement changes to the Style Sheet.

For example, to change the font and color of the KPI Label and KPI Results appearing in the Performance Tab:

1. Make a backup copy of the iWellFile.css file.

2. Open iWellFile.css with Wordpad.

3. Navigate to ".KPILabel"

4. Make the following changes:

• change the font family to Comic Sans MS

• color the font blue

Changes in the iWellFile.css file are highlighted in red below for the .KPILabel.

.KPILabel

Backup CSS File!

Save a backup copy of the original iWellFile.css file prior to making any changes.


134 Configure the iWellFile Style Sheet 5000.1.10.0

{

font-family:Comic Sans MS;

font-size:10;

text-align:left;

font-weight:normal;

padding-left: 4px;

color: blue;

}

5. Navigate to ".KPIResult"

6. Make the following changes:

• color the font red

Changes in the iWellFile.css file are highlighted in red below for the .KPIResult.

.KPIResult

{

font-family:Arial;

font-size:11;

text-align:right;

font-weight:bold;

padding-left: 8px;

padding-right: 4px;

color: red;

}

7. Save iWellFile.css

8. Refresh iWellFile™ software using the F5 key.


5000.1.10.0 Configure the iWellFile Style Sheet 135

The following images show the Performance Tab fields before after editing the iWellFile.css file.

Before After


136 Themes 5000.1.10.0

Themes

Administrators have the ability to customize the look of iWellFile™ software based on a selected Theme. Themes are based on a cascading style sheet and images. iWellFile software currently ships with three Themes: Standard (blue), RedYellow and YellowGreen.

To change the iWellFile software theme:

1. On the server, navigate to the Themes folder (e.g., C:\Inetpub\wwwroot\iWellFile\Themes).

2. Open the folder containing the theme to be used and copy the “css” and “images” folders (e.g., C:\Inetpub\wwwroot\iWellFile\css and C:\Inetpub\wwwroot\iWellFile\images).

3. Paste these folders in the iWellFile software root directory thereby replacing the current “css” and “images” folders.

4. Next time the application is launched from the browser the new theme will be used.


5000.1.10.0 Restarting the iWellFile™ software Service 137

Restarting the iWellFile™ software Service

The iWellFile software web server must be restarted when changes to any configuration files have been made. Restarting the web server enables iWellFile software to recognize the changes. The following two methods can be used to restart the iWellFile software server:

Stopping and Restarting IIS on the Web Server:

1. Follow the menu path; Start > Run.

2. Enter iisreset.

3. Click OK.

Rebooting the Web Server

1. The other method to restart iWellFile software is to reboot the web server PC. If IISRESET fails to restart iWellFile software or fails to solve your problem, try rebooting the web server.


138 Text Labels and Internationalization 5000.1.10.0

Text Labels and Internationalization

iWellFile™ software has been designed to enable the administrator to customized text labels. iWellFile software also supports use in all regions of the world, by working with the current Windows Regional Options locale configured on the web server. This enables date, time, and number fields to be displayed appropriately. iWellFile software also provides comprehensive multi-language support in order to enable use of iWellFile software where EDM™ database has been customized for use in other languages.

Prior to upgrading to a newer version of iWellFile software, verify that the customized file has been backed up. A newer version of the application will overwrites any changes that have been made to this file.

Required Knowledge: Knowledge of HTML is required to configure this file.


Save a backup copy of the original Strings_en-US.xml file prior to making any changes.


Once the iWellFile software configuration file has been modified, the IIS Service must be restarted on the web server for the changes to take effect.

The default user interface text used in iWellFile software labels are found in the Inetpub\wwwroot\<web server name>\resources\Strings en-US.xml file. This XML file contains Unicode information and the names of fields displayed in the software. These field names can be edited to meet the needs of the company.

To change a field name:

1. Make a backup copy of the Strings en-US.xml file.

2. Open the Strings en-US.xml file.


5000.1.10.0 Text Labels and Internationalization 139

3. Navigate to the location of the string id that identifies the field to be changed (e.g., <string id="Calendar.Reports On This Day">Reports on this day:</string>)

4. Edit the fields label (e.g., change <string id="Calendar.Reports On This Day">Reports on this day:</string> to <string id="Calendar.Reports On This Day">Current Days Reports:</string>).

5. \Save the Strings en-US.xml file.

To customize the messages for a different language:

1. Copy the Strings en-US.xml file and rename it with the appropriate language code (e.g., Strings es-MX.xml).

2. Edit the contents of the new .XML file to define field labels in the new language.

3. Place the copied file in the same directory as the original Strings en-US.xml file (i.e., <web site folder>\resources).

4. The matching Regional Options locale for the system detects the customized .XML file by it's Language code name. For example, if the current Regional Option is set to Spanish (Mexico), iWellFile will use the Strings es-MX.xml file to define the field labels.

For a listing of language codes see “Appendix A” on page 157.

Note

Output Report hyper link mouse-over text can be internationalized by editing the following string: <string id="OutputReports/Landmark/DDR/OpenWellsDDR/">Daily Drilling Report</string>


140 Text Labels and Internationalization 5000.1.10.0

Uninstall Procedures iWellFile™ Software Installation Guide

5000.1.10.0 iWellFile™ software 5000.1.10.0 Uninstall 141

Uninstall Procedures

This section describes the uninstall procedure for Landmark’s iWellFile™ software application.

iWellFile™ software 5000.1.10.0 Uninstall

1. From the Windows Add/Remove Programs dialog in Control Panel, select Landmark iWellFile 5000.1.10 and click Remove.

2. The Confirm Uninstall dialog box appears, prompting you “Are you sure you want to remove Landmark iWellFile 5000.1.10 from your computer?”

3. Click Yes to continue with the Uninstall.

or

Click No to return to Add/Remove Programs window.

The uninstall will remove files. When the uninstall is complete the setup will return to Add/Remove Programs window.

It is strongly recommended that you reboot the system after setup has completed the selected option.

Important Note: If you already have iWellFile 5000.1.1.0 installed...

If you already have iWellFile 5000.1.0 software installed, then install 5000.1.1 software, and then choose to uninstall 5000.1.1 software, the iWellFile Service will not be removed. To fix this, you can get rid of the service prior to uninstalling 5000.1.1.0 by running the following BAT file:

\services\5000.1\Uninstall_iWellFileService_5000.1.bat (depending on the version of EDT software that is present on your system.)

iWellFile™ Software Installation Guide Uninstall Procedures

142 iWellFile™ software 5000.1.10.0 Uninstall 5000.1.10.0

Troubleshooting iWellFile™ Software Installation Guide

5000.1.10.0 143

Troubleshooting

Some problems may occur with the iWellFile™ software installation on machines that have had previous installations, crashes during installations, or are otherwise corrupted.

The following procedures have been performed on the machines where problems have been reported to allow the installation to proceed without incident.

This information is also contained in the iWellFile software Help.

iWellFile Software Security Tokens

iWellFile software uses a number of security tokens to control access certain areas of the application. If these tokens area not granted then the application may not work as expected. The following tokens are available and can be granted to users in the EDM™ Administration Utility so they can perform tasks with the following features.

• iWellFile.Administration - access to the Administration Page in the application. When this token is revoked the Administration link does not appear in the application. By default, this token in revoked.

• iWellFile.Lesson.admin - edit or delete Lessons regardless of which user created it. By default, this token in granted.

• iWellFile.Lesson.edit - edit the Discussion, Bibliography and Attachments areas of a Lesson regardless of the Lesson owner. By default, this token in granted.

• iWellFile.Template.Edit - create and edit Well Initialization templates. By default, this token in granted.

• iWellFile.Upload - upload well filters to the iWellFile software server. By default, this token is granted.

• iWellFile.Well.Edit - access the Well Initialization Page in the application. When this token is revoked, the Well Initialization

iWellFile™ Software Installation Guide Troubleshooting

144 5000.1.10.0

link does not appear in the application. By default, this token is revoked.

• EDM.Explorer.Site.add - add a Site to the EDM™ database. Sites can be added when initializing a Well. By default, this token is granted.

• EDM.Explorer.Well.add - add a Well to the EDM database. Wells are added when initializing a Well. By default, this token is granted.

iWellFile.log Errors

Problem: The following error appears in the iWellFile™ Software log file.

EXCEPTION: OdbcException EXCEPTION MESSAGE: ERROR [HYC00] [Oracle][ODBC]Optional feature not implemented. STACK TRACE: at System.Data.Odbc.OdbcConnection.HandleError(HandleRef hrHandle, SQL_HANDLE hType, RETCODE retcode) at System.Data.Odbc.OdbcCommand.ExecuteReaderObject(CommandBehavior behavior, String method) at System.Data.Odbc.OdbcCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Odbc.OdbcCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior) at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)

at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) at iWellFile.Utils.DataAccess.ExecuteQuery(String sql, IList paramArray, Boolean DisplayErrorMsg)

Solution: These errors occur when configuring iWellFile™ software for use on Oracle and the KPIs are not configured to use the provided Oracle-only versions.


5000.1.10.0 145

Cannot see the Administration options in iWellFile Software

Problem: When logging into iWellFile software the administration user cannot see the Administration option in the toolbar.

Solution: Verify that the user has permission to the iWellFile Administration token in the EDM™ Administration Utility.

ERROR [HYC00] [Oracle][ODBC]Optional feature not implemented

Problem: The error "ERROR [HYC00] [Oracle][ODBC]Optional feature not implemented" occurs in iWellFile™ Software log file because KPI scripts configured for MSDE are being run against an Oracle database.

Solution: Use the Oracle scripts configured for the KPI.

Multiple EDM Report windows stay after a report is generated

Problem: When viewing EDM Reports in iWellFile software, a blank EDM Report window appears and must be manually closed even after the report has been closed.

Solution: In Acrobat Reader, open the Preferences dialog and select the Internet category. Select the "Display PDF in browser" checkbox and click OK.

When cached reports are opened in iWellFile software the PDF launches directly in the browser window and the extra blank window does not appear.


146 5000.1.10.0

iWellFile™ Software Server cannot process your request error

Problem: When using iWellFile software the error "Sorry, the iWellFile server cannot process your request because an error occurred. Please press the Internet Explorer refresh button and login to iWellFile™ software again."

Solution: This error may occur when ASP.NET has timed out. Check the iWellFile software log for a ThreadAborted exception.

If a "ThreadAbortException" appears in the iWellFile software log file, then increase the ASP.NET timeout from 90 seconds to 180 seconds.

The ASP.NET timeout can be edited in file, by editing the following entry:

<httpRuntime executionTimeout="180" />

Internet Explorer "Connect to" Dialog appears when using iWellFile

Problem: When using iWellFile software the Internet Explorer "Connect to" dialog appears requesting a user name and password.

Solution: To resolve this problem, from the Internet Explorer window, follow the menu path Tools > Internet Options.

Select the Security tab and select the Trusted Sites zone.

Click the Sites button. The Trusted Sites dialog appears.

Enter the iWellFile software web site address in the Add this Web site to the zone: field (e.g, www.server.lgc.com/iWellFile).

Click the Add button.

Click OK to close the dialog.

Select the Advanced tab.

Verify that the Enable Integrated Windows Authentication setting is selected.

Click OK to close the Internet Options dialog.

Close all your Internet Explorer windows before trying iWellFile software again.


5000.1.10.0 147

iWellFile™ Software External Components (Analysis, Output Reports, COMPASS Plots, Schematics) do not work

Problem: When using Windows Authentication the Analysis page, Output Reports, COMPASS™ software Plots and Schematics do not work in iWellFile software.

Solution: This error occurs when iWellFile software is located on a drive other than the C:\ drive.

To resolve this issue, grant the iWellFile Users group read access to the drive iWellFile™ Software is installed on (e.g. D:\).

"Page Not Found" error occurs when accessing Log files

Problem: When attempting to view a log file on the Administration Page the "Page Not Found" message appears in Internet Explorer.

Solution: This error occurs because by default IIS is not configured to serve the .LOG, .CSV and .MSC (Event Viewer) files to client machine. To configure IIS to serve these file types:

From the Internet Information Services Manager, open the Properties dialog of the iWellFile software web application node.

In the HTTP Headers tab, click on the MIME Types button and add the three extensions to the MIME Types.


148 5000.1.10.0

No report was generated error

Problem: When generating a report the following error occurs:

Solution: This error occurs when the EDT™ software Drilling Patch is not installed, or the directory where the patch files were extracted was not the EDT software installation directory. Install the Drilling Patch in the EDT software installation directory.

Schematics, Wall Plots and Reports may not work

Problem: The Wellbore Schematic images do not appear after clicking on the generate button. In addition, the wall plots and the BHA Summary Report schematics may not work. The progress indicator in Internet Explorer flashes very quickly and schematic generation stops. If viewing Task Manager, the SchematicCmd.exe process will execute very quickly (less than one second) and then disappear. This may occur due to the failure of C:\WINNT\system32\OpenGL32.DLL to correctly initialize, causing schematic generation to abnormally terminate before schematic generation starts. This can be an intermittent problem, and only on certain hardware configurations.


5000.1.10.0 149

Solution: On the iWellFile™ Software server, add the ASPNET user to the local Administrators group and then run IISRESET.EXE to restart the service. If this configuration is unacceptable or does not work, Landmark recommends installing iWellFile software on Windows 2003 Server. This problem does not occur on Windows 2003 Server.

Login.aspx Text Displayed When Launching iWellFile Software

Problem: When launching iWellFile software in Internet Explorer the window displays the iWellFile software login.aspx source code text.

Solution: This is due to the ASPX extension is not defined in the Internet Information Services management console.

1. Open the iWellFile software site properties in the Internet Information Services management console.

2. Select the Configuration button on the Virtual Directory tab.

3. Select the .aspx extension and click the Add button.

4. Enter the Execution Path C:\windows\microsoft.net\framework\v1.1.4322\aspnet_isapi.dll and click OK.

5. Click OK to close the Properties dialog.

6. Restart the iis service using the iisreset command.


150 5000.1.10.0

Reports, Wellbore Schematics, PROFILE™Software Wall Plots Not Responding

Problem: The Reports, Wellbore Schematics, and PROFILE software Wall Plots are not being generated.

Solution: This may be due to the Report Generator Port 5015 being used by another application. Open the iWellFile™ Software Configuration file () located on the web server in the virtual directory where iWellFile™ Software has been installed (e.g., C:\Inetpub\wwwroot\iWellFile_5000.1.1). Change the ReportGenerator.Port key value. Once the iWellFile software configuration file has been modified, the IIS Service must be restarted on the web server for the changes to take effect.

PROFILE Software Wall Plots Will Not Generate to JPG Format

Problem: PROFILE software Wall Plots fail to generate when the selected Image Type output format is JPG.

Solution: Check to see if the Display Properties has Color quality set to 256 Colors (Control Panel > Display > Settings Tab). The iWellFile software JPG generator works in High Color (16 bit) and True Color (32-bit) mode only and cannot output to JPG with 256 Colors set. A very simple resolution to this issue is to change Display Properties on the Web Server to High Color or True Color, the higher the better as this will directly affect the quality of the images generated.

iWellFile™ Software Does Not Respond

Problem:

iWellFile software stops responding after clicking on the Login button on the EDM™ database Login page.

Solution: Change the HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\LICSRV_LICENSE_FILE registry entry to "2013@license_server_address" (e.g., 2013@myserver).


5000.1.10.0 151

iWellFile™ Software Windows and Help Cannot be Accessed

Problem: Components of iWellFile software do not function properly. When the user attempts to view the On-line help, Data Analyzer™ software Queries, Daily Reports, or Summary Reports they can not be accessed.

Solution: This problem occurs because Popup’s have been disabled in the Browsers settings. Popups can also be disabled using browser plug-ins such as the Google Toolbar. Enabling Popups will resolve this issue.

HTTP 403.9 Error

Problem: The following error message appears in Internet Explorer:

Error Message: HTTP 403.9 - Access Forbidden: Too many users are connected

IIS on Windows XP Professional is limited to 10 concurrent connections. Only Windows Server operating systems should be used for distributed Web Server implementations. iWellFile software 5000.1.10 supports use with Windows 2003 SP3, 32-bit Server and Windows 2008 SP2, 64-bit Server.

Solution: Refer to the following Microsoft Knowledge Base article: http://support.microsoft.com/default.aspx?scid=kb;en-us;262635

EDM™ Database Login Error When Using Oracle ODBC Database

Problem: One of the following error messages is displayed in the EDM database Login tab when using an Oracle ODBC data source:

• Unable to login to the selected data source. ERROR [IM003] Specified driver could not be loaded due to system error 5 (Oracle in OraHome92).

• Unable to login to the selected data source. Specified driver could not be loaded due to system error 5 (Oracle in OraHome92).

Solution: Modify the security settings on the Oracle client home folder (e.g., C:\oracle\ora92). Grant the local "Users" group Read & Execute, List Folder Contents, and Read permissions.


152 5000.1.10.0

Oracle ODBC Data Source

Problem: The following error is displayed when trying to log into an Oracle ODBC data source:

ERROR [IM003] Specified driver could not be loaded due to system error 5 (Oracle in OraHome92).

Solution: Modify the security settings on the Oracle client home folder (e.g., c:\oracle\ora92) to give the local "Users" group Read & Execute, List Folder Contents, and Read permissions.

Oracle Login Error

Problem: The following error is displayed when attempting to log into an Oracle ODBC data source:

ERROR [IM003] Specified driver could not be loaded due to system error 5 (Oracle in OraHome92).

Solution: Modify the security settings on the Oracle client home folder (e.g., c:\oracle\ora92) to give the local “Users” (i.e., <machine name>\Users) group Read & Execute, List Folder Contents, and Read permissions.

Restarting iWellFile

Restarting Internet Information Services on the iWellFile™ Software web server can clear up problems that are occurring in the iWellFile software. There are two ways in which to restart Internet Information Services:

Stopping and Restarting the Service

1. Follow the menu path; Start > Run.

2. Enter iisreset

3. Click OK.

Rebooting the Web Server

The other way to restart iWellFile™ Software is to reboot the machine acting as the web server. If iisreset fails to restart iWellFile software or fails to solve your problem, try rebooting the web server.


5000.1.10.0 153

Log File Generation

iWellFile software populates a log file automatically each time an error occurs in the application. New errors are appended to the end of the log file. The iWellFile software log file (iWellFile.log) is located in the virtual directory configured during installation.

Changing Regional Settings

For information on changing the Regional Settings for iWellFile software see the iWellFile software Regional Settings topic in the iWellFile software on-line help.

Popups Blocked or Runtime Error Displayed

Problem: iWellFile software displays popups for certain functions, for example, PROFILE™ software Wall Plots in Single Well page, Modify Parameters in Analysis page. Internet Explorer security may be configured to block popups from being displayed. Depending on which version of Internet Explorer and/or Windows is being used, different behaviors may occur when the popup is blocked. For example, a Runtime Error dialog may appear.

or a Popup Notice may display above the website.

Solution: Configure the browser to accept popups for the iWellFile™ Software site. For example, in Microsoft Internet Explorer 6.0, select Tools > Popup Blocker > Turn Off Pop-up Blocker to always allow popups for the current site.


154 5000.1.10.0

Windows 2003 Server—Windows\System32 Path/Environment Variable Corruption

Problem: There have been instances where the iWellFile software installation has affected the Windows\System32 and/or %SystemRoot% Environment variables. This has manifested itself as a failure in Windows Utility programs and/or other applications dependent on the Windows\System32 directory or the Windows %SystemRoot% environment variable. An following shows an example of a Windows Utility failure caused by this issue.

Solution: Specify a fully reconciled Windows\System32 directory in the Windows System Path. One way to adjust the Windows Path is through the Environment Variables dialog.

1. Right click on My Computer and select Properties.


3. Click the Environment Variables button.

4. From the Environment Variables dialog, under System Variables, scroll down to the ‘Path’ variable.

5. Select the Path variable and click Edit.

6. Click at the end of the value displayed in the Variable Value field. At the end of this value, enter your fully reconciled Windows\System32 path, preceded by a semi-colon (;). For example, on a standard Windows 2003 installation, defaulting to a c drive, this addition would include: “;c:\windows\system32”.


5000.1.10.0 155

The complete, updated path would look like:

C:\Program Files\Landmark\EDT_2003.16\Common Files\JDK\jre\bin;C:\Program Files\Landmark\EDT_2003.16\Common Files\JDK\jre\bin\client;C:\oracle\ora92\jre\1.4.2\bin\client;C:\oracle\ora92\jre\1.4.2\bin;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Landmark\LAM\bin;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Landmark\EDT_2003.16\Common Files;C:\Program Files\Landmark\EDT_2003.16\Common Files\WellSchematic;C:\Program Files\Landmark\EDT_2003.16\Common Files\DEX;C:\Program Files\Landmark\EDT_2003.16\Common Files\Data Services;C:\inetpub\wwwroot\iWellFile_2003.16\BIN;c:\windows\system32

Using FileMon and RegMon to Troubleshoot

If iWellFile™ Software features do not function and there is suspicion that it may be a securities or permissions issue on the server, use the FileMon or RegMon utilities to search for any additional access made by iWellFile™ Software that is not covered by the Install Guide Instructions.


156 5000.1.10.0

Appendix A iWellFile™ Software Installation Guide

5000.1.10.0Configuring iWellFile™ Software to Support Both Windows Authenticated and EDM User Cre-

Appendix A

Configuring iWellFile™ Software to Support Both Windows Authenticated and EDM User Credentials

iWellFile™ software can be configured to provide an option (at the time of login) to users that allow them to login either using windows credential or EDM™ login-password. In this configuration, on accessing the iWellFile URL user is prompted with a login/password dialog for entering Windows credentials. User has the choice either to enter Windows credentials and login into iWellFile software using them, or press the Cancel button that in turn will take the user to the iWellFile login page to enter the EDM login password.

Router

IWellFile (WA)

IWellFile (NWA)

iWellFile™ Software Installation Guide Appendix A

158 Configuring iWellFile™ Software to Support Both Windows Authenticated and EDM User Cre-

To configure, perform the following steps on iWellFile server.

1. Set up two different iWellFile instances on the same machine. Configure one to use the Windows authentication method of authentication, and another to use non-Windows authentication.

2. Create a third blank web application (virtual directory) and configure IIS to allow only Integrated Windows Authentication for it.



3. From the iWellFile folder (set up in step 1) unzip the contents of router\Routersite.zip into the blank web application (Router) created in step 2.



4. In inetmgr, right-click on the virtual directory of the router site— Select Properties, then click Documents. Then set login.htm as the default Document and remove other entries.



5. Again in Properties, click the Custom Errors tab, and select HTTP error 400 > Edit Properties.

Set the message type as File and the File Name as <Router site root directory path>\login2.htm. Click OK to accept.

6. Repeat step 5 for HTTP errors 401.1, 401.2 and 401.3.



7. Edit the login.htm page from the Router site. Set "urlWindowAuthentication" equal to "http:\\WindowAuthenticationSiteName\\login.htm" where WindowAuthenticationSiteName is the name of the iWellfile virtual directory set up in Windows authentication mode.



8. Edit the login2.htm page from the Router site. Set "urlWindowAuthentication" equal to "http:\\NonWindowAuthenticationSiteName\\login.htm" where NonWindowAuthenticationSiteName is the name of the iWellfile virtual directory set up in non-Windows authentication mode.

Once the above steps are done, Router site's URL can be used by all users. Router site will prompt for the Windows credentials. If the correct credentials are given, the user will be redirected to the Windows-authenticated instance of iWellfile; if not, then they will be directed to the non-Windows-authenticated instance.

Appendix B iWellFile™ Software Installation Guide

5000.1.10.0 Language Codes 165

Appendix B

Language Codes

The following table displays the language codes used when naming Strings xx.xml file for Internationalizing iWellfile. Click a letter below to go to the Language beginning with that letter.

Language letter codes must appear in the file name in lowercase and regional letter codes must appear in the file name in UPPERCASE.

For example, the file name for the French language would be Res_fr.properties and the file name for the French Canadian language would be Res_fr-CA.properties.

Language Code

A

Afrikaans af

Afrikaans - South Africa af-ZA

Albanian sq

Albanian - Albania sq-AL

Arabic ar

Arabic - Algeria ar-DZ

Arabic - Bahrain ar-BH

Arabic - Egypt ar-EG

Arabic - Iraq ar-IQ

Arabic - Jordan ar-JO

Arabic - Kuwait ar-KW

Arabic - Lebanon ar-LB

Arabic - Libya ar-LY

Arabic - Morocco ar-MA

Arabic - Oman ar-OM

Arabic - Qatar ar-QA

Arabic - Saudi Arabia ar-SA

iWellFile™ Software Installation Guide Appendix B

166 Language Codes 5000.1.10.0

Arabic - Syria ar-SY

Arabic - Tunisia ar-TN

Arabic - United Arab Emirates ar-AE

Arabic - Yemen ar-YE

Armenian hy

Armenian - Armenia hy-AM

Azeri az

Azeri (Cyrillic) - Azerbaijan az-AZ-Cyrl

Azeri (Latin) - Azerbaijan az-AZ-Latn

B

Basque eu

Basque - Basque eu-ES

Belarusian be

Belarusian - Belarus be-BY

Bulgarian bg

Bulgarian - Bulgaria bg-BG

C

Catalan ca

Catalan - Catalan ca-ES

Chinese - Hong Kong SAR zh-HK

Chinese - Macau SAR zh-MO

Chinese - China zh-CN

Chinese (Simplified) zh-CHS

Chinese - Singapore zh-SG

Chinese - Taiwan zh-TW

Chinese (Traditional) zh-CHT

Croatian hr

Croatian - Croatia hr-HR

Czech cs

Czech - Czech Republic cs-CZ

D

Danish da

Danish - Denmark da-DK

Language Code



Dhivehi div

Dhivehi - Maldives div-MV

Dutch nl

Dutch - Belgium nl-BE

Dutch - The Netherlands nl-NL

E

English en

English - Australia en-AU

English - Belize en-BZ

English - Canada en-CA

English - Caribbean en-CB

English - Ireland en-IE

English - Jamaica en-JM

English - New Zealand en-NZ

English - Philippines en-PH

English - South Africa en-ZA

English - Trinidad and Tobago en-TT

English - United Kingdom en-GB

English - United States en-US

English - Zimbabwe en-ZW

Estonian et

Estonian - Estonia et-EE

F

Faroese fo

Faroese - Faroe Islands fo-FO

Farsi fa

Farsi - Iran fa-IR

Finnish fi

Finnish - Finland fi-FI

French fr

French - Belgium fr-BE

French - Canada fr-CA

French - France fr-FR

Language Code



French - Luxembourg fr-LU

French - Monaco fr-MC

French - Switzerland fr-CH

G

Galician gl

Galician - Galician gl-ES

Georgian ka

Georgian - Georgia ka-GE

German de

German - Austria de-AT

German - Germany de-DE

German - Liechtenstein de-LI

German - Luxembourg de-LU

German - Switzerland de-CH

Greek el

Greek - Greece el-GR

Gujarati gu

Gujarati - India gu-IN

H

Hebrew he

Hebrew - Israel he-IL

Hindi hi

Hindi - India hi-IN

Hungarian hu

Hungarian - Hungary hu-HU

I

Icelandic is

Icelandic - Iceland is-IS

Indonesian id

Indonesian - Indonesia id-ID

Italian it

Italian - Italy it-IT

Italian - Switzerland it-CH

Language Code



J

Japanese ja

Japanese - Japan ja-JP

K

Kannada kn

Kannada - India kn-IN

Kazakh kk

Kazakh - Kazakhstan kk-KZ

Konkani kok

Konkani - India kok-IN

Korean ko

Korean - Korea ko-KR

Kyrgyz ky

Kyrgyz - Kazakhstan ky-KZ

L

Latvian lv

Latvian - Latvia lv-LV

Lithuanian lt

Lithuanian - Lithuania lt-LT

M

Macedonian mk

Macedonian - FYROM mk-MK

Malay ms

Malay - Brunei ms-BN

Malay - Malaysia ms-MY

Marathi mr

Marathi - India mr-IN

Mongolian mn

Mongolian - Mongolia mn-MN

N

Norwegian no

Norwegian (BokmÂl) - Norway nb-NO

Norwegian (Nynorsk) - Norway nn-NO

Language Code



P

Polish pl

Polish - Poland pl-PL

Portuguese pt

Portuguese - Brazil pt-BR

Portuguese - Portugal pt-PT

Punjabi pa

Punjabi - India pa-IN

R

Romanian ro

Romanian - Romania ro-RO

Russian ru

Russian - Russia ru-RU

S

Sanskrit sa

Sanskrit - India sa-IN

Serbian (Cyrillic) - Serbia sr-SP-Cyrl

Serbian (Latin) - Serbia sr-SP-Latn

Slovak sk

Slovak - Slovakia sk-SK

Slovenian sl

Slovenian - Slovenia sl-SI

Spanish es

Spanish - Argentina es-AR

Spanish - Bolivia es-BO

Spanish - Chile es-CL

Spanish - Colombia es-CO

Spanish - Costa Rica es-CR

Spanish - Dominican Republic es-DO

Spanish - Ecuador es-EC

Spanish - El Salvador es-SV

Spanish - Guatemala es-GT

Spanish - Honduras es-HN

Language Code



Spanish - Mexico es-MX

Spanish - Nicaragua es-NI

Spanish - Panama es-PA

Spanish - Paraguay es-PY

Spanish - Peru es-PE

Spanish - Puerto Rico es-PR

Spanish - Spain es-ES

Spanish - Uruguay es-UY

Spanish - Venezuela es-VE

Swahili sw

Swahili - Kenya sw-KE

Swedish sv

Swedish - Finland sv-FI

Swedish - Sweden sv-SE

Syriac syr

Syriac - Syria syr-SY

T

Tamil ta

Tamil - India ta-IN

Tatar tt

Tatar - Russia tt-RU

Telugu te

Telugu - India te-IN

Thai th

Thai - Thailand th-TH

Turkish tr

Turkish - Turkey tr-TR

U

Ukrainian uk

Ukrainian - Ukraine uk-UA

Urdu ur

Urdu - Pakistan ur-PK

Uzbek uz

Language Code



Uzbek (Cyrillic) - Uzbekistan uz-UZ-Cyrl

Uzbek (Latin) - Uzbekistan uz-UZ-Latn

V

Vietnamese vi

Vietnamese - Vietnam vi-VN

Language Code

Appendix C iWellFile™ Software Installation Guide

5000.1.10.0 Contacting Landmark Customer Support 173

Appendix C

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 regional support offices around the world.

• Support Via Web Portal

• Technical Assistance Centers

• Regional Offices

• Helpful Links

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.com/InfoCenter/index?page=home

To request support in the Landmark Customer Support Portal:

1. In the PIN and Password text boxes in the Please Sign In area, enter your registered personal identification number and password.

2. Click the Sign In button.

3. In the Case & Defect Information area, click the Create A New Case link.

4. In the Create Case area, fill in the necessary information. Provide details about your technical concern, including any error messages, the workflow steps where the problem occurred, and attachments of screen shots that display the problem. To help understand the concern, you can also attach other files too, such as example data files.

5. Click the Submit button. A support analyst in the nearest Technical Assistance Center will respond to your request.


iWellFile™ Software Installation Guide Appendix C

174 Contacting Landmark Customer Support 5000.1.10.0

Technical Assistance Centers

Regional Offices

For contact information for regional offices, see the Contact Support page located at:

http://css.lgc.com/InfoCenter/index?page=contact&section=contact

If problems cannot be resolved at the regional level, an escalation team is called to resolve your incidents quickly.

Helpful Links

Asia, Pacific8:00 am - 5:00 pm Local Time Monday-Friday, excluding holidays

61-8-9481-4488 (Perth, Australia) Toll Free 1-800-448-488Fax: 61-8-9481-1580Email: [email protected]

Europe, Africa, Middle East9:00 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

44-1372-868686 (Leatherhead, UK) Fax: 44-1224-723260 (Aberdeen, UK)Fax: 44-1372-868601 (Leatherhead, UK)Email: [email protected]

Latin America (Spanish, Portuguese, English)7:00 am - 5:00 pm Local Time

713-839-3405 (Houston, TX, USA)Fax: 713-839-3646Email: [email protected]

North America7:30 am - 5:30 pm Central Standard TimeMonday - Friday, excluding holidays

713-839-2200 (Houston, TX, USA)Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 713-839-2168Email: [email protected]

Name Website Address

Landmark Software & Services home page http://www.halliburton.com/landmark

Landmark Support Portal http://css.lgc.com/InfoCenter/index?page=home

Oracle home page http://www.oracle.com

FLEXNet Publisher (Flexera Software, Inc.) http://www.flexerasoftware.com

Microsoft SQL Server home page http://www.microsoft.com/sqlserver

Adobe Acrobat Reader http://www.adobe.com

Microsoft SQL Server Express home page http://www.microsoft.com/express/sql

mailto:[email protected]




http://css.lgc.com/InfoCenter/index?page=contact&section=contact

http://www.halliburton.com/landmark


http://www.oracle.com

http://www.flexerasoftware.com

http://www.microsoft.com/sqlserver

http://www.adobe.com

http://www.microsoft.com/express/sql

Installation Checklists iWellFile™ Software Installation Guide

5000.1.10.0 175

Installation Checklists

The checklists provided in this chapter, can be printed and used as a guide in tracking or troubleshooting the installation process. You MUST follow the steps outlined in the <Helv12BlueBold>Installation chapter of this manual, in order to install iWellFile™ software correctly.

The following checklists are available:

“Install iWellFile 5000.1.1 Checklist” on page 176

“iWellFile 5000.1.10 Software 32-Bit Installation Checklist” on page 178

“iWellFile Software 64-Bit Installation Checklist” on page 180

“Configure iWellFile Checklist” on page 184

“Configure Windows Authentication” on page 185

iWellFile™ Software Installation Guide Installation Checklists

176 Install iWellFile 5000.1.1 Checklist 5000.1.10.0

Install iWellFile 5000.1.1 Checklist

Perform this install if iWellFile 5000.1.0 or later has not been installed previously on the server.

Otherwise skip to one of the following:

• “iWellFile 5000.1.10 Software 32-Bit Installation Checklist” on page 178

• “iWellFile Software 64-Bit Installation Checklist” on page 180

Prerequisites Checklist

(See “Before You Install” on page 5.)

Engineer’s Desktop 5000.1.x installed and includes:

Data Analyzer

PROFILE

COMPASS

EDM Report Manager

EDM ODBC Data Source Connection Configured

Internet Information Services (IIS) and other Windows Components installed

Application Server Console


ASP.NET

Internet Information Services (IIS)

Internet Information Services Manager Components

Common Files

Internet Information Services Manager

World Wide Web Service

World Wide Web Service Components

Active Server Pages

Server Site Includes


Adobe Acrobat Reader 7.09 or later installed

Oracle Client installed (on EDM Oracle Systems only)


5000.1.10.0 Install iWellFile 5000.1.1 Checklist 177


(See “5000.1.1 Installation Procedure” on page 12.)

If installing on a 32-bit system, “iWellFile 5000.1.10 Software 32-Bit Installation Checklist” on page 178.

If installing on a 64-bit system, “iWellFile Software 64-Bit Installation Checklist” on page 180.

Run iWellFile 5000.1.1 Installation Setup.EXE

Enter Customer Information

Select Setup Type

Enter Installation Folder (or keep default)

Enter Virtual Directory Name

Select Install

REBOOT Computer

GO TO Configure iWellFile Checklist below.


178 iWellFile 5000.1.10 Software 32-Bit Installation Checklist 5000.1.10.0

iWellFile 5000.1.10 Software 32-Bit Installation Checklist

iWellFile 5000.1.0 or later must be installed and configured prior to installing the 5000.1.10 version.



Engineer’s Desktop 5000.1.10 installed and includes:

Data Analyzer

PROFILE

COMPASS

EDM Report Manager

iWellFile 5000.1.0 or later has been installed and configured. If not, then see “Install iWellFile 5000.1.1 Checklist” on page 176.





ASP.NET



Common Files




Active Server Pages






5000.1.10.0 iWellFile 5000.1.10 Software 32-Bit Installation Checklist 179


(See “5000.1.10 Update Installation Procedure” on page 10.)

Next, go to “Configure iWellFile Checklist” on page 184.

OR

If this is an update and iWellFile 5000.1.1 was installed using Windows Authentication see “Configure Windows Authentication” on page <blue bold text>185.

Ensure the iWellFile 5000.1.1 installation and configuration has been successfully completed. (See the iWellFile 5000.1.1 checklist that follows.)


Click the OK button for the message that appears.

Click the Setup button to extract the files and begin the installation.

Follow the prompts.

If this is an update and iWellFile 5000.1.1 was installed using Windows Authentication see “Configure Windows Authentication” on page <blue bold text>185

Otherwise, Launch iWellFile.


180 iWellFile Software 64-Bit Installation Checklist 5000.1.10.0

iWellFile Software 64-Bit Installation Checklist

iWellFile 5000.1.0 or later must be installed and configured prior to installing the 5000.1.10 version.

Install Engineer’s Desktop 64-Bit Checklist

(See “Install iWellFile on a Windows 2008 Server (64-bit)” on page 19.)

Login as Administrator

Disable hardware-based DEP (Data Execution Prevention) in BIOS, if machine has hardware-based DEP.

Set Software-based DEP to "Turn on DEP for essential Windows programs and services only" as stated in the Release Notes.

Disable User Account Control.

If the machine uses SMS (Software Management Service), then unplug the network cable as SMS conflicts with EDT installations.

Follow the instructions found in the Engineer’s Desktop™ Software Version 5000.1.10 Release Notes (EDT_Drilling_SummaryReleaseNotes.pdf) sections:

• Before You Install

• Installation: 64-Bit Operating Systems


5000.1.10.0 iWellFile Software 64-Bit Installation Checklist 181



Engineer’s Desktop 5000.1.10 installed and includes:

Data Analyzer

PROFILE

COMPASS

EDM Report Manager

iWellFile 5000.1.0 or later has been installed and configured. If not, then see “Install iWellFile 5000.1.1 Checklist” on page 176.





ASP.NET



Common Files




Active Server Pages






182 iWellFile Software 64-Bit Installation Checklist 5000.1.10.0

Install IIS 7.0 With ASP.NET Support Checklist

(See “Install IIS 7.0 With ASP.NET Support” on page 19.)

Create Application Pool Checklist

(See “Create an Application Pool” on page 22.)


(See “5000.1.10 Update Installation Procedure” on page 24.)

Add “Web Server” Role

Select Default Role Services

Click Install

Add a new Application Pool for iWellFile

Choose .NET Framework version 2.0.50727

Choose “Classic” Managed Pipeline mode

Set “Enable 32-Bit Applications” flag to True

Ensure the iWellFile 5000.1.1 installation and configuration has been successfully completed. (See the iWellFile 5000.1.1 checklist that follows.)


Click the OK button for the message that appears.

Click the Setup button to extract the files and begin the installation.

Follow the prompts.


5000.1.10.0 iWellFile Software 64-Bit Installation Checklist 183

Configure iWellFile Application Pool Checklist

(See “Configure iWellFile Application Pool” on page 25.)

Next, go to “Configure iWellFile Checklist” on page 184.

OR

If this is an update and iWellFile 5000.1.1 was installed using Windows Authentication see “Configure Windows Authentication” on page <blue bold text>185.

Open IIS Manager

Select the iWellFile application under Default Websites

Open Advanced Settings

Set Application Pool as the one created in the previous section

Grant Full access to the local “Users” group on the iWellFile Installation folder.

RESET IIS


184 Configure iWellFile Checklist 5000.1.10.0

Configure iWellFile Checklist

(See “Configure iWellFile” on page 27.)

Adjust KPI files for SQL Database only

Register ASP.NET ON 32-Bit SERVERS ONLY

Set ASP.NET v2.0.50727 Web Services Extension to ALLOW ON 32-Bit SERVERS ONLY

Create iWellFile Application Pool (iWellFileAppPool) ON 32-Bit SERVERS ONLY

select “Use existing application pool as template (DefaultAppPool)”

Configure iWellFile to use new iWellFileAppPool ON 32-Bit SERVERS ONLY

Register .CVS, .LOG and .MSC MIME Types

RESET IIS Service

Run MATERIALIZED VIEWS Database Script on ALL EDM Databases accessed by iWellFile

REBOOT Server

Set Internet Explorer Security Options on ALL MACHINES accessing iWellFile

Enter the Server name or IP address to Trusted Sites

DO NOT select “Require server verification (https:) for all sites in this zone.

Enter the iWellFile web site http address to Trusted Sites

Select “Enable Integrated Windows Authentication (requires restart)” option in Advanced tab

Setup the Default DSN to Generate KPIs Asynchronously using the Analytical Service

RESET IIS Service


5000.1.10.0 Configure Windows Authentication 185

Configure Windows Authentication

Create iWellFile User Group

(See “Create an iWellFile™ Software Users Group” on page 52.)

Grant Privileges to User Rights Assignment

(See “Grant Privileges to User Rights Assignment” on page 54.)

Grant iWellFile Group Permissions to Various Folders

(See “Grant Permissions to Various Folders” on page 56.)

ON DOMAIN CONTROLLER

Create Domain Group called iWellFile Users

Add all domain users accessing iWellFile to new Domain Group: iWellFile Users

ON iWellFile SERVER

Create local Group called iWellFile Users

Add the Domain Group to the Local Group

Add local Network Service, Authenticated Users user to the local group

ON iWellFile SERVER

Grant the Debug program privilege to the local group iWellFile Group

ON iWellFile SERVER

iWellFile software Installation folder (e.g., C:\Inetpub\www-root\iWellFile_5000.1.1

Read / Write / Execute

Windows XP Documents and Settings folder Full Control

Windows Vista and 7 Users folder Full Control

• Create a folder Landmark\Cache on drive where iWellFile software is installed.

• Create a folder Landmark\Cache on drive where EDT soft-ware is installed.

Read / Write / Modify

EDT installation folder (e.g., C:\Landmark\EDT_5000.1) Read / Write / Execute


186 Configure Windows Authentication 5000.1.10.0

Configure IIS

(See “Configure IIS” on page 57.)

Windows 2003 Server

Windows 2008 Server

Configure Web.Config File

(See “Configure Web.Config File” on page 59.)

In IIS Manager, navigate to Web Sites > iWellFile site name > Properties dialog.

In the Directory Security tab > Authentication & Access Control > Edit button:

For Oracle, select Integrated Windows Authentication

For SQL Server, select Basic authentication

Deselect all other options including:

• Enable anonymous access,

• Digest authentication for Windows domain servers

• .NET Passport authentication.

In IIS Manager, navigate to the iWellFile virtual folder > Authentication.

Set ASP.NET Impersonation to ENABLE.

If using SQL Server, ENABLE Basic Authentication

If using Oracle, ENABLE Windows Authentication

Deselect ALL other options.

In Web.Config File

Comment out the authentication mode =None entry

Comment in the authentication mode =Windows and identity impersonate=true entries.


5000.1.10.0 Configure Windows Authentication 187

Redirect PROFILE™ Software Log File

(See “Redirect PROFILE™ Software Log File” on page 60.)

Configure EDM Database

(See “Configure EDM™ Database” on page 61.)

Configure SQL Server and Oracle to Use Windows Authentication

(See “Configure SQL Server and Oracle to Use Windows Authentication” on

page 62.)

SQL Server

Oracle Server

Edit or Add registry setting:

Registry Path: HKEY_LOCAL_MACHINE\Software\Landmark Graphics Corporation\EDT\5000.1\Profile

String Value: Log File

Log File Data String: C:\Inetput\wwwroot\iWellFile_5000.1.1\Output\NGProfile.log

Add Window Environmental Variable LGC_EDM_REMOTE_OS_AUTHENT

Set to TRUE to show Windows Authentication checkbox

Set to FALSE to hide Windows Authentication checkbox

In ODBC Data Source Administrator

With Integrated Windows authentication option

Change the default database to: and select the database file


Remove the user name from the User ID field


188 Configure Windows Authentication 5000.1.10.0

Configure a DSN when using a SQL Server Database

(See “Configure a DSN when using a SQL Server Database” on page 64.)

Create a SQL Server Authentication DSN

Configure the SQL Server Authentication DSN in iWellFile™ software


Add new System DSN

Select SQL Native Client driver

Enter DSN and Select SQL Server instance where db resides

Select the With SQL Server authentication using a login ID and password entered by the user option

Select the Connect to SQL Server to obtain default settings for the additional configuration options checkbox.

Enter the Login ID and Password for the SQL Server.

Select the Change the default database to: checkbox and select the EDM database

Open web.config file

Add the following, using the SQL Server Authentication DSN:

<add key="PrivilegeDsn" value="PUT-DSN-NAME-HERE"/>

RESET IIS

Set System DSN Credentials for both the Windows Authenticated DSN and the SQL Server Authenticated DSN.