EDM AutoSync Server Software 5000.1.10.2 Administrator Guide - …esd.halliburton.com/support/LSM/Drilling/EDMEDTSuite/EDM/... · 2013. 8. 22. · 2 EDM™ AutoSync Server and EDM™

Dra ft

EDM™ AutoSync Server Software 5000.1.10.2Administrator Guide

© 2013 Halliburton

July 2013

© 2013 HalliburtonAll 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, Barrier Assurance Monitoring, BLITZPAK, CartoSnap, CasingLife, CasingSeat, CDS Connect, CGMage Builder, Channel Trim, COMPASS, Contract Generation, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataServer, DataStar, DataVera, DBPlot, Decision Management System, DecisionSpace, DecisionSpace 3D Drill View, DecisionSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace Atomic Meshing, DecisionSpace Base Module, DecisionSpace Desktop, DecisionSpace Geosciences, DecisionSpace GIS Module, DecisionSpace GRC Module, 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, Discovery Suite, DMS, Drillability Suite, Drilling Desktop, DrillModel, DrillNET, Drill-to-the-Earth-Model, Drillworks, Drillworks ConnectML, Drillworks Predict, DSS, Dynamic Frameworks to Fill, Dynamic Reservoir Management, Dynamic Surveillance System, EDM, EDM AutoSync, EDT, eLandmark, Engineer’s Data Model, Engineer’s Desktop, Engineer’s Link, ENGINEERING NOTES, eNotes, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, ezTracker2D, ezValidator, FastTrack, Field Scenario Planner, FieldPlan, For Production, FrameBuilder, Frameworks to Fill, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, Geologic Interpretation Component, Geometric Kernel, GeoProbe, GeoProbe GF DataServer, GeoSmith, GES, GES97, GesFull, GESXplorer, GMAplus, GMI Imager, Grid3D, GRIDGENR, H. Clean, Handheld Field Operator, HHFO, High Science Simplified, Horizon Generation, I2 Enterprise, iDIMS, iEnergy, Infrastructure, iNotes, Iso Core, IsoMap, iWellFile, KnowledgeSource, Landmark (as a service), Landmark (as software), Landmark Decision Center, LandNetX, Landscape, Large Model, Lattix, LeaseMap, Limits, LithoTect, LogEdit, LogM, LogPrep, MagicDesk, Make Great Decisions, MathPack, MDS Connect, MicroTopology, MIMIC, MIMIC+, Model Builder, NETool, Nexus (as a service), Nexus (as software), Nexus View, Object MP, OneCall, OpenBooks, OpenJournal, OpenLink, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWire Client, OpenWire Server, OpenWorks, OpenWorks Development Kit, OpenWorks Production, OpenWorks Well File, Operations Management Suite, PAL, Parallel-VIP, Parametric Modeling, Permedia, Petris WINDS Enterprise, PetrisWINDS, PetroBank, PetroBank Explorer, PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PLOT EXPRESS, 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 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, Recall, Reference Data Manager, Reservoir, Reservoir Framework Builder, RESev, ResMap, Resolve, RTOC, SCAN, SeisCube, SEISINFO, SeisMap, SeisMapX, Seismic Data Check, 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, Smart Change, Smart Deploy, Smart Flow, Smart Skills, Smart Start, Smart Sustain, Smart Transform, Smart Vision, SmartFlow, smartSECTION, smartSTRAT, Spatializer, SpecDecomp, StrataMap, StrataModel, StratAmp, 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, Tubular Basic, 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,

5000.1.10.2 ii

vSpace Blueprint, vSpace Onsite, WavX, Web Editor, Well H. Clean, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellSolver, WellXchange, WOW, Xsection, You’re in Control. Experience the difference., ZAP!, ZEH, ZEH Plot, ZetaAnalytics, Z-MAP, Z-MAP Plus, and ZPS 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.

5000.1.10.2 iii

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.

5000.1.10.2 iv

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.

5000.1.10.2 v

Contents EDM™ AutoSync Server Admin Guide

Contents

Introduction ....................................................................................................................... 1Welcome to EDM™ AutoSync Server Admin Guide ....................................................... 1EDM™ AutoSync Server and EDM™ AutoSync Client Software Documentation.......... 2

Installation Instructions .............................................................................................. 5Installation Overview ......................................................................................................... 5Installing EDM™ AutoSync Server Software.................................................................... 6

Prerequisites ................................................................................................................. 6Major Installation Steps ............................................................................................... 6Uninstall previous versions .......................................................................................... 8Install EDM™ AutoSync Server ................................................................................. 8

Post Installation................................................................................................................... 15Run EDM Database Scripts ......................................................................................... 15Import Site Configuration File ..................................................................................... 18Editing Config file for ZetaAnalytics™ ...................................................................... 19Create AutoSync Users ................................................................................................ 20

EDM Security Tokens and Roles ........................................................................... 20AutoSync.Start Token and AutoSync Admin Role 21AutoSync.remoteConnection Token and AutoSync Data Transfer Role 21

Policy Implementation for EDM AutoSync Server ..................................................... 23Managing Templates for AutoSync Server ........................................................... 23

Setup the Mobile Device Token .................................................................................. 24Run EDM AutoSync Server Software ......................................................................... 25

Configure AutoSync Server Database Connection ................................................ 25Start AutoSync Server Software ............................................................................ 26

Using EDM™ AutoSync Server .............................................................................. 31Overview ............................................................................................................................ 31Web-enabled Interface ........................................................................................................ 32

Database Connection Configuration ............................................................................ 33Step 1: Initialize ..................................................................................................... 35Step 2: Setup Remote Event Notifications ............................................................ 36Step 3: Add Connection ......................................................................................... 38

Multi-version Database Support .................................................................................. 39Synchronization Suspension Scheduling ..................................................................... 39Customizing the Interface with New Event Notifications ........................................... 40Optimized Synchronization with Corporate ................................................................ 40Policies and Templates ................................................................................................ 49

Integration with EDM™ AutoSync Client ......................................................................... 52

5000.1.10.2 vi

EDM™ AutoSync Server Admin Guide Contents

Integration with ZetaAnalytics™ ....................................................................................... 53Integration with OpenWells® Mobile for Workovers........................................................ 54

Registration tab ...................................................................................................... 54Forms tab ............................................................................................................... 55Services tab ............................................................................................................ 56

Troubleshooting .................................................................................................................. 58Repairing the AutoSync Server Software Installation ................................................. 58Reinstalling the AutoSync Server Software Installation ............................................. 58Problems With Interrupting the Installation ................................................................ 60Incorrect Database Name or User Credentials Entered During Installation ................ 61

HTTPS Security ............................................................................................................... 63Overview ............................................................................................................................ 63AutoSync HTTPS Security ................................................................................................. 65

AutoSync Server .......................................................................................................... 65AutoSync Client ........................................................................................................... 65

Appendix A......................................................................................................................... 67EDM Mapping Resources .................................................................................................. 67

vii 5000.1.10.2

Introduction EDM™ AutoSync Server Admin Guide

Introduction

Welcome to EDM™ AutoSync Server Admin Guide

EDM AutoSync Server software was created to add data replication functionality to EDM databases for the COMPASS™ and OpenWells® applications, where automated data synchronization did not currently exist. Synchronization supports immediate access to input as it is made available across networked databases.

Synchronization between multiple Regional EDM databases with one instance (e.g. Head Office) was possible with the initial release of AutoSync. Later releases continued that same functionality and expanded integration with AutoSync Client - bi-directional functionality between Rig/Field offices and the connected Corporate/Regional EDM database.

New with AutoSync 5000.1.10.2 is support for ZetaAnalytics™ WITSML Services 5000.0.0. Users may synchronize WITSML high frequency high volume data from a WITSML Server with a qualified warehouse.

AutoSync supports Landmark’s OpenWells® Mobile for Workovers. Data entry for Workover operations can be performed in a connected or disconnected environment directly into your iPad®. Integration with AutoSync server allows for synchronization with the Corporate/Regional EDM database once you are back in range of the network. See the OpenWells Mobile for Workovers Administration Guide for information on requirements and features.

This document will help you install, initialize and setup EDM AutoSync Server. Some troubleshooting advice is offered and information about mapping resources and performance testing.

Requirements for setting up AutoSync Client and users are discussed in the EDM AutoSync Client Administrator Guide and EDM AutoSync Client Release Notes.

5000.1.10.2 Welcome to EDM™ AutoSync Server Admin Guide 1

EDM™ AutoSync Server Admin Guide Introduction

EDM™ AutoSync Server and EDM™ AutoSync Client Software Documentation

Documentation for EDM™ AutoSync Server software consists of

Online Help - Delivered as HTML Help and accessible from the application or via Start > All Programs > Landmark EDM AutoSync Server> Help.

On the Landmark Software Management web site you can find pdf files of the following:

• EDM™ AutoSync Server Release Notes• EDM™ AutoSync Server Administrator Guide

The same pdf files can be accessed from Start > Programs > Landmark EDM AutoSync Server

Additional documentation is available in EDM™ AutoSync Client installation

Online Help - Delivered as HTML Help and accessible from the application or via Start > All Programs > Landmark EDM AutoSync Client> Help.

On the Landmark Software Management web site you can find pdf files of the following:

• EDM™ AutoSync Client Administrators Guide• EDM™ AutoSync Client Release Notes

The same pdf files can be accessed from Start > All Programs > Landmark EDM AutoSync Client. Additionally, the Online Help and the EDM™ AutoSync Client Rig Supervisor Guide can be accessed from here.

Adobe® Acrobat Reader is required to read the pdfs and Internet Explorer is required for the Online Help.

Help on well assignments can be found in the OpenWells® Online Help system.

Help on using the EDM Administration Utility can be found in the application’s Online Help system.

2 EDM™ AutoSync Server and EDM™ AutoSync Client Software Documentation 5000.1.10.2

Introduction EDM™ AutoSync Server Admin Guide

For help on setting up and using EDM™ AutoSync Server with OpenWells® Mobile, see the OpenWells® Mobile for Workovers Administration Guide.

For help with ZetaAnalytics configurations see ZetaAnalytics™ WITSML Services Installation Guide.

5000.1.10.2 EDM™ AutoSync Server and EDM™ AutoSync Client Software Documentation 3

EDM™ AutoSync Server Admin Guide Introduction

4 EDM™ AutoSync Server and EDM™ AutoSync Client Software Documentation 5000.1.10.2

Installation Instructions EDM™ AutoSync Server Admin Guide

Installation Instructions

Installation Overview

This chapter will walk you through the installation of EDM™ AutoSync Server and its related third-party products. The installation will be followed by post-installation instructions. The main sections of this chapter are:

• Prerequisites (page 6)

• Major Installation Steps (page 6)

• Install EDM™ AutoSync Server (page 8)

• Post Installation (page 15)

• Troubleshooting (page 58)5000.1.10.2

5000.1.10.2 Installation Overview 5

EDM™ AutoSync Server Admin Guide Installation Instructions

Installing EDM™ AutoSync Server Software

This section contains the instructions for installing the application.

Prerequisites

The following programs must be installed on the EDM™ AutoSync Server installation machine prior to installing the application:

Microsoft® Internet Explorer 8.0 or higher

EDM™ AutoSync Server was tested to support Microsoft Internet Explorer 8.0 which is required to run the AutoSync Server interface. Limited testing was done with Mozilla.

Adobe® Acrobat Reader

Required for viewing the EDM™ AutoSync Server Administrator Guide.

If using AutoSync Server and OpenWells® Mobile for WorkOvers

OpenWells Mobile for Workovers requires the EDM installation and Third Party components to reside on the same machine as EDM AutoSync Server. This EDM installation is not necessarily the database repository, but certain dlls and files are needed to ensure reports and schematics can be successfully generated. Refer to the OpenWells Mobile for Workovers Administration Guide for more information.

You must have Database Administrator permissions to “Run EDM Database Scripts” on page 15 or you will need to request this step to be completed by your IT department.

Major Installation Steps

The major steps for the EDM™ AutoSync Server installation are shown below along with a page reference or explanation for each step.

1. Uninstall any previous version of AutoSync Server if installed - see page 8 of this Guide

6 Installing EDM™ AutoSync Server Software 5000.1.10.2


2. Install AutoSync Server - see page 8 of this Guide

3. Run EDM database scripts - see page 15 of this Guide

4. Create AutoSync users - see page 20 of this Guide

5. Set up AutoSync Server policies - see page 23 of this Guide

6. Run AutoSync Server software - see page 25 of this Guide.

Additional steps if you plan to use OpenWells Mobile for Workovers with AutoSync Server: See OpenWells® Mobile for Workovers Administration Guide for detailed instructions:

7. Assign mobile tokens to mobile users - see page 24 of this Guide

8. Install OpenWells Mobile app on mobile device - see the OpenWells® Mobile for Workovers Administration Guide

9. Download well to register mobile device - see the OpenWells® Mobile for Workovers Administration Guide

NOTE: If you choose to run the OpenWells® Mobile for Workovers application without installing EDM on the same machine as AutoSync Server, the reports and schematics will not be available.

5000.1.10.2 Installing EDM™ AutoSync Server Software 7


Uninstall previous versions

Before upgrading to EDM™ AutoSync Server 5000.1.10.2 you will need to uninstall any previous version of AutoSync Server.

1. From the Start menu select Control Panel > Add Remove Programs.

2. Select the EDM™ AutoSync Server installation from the list and click Change/Remove.

When the removal is complete, use Windows Explorer to navigate to C:\Landmark (for a default installation) and delete the folder “AutoSync” or “AutoSync Server” depending on your version.

Install EDM™ AutoSync Server

This section describes the EDM™ AutoSync Server installation process. The installation will load the following programs:

• EDM™ AutoSync Server

• Third-party components (e.g. Apache Tomcat™ Server 6.0 64-bit, Sun™ MicroSystems Java™ 2 Runtime Environment 1.7.x).

Post installation steps located on page 15 are required to complete the installation.Installing EDM™ AutoSync Server Software

Make sure you have administrative rights to install software. You may check Control Panel > Administrative Tools > Computer Management > Local Users and Groups to see if your login is a member of an Administrative Group.

If you download the installation files from the Landmark Software Manager, the files may be zipped. If so, unzip the files to a temporary location and locate the setup.exe to begin the installation.



1. Run the EDM AutoSync Server _ 5000.1.10.2_Release.exe file located in the temporary installation folder to start the installation.

A splash screen displays as the installation initializes.

2. The Installation Wizard displays.

Windows Automatic Updates

Landmark recommends disabling the Windows Automatic Updates feature if it is enabled prior to installing AutoSync software. This reduces the possibility of receiving an error during the installation. After installation, Automatic Updates can be turned back on if needed. See Microsoft Help for details on how to disable and enable Windows Automatic Updates.

Avoid conflicts with running programs

Shutdown all other programs during AutoSync Server installation or repair operations to prevent possible conflicts.



3. Click Next to proceed to the End User License Agreement. After reading and agreeing to accept the agreement, select the I accept the terms in the license agreement option to enable the “Next” button in order to continue with the installation.

4. Click Next to proceed with the installation.

5. The Customer Information dialog box displays. Enter the User Name and Organization that will display as the licensed owner of EDM™ AutoSync Server. You may choose to limit access if you wish.



.

6. Click Next to proceed with the installation

7. The Database Connection Information dialog displays..

8. Enter the User Name and Password for the user who will run AutoSync Server.

Back button

To change installation selections, click on the Back button to navigate to previous panels.



9. Choose a database type, enter the host name (where the EDM database resides) and the Port number:

• Teradata - Enter the name of the EDM database and the Port number. This EDM database will be initialized as the Head Office.

• Oracle - The database name is the SID found in the tsnames.ora file. This EDM database will be initialized as the

• MSDE/SQL Server - The database name is found in the ODBC Data Source Connections.

The above connection information is stored in the hibernate.cfg.xml file located in the \AutoSync\Server\autosync\config directory.

10. Click Next to proceed with the installation.

Default “autosync” user

The database scripts run in the Post Installation section on page 15 create a new “autosync” user. Landmark recommends running the EDM AutoSync Server software with this new “autosync” user.

It is a good practice to change the default “Landmark1” password for the “autosync” user in the EDM Administration Utility after the installation is complete.

Database Ports

Default database ports are listed below. However, you should always determine the port that is assigned to the database before continuing with the EDM AutoSync Server software installation.

• MSDE/SQL Server/SQL Server Express: 1433• Oracle: 1521



11. Optional step: to install to a different location, click on the Change button to open a dialog and navigate to another location to install EDM™ AutoSync Server software. When finished selecting the installation directory, click OK to return to the previous panel. Click Next.

12. The Ready to Install dialog displays. Click Install.



Installation progress is shown.

13. Click Finish.

14. Proceed to the Post Installation section on the next page and perform the required steps to complete the EDM™ AutoSync Server installation.



Post Installation

This section outlines the steps required to complete the EDM™ AutoSync Server software installation.

The following steps must be performed sequentially to complete the installation:

To be performed by Database Administrator

1. Run EDM database scripts. See either

• “If you had a previous installation of EDM™ AutoSync Server” on page 16

• “For a new installation of EDM™ AutoSync Server” on page 16

To be performed by EDM Administrator

1. Import Site Config file for establishing AutoSync roles.

2. Create EDM™ AutoSync Admin and service accounts for users.

3. Implement server conflict and lock policies.

4. Set up Tight groups and permissions for users if using OpenWells® Mobile for Workovers.

5. Run EDM™ AutoSync Server software.

Detailed instructions about how to perform each step are shown below.

Run EDM Database Scripts

Scripts for EDM Oracle and SQL/MSDE database versions 2003.16.1.15 and higher, and 5000.1.0 and higher are distributed in the \AutoSync\Server\autosync\scripts installation directory, and must be executed after running EDM™ AutoSync Server software’s setup executable installation file. There are separate scripts for updating existing installation and for new installations.

These must be run by a DBA account that has rights to create and/or drop tables, EDM/PK schemas, user roles and profile privileges

5000.1.10.2 Post Installation 15


(profiles are for managing Oracle resources only). Run each script with a SQL tool against the EDM database that AutoSync will log in to. Depending on the tool you choose to run the scripts, you may have to change the file extension of the scripts from “ora” or “syb” to “sql”.

Navigate to the \AutoSync\Server\autosync\scripts\<EDM version>directory to locate the following files:

• dropOldTriggers.ora for Oracle database and/or dropOldTriggers.syb for SQL/MSDE database.

• delta_tables.ora for Oracle database and/or delta_tables.syb for SQL/MSDE database.

• triggers.ora for Oracle database and/or triggers.syb for SQL/MSDE database.

The above scripts must be run by the owner of all EDM tables, and the owner must have rights to create triggers. These scripts are required to complete the installation.

If you had a previous installation of EDM™ AutoSync Server

1. Run the appropriate dropOld Triggers script FIRST against the EDM database you will login to. This is necessary as some trigger names have changed. You may receive error messages as your database may not have all the triggers that need to be dropped.

2. Run the appropriate delta_tables script

3. Run the appropriate triggers script

For a new installation of EDM™ AutoSync Server

1. Run the appropriate delta_tables script

2. Run the appropriate triggers script

The script listed below is NOT to be run as a post installation step, but reserved for database updates or if the application is reinstalled.

dropTriggers.ora for Oracle database and/or dropTriggers.syb for SQL/MSDE database

16 Post Installation 5000.1.10.2


The default AutoSync User is created when running the delta_tables scripts. To change the default user, open the script and modify the text at the bottom of the script under the section titled “Create the default AutoSync user”

The script tables are setup to create the tables in the schema “edmadmin” for Oracle, or “dbo” for SQL/MSDE. If the schema owner is not “edmadmin” or “dbo”, the scripts need to be modified to reflect the correct schema owner.

Invoke the SQL spool command to create a log when scripts are run.

.

The default for the scripts include the AutoSync login user to be associated with the EDM database. If you wish to change this association, use the Microsoft SQL Server Management tool to run the following script:

Contact your Database Administrator if you have questions about database rights.

SQL Database Names with Special Characters and Spaces

Problems running scripts may occur since some SQL tools can not connect to SQL Server database names that contain spaces, special characters, or a numeral as the first character. Landmark suggests the following workarounds for such scenarios

• Run the scripts using Microsoft SQL Server Management Studio Express tool, make sure the target database is selected in the ‘Object Explorer’ panel.

• Enclose the database name in brackets, as is shown in the example, below.

$conn = mssql_connect('SQLSERVERHOST', 'username', 'password');

mssql_select_db('[database-name]', $conn);

Run EXEC sp_change_users_login ‘Auto_Fix’, ‘autosync’, NULL, ‘Landmark1’ to attach the login account.



Import Site Configuration File

In order to enable the display of EDM™ AutoSync Server software specific User Role functionality within the EDM Administration Utility, the site configuration user information stored in the EDM database must be updated as follows:

1. Navigate to the \AutoSync\server\autosync\config directory and copy “pe-role-config.xml” to the location where it exists in the Engineer’s Desktop™ (EDT) installation directory. Overwrite the existing file. By default, the location for EDT™ 5000.1 is:

\<install directory>\EDM\Site Configuration Files\db\Permissions\Landmark

2. Open EDM Administration Utility on the machine where EDT applications are installed.

3. Log in to the EDM Database used for EDM AutoSync Server software’s local database connection as a user with Administrator rights.

4. Select the target database node on the tree located in the left panel so that it highlighted.

5. Select Tools > Import and Export from the menu.

The “Import and Export Wizard” displays.

6. Select Import configuration data from local directory.

7. Click Next.

8. Enter the top level directory containing the configuration files to be imported or click on the Browse button to navigate to this directory. Imported files that are not located in the proper hierarchy will cause functionality within the EDM Administration Utility to fail. For a default EDT 5000.1 and higher installation, the top level directory is:

<install directory>\EDM\Site Configuration Files

If you are unable to verify the correct hierarchy exists, contact Landmark Support.

9. Leave the XML file descriptor field blank.



10. Select the Check box to overwrite existing files in the EDM database.

11. Click Finish.

When the import is complete, the ImportResults.log file appears. This file summarizes the results of the import.

The following lines from “pe-role-config.xml” are added to the database configuration table:

<peroledata:role label=“AutoSync Admin”>AutoSyncAdmin</peroledata:role>

<peroledata:role label=“AutoSync Data Transfer”>AutoSyncDataTransfer</peroledata:role>

The “AutoSync Admin” and “AutoSync Data Transfer” roles now appear in the “Available Roles” area located in the EDM Security > Users > autosync user pane.

For more information about adding roles to the EDM database, see EDM Administration Utility Help.

Editing Config file for ZetaAnalytics™

Navigate to the \Landmark\AutoSync\Server\autosync\config directory and open the autosync.xml file.

The following changes will need to be made in both the Local Office and the Head Office installations for the application to work with ZetaAnalytics:

<autosync-module class="com.lgc.fsu.wsi.service.ContainerLifeCycleBootstrap"> <module_services>   </module_services> </autosync-module><autosync-module



For the Head Office installation only (at the warehouse), the category tags need to be removed so that the file shows:

<?xml version="1.0" encoding="UTF-8"?><master-data-categories></master-data-categories>

Create AutoSync Users

The EDM Security model is used for login to EDM AutoSync Server software, EDM™ AutoSync Client software and for EDM database connection validation. When the “delta_tables.ora” script is run against the EDM database, application specific security tokens are created and activated in a newly created default “autosync” EDM user.

EDM Security Tokens and Roles

To successfully login to any AutoSync software and connect to an EDM database, each AutoSync user must have the following EDM security tokens and user roles assigned to their account by the EDM Database Administrator.

AutoSync.Start token and AutoSync Admin role - permits login to EDM AutoSync Server via the web interface. This token is required to login to any AutoSync software in order to perform administrative tasks.

AutoSync.remoteConnect token and AutoSync Data Transfer role - permits EDM AutoSync Server software to establish remote connections to, and run authenticated synchronization related queries against, the remote EDM database. This token is optional for EDM/EDT but is required to be activated if the EDM AutoSync Server user needs to perform synchronization tasks between the Corporate and Local offices (the “AutoSync.start” token must also be activated).

For EDM Security tokens and roles for AutoSync Client, see the EDM AutoSync Client Administrators Guide.

DO NOT log in to EDT Applications with the AutoSync Software User Account!

Never use the default “autosync” user (or whatever user that is set up to log in to AutoSync software) to enter data in EDT applications. Any updates from engineering applications made by the AutoSync software user are treated as synchronization events and ignored.



AutoSync.Start Token and AutoSync Admin Role

If the “AutoSync.start” security token and/or “AutoSync Admin” role assigned to the user logging into an AutoSync application is not activated, a message with the following text displays after log in.

Failed to connect to the EDM database. Using data source <Data Source Name>. Error: You do not have permission to run EDM AutoSync against <Data Source Name> data source; please contact your EDM System Administrator to gain access to the application.

To correct this problem, the EDM Database Administrator must:

1. Open the EDM Administration Utility and login to the database that AutoSync Server uses.

2. On the EDM Administration Utility tree, navigate to EDM Security > Users and click on the user account used to login to AutoSync software.

3. In the “Application Tokens” group on the user panel, scroll through the list of tokens and activate the “AutoSync.start” checkbox.

4. In the “Available Roles” group on the user panel, scroll through the list of roles and activate the “AutoSync Admin” checkbox.

5. Save the change, then close EDM Administration Utility.

The EDM AutoSync Server application must be restarted for the changes to take affect.

AutoSync.remoteConnection Token and AutoSync Data Transfer Role

If the “AutoSync.remoteConnection” security token and/or “AutoSync Data Transfer” role assigned to the user logged in to any AutoSync



Server software is not activated, and the user attempts to create a connection to a remote database, a connection failure message displays.

To correct this problem, the EDM Database Administrator must:

1. Open the EDM Administration Utility and login to the database that AutoSync uses.

2. On the EDM Administration Utility tree, navigate to EDM Security > Users and click on the user account used to login to EDM AutoSync Server software.

3. In the Application Tokens group on the right side of the window, scroll through the list of tokens and activate the “AutoSync.remoteConnection” checkbox.

4. In the “Available Roles” group on the user panel, scroll through the list of roles and activate the “AutoSync Data Transfer” checkbox.

5. Save the change, then close EDM Administration Utility.

The EDM AutoSync Server application must be restarted for the changes to take affect.

Login failure

Connection failure



Policy Implementation for EDM AutoSync Server

Shipped with AutoSync Server are default conflict and lock policies for Server configurations. You may customize these policies and export the configurations as templates to use in other installations. See “Managing Templates for AutoSync Server” on page 23 for details.

Additionally, there are three sample files for server policies that can be used as starting points for establishing custom configurations.

For a typical installation, the template files are located here:

C:\Landmark\AutoSync\Server\autosync\config\Server Policy

• Default.server.policy.xml - default policy

• High_security.server.policy.xml

• Low_security.server.policy.xml

• Centralized _Organization.server.policy.xml

These templates may be imported for use via the Template Manager function. See “Managing Templates for AutoSync Server” on page 23 and the AutoSync Server on line help files for details.

Managing Templates for AutoSync Server

EDM Database Administrator may import the sample files as a starting point for custom configurations Regional/Corporate policies. These are .xml documents.

Also, configurations policies can be exported and saved as templates to be imported and used in other situations.

To access the Template Manager log in to EDM AutoSync Server

From Remote > Connections> Properties > Synchronization tab to access the Template Manager for Corporate to Regional policies. You must have one connection listed for the Properties dialog to be activated.

To export a configuration template

1. Click Export Template



2. On the File download dialog, click Save.

3. On the Save As dialog, select a location to save the file. You may change the file name but the file extension must be “filename.server.policy.xml” or “filename.rig.policy.xml”

4. Click Save.

To import a configuration template

1. Click Browse to navigate through Windows to the desired file.

2. Select the file and click Open. The location and file name is transferred to the dialog.

3. Click Upload Template.

The configuration template is uploaded and applied to the selected location.

Setup the Mobile Device Token

Additional steps are needed if you are setting up AutoSync Server to run with the OpenWells® Mobile for Workovers application:

1. Launch the EDM Administration utility and log into EDM database.

2. Navigate to EDM Security > Users node.

3. Select the username that will be used to connect the iPad® to the EDM AutoSync Server.

4. Grant the ‘autosync’ user access to the “AutoSync.remoteConnect” token. If a user does not have access to this token, then the mobile device cannot register with the EDM AutoSync Server. This account is used to generate Wellbore Schematics and Output Reports on the iPad.®.

5. Repeat steps 3 - 4 for each named user that will connect the mobile device to the EDM AutoSync Server.

Refer to the OpenWells® Mobile for Workovers Administration Guide for more information.



Run EDM AutoSync Server Software

After the database scripts are run, and the security token and user role is granted to the EDM User ID that will log in to an Oracle database, you can run AutoSync Server software. If you desire to assign tokens and roles to a different user than the “autosync” user designated during installation, you must first modify an XML file.

Configure AutoSync Server Database Connection

The default AutoSync Server software installation is configured to synchronize an EDM database running on either Oracle 11g. In order to configure AutoSync Server to properly synchronize different database/instance names, ports, and type, you must modify the “hibernate.cfg.xml” file located in the \AutoSync\Server\autosync\config directory.

In the “hibernate.cfg.xml” file, examples are commented out that show the properties needed to configure the following database types:

• Oracle 11g

• SQL Server/SQL Express

• SQL Server/MSDE 2000

• ZetaAnalytics

1. Open the “hibernate.cfg.xml” file located in the \AutoSync\server\autoync\config directory.

Notice the following lines that are NOT commented out.

IMPORTANT! Always configure AutoSync Server software to the cor-rect database type after installation

You cannot add remote connections to database types or major versions that differ from the initialized database. AutoSync Server software performs a check when connections are created, and will display a notification that the database version is incompatible with the initialized database. For example, an AutoSync Server installation that is initialized to run EDM 2003.16.1.15 on Oracle cannot add connections to EDM 5000.1 on Oracle (version conflict), or EDM 2003.16.1.15 and higher on SQL Express (database type conflict).



<property name="hibernate.connection.password">autosync</property><property name="hibernate.connection.url">jdbc:oracle:thin:@localhost:1521:vmedm161</property><property name="hibernate.connection.username">autosync</property><property name="hibernate.default_schema">EDMADMIN</property>

Edit the lines as needed to properly configure AutoSync Server software to connect to the appropriate database. For example, the Oracle SID “vmedm161” and port number “1521” could be changed to reflect AutoSync software’s initialized database.

Start AutoSync Server Software

This section specifies how to start AutoSync Server software and configure a remote connection with a database that resides on a machine where the application is also installed.

1. Select Start > All Programs > Landmark > AutoSync Server > Start Server to start the EDM AutoSync service.

The LGC EDM AutoSync service starts Apache Tomcat Server. Once the LGC EDM AutoSync service is running, you can activate a configuration control in the system tray as follows:

Open a command prompt and change directory to \AutoSync\server\autosync\bin and run “tomcat6w.exe”.

Change the command line directory, and then run “tomcat5w.exe”



To enable running this configuration control at machine startup, select the “Log On” tab and activate the “Allow service to interact with desktop” checkbox.

2. Select Start > All Programs > Landmark > AutoSync Server

The default web browser starts and opens to the EDM AutoSync Server log in screen. Initial startup after installation will take about 30 seconds to allow for starting the LGC EDM AutoSync service.

3. Enter the User Name and Password of the EDM user ID that retains the “AutoSync.start” application token and the

URL locator service

Due to the configuration of some networks, “localhost” may not be recognized as a valid hostname. It is recommended that the IP address be used in the login and connection URL addresses, as seen in the example below:

http://192.168.0.1:8095/axis2/wsi/app

Activate the “Allow service to interact with desktop” checkbox to run place the control in the System Tray during machine startup



“AutoSyncAdmin” role. The default user created during installation is “autosync” with password “Landmark1”.

4. By default, the “AutoSync” pane displays in the work area. Notice in “Connection Information”, the web service URL that AutoSync software extends displays as shown in the example below:

AutoSync Server web service URL



The web service URL is the address you would enter in another machine where AutoSync Server is installed, and which you desire to synchronize. For example, if the URL shown above is extended by machine “PC-1”, then you would use this URL when adding a remote AutoSync Server connection on machine “PC-2”.

As noted on page 27, Landmark recommends using IP addresses in place of “localhost” if the network protocol/configuration causes a name locator issue.

5. Before you add a remote connection, the role of the local and remote installations must be defined. Perform the following steps on the head office (e.g. corporate office), and any local (remote office) databases that will synchronize with the head office.

a. From the Local > AutoSync pane, click on the Reset button located in the “Initialization” area. Click OK on the confirmation dialog that appears.

b. Click on the Initialize button. On the dialog that appears, enter a name for the database type that is descriptive of the role (head office or local). Select the option to initialize as either Head Office - or - Local Office.

c. Click OK.

6. Once the Head and Local Office databases are initialized, add a connection in the Head Office installation, and then add a connection in the Local Office installation.

a. From the machine with the AutoSync installation configured as the Head Office, select the Remote > Connections pane.

b. From the Connections pane, click on the Add button. The “Remote Container URL Request” dialog appears.

c. From the “Remote Container URL Request” dialog, enter the URL of the Head Office



d. Log in to the AutoSync Server installation on the remote database and repeat steps a through c above. Perform steps a through c on all other databases that you wish to synchronize with the Head Office. Be sure to add connections in both locations, Head Office and Local Office.

Once the connection is configured on the Local Office, synchronization begins.

Initial Synchronization

Initial synchronization of large data sets will take some time. Landmark observed that moving a data set with 12,500 wells and 260,000 reports took approximately 18 hours with an average network speed of 1 Gbps.


Using EDM™ AutoSync Server EDM™ AutoSync Server Admin Guide

Using EDM™ AutoSync Server

Overview

This chapter will walk you through the interface of EDM™ AutoSync Server how to setup users and connections. The main sections of this chapter are:

• “Web-enabled Interface” on page 32

• “Database Connection Configuration” on page 33

• “Synchronization Suspension Scheduling” on page 39

• “Customizing the Interface with New Event Notifications” on page 40

• “Integration with EDM™ AutoSync Client” on page 52

• “Integration with ZetaAnalytics™” on page 53

• “Integration with OpenWells® Mobile for Workovers” on page 54

• “Troubleshooting” on page 58

5000.1.10.2 Overview 31

EDM™ AutoSync Server Admin Guide Using EDM™ AutoSync Server

Web-enabled Interface

The EDM™ AutoSync Server software interface can be viewed from anywhere a connection to the corporate network is available. The interface is designed with the busy Administrator in mind, with a minimalistic approach that allows easy navigation, and streamlined tasks to optimize the user experience.

The main interface was created with the user in mind. Panels in the main working area are viewed by clicking on links inside a common menu bar control, which is familiar to PC software users. Very few dialogs exist, and are only invoked where absolutely necessary.

32 Web-enabled Interface 5000.1.10.2


Database Connection Configuration

EDM™ AutoSync Server software’s easy to use interface allows Administrators to configure database connections in only a few simple steps.

The following illustrates a typical installation synchronizing a Corporate Office and multiple Regional Offices using only AutoSync Server:

A large company may want to synchronize the Corporate Office and Regional Offices and utilize AutoSync Client to synchronize changes with Rig users. Administrative users may also utilize AutoSync Client to synchronize picklists and configuration changes:

5000.1.10.2 Web-enabled Interface 33




Another scenario a company might implement is shown below:

Step 1: Initialize

In each EDM™ AutoSync Server software installation, from the Local menu item on the side bar menu click AutoSync. On the pane that appears, scroll to the Initialization section.

Click Initialize.

On the dialog that appears, enter a Name, set the type (Head Office or Local Office), then click OK



Figure 1 : Initialize EDM™ AutoSync Server Software System

Step 2: Setup Remote Event Notifications

To set up Email notifications, from the Email menu item on the left side bar, select Settings. Click Modify and enter the SMTP Server and user account info, then click Save

.

Figure 2 : Email Setup



Once the SMTP Server connection is configured, add user(s) and assign notification(s) by selecting the Remote > Events menu item .

Figure 3 : Setting Up Event Notifications

The following event types are found in the default installation, and will trigger notifications when assigned to an email account found on the SMTP Server used by EDM™ AutoSync Server software:

• Tight Group - upon initial synchronization, the user is notified of all tight groups, and any subsequent tight group additions

• Delete - any deletion of data on the remote database

• Delete Locked - any deletion of data on the remote database that is flagged by EDM AutoSync software (See “Synchronization Policy” on page 47.). The deletion will not synchronize with the local/corporate instance.

• Error - any synchronization error (set at Debug level)

You can add other event types by editing the “autosync.xml” file (See “Customizing the Interface with New Event Notifications” on page 40.)



Step 3: Add Connection

Click Remote > Connections on the left menu list. Click Add. Enter a remote connection, enter a URL and user credentials, and then click OK.

Figure 4 : Adding a Connection to a Remote AutoSync Instance

When you click OK to save the URL, synchronization begins and continues with no further user intervention under normal circumstances.

Rig Event Notifications

See the EDM AutoSync Client Administration Guide for setting up event notifications from Rig AutoSync Client users.

Data Backup

An optional step is available to reconfigure AutoSync software’s inherent backup/restore functionality. By default, all resources are set to be backed up if deleted on the remote/regional instance. For more information about how to configure the backup/restore function, see “Synchronization Policy” on page 47.



Multi-version Database Support

For this release, EDM™ AutoSync Server software supports synchronization of the following EDM database versions:

• 2003.16.1.15 and higher (Microsoft SQL Server Desktop Engine 2000 (MSDE 2000), Oracle 9i)

• 5000.1.0 and higher (SQL Server 2005, SQL Server Express 2005, Oracle 10g/11g)

The default EDM™ AutoSync Server software installation is configured to connect to a 2003.16.1.15 and higher, or 5000.1.0 and higher Oracle instance.

For more information about how to configure the installation for other database types, see the illustration “Database Connection Configuration” on page 33 “

Synchronization Suspension Scheduling

Regional EDM™ AutoSync Server instances can set multiple time periods during the day when data changes are not published to the Corporate datastore. The suspension of synchronization allows time to review daily reports, or accommodates scheduled database backups.

The figure below shows an example suspension schedule. From 7:00 - 8:00 am, the office collates daily reporting data, and on Sunday plans to perform a database maintenance activity.

Figure 5 : Synchronization Suspension Schedule



Customizing the Interface with New Event Notifications

EDM™ AutoSync Server software supports adding new Event Notifications to the interface, which is accomplished by editing the “autosync.xml” file located in the \AutoSync\Server\autosync\config directory. To apply changes made to the “autosync.xml” file, you must restart the LGC EDM AutoSync service.

Figure 6 : Event Notification Configuration

Optimized Synchronization with Corporate

EDM™ AutoSync Server software architecture is built to minimize the impact of synchronization on network resources, and designed to allow Administrator control over the replication process.

Background Updates

Background synchronization follows a “trickle approach” when updating data across the network. Landmark developed a synchronizing technology based on a federated architecture that continuously moves data all the time, but not all at once. Background updates also leverage this “trickle approach” to continuously move small amounts of data to prevent network saturation.

Default email settings

Event configuration



Modular Data Object Transfers

Only specific data changes are sent during synchronization, not the baggage. EDM™ AutoSync Server software’s design minimizes network cost during synchronization by not sending unchanged data. The program automatically identifies new and newly modified data, and replicates the changes as modular objects.

Performance Management

Several slider-bar controls are included with EDM™ AutoSync Server software to maximize synchronization efficiency, and manage the level of work the program applies to the data replication process.

Network Optimization

EDM™ AutoSync Server optimizes the load on the network with this control, which configures the number of simultaneous connections. During peak usage, lower the setting, or increase the setting if network usage is low.

Figure 7 : Optimizing the AutoSync Server Load on the Network

The adjustment range is 1 - 10, with default set at 1.

Note: For a warehouse connection, set the control at 1.



Database Optimization

EDM™ AutoSync Server software uses resource loaders that act like “buckets” to transfer data. During peak usage, lower the setting to limit the number of resource loaders that AutoSync Server will use to transfer data across the network. If network usage is low, increase the setting to add more resource loaders to optimize the synchronization process.

Figure 8 : Optimizing Database Transfers

Synchronization Frequency

You can control overall software performance at the program level. Or, you can control connection specific synchronization frequency at the connection level.

Figure 9 and Figure 10 show the locations of each control.

Overall Program Synchronization Frequency

When large modifications of data require synchronization between Regional and Corporate databases, EDM™ AutoSync Server software controls data throughput to prevent network saturation. Use this control


Note: For a warehouse connection, set the control at 1



to adjust the rate of AutoSync Server communication with the initialized database.

Figure 9 : Overall Program Synchronization Frequency Control

Connection Synchronization Frequency

Synchronization frequency between Regional and Corporate is adjusted in the “Remote Connection Properties” dialog and is important to fine tune individual connections.

This control should not be confused with the Synchronization Rate in the Performance pane, which controls overall AutoSync Server software performance between Corporate and Regional databases. Each connection can be adjusted in the Properties dialog to differentiate the synchronization frequency per connection. AutoSync Server software polls each remote database, acting much like a heartbeat function. The slider control adjusts the period of time between each poll.

An example of how this control may be used would be if a connection experiences very little activity it may be less critical and require infrequent updates. This connection with a low activity level would be


Note: For a warehouse connection, set the control at 1



a good candidate for a lower synchronization frequency setting than another more active connection.

Figure 10 : Remote Connection Synchronization Frequency Control

Error Handling and Recovery

EDM™ AutoSync Server software automatically recovers from synchronization interruptions caused by network failure or user intervention. The error handling and recovery component of the software is based on architecture that stores a record of all failed synchronization events, and employs a mechanism to successfully correct each error to complete synchronization.

Diagnostic information is found in the following locations:

• SYNC_CONTAINER_TASK table - AutoSync Server software creates a table in the EDM database named “SYNC_CONTAINER_TASK”. In this table, all error events are recorded for the purpose of retrying the synchronization task. The program retries after 1 minute, then retries occur on a double-double basis until the 24 hour point is reached and an endless loop occurs of one retry per day. Notifications occur when 1 day is met, and then on a recurring basis every day.

Helpful diagnostic information is found in the “TASK_COMMENT” column.

Drag the slider control to change the frequency.



• System logs - logs are created that contain information helpful to diagnose errors (“Detailed Error Logging” on page 46).

• Resource failure files- diagnose resource failure files in the \AutoSync\autosync\failure directory.

Data Validation and Auditing

EDM™ AutoSync Server software leverages the robust historical auditing features of EDT applications.

Changes to Wellbores, Designs, and Cases are tracked as historical audit information.

To enable the recording of Change History in the Corporate instance, the “ChangeHistoryLogging” EDM System Setting must be set to “TRUE” in the EDM Administration Utility (Figure 11). This will result in auditing all changes made due to synchronization with For more information, see EDM Administration Utility Help.

Because all synchronization updates are tracked as modifications made by the AutoSync Server user, the AutoSync Server user account should never be used to log into an EDT application for data entry.

Figure 11 : Change History Logging Setting



Detailed Error Logging

Debug logging of EDM™ AutoSync Server software and SQL logs System logs are available to troubleshoot problems with the AutoSync Server application or the SQL Server. By default, each log is 1 MB in size. When the size limit is reached, additional logs are created with iterative numbers appended to the extension. The size and number of logs stored are fully configurable.

EDM™ AutoSync Server software contains a built-in log viewer, as seen in the figure below, that provides ready access to system logs.

Figure 12 : AutoSync Server Software Log Viewer

From the Logs menubar, click on the AutoSync or SQL tabs to view the logs

The “autosync.log” and “autosync_sql.log” files are located in the \AutoSync\ Server\logs directory



Synchronization Policy

Synchronization Policy allows AutoSync Server Administrators to configure how the subscribing database manages the synchronization of the publishing database's synchronization events. A tree control is used that mirrors the table/object structure of the database model. Synchronization Policy can be configured on either the Head Office (Corporate) or Local Office (Regional) machines. If the policy is configured in AutoSync Server software initialized as the Head Office, synchronization of objects in the remote database are controlled. If the policy is configured in AutoSync Server software initialized as the Local Office, synchronization of only Catalogs and Lithology records are controlled.

Figure 13 : Synchronization Policy

Click Remote on the left menu bar, and select a connection. Click Properties to open the dialog

On the Remote Connection Properties dialog, select the Synchronization tab and then a resource to configure policy.



Notification event options available for users who have event notifications enabled include:

• If a resource is deleted or a block delete attempted. Note, if a child object is marked to not allow deletion, all parent tables are also protected from being updated as deleted during the synchronization.

• If resources are added, or modified

• If conflicts are detected that originate from different AutoSync Server instances synchronizing the same data

When a table/object (resource) is selected in the tree, the right panel displays the following controls, which are all activated by default.

Delete Policy

• Allow Deletes - when activated, the resource can be updated in the subscribing database as deleted. The deleted resource can be further protected if the “Backup Resource” checkbox is activated. For more information about the “Backup Resource” option, see below. When deactivated, all parent tables cannot be deleted and display as grayed out in the tree.

• Backup Resource - this checkbox is available only when the “Allow Deletes” option is activated. When activated, the “Backup Resource” checkbox forces AutoSync Server software to store all deleted data as XML files in the \AutoSync\server\delete directory. When used in conjunction with the Event Notification feature (see “Step 2: Setup Remote Event Notifications” on page 36), the Backup Resource option triggers email messages to designated AutoSync Server Administrator(s), who can then restore the data to the local/corporate database. For more information about how to restore deleted data, see “Resource Restore” on page 50.

Email Notification Policy

• New Resources - when activated, email notifications are sent to users who are specified to receive “Add” notifications in the Event Notifications pane. Any data added to the remote database triggers email to users specified to receive “Add” notifications.

• Deleted Resources - when activated, email notifications are sent to users who are specified to receive “Delete” notifications in the Event Notifications pane. Email Notification can be activated whether the objects are marked for deletion or not. If the object is marked to not allow deletion, and the email notification is



activated, the event notification will be triggered if a user attempts to delete the object.

• Updated Resources - when activated, email notifications are sent to users who are specified to receive “Update” notifications in the Event Notifications pane. Any existing data in the remote database that is modified after synchronization will trigger email to the users specified to receive “Update” notifications.

• Conflicted Resources - when activated, email notifications are sent to users who are specified to receive “Conflict” notifications in the Event Notifications pane. Any data in the remote database that causes synchronization errors will trigger email to the users specified to receive “Conflict” notifications.

Policies and Templates

EDM™ AutoSync Server provides templates to set up policy configurations between a Local Office (Regional) and Head Office (Corporate) instances. See “Policy Implementation for EDM AutoSync Server” on page 23 of this manual for details.



Resource Restore

EDM™ AutoSync Server software supports the restoration of objects deleted in a remote/regional database, if the “Backup Restore” option is enabled in the target local/corporate datastore.

With the “Backup Restore” option activated in the Delete Policy pane, and an email account with notification enabled, a message is generated and sent to the designated email account when that resource is deleted on the remote/regional instance. This email notification contains a unique key that can be entered in the Resource Restore pane to restore the deleted object, and associated children, to the local/corporate instance.

Figure 14 : Resource Restore Process

Confirmation when restore completes.



EDM Security Model Integration

EDM™ AutoSync Server software is integrated with EDM software through new security tokens and user roles added to the EDM data model.

• AutoSync.start - EDM user security token that allows log in to the AutoSync application console. Once revoked, the LGC AutoSync service must be restarted to startup.

• AutoSync.remoteConnect - EDM user security token that allows database connection create/modify/delete

• AutoSync Data Transfer - EDM user role that allows the running of synchronization activity against the EDM database

• AutoSync Admin - EDM user role that allows the performance of all administrative tasks, except create/modify/delete connections.

:EDM Administration Utility User Pane

Select the “autosync” user, and then review/configure the Application Tokens and Available Roles as needed.



Integration with EDM™ AutoSync Client

See the EDM™ AutoSync Client Administration Guide for details of setting up AutoSync Client users and administrative tasks. Additional tokens are required

Resource Configuration Policies and Rig Security Group Assignments (found under the Rig tab on the left of the application) are explained in the EDM™ AutoSync Client Administration Guide

52 Integration with EDM™ AutoSync Client 5000.1.10.2


Integration with ZetaAnalytics™

EDM™ AutoSync Server plays an integral role in the ZetaAnalytics data aggregation workflow. ZetaAnalytics allows you to aggregate high-frequency, high-volume real-time data from a WITSML source with low-frequency, low-volume contextual data (traditionally stored in EDM) into a qualified data warehouse.

For this configuration you will need to initialize the AutoSync Server as the Local Office for the EDM installation that receives data from EDT applications and any low frequency, low volume data from the ZetaAnalytics WITSML Sever. Please see the ZetaAnalytics Installation Guide for more details

5000.1.10.2 Integration with ZetaAnalytics™ 53


Integration with OpenWells® Mobile for Workovers

See the OpenWells Mobile for Workovers Administration Guide for details of setting up and using an iPad® for data entry for OpenWells.

An overview of integrating this application with AutoSync Server:

1. Make sure the EDM installation and Third Party components reside on the same machine where AutoSync Server will be installed.

2. The EDM Administrator needs to grant AutoSync.remoteConnect tokens to all iPad® users.

Registration tab

Once a user downloads a well from the EDM database, the mobile device is registered with AutoSync Server but the EDM Admin must activate the device.

Users can contact the EDM Admin to request enabling the device or the EDM Admin can browse the Registration page to view new logins.

1. Select Mobile Devices > Registration.

2. Select the desired EDM login and the Enable check box.

54 Integration with OpenWells® Mobile for Workovers 5000.1.10.2


In the event a device needs to be de-registered to release a license, follow these instructions:

1. Select Mobile Devices > Registration.

2. Select the desired EDM login and click Remove.

The license is no longer associated with the device. Data previously downloaded to the device is preserved but no synchronization with a database is possible. To prevent re-registration, the EDM Admin should revoke the AutoSync.remoteConnect token.

Forms tab

To change or edit the data entry forms used by OpenWells Mobile for Workovers use this facility.

1. Select Mobile Devices > Forms

2. Download the current configuration file and edit.

3. Upload the changed file. Use Browse to navigate to the file location. Click Send to upload the changed file.

4. Use the Reset button to restore the data entry configuration file to the default status.

5000.1.10.2 Integration with OpenWells® Mobile for Workovers 55


Services tab

Select Mobile Devices > Services

Enter the DSN or Data Source Name of the EDM database the mobile device will connect with.

You may also view the status of Reports and Wellbore Schematics generated by the mobile device. If you do not have an EDM installation on the same machine with EDM AutoSync Server, the Reports and Schematics will not be available.

56 Integration with OpenWells® Mobile for Workovers 5000.1.10.2


5000.1.10.2 Integration with OpenWells® Mobile for Workovers 57


Troubleshooting

The following lists some potential problems that may exist during installation of AutoSync Server software.

Repairing the AutoSync Server Software Installation

Prior to contacting Landmark Support, it is recommended to always perform a repair operation and run the AutoSync Server installation again.

1. Shutdown the EDM™ AutoSync Server service.

2. From Windows “Add or Remove Programs”, select the Click here for support information link under the “Landmark EDM™ AutoSync Server” entry. From the “Support Info” dialog that appears, click on the Repair button.

A confirmation that the repair process has begun displays with a progress bar. When the repair is complete, the progress bar dialog closes.

Reinstalling the AutoSync Server Software Installation

Download the installation from the Landmark Software Manager software, and then run executable. Make sure EDM™ AutoSync Server is not running when you re-install.

1. A splash screen appears. Click Next to proceed.

2. The next panel displays with two options:

• Repair - repairs the existing installation. The installation will run a validation routine on existing AutoSync Server files and registry keys then replace any that are missing or corrupt.

• Remove - removes AutoSync Server from the system.

Conflicts with running programs

Shutdown all other programs during AutoSync Server installation or repair operations to prevent possible conflicts.

58 Troubleshooting 5000.1.10.2


• Select the Repair option, and then click Next to proceed.

3. Click on Install.

The AutoSync Server repair process is run.

At the end of the process, click Finish

.Reboot the machine to complete the repair operation. The reboot ensures theEDM™ AutoSync Server is properly reinstalled.

5000.1.10.2 Troubleshooting 59


If errors occur during the repair process, review the remaining Troubleshooting topics and perform actions that relate to the problem(s). If errors display that are not mentioned in the Troubleshooting section, or continue to persist after troubleshooting actions are taken, contact Landmark Support.

Problems With Interrupting the Installation

If the installation was interrupted, you will not be able to log into the AutoSync Server application. The problem will usually be caused by rebooting when a popup window occurs prior to the Installation Wizard finishing.

To correct the problem you will have to delete the installation key in the registry, and the Install Shield installation information in Program Files.

1. To edit the registry, select Start > Run, then type regedit and click the OK button.

2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE > Microsoft > Windows >CurrentVersion >Uninstall.

3. Look for the following application ID.

{B724876D-C000-4EB5-AD6A-C7B88F7E7A85}

Re-running scripts after a repair or re-installation

The appropriate scripts are found in AutoSync\Server\autosync\scripts\<EDM version> directory.

• First, run the dropTriggers.ora or dropTriggers.syb • Second, run the appropriate delta_tables script• Last, run the appropriate triggers script

Windows Automatic Updates

Landmark recommends disabling the Windows Automatic Updates feature if it is enabled prior to installing AutoSync Server software. This reduces the possibility of receiving an error during the installation. After installation, Automatic Updates can be turned back on if needed. See Microsoft Help for details on how to disable and enable Windows Automatic Updates.



4. When you click on the ID, which is on the left side of the dialog box, the DisplayName, on the right side of the dialog, should be “Landmark EDM AutoSync Server 5000.X”.

5. If you cannot find the ID listed in Step 3, you will need to click on each of the IDs and look at the DisplayName for each. When “Landmark EDM AutoSync Server 5000.X” appears as the DisplayName write down the ID.

6. To remove the ID, right click on the ID, and then select Delete.

7. Close the Registry window.

8. Open Windows Explorer.

9. While in Windows Explorer go to the <Install Directory>\AutoSync Server directory. If the directory is present, right click on it, and then select Delete.

10. You will now need to reinstall AutoSync Server. Reboot the computer prior to reinstallation, and make sure the Installation Wizard finishes before rebooting.

Incorrect Database Name or User Credentials Entered During Installation

If the Database name, user name and/or password are incorrectly entered during EDM™ AutoSync Server software installation, AutoSync Server software will not run, and the log in screen will not display in a browser.

To correct this issue:

1. Open the “hibernate.cfg.xml” file located in the \autosync server\config directory.

2. Search for the following lines. Disregard the brackets “[ ]” shown below, which are added to the example strings only:

<property name="hibernate.connection.password">edmadmin</property>

<property name="hibernate.connection.url">jdbc:oracle:thin:@[machine name]:[database port]:[database name]</property>

<property name="hibernate.connection.username">edmadmin</property>

5000.1.10.2 Troubleshooting 61


3. Enter the correct Database name, user name and password into the lines as needed.

4. Save the “hibernate.cfg.xml” file.

5. Start up the AutoSync Server application.

Database Types

For an example list of database types found in an EDM 2003.16.1.15 database version, see “EDM Mapping Resources” on page 67.


HTTPS Security EDM™ AutoSync Server Admin Guide

HTTPS Security

Overview

EDM™ AutoSync Server and EDM™ AutoSync Client employ a stronger level of point to point security, using https protocol and digital certificates for secure socket connections. The data is also compressed on the EDM™ AutoSync Client side while the data is secured by the protocol.

Both AutoSync Server and AutoSync Client can be configured to use signed digital certificates to ensure encrypted data transmission. The the address bar of the AutoSync Server browser will indicate https:// instead of http:// when the protocol is implemented.

A Certification Authority is an entity that can provide authenticating certificates, enabling an organization to create a system of trust without pre-built software or commercial services. It is a trusted third party that vouches for the authenticity of a site to browser connections. There are commercial Certificate Authorities where digital certificates can be purchased. Some large institutions or corporations may have their own Certificate Authorities.

The general process is for the owner of a server to generate a public/private key pair for the web server. A Certificate Signing Request is generated and sent to a Certificate Authority for signing. It contains the public key (to be signed by the Certificate Authority) and the private key (signed by the requestor).

The Certificate Authority may request additional identifying information about the requestor, server and location before granting the signature.

The signed certificates are then imported to the server in a special file, usually called “yourname.keystore”. The web server should be configured to use this file as the keystore. Landmark recommends this procedure is implemented.

For more information see

http://en.wikipedia.org/wiki/Certificate_authority

5000.1.10.2 Overview 63

http://en.wikipedia.org/wiki/Certificate_authority

EDM™ AutoSync Server Admin Guide HTTPS Security

http://en.wikipedia.org/wiki/HTTP_Secure

http://en.wikipedia.org/wiki/Transport_Layer_Security

64 Overview 5000.1.10.2

http://en.wikipedia.org/wiki/HTTP_Secure

http://en.wikipedia.org/wiki/Transport_Layer_Security

HTTPS Security EDM™ AutoSync Server Admin Guide

AutoSync HTTPS Security

EDM™ AutoSync Server and EDM™ AutoSync Client ship with default settings for your IT department to secure the web server via HTTPS.

AutoSync Server

In the installation directory

AutoSync/Server/autosync/tomcat/config/server.xml

Find the section called “Define a SSL HTTP” and edit to your reflect your keystore file and password.

for example,

 <Connector port="8443" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" maxSpareThreads="75" enableLookups="false" disableUploadTimeout="true" acceptCount="100" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keystoreFile="autosync\keystore\server.keystore" keystorePass="changeit"

AutoSync Client

In the installation directory

AutoSync/Client/autosync/bin

There are two files

• autosync_client.bat• client.keystore [substitute your own file]

5000.1.10.2 AutoSync HTTPS Security 65

EDM™ AutoSync Server Admin Guide HTTPS Security

The autosync_client.bat file must be edited to refer to your own client.keystore file and reflect the correct password.

For example,

start "AutoSync Client" "%JAVA_CMD%" -Djavax.net.ssl.trustStore=client.keystore -Djavax.net.ssl.trustStorePassword=changeit -Djava.rmi.server.codebase=file:../lib/modules/client_service_api.jar -XX:MaxPermSize=128m -Xms256m -Xmx1024m -classpath %CLASSPATH% -splash:..\images\AutoSyncClient.jpg -ea com.lgc.autosync.client.MainEntry

66 AutoSync HTTPS Security 5000.1.10.2

Appendix A EDM™ AutoSync Server Admin Guide

Appendix A

EDM Mapping Resources

The following pages show the objects used to synchronize the EDM 2003.16.1.0 and higher databases, plus the 5000.1.0 and higher databases.

To view the mapping tables, consult the appropriate database version in

C:\Landmark\AutoSync\server\autosync\scripts

for a normal installation.

5000.1.10.2 EDM Mapping Resources 67

EDM™ AutoSync Server Admin Guide Appendix A

Resource Tree

68 EDM Mapping Resources 5000.1.10.2

Appendix A EDM™ AutoSync Server Admin Guide

Expanded Events objects

5000.1.10.2 EDM Mapping Resources 69

EDM™ AutoSync Server Admin Guide Appendix A

70 EDM Mapping Resources 5000.1.10.2

Documents

EDM AutoSync Server Software 5000.1.10.2 Administrator Guide - …esd.halliburton.com/support/LSM/Drilling/EDMEDTSuite/EDM/... · 2013. 8. 22. · 2 EDM™ AutoSync Server and EDM™