OpenWorks Connect 5000.7.1 Installation Guide & Release...

OpenWorks® Connect 5000.7.1Installation Guide & Release

January 2012

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, vSpace, 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.

GeoFrame is a registered trademark of Schlumberger.

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:

$PE_HOME/www/help/pdf/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.

Contents OpenWorks® Connect Installation Guide & Release Notes

5000.7.1 v

Contents

Introduction to OpenWorks® Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Platform Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Digital Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Installing OpenWorks® Connect 5000.7.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Installation Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Pre-Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Compatible Software Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installation Procedure (Update from Original Document) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Start the Installation Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Installation Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Post Installation / Post Upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Installing KRS Data from OpenExplorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configurations for a KRS Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Security for a KRS Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Foreign Key Constraints Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

OpenWorks® Startup Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Introduction to Startup Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

OpenWorks® Startup Service for OWSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26OpenWorks® Startup Service for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Types of OpenWorks® Startup Service for Projects . . . . . . . . . . . . . . . . . . . . . . . . . 27

Managing the Startup Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Service Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Service Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Starting the Startup Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Starting the OpenWorks® Startup Service for OWSYS . . . . . . . . . . . . . . . . . . . . . . . . . 32Starting the OpenWorks® Startup Service for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Entries in the Startup_services.props File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Starting the OpenWorks® Startup Service for OWSYS . . . . . . . . . . . . . . . . . . . . . . . . . 35

OpenWorks® Connect Installation Guide & Release Notes Contents

vi 5000.7.1

Starting the OpenWorks® Startup Service for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . 35Starting the Data Comparison Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Properties of Startup Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Properties of the OpenWorks® Startup Service for Projects . . . . . . . . . . . . . . . . . . . 36

OpenWorks® Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Adding OpenWorks® Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

to the PowerExplorer® Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40to tnsnames.ora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Adding the Databases to Global Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . 43Removing the OpenWorks® Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Adding a Temporary Table for Drill down Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Execute Table Creation Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Global Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Projects task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Project User task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Security Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49The OpenWorks® Connect Access Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Adding Tvd, Tvdss, Interpolated X and Interpolated Y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Data Model Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

USE_RMI_GDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

OpenWorks® Connect 5000.7.1 Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . 57Contacting Landmark Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Introduction to OpenWorks® Connect OpenWorks® Connect Installation Guide

5000.7.1 Welcome 1

Introduction to OpenWorks® Connect

Welcome

The OpenWorks® Connect module is used to access OpenWorks® Oracle databases for browsing in tabular, chart, and map form.

This chapter introduces you to OpenWorks® Connect before you begin installing it. The following items are discussed in this chapter;

• System Requirements (page 2)

• Platform Requirements (page 2)

• Documentation (page 3).

The detailed installation information starts in Installing OpenWorks® Connect 5000.7.1 (page 5).

A later version of the OpenWorks® Connect 5000.7.1 Installation Guide & Release Notes may be available on the Landmark Software Manager. If the document on Landmark Software Manager is a later version it will be noted on the title page of the document. You can find changes from the original document by searching the phrase “Update from Original Document”.

OpenWorks® Connect Installation Guide Introduction to OpenWorks® Connect

2 System Requirements 5000.7.1

System Requirements

Prerequisite Software

OpenWorks® Connect has the following prerequisites:

• PowerHub™ software 5000.7.0.

Platform Requirements

The platform requirements for OpenWorks® Connect 5000.7.1 are as follows:

Platform Requirements for the PowerExplorer® Software

Resource Platform Requirements - PC(Intel)

CPU Intel Pentium 1 GHz, or higher

RAM 1 GB

Disk space 2 GB for the PowerHub™ software, PowerExplorer® software, connect modules and web services

Operating Systems Linux Red Hat ES 5.5 or greater (64-bit) (tested on 5.5.& 5.6) built on RH 4.4 with SELinuxa enabled.

a. Enabling SELinux: Once you have installed Oracle Enterprise Edition 10.2.0.5 or 11.2 Server, enable the SELinux module (for enhanced security) by launching the “system-config-securitylevel” tool and selecting Enforcing under the SELinux tab. You must restart the system for the change to take effect.

Introduction to OpenWorks® Connect OpenWorks® Connect Installation Guide

5000.7.1 Documentation 3

Documentation

Documentation for OpenWorks® Connect 5000.7.1 consists of online help (in HTML format) and online manuals (in PDF format).

Digital Documents

The OpenWorks® Connect Installation Guide & Release notes (owc_5000_7_1_rls_installrlsnotes.pdf) is provided in digital format. This document can also be found on the directory where OpenWorks® Connect is installed under $PE_HOME/www/help/pdf.

Online Help

Instructions for using OpenWorks® Connect are provided in the online help for the PowerExplorer® software, which is installed along with OpenWorks® Connect. Please refer to: Connect Modules >> OpenWorks Connect, in the online help for the PowerExplorer® software.

OpenWorks® Connect Installation Guide Introduction to OpenWorks® Connect

4 Documentation 5000.7.1

This page is intentionally blank.

OpenWorks® Connect Installation Guide OpenWorks® Connect Installation Guide

5000.7.1 Overview 5

Installing OpenWorks® Connect 5000.7.1

Overview

The steps in this chapter guide you through a typical new installation/upgrade of OpenWorks® Connect. The following items are discussed in this chapter:

• Installation Workflow on page 6

• Pre-Installation Instructions on page 7

• Installation Procedure (Update from Original Document) on page 8

• Post Installation / Post Upgrade Procedures on page 19.

OpenWorks® Connect Installation Guide Installing OpenWorks® Connect

6 Installation Workflow 5000.7.1

Installation Workflow

The typical installation workflow for installing OpenWorks® Connect is as follows:

Check the platform requirements(page 2)

Install prerequisite software(page 2)

Install OpenWorks® Connect(page 8)

Workflow for installing OpenWorks® Connect

Perform post-installation steps(page 19)

5000.7.1 Pre-Installation Instructions 7

Pre-Installation Instructions

Before installing or upgrading OpenWorks® Connect, perform the following pre-installation steps:

• In case of upgrading OpenWorks® Connect, it is highly recommended that you take a backup of the dictionary. If the upgrade fails, you can use the backup to revert to the previous version of OpenWorks® Connect.

• OpenWorks® Connect must be installed using the same PowerHub™ user created prior to the installation of the PowerHub™ software. The default user name of the PowerHub™ software is ‘pe’.

• Stop the PowerHub™ server prior to running the OpenWorks® Connect Installation program.

• The pe PowerHub™ user’s environment must contain the location of $PE_HOME and contain $PE_HOME/bin as part of the path. To set the PE_HOME and extend the path variable, use the following commands:

export PE_HOME=/apps/Landmark/PowerExplorer5000.7.1export PATH=$PE_HOME/bin:$PATH

Compatible Software Releases

The following software products are compatible with OpenWorks® Connect 5000.7.1:

— PowerHub™ software 5000.7.0.

— PowerExplorer® software 5000.7.1.

— MDS Connect 5000.7.0 and above.

— PowerHub™ Connect for OpenSpirit 5000.7.0

— GeoFrame Connect 5000.7.0

— EDM Connect 5000.7.1

— Advanced Data Transfer 5000.7.0

8 Installation Procedure (Update from Original Document) 5000.7.1

Installation Procedure (Update from Original Document)

The procedures in this section will guide you through the installation of OpenWorks® Connect.

Start the Installation Wizard

The OpenWorks® Connect installer is a self-extracting, Java-based archive. To install OpenWorks® Connect follow the steps mentioned below:

1. Change the user to the PowerHub™ administrative user (for example, pe).

2. Make sure the $DISPLAY variable is correctly set. If not, set it to:

xhost +

export DISPLAY=<HostName or IPaddress>:0.0

3. Extract the installer from the tar file available in LSM using the following command:

tar -xvf OW_Connect_5000_7_1_0_Rls.tar

After extracting the installer you will get the installer bin file.

The OpenWorks® Connect Release 5000.7.1 supports the upgrade install only.

5000.7.1 Installation Procedure (Update from Original Document) 9

4. Start the installation program.

./OW_Connect_5000_7_1_0_Rls.bin

5. Please read the instructions on the Introduction screen and click Next.

6. Please review the Trademark and Copyright notices on the Trademark Notice screen and click Next.

7. Please read the Licensing Agreement on the License Agreement screen. Select the I accept the terms of the license agreement option and click Next.

If you do not accept the terms of agreement, select the I do not accept the terms of the license agreement option. The License Agreement Warning dialog appears. Click Quit to abort the installation.

8. In the Choose Install Set screen, click the icon for installing OpenWorks® Connect and click Next.

9. Select an appropriate location for the installation. OpenWorks® Connect must be installed under the $PE_HOME directory defined during the PowerHub™ installation. This should be the location shown on the Choose Install Folder screen. Click Next after selecting the installation location.

10. The OpenWorks® Connect Installation Found dialog displays. Click Continue to continue with the upgrade procedure.

11. Click Next in the Select Dictionary screen.

• If there is only one dictionary, the Main Dictionary will be selected and this option will be disabled.

• If there is more than one dictionary, select the main dictionary from the drop down list.

12. Review the information in the Version Summary screen, and then click Next. The Version Summary screen will display the following information:

• Module Name: name of the component to be installed.• Current Version: version of the component currently

installed.• Current Status: indicates whether a component that is already

installed was installed correctly. (N/A = not currently installed).

• New Version: version of the component that is about to be installed.

• Status: indicates if the installation can proceed without problems. This column can have three possible values:

— Error = The component cannot be upgraded because of a version incompatibility between the previously installed version and the version you are about to install.

— Warning = You can proceed with the installation, but you are re-installing or re-upgrading the same version of the component.

— OK = The installation or upgrade can proceed.

13. Review the information in the Pre-Installation Summary screen, and click Install.

14. After the OpenWorks® Connect metadata is loaded, click Next in the Verify Output screen.

15. Select the path for OpenWorks home and Oracle home in the OpenWorks/Oracle Environment Settings screen.

16. Click Next.

17. Click Next in the Corporate Data Archiver Parameters 1/2 screen.

18. Click Next in the Corporate Data Archiver Parameters 2/2 screen.

19. The OpenWorks Connect Module screen informs the user that OpenWorks® Connect has been upgraded successfully. Click Next to continue.

Installation Complete

20. Click Done in the Install Complete screen to close the installer.

5000.7.1 Post Installation / Post Upgrade Procedures 19

Post Installation / Post Upgrade Procedures

Once you have finished installing/upgrading OpenWorks® Connect, you may need to perform additional steps. These steps are very important for the successful completion of your installation. The following post-installation / post-upgrade instructions are available.

• Installing KRS Data from OpenExplorer on page 19.

Installing KRS Data from OpenExplorer

The PowerExplorer® software can read Knowledge Reference System (KRS) data from OpenExplorer. The documents are served using the Apache web server and the web server’s ability to display the content of files to a browser. The PowerExplorer® software can only view KRS data, not create new KRS data.

The PowerExplorer® software can recognize the following locations for a KRS document:

• As a URL. (for example: www.a2d.com)• As a path name in Unix. For example:

/data1/krs/images/northsea_2dseismic.gif$KRS_DATA/images/northsea_2dseismic.gif

• As a path name in Windows. For example:

c:\krs_data\NORTHSEA\northsea_2dseismic.gif%KRS_DATA%\NORTHSEA\northsea_2dseismic.gif

Configurations for a KRS Document

If a KRS document is available as a URL, there are no further configurations.

20 Post Installation / Post Upgrade Procedures 5000.7.1

Path Names in Unix

If your KRS documents are stored as path names, perform the following steps as a Super User on the computer where the PowerHub™ server runs:

1. Mount the base directory of the path name where the files are stored.

Given a path name like one of the following on a computer named remote :

/data1/krs/images/image92.gif if using relative path; e.g. /data1/krs/images/

$IMG_HOME/image100.gif if using environmental variable; e.g. IMG_HOME

where $IMG_HOME is assigned the path of /d0/krs

mount a directory with the mount command. For example:

mount –r remote:/data1 /mnt/data1 For the files where image92.gif is located

mount –r remote:/d0/krs /mnt/image For the files with the path name with the variable IMG_HOME.

2. Create a link in the /usr/local/apache/htdocs/krs directory on the web server to the mounted directory where the documents are stored.

A link for a directory should have the following format:

ln –s LocalDirectory SymbolicName

where the LocalDirectory is a local directory used in the mount command in the previous step, and the SymbolicName is composed in the following manner:

OWSYSID:ProjectName if using relative path; e.g./data1/krs/images/OWSYSID:ProjectName:KRS_DATA if using environmental variable; e.g. IMG_HOME

In the OpenWorks® software, the SID, ProjectName, and KRS_DATA are separated by a colon. KRS_DATA is only necessary if using variables.

If the documents are associated with a project called NORTHSEA and with an OpenWorks® SID name of owremote, the link would be one of the following:

ln -s /mnt/data1 owremote:NORTHSEA:KRS_DATAln -s /mnt/image owremote:NORTHSEA:KRS_DATA

Path Names in Windows

If the KRS files are located on a Windows server, do the following:

1. Copy the KRS documents from the Windows server to a directory on the PowerHub™ server. For example, /data2/krs_data_for_windows on the PowerHub™ server.

For example, a path name on the Windows server might be one of the following:

c:\krs_data\NORTHSEA\northsea_2dseismic.gif%KRS_DATA%\NORTHSEA\northsea_2dseismic.gif

2. Create a link in the /usr/local/apache/htdocs/krs directory on the web server to the mounted directory where the documents are stored.

A link for a directory should have the following format:

ln –s LocalDirectory WinSymbolicName

where the LocalDirectory is a local directory to where the files were copied in the previous step, and the WinSymbolicName is composed in the following manner:

OWSYSID:ProjectName:WINDOWS

In the OpenWorks® software, the SID and ProjectName are separated by a colon, and ProjectName and the word WINDOWS are separated by a colon.

If the documents are associated with a project called NORTHSEA and with an OpenWorks® SID name of owremote, the link would be one of the following:

ln -s /data2/krs_data_for_windows owremote:NORTHSEA:WINDOWSln -s /data2/krs_data_for_windows owremote:NORTHSEA:WINDOWS

Security for a KRS Document

If the KRS documents on the site are sensitive or are intended for only a small group of people, you can protect the documents from unauthorized use by implementing Apache’s authentication, authorization, and access control measures. For more information, refer to the PowerExplorer® Software System Administration Guide and the documents on Apache’s web site (www.apache.org).

Foreign Key Constraints Script

The foreign key constraints script is used to create foreign key data tables. These tables are used by the create, update and delete functionality in the OpenWorks® software.

1. In a terminal window, log on as a PowerExplorer® system administrative user.

2. Enter the following command:

cd $PE_HOME/conf/ow/dbadmin_scripts

3. Start the foreign key constraints script:

./process_OWProject_constraints.sh

4. Enter the ORACLE_HOME location. For example:

/Landmark/ora11g

5. Enter the OpenWorks® project name. For example:

GOM_WLX

6. Enter the SID for the OpenWorks® project. For example:

argent11g

7. Enter the DBA username (system) and password. The script creates the foreign key data table.

8. Repeat step 3 through step 7 for all the OpenWorks® projects on which create, update, delete functionality will be used.

OpenWorks® Startup Services OpenWorks® Connect Installation Guide

5000.7.1 Overview 25

OpenWorks® Startup Services

Overview

This chapter provides detailed information about the OpenWorks® startup services. The following items are discussed in this chapter:

• Introduction to OpenWorks® Startup Services (page 26).

• Managing the Startup Services (page 29).

• Starting the OpenWorks® Startup Services (page 32).

• Entries in the startup_services.props File (page 35).

OpenWorks® Connect Installation Guide OpenWorks® Startup Services

26 Introduction to Startup Services 5000.7.1

Introduction to Startup Services

While installing OpenWorks® Connect, you can add as many projects against as many SIDs as required (please see Step 14 on page 15 in Installation Procedure (Update from Original Document)). However, there is no effective post-installation mechanism which automatically adds new OpenWorks® projects into the PowerExplorer® software. The OpenWorks® startup services enable you to add subsequent projects in the PowerExplorer® software after you have installed OpenWorks® Connect.

The OpenWorks® startup services monitor the PowerHub™ dictionary for a new incoming OWSYS schema. As soon as a new schema is detected, a child service is created which monitors the new schema for new projects. Two types of OpenWorks® startup services exist in the PowerExplorer® software:

• OpenWorks® Startup Service for OWSYS (page 26)

• OpenWorks® Startup Service for Projects (page 26).

OpenWorks® Startup Service for OWSYS

The OpenWorks® startup service for OWSYS monitors the dictionary for a new OWSYS schema added by a user to access OWSYS_2003 or OWSYS_5000. When this service detects a new OWSYS schema, it automatically adds an OpenWorks® startup service for projects for this schema.

OpenWorks® Startup Service for Projects

The OpenWorks® startup service for projects monitors OpenWorks® projects in the OWSYS schema. When a new project is added, deleted or updated in the OpenWorks® software, this service adds/deletes or

• The OpenWorks® startup service for OWSYS is a single service which monitors the dictionary for a new OWSYS schema. Multiple instances of this service do not exist.

• The startup service for OWSYS only starts a project ADD service for a new OWSYS schema, if the entry for that schema exists in System Administration > Dictionary > Topics > Databases.

5000.7.1 Introduction to Startup Services 27

updates it in the PowerHub™ dictionary. Ideally, the number of project services should be equal to the OWSYS entries in the dictionary.

Types of OpenWorks® Startup Service for Projects

The following three startup services for projects are defined in OpenWorks®:

• Project ADD service

• Project UPDATE service

• Project DELETE service.

• To stop adding new projects, stop the OWSYS service.

• The OpenWorks® startup service for projects adds both public and private projects.

• It is not necessary that an OWSYS service should be added prior to adding an OpenWorks® startup service for projects. You can start an OpenWorks®

startup service for projects directly.

• To enable a project ADD service to add OpenWorks® projects for a new OWSYS schema, the user name and password for that schema must be saved in System Administration > Manage Security > Database Credentials.

28 Introduction to Startup Services 5000.7.1

Project ADD Service

The project ADD service monitors the OWSYS schema for new OpenWorks® projects. When a new project is found, this service adds it in the PowerHub™ dictionary.

Project UPDATE service

When an OpenWorks® project is moved from one district to another, the project UPDATE service updates the district information in the PowerHub™ dictionary.

Project DELETE service

When a project is deleted from OpenWorks®, the project DELETE service deletes the relevant information of this project from the PowerHub™ dictionary.

5000.7.1 Managing the Startup Services 29

Managing the Startup Services

The System Administration > Manage Startup Services node in the PowerExplorer® task tree manages information regarding the startup services. The Manage Startup Services node consists of the following tasks:

• Services

• Service Properties

• Service Messages.

30 Managing the Startup Services 5000.7.1

Services

The services task contains information about all startup services which are currently running. Once a startup service is created, you can use the Service Status column in the services task to start or stop a service. The information in the services tasks is organized in terms of the following attributes:

• Service Name: Name of the startup service.

• Service Status: Is the service currently running or not? It can only have two values, Started / Stopped.

• Row Status.

Service Properties

The services properties task stores all properties defined against a start up service. Every property has a value associated with it. Using the service properties task, users can:

• Define (insert) a new property: You can define a new property and its associated value for a startup service.

• Remove (delete) an existing property: You can delete a property defined for a startup service

• Edit (update) an existing property: You can edit the value of a property defined for a startup service.

The properties and their values are available in a picklist and a user may choose any property and value from these picklists. User defined properties and values are not allowed. The information in the services properties task is organized in terms of the following attributes:

• Property: Name of the property e.g. DATASOURCE.

• Value: Value of the property defined e.g the property DATASOURCE has the value 134.132.108.139(owr5test).

• Row status

5000.7.1 Managing the Startup Services 31

An explanation of these properties is as follows:

Service Messages

The service message task stores all messages output by a startup service at different time intervals. The information in the service messages task is organized in terms of the following attributes:

• Time Stamp: The time on which a message was output by a given startup service.

• Message: The message output by a given startup service.

Properties of an OpenWorks® Startup Service

REFRESH_RATE Defines the time after which a startup service searches for a new OWSYS schema or a new project within an OWSYS schema.

MAX_MESSAGES_COUNT defines the maximum message count of a startup service. For further details please see MAX_MESSAGE_COUNT on page 31.

NAME_PATTERN The database name required to add a project in the PowerExplorer® software.

DATASOURCE The data source name in the dictionary.

DATA_MODEL OW2003_SYS or OW5000_SYS

INFO_FETCH_ENABLE This can either be true or false. I

If this is set to true, the project ADD service fetches the user name and password of the OWSYS schema from System Administration > Manage Security > Database Credentials. If a user name and password are not found the project ADD service is unable to add new OpenWorks® projects.

MAX_MESSAGE_COUNT

The total number of messages (rows) saved in the services messages task can be configured through the MAX_MESSAGE_COUNT property in the service properties task. If MAX_MESSAGE_COUNT is set to 300, the service messages task will retain 300 messages only. As new messages are added the previous ones are deleted. A large number of messages can reduce memory performance. Hence it is recommended that the MAX_MESSAGE_COUNT is kept at a moderate or default figure.

32 Starting the Startup Services 5000.7.1

Starting the Startup Services

To start the OpenWorks® startup services, you must add them in the startup_services.props file. You can also define properties of these services in the startup_services.props file.

Starting the OpenWorks® Startup Service for OWSYS

Use the startup_services.props file to start the OpenWorks® startup service for OWSYS. Access the file at the following location:

$PE_HOME/conf/startup_services.props

1. Uncomment the following line in the startup_services.props file:

service.1.class=com.pgs.dm.slegge.server.services.ow.startup.OWSYSAddService

2. Restart the PowerHub server by using the following command:

./runServerManager -restart_servers

Once the startup_services.props file has an entry for an OpenWorks® startup service for OWSYS, you can start and stop it manually using Services on page 30 in the PowerExplorer® client. By default, the service starts as soon as it is created in the startup_services.props file.

Renaming the startup_services.props file

If you intend renaming the startup_services.props file, you must mention its name in the pe_dic.props file. Access the pe_dic.props file at the following location:$PE_HOME/conf/<dictionary e.g. pe_dic.props>

Add the following line to the file: StartupServices.file=<new file name>

5000.7.1 Starting the Startup Services 33

The properties for the OpenWorks® startup service for projects are defined in the startup_services.props file.

3. Define the OW SIDS in the task System Administration > Dictionary > Topics > Databases.

4. Open the task System Administration > Manage Startup Services > Services to view services relevant to each of the OW SIDS added in step 3. You can also use this task to start or stop a particular service. For further details please see Services on page 30

5. If required, you can edit the properties of a startup service by accessing the System Administration > Manage Startup Services > Service Properties task. For further details please see Service Properties on page 30

6. Enter credentials in System Administration > Manage Security > Default Database Credentials task. These credentials are used for the user account for accessing OW OWSYS (SID).

7. Check the System Administration> Dictionary> Topics> Databases task for the newly added OW projects.

8. Check the System Administration > Manage Startup Services > Service Messages for log messages. For further details please see Service Messages on page 31.

Removing an OpenWorks® Startup Service for OWSYS

To remove an OpenWorks® startup service for OWSYS, simply remove or comment its entry from the startup_services.props file.

34 Starting the Startup Services 5000.7.1

Starting the OpenWorks® Startup Service for Projects

Once an OpenWorks® Startup Service for OWSYS is started, it automatically starts an OpenWorks® startup service for projects as soon as it finds a new OWSYS schema.

Hence, you do not need to explicitly start an OpenWorks® startup service for projects. If you have not started an OpenWorks® Startup Service for OWSYS and intend starting an OpenWorks® startup service for projects, for a particular OWSYS schema, enter the following line in the startup_services.props file:

service.2.class=com.pgs.dm.slegge.server.services.ow.startup.ProjectAddService

Users can add as many project services for different OWSYS schemas as required. The properties for the OpenWorks® startup service for projects are defined in the startup_services.props file.

Removing an OpenWorks® Startup Service for Projects

To remove an OpenWorks® startup service for projects, simply remove its entry from the startup_services.props file.

5000.7.1 Entries in the Startup_services.props File 35

Entries in the Startup_services.props File

You can define as many OpenWorks® startup_services as required in the startup_services.props file. You can also define different properties related to these startup services.

Starting the OpenWorks® Startup Service for OWSYS

To start an OpenWorks® startup service for OWSYS, add the following line in the startup_services.props file:

service.1.class=com.pgs.dm.slegge.server.services.ow.startup.OWSYSAddServicecom

Starting the OpenWorks® Startup Service for Projects

To start an OpenWorks® startup service for projects, add the following line in the startup_services.props file:

service.2.class=com.pgs.dm.slegge.server.services.ow.startup.ProjectAddService

Starting the Data Comparison Service

To start the Data Comparison service in the PowerExplorer® software add the following line in the startup_services.props file:

service.2.class=com.pgs.dm.slegge.server.startup.datacompare.DataCompareService

Properties of Startup Services

You can also define different properties of the startup services in the startup_services.props file. These properties are also visible in the Service Properties task in the PowerExplorer® software. For example if an OpenWorks® startup service for OWSYS is defined as follows:

service.1.class=com.pgs.dm.slegge.server.services.ow.startup.OWSYSAddServicecom

You can define a property to set its name as follows:

36 Entries in the Startup_services.props File 5000.7.1

service1.NAME=MyService

You can set the message count of this service as follows:

service1.MAX_MESSAGES_COUNT=200

These properties are available for all startup services currently running in the PowerExplorer® software. Some properties are similar between the OpenWorks® startup service for OWSYS and OpenWorks® startup service for projects, while other properties differ. Some common properties are as follows:

Properties of the OpenWorks® Startup Service for Projects

The following properties are defined for the OpenWorks® startup service for projects:

Common Properties of the OpenWorks® Startup Services

service1.#id#.NAME=MyService Defines the name of startup service.

service1.#id#.MAX_MESSAGES_COUNT defines the maximum message count of a startup service. For further details please see MAX_MESSAGE_COUNT on page 31.

service1.#id#.REFRESH_RATE=<After x milliseconds the service should process>

Defines the time after which a startup service searches for a new OWSYS schema or a new project within an OWSYS schema.

Service ID

#id# is the service id allotted to a startup service when it is defined in the startup_services.props file.

service.#id#.DATA_MODEL=<> OW2003_SYS or OW5000_SYS

service.#id#.DATASOURCE=<> The data source name in the dictionary.

service.#id#.USERNAME=<> The username required to log on to the OWSYS schema.

service.#id#.PASSWORD=<> The password required to log on to the OWSYS schema.

service.#id#.URL=<> The URL of the OWSYS schema.

service.#id#.DRIVER=<> The driver required to connect to the OWSYS schema.

service.#id#.NAME_PATTERN=<> The database name required to add a project in the PowerExplorer® software.

5000.7.1 Entries in the Startup_services.props File 37

service.#id#.INFO_FETCH_ENABLE=<> This can either be true or false. It is used to fetch missing information from the dictionary. If the username is not explicitly mentioned then try fetching information from the dictionary username/password persistence store.

38 Entries in the Startup_services.props File 5000.7.1

OpenWorks® Connect OpenWorks® Connect Installation Guide

5000.7.1 Overview 39

OpenWorks® Connect

Overview

The OpenWorks® Connect module has been fully synchronized with the OpenWorks® 5000.0.3.5 data model, hence providing create, read, update and delete capabilities for all data types. In addition, the OpenWorks® software maintains read-only connectivity with the OpenWorks® 2003.12.x databases.

Removing the Openworks® CRS Information from Lookup Tables

Spatial data from the OpenWorks® software is now accessed using Blue Marble transformation methods. However, entries in the lookup table have precedence over the CRS information accessed from the OpenWorks® software. Therefore, entries from OpenWorks® CRS in the lookup table should be removed to take advantage of this new functionality.

Execute the following task: System Administration > Manage PowerHub Coordinate Systems > Coordinate System Lookup Table> Edit Coordinate System Lookup Table.

OpenWorks® Connect Installation Guide OpenWorks® Connect

40 Adding OpenWorks® Databases 5000.7.1

Adding OpenWorks® Databases

Typically, OpenWorks® databases are added during the installation of the PowerExplorer® software, but they can also be added after the installation using the steps in this section.

Use the PowerExplorer® software to add databases. Add the SID(s) to tnsnames.ora if you need to perform create, update, delete operations on the project data.

to the PowerExplorer® Software

To configure access to additional OpenWorks® databases, perform the following steps as the PowerExplorer® System Administrator.

1. Launch the PowerExplorer® software.

2. Log on as the PowerExplorer® system administrator (default: system_admin).

3. Execute the task System Administration > Dictionary > Topics > Databases.

4. Select TableView >Insert Mode.

5. Select TableView > Insert Rows. The Insert Rows dialog displays.

6. Select the placement of the rows.

7. Enter the number of new rows in the text box.

8. Click OK. The new rows appear in the TableView.

9. Fill in the fields for each OpenWorks® database.

• Data Model—the data model of the OpenWorks® database. Typically OW5000. This field is mandatory.

Please note that at least one OpenWorks® project must be added in the PowerExplorer® software in order to make the OpenWorks® task tree visible. Also, a user must have access to that project.

5000.7.1 Adding OpenWorks® Databases 41

• Database—the OpenWorks® project name with the SID as a prefix. This field is mandatory.

• District• Master Project • Project—typically a presentation name. This field is only

required for OpenWorks® Connect.• Private—typically False for not private.• Type—the kind of database. Typically OpenWorks® software.

This field is mandatory.• URL—the URL of the OpenWorks® instance. This field is

mandatory. The URL has the following format:

jdbc:oracle:thin:@<HOST>:<PORT>:<SID>

• Sequence—typically blank.0• Def Sequence—typically blank.• Need Credentials—typically False for no credentials needed.• Driver— name of the database driver. This field is mandatory.

and its value is:

oracle.jdbc.driver.OracleDriver

• TWO_TASK— Leave blank if the OpenWorks® software and the Corporate Data Store™ software are on different machines. If the OpenWorks® software and the Corporate Data Store™ software are on the same machine, enter the SID.

10. Select TableView > Save to save the configuration of the databases.

11. Launch the PowerExplorer® software and log on as the PowerExplorer® user (pe).

If you do not know which projects are available on a particular SID then an alternate way to configure access to the additional OpenWorks® databases is as follows:

Adding OW2003

The PowerExplorer® software continues to support the OW2003 data model. If required, you can choose OW2003 instead of OW5000. However, OW2003 is only supported with read only access.

1. Execute the task System Administration > Manage OpenWorks > Manage OpenWorks Projects > Projects.

2. When prompted, select a data source (SID).

3. When prompted, enter the user name and password for the SID and click Connect.

• All of the projects on the SID are shown in the resulting table.• The SID and user name is shown in the table title bar.

4. Select a project from the results set, for which you want to configure access.

5. Double-click Make available in the Related Information panel.

A Database(s) create sheet/table opens in the Create mode, containing a row for the selected project. The configuration information automatically displays in the appropriate cells.

6. Specify a name for the new Database and select TableView > Save to save the configuration of the database.

Connecting to Multiple SIDs

You can also connect to multiple SIDs; in that case a ‘Data Source’ column will be added to the table.

Checking the Project Availability

You can view the project availability by selecting the desired project from the results set, and executing the Show availability link in the Related Information panel. The new sheet will display the data source information for the selected project.

Configuring access to multiple OpenWorks® projects

You can also select more than one project from the results set; in that case the new sheet will contain a separate row for each selected project, in the Create mode.

to tnsnames.ora

If an OpenWorks® project is on a SID that is not defined in the tnsnames.ora file, you will not be able to perform create, update, delete operations on the project data.

1. Execute the task System Administration > Manage OpenWorks > Manage OpenWorks Connect > Does OpenWorks Database SID Exist in Tnsnames.ora?

• If the SID is defined, no further steps are required. • If the SID is not defined, proceed to the next step.

2. In a terminal window, su - oracle

3. Edit $ORACLE_HOME/network/admin/tnsnames.ora

4. Copy and paste an existing database entry to add the database. For example:

5. Save and close tnsnames.ora.

Adding the Databases to Global Project Management

To add the OpenWorks® databases to Global Project Management, do the following:

1. Log on to the PowerExplorer® software as system_admin.

2. Execute the task System Administration > Dictionary > Topics > Databases.

3. Insert Rows into the table: specify the location and number of rows to insert, then click OK.

argent9i = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = argent.company.com)(PORT =1521))oooo) (CONNECT_DATA = (SERVICE_NAME = argent11g) ) )

4. Fill in the fields for each OpenWorks® database.

• Data Model: OW2005_SYS• Database: HostName(SID:DatabaseInstanceName)

for example: pbmoon5(SID:owpbmoon5)

• Private: not private. • Project: leave blank• Type: data model type. sql• URL: the URL of the OpenWorks® instance. The URL format

jdbc:oracle:thin:@HostName:1521:DatabaseInstanceName

for example: jdbc:oracle:thin:@pbmoon5:1521:owpbmoon5

• Sequence: leave blank• Def Sequence: leave blank• Need Credentials: no credentials needed. N• Driver: the name of database driver. The format of the name

oracle.jdbc.driver.OracleDriver

• TWO_TASK: the DatabaseInstanceName; for example owpbmoon5

5. Save the changes.

Removing the OpenWorks® Projects

1. Execute the task System Administration > Dictionary > Topic > Databases.

2. In the resulting Databases table, select all of the databases that should be deleted.

3. Put the Databases table in the Delete Mode.

4. Click on the Delete Selected Rows icon and save the changes to the database.

5. Remove access permission from the OpenWorks® project. See the OpenWorks® Software Project Management documentation for details.

46 Adding a Temporary Table for Drill down Support 5000.7.1

Adding a Temporary Table for Drill down Support

To facilitate drill downs and long IN clauses, the PowerHub™ software looks for a certain temporary table. For the OpenWorks® software, this table should be put in the OWSYS schema. The file $PE_HOME/conf/ow/createPhsJoinValues.sql contains the necessary commands to create it:

create global temporary table OWSYS.PHS_JOIN_VALUES

COLUMN_1 varchar2(160),

COLUMN_5 varchar2(160)

grant all on OWSYS.PHS_JOIN_VALUES to public;

Failing to create this table reduces the efficiency of the drill down execution and limits the number of rows that can be selected in a drill down.

Execute Table Creation Script

To execute the table creation script:

1. Log on to the Server Terminal Window.

2. Set the PE_HOME,ORACLE_HOME environment variables.

3. On the command prompt enter:

cd $PE_HOME/conf/ow

4. Log on as a database administrator for the Oracle instance.

5000.7.1 Adding a Temporary Table for Drill down Support 47

5. At the command prompt enter:

sqlplus system/<password for system>@<SQL*Net alias for ORACLE_SID>

6. At the SQL*Plus command prompt, enter:

@createPhsJoinValues.sql

The user must be a SYSTEM Oracle user.

48 Global Project Management 5000.7.1

Global Project Management

Two new tasks allow you to view the OpenWorks® project locations across all available OWSYSSIDs and to list the users that have permission to access the OpenWorks ®projects.

Projects task

1. Execute the task System Administration > Manage OpenWorks > Manage OpenWorks Projects > Projects.

2. When prompted, select a data source (SID).

3. When prompted, enter the user name and password for the SID and click Connect.

• All of the projects on the SID will be shown in the resulting table.

• The SID and user name will be shown in the table title bar.

4. To view all the project’s users, double-click Project Users in Related Information.

Project User task

1. Execute the task System Administration > Manage OpenWorks > Manage OpenWorks Projects > Project User.

2. Put the Project User table into one of the following appropriate modes:

• Insert: to assign a particular project to an OpenWorks® user.• Update: Change security level of a user in any project (see

Security Levels on page 49)• Delete: Remove user from any project

Connecting to Multiple SIDs

You can also connect to multiple SIDs; in that case a ‘Data Source’ column will be added to the table.

5000.7.1 Global Project Management 49

3. Save the changes.

Security Levels

When you create an OpenWorks® project, you are the only person who can access it. You can grant other users access to your project, and you can control their level of access.

The table below shows the available levels of project access—Browse, Limited Interpret, Interpret and Manage—and lists the actions each user type can perform.

Note that Limited Interpret access can be changed and Manage access can also be controlled depending on your site’s preferences. See the OpenWorks® Software Project Management documentation for more information.

Setting Security Level

The user must have access permission on a project in order to perform Insert, Update or Delete operations on that project in the Project User table (see Security Levels on page 49).

For example, if the user wants to change the access permission (‘Security Level’) of another user on any project XYZ, then he/she should have Manage (M) access permission on the project XYZ.

Access Permissions

Browse (1) Can view project data, but cannot create, update, or delete data.

Interpret (2) Can create, update, and delete own project data or the data of a PUBLIC interpreter.

Manage (3) Can view and modify all project data regardless of who created it, and can grant other users’ access. User with manage access can also delete the project. May perform project management functions only if the OW_ADMINISTRATOR role is also granted.

Limited Interpret (4) Can view project data and modify interpretive data (e.g., faults and picks), but cannot modify reference data (e.g., well master data).

50 The OpenWorks® Connect Access Groups 5000.7.1

The OpenWorks® Connect Access Groups

When the metadata for the OpenWorks® Connect module is installed (or upgraded), the installation program installs three access groups. Previously there was just one access group called ow_connect, which allowed read access to the OpenWorks® data.

The OpenWorks® access groups are:

• ow_connect: allows read access to the OpenWorks® data.

• ow_connect_write: allows write access to OpenWorks® data.

• ow_connect_data_admin: allows a user to manage the OpenWorks® reference data.

The new access groups need to be set up so that ow_connect_write is based on a model group of ow_connect, and ow_connect_data_admin is based on a model group of ow_connect_write.

1. Execute the task System Administration > Manage Users > Groups.

2. Put the Groups table into Update Mode.

3. For ow_connect_write, click the Picklist button in the Model Group column and select ow_connect.

4. For ow_connect_data_admin, click the Picklist button in the Model Group column and select ow_connect_write.

5. Save the changes made to the database.

Users must restart the PowerExplorer® client to apply these changes.

5000.7.1 Adding Tvd, Tvdss, Interpolated X and Interpolated Y 51

Adding Tvd, Tvdss, Interpolated X and Interpolated Y

Tvd, Tvdss, Interpolated X and Interpolated Y are well attributes calculated on the basis of functions defined in the PowerHub™ metadata. Users can use these functions to add these attributes to any OpenWorks® well related tasks. Functions responsible for calculating these attributes belong to the wellbore package in the PowerHub™ metadata. A description of these functions is as follows:

To add these well attributes to a PowerExplorer® task, add the following functions in the relevant PowerHub™ metadata TOPIC:

attribute ‘Tvd’: expr=”@wellbore.tvd(@ow.wellbore_path(uwi), Depth, DepthUnit)”type=double FORMAT=’#.0000’;

attribute 'Tvdss':expr="@wellbore.tvdss(@ow.wellbore_path(uwi), Depth,DepthUnit)" type=double FORMAT='#.0000';

attribute 'InterpolatedX': expr="@wellbore.x_lon (@ow.wellbore_path(uwi),Depth,DepthUnit)" type=double FORMAT='#.0000';

attribute 'Interpolated Y':expr="@wellbore.y_lat (@ow.wellbore_path(uwi),Depth,DepthUnit)" type=double FORMAT='#.0000';

To ensure visibility in the PowerExplorer® Interface, define the well attributes under the READ CAPABILITY as follows:

ATTRIBUTE 'Interpolated X': SELECTABLE;ATTRIBUTE 'Interpolated Y': SELECTABLE;ATTRIBUTE 'Tvd': SELECTABLE;ATTRIBUTE 'Tvdss': SELECTABLE;

For further details on these wellbore functions, please see the PowerHub™ Software Metadata Guide.

@wellbore.tvd calculates total vertical depth at a given measured depth.

@wellbore.tvdss calculates total vertical depth sub-surface at a given measured depth.

@wellbore.x_lon calculates the x-coordinate at the specified measured depth.

@wellbore.y_lat calculates the y-coordinate at the specified measured depth.

52 The OpenWorks® Connect Access Groups 5000.7.1

Data Model Properties

The OpenWorks® data model has different properties associated with it. Setting these properties to different values alters the behavior of the data model accordingly.

When you open the PowerExplorer® software, you are not automatically connected to any data source. You are prompted to establish a connection when you run your first task. You can change data sources at any time, and you can connect to multiple data sources simultaneously. In some instances, OpenWorks® users are not prompted for logon credentials when connecting to a data source. The following metadata properties enable you to manipulate the logon mechanism of a user connecting to OpenWorks® databases:

• USE_PE_CREDENTIALS/USE_APP_CREDENTIALS

• ONLY_SHOW_ACCESSIBLE _PROJEC TS

• USE_SID_CREDENTIALS

When you set different combination of these properties, the following behavior is observed:

The USE_PE_CREDENTIALS and USE_APP_CREDENTIALS properties are used interchangeably. If both the properties are set, preference is given to USE_PE_CREDENTIALS. If USE_PE_CREDENTIALS is missing, USE_APP_CREDENTIALS is used instead.

USE_PE_CREDENTIALS /

USE_APP_CREDENTIALS

ONLY_SHOW_ACCESSIBLE_PROJECTS

USE_SID_CREDENTIALS

Desired Behavior

yes yes yes • PE credentials are used for connecting to OWSYS for checking project access.

• Only accessible projects of the user are displayed.

• Since user has already connected to a sid with PE credentials, only PE credentials are used to connect to any project on any sid.

• PE credentials override sid credentials. Hence, setting the use_sid_credentials property to “no” has no effect.

5000.7.1 Data Model Properties 53

yes yes no • PE credentials are used for connecting to OWSYS for checking project access.

• Only accessible projects of the user are displayed.

• Since user has already connected to a sid with PE credentials, only PE credentials are used to connect to any project on any sid.

yes no yes • All projects of the user are displayed.

• PE credentials are used for connecting to a project on any sid for the first time only. PE credentials are saved as sid credentials for this sid and user is not prompted for subsequent logons to this sid.

yes no no • All projects of the user are displayed.

• PE credentials are used to connect to any project on any sid.

no yes yes • All projects of the user are displayed.

• The value of only_show_accessible_projects has no effect in this case because pe_credentials is set to “no”. No credentials are available for connecting to OWSYS for checking accessible projects.

• Users are prompted every time for connecting to any project on any sid. Credentials are not saved unless saved explicitly by the user.

no yes no • All projects of the user are displayed.

• The value of only_show_accessible_projects has no effect in this case because pe_credentials is set to “no”. No credentials are available for connecting to OWSYS for checking accessible projects.

no no yes • All projects of the user are displayed.

• User is prompted for user name/password while connecting to any sid for the first time only. For subsequent logons, these credentials are used for connecting to this sid.

54 Data Model Properties 5000.7.1

USE_RMI_GDI

• If the USE_RMI_GDI=TRUE, the OpenWorks® Connect operations run in a separate process and protect the PowerHub™ software against any probable memory leaks and segmentation violation crashes.

• If the USE_RMI_GDI=FALSE, the OpenWorks® Connect operations are run in a server process space. By default, this property is set to TRUE.

This property can only be set by a PowerExplorer® system administrator at a data model level. To set this property, use the Data Model Properties task (System Administration > Dictionary > Topics > Data Model Properties). Restart the PowerExplorer® software to see the changes into effect.

no no no • All projects of the user are displayed.

5000.7.1 Data Model Properties 55

56 Data Model Properties 5000.7.1

OpenWorks® Connect 5000.7.1 Release Notes OpenWorks® Connect Release Notes

5000.7.1 Enhancements and New Functionality 57

OpenWorks® Connect 5000.7.1 Release Notes

Enhancements and New Functionality

OpenWorks® Connect 5000.7.1 fully replaces it predecessor, OpenWorks® Connect 5000.7.0 and offers the following enhancements and features:

• Users can now update the Well Location (map) task located under OpenWorks > Well Data > Well Location> Well Location (map).

• Picklists have been introduced for the Well Location (map) task.

• A new task, Directional Survey Viewing, has been added under OpenWorks > Well Data > Directional Survey / Position Log.

• Users can now calculate the position log for the directional survey header. For further details, please see the OpenWorks® Connect Online Help.

OpenWorks® Connect Release Notes OpenWorks® Connect 5000.7.1 Release Notes

58 Enhancements and New Functionality 5000.7.1

Fixed Issues

A number of issues fixed by internal testing are included in this release.

5000.7.1 Enhancements and New Functionality 59

Known Issues

There are no known problems for the OpenWorks Connect® software 5000.7.1.

60 Contacting Landmark Customer Support 5000.7.1

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

5000.7.1 Contacting Landmark Customer Support 61

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: apsupport@lgc.com

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: support@lgc.com

Latin America (Spanish, Portuguese, English)7:00 am - 5:00 pm Local Time

713-839-3405 (Houston, TX, USA)Fax: 713-839-3646Email: soporte@lgc.com

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: support@lgc.com

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

62 Contacting Landmark Customer Support 5000.7.1

OpenWorks Connect 5000.7.1 Installation Guide & Release...

Documents

Introduction to Wellbore Surveying_eBook

Introduction to Wellbore Positioning_V01.7.12

Wellbore Utility Chart10

NOV Wellbore Technologies · NOV Wellbore Technologies | KEY PRODUCTS AND SERVICES ... Grant Prideco DRILLPIPE DELIVERED ... The Future of Drilling ©2014 NOV NOV Wellbore Technologies

Wellbore stress analysis

Optimizing Wellbore Integrity in Well Construction - PTRCpub/document/Kirksey - Optimizing Wellbore... · Optimizing Wellbore Integrity in Well Construction ... 1980 Basic Mechanism

Measuring Effective Wellbore Permeability

Simulation of Wellbore Stability during Underbalanced ...aurak.ac.ae/publications/Simulation-of-Wellbore-Stability-during...Simulation of Wellbore Stability during Underbalanced Drilling

Ramey_ Wellbore Storage II

Planne Parenthood - PR Strategeis

Wellbore Clean Up

Agarwal Wellbore Storage

Wellbore Completion Concepts

Wellbore Stability Training

Wellbore Enlargement DPA Rio

WELLBORE STABILITY.pdf

Mudcake effects on wellbore stress and fracture initiation ... · ORIGINAL PAPER Mudcake effects on wellbore stress and fracture initiation pressure and implications for wellbore

The Best Palm Beach Wedding Venues| Kay Weddings.com Florida wedding planne

Birthda Part Inspiration Planne - BettyCrocker.com...Birthda Part Inspiration Planne Gather your ideas and arty-planning inspiration ith etty’s all-in-one orksheet. me Invitations

3D Wellbore&SurveyCheck