ZetaAnalyticsTM - esd.halliburton.com

ZetaAnalytics

Installation Guide

Version 5000.1.0August 2013

TM

© 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, 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 Frameworks to Fill, Dynamic Reservoir Management, Dynamic Surveillance System, EDM, EDM AutoSync, EDT, eLandmark, Engineer’s Data Model, Engineer’s Desktop, Engineer’s Link, eNotes, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, ezTracker2D, FastTrack, Field Scenario Planner, FieldPlan, For Production, FrameBuilder, Frameworks to Fill, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, 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, iNotes, Iso Core, IsoMap, iWellFile, KnowledgeSource, Landmark (as a service), Landmark (as software), Landmark Decision Center, Landscape, Large Model, Lattix, LeaseMap, 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, 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, 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, SeisMapX, 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, 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, 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, vSpace Blueprint, vSpace Onsite, WavX, Web Editor, 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, Z-MAP, and Z-MAP Plus are trademarks, registered trademarks, or service marks of Halliburton.

GeoFrame is a registered trademark of Schlumberger Corporation.

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

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

Third Party Licenses and AttributionsHalliburton acknowledges that certain third party code has been bundled with, or embedded in, its software. The licensors of this third party code, and the terms and conditions of their respective licenses, may be found at the following location:

PathNameInInstallationDir/Third_Party.pdf

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

ZetaAnalytics Installation Guide

5000.1.0.0 v

CONTENTS

Planning the Installation .................................................................................................. 1Component Requirements for ZetaAnalytics Integration ................................................. 2

ZetaAnalytics Components ......................................................................................... 3Other Landmark Components .................................................................................... 3

Data Warehouse................................................................................................................ 4Hadoop .............................................................................................................................. 4Example Installation Plans................................................................................................. 4Landmark Software Manager............................................................................................ 7Licensing ............................................................................................................................ 7

Verify or Add Product License .................................................................................... 8License Checkin and Checkout ................................................................................... 8

Installation ........................................................................................................................... 11Installation Workflow ........................................................................................................ 11Step 1: Install Pre-Requisite Software ............................................................................... 12

Data Warehouse ......................................................................................................... 12Zeta WITSML Services ................................................................................................. 13EDM AutoSync Server ................................................................................................. 13Hadoop ....................................................................................................................... 14

Step 2: Download Installer ................................................................................................ 14Step 3: Install ..................................................................................................................... 14Step 4: Database Setup ..................................................................................................... 28Step 5: LDAP Security Configuration ................................................................................. 28Step 6: Server Integration ................................................................................................. 28Un-Configured Install Workflow........................................................................................ 29

Step 1: Setup ZetaAnalytics Server Machine .............................................................. 30Step 2: Run Install on Component Server Machines .................................................. 32Step 3: Edit Server Configuration Files on Each Component Server Machine ............ 33Step 4: Edit Server Configuration Files on ZetaAnalytics Server Machine .................. 34

Starting ZetaAnalytics........................................................................................................ 35Uninstalling ZetaAnalytics Software.................................................................................. 36

Restoring the MMS from Backup when Re-Installing ................................................. 38

Database Setup................................................................................................................... 41Database Setup Workflow................................................................................................. 41Step 1: Install Database Drivers......................................................................................... 42Step 2: Create Databases .................................................................................................. 42Step 3: Setup and Run Pipeline in ZetaAnalytics WITSML Services................................... 50Step 4: Run Default Job Script ........................................................................................... 53


vi 5000.1.0.0

Server configuration.......................................................................................................... 55LDAP Security .................................................................................................................... 55Component Integration..................................................................................................... 57

FTQS: Fact Table Query Service .................................................................................. 58MMS: Model Management Service ............................................................................ 59Scoring ........................................................................................................................ 60Simulator .................................................................................................................... 61Streaming ................................................................................................................... 61Wellspace ................................................................................................................... 63zetaanalytics_service .................................................................................................. 65

Performance Tuning .......................................................................................................... 66Change ESRI Map Server ................................................................................................... 67

Troubleshooting ................................................................................................................. 69Installer Errors ................................................................................................................... 69Log Files ............................................................................................................................. 69Port Conflicts ..................................................................................................................... 71Data Display Problems....................................................................................................... 72Web Server Unavailable .................................................................................................... 74Streaming or Scoring Job Status ........................................................................................ 74Restarting Services ............................................................................................................ 75

Appendix: Teradata Administration.............................................................................. 77Teradata Client .................................................................................................................. 77Specify ODBC Driver .......................................................................................................... 77Create a User and Database for the Analytic Data Source Tables..................................... 79

Index ...................................................................................................................................... 83


5000.1.0.0 1

PLANNING THE INSTALLATION

This chapter describes system requirements that must be met before installing and configuring the ZetaAnalytics software. It also describes how to plan for different software and hardware arrangements to best match your work environment.

Before installing ZetaAnalytics, additional Landmark and third-party software must be installed and correctly configured to communicate together as an integrated solution, including a Zeta-qualified Data Warehouse. Additional requirements may be documented in the installation instructions for each required component. It is important to understand these requirements so you can decide how to best deploy the software to meet your requirements.

The complete ZetaAnalytics eco-system would consist of:

• the ZetaAnalytics software

• the Zeta WITSML Services software

• a qualified Data Warehouse solution

• at least one EDM instance and AutoSync installation

Each piece of software can be installed on a separate machine and different components of the ZetaAnalytics software can be configured to run on different machines. Finally, different components of the Zeta data-model could be configured to run in different Data Warehouses. For clarity these install instructions assume that only one Data Warehouse exists. The following diagram shows the various components that describe the complete ZetaAnalytics system and how they interact.


2 5000.1.0.0

Component Requirements for ZetaAnalytics Integration

This section describes certain requirements that ZetaAnalytics and its components need in order to communicate with each other and to work with the Data Warehouse. Additional requirements and pre-requisites for other Landmark and third-party components are in the installation instructions for each of those components.


5000.1.0.0 3

ZetaAnalytics ComponentsThese components are installed as part of the ZetaAnalytics Client-Server installation or are additional pre-requisites that may be required to support each component.

ZetaAnalytics Desktop Client, Version 5000.1.0

• Browser: Mozilla Firefox, Google Chrome, Internet Explorer 9• Display: 1980 x 1080 or higher

ZetaAnalytics Server, Version 5000.1.0

• Platform: Windows 2008 Server R2 or Red Hat Enterprise Linux 5.8

• HTTP Server: Apache Tomcat • Qualified Database: Teradata, Greenplum, or Netezza• Messaging Server: Apache ActiveMQ

Other Landmark ComponentsThese components are Landmark products that must be installed and configured separate from the ZetaAnalytics Client-Server installation.

These are pre-requisites that are expected to be in place before the ZetaAnalytics product can be fully configured and used. See the documentation for each component to determine additional requirements.

ZetaAnalytics WITSML Services, Version 5000.1.0

• Platform: Windows 7, XP, Vista, 2003 Server or 2008 Server• Browser: Internet Explorer 8• Infrastructure:

- .NET Framework 3.5- Java Developers Kit (JDK) - Apache Tomcat Server

EDM AutoSync Server, Version 5000.10.2 (or higher)

• Platform: Windows 2003 Server or 2008 Server


4 5000.1.0.0

Data Warehouse

The ZetaAnalytics product requires a compatible database appliance for its Data Warehouse. Landmark has qualified the ZetaAnalytics software using Teradata, EMC Greenplum, and IBM Netezza. Please see the ZetaAnalytics Release Notes for the most up to date qualified versions.

Before installing and configuring ZetaAnalytics software, ensure that the Data Warehouse you use for drilling data is created and running.

Scripts to create the various Zeta-specific database components within the Data Warehouse will need to be run as part of the installation process. These require database administrator (DBA) rights.

Hadoop

The ZetaAnalytics product requires Apache Hadoop for model scoring and real-time streaming.

If you do not already have an Apache Hadoop cluster installed in your environment, please install it before running the ZetaAnalytics installer, which will prompt you for the name and port number of your Hadoop Name Server and Map Reducer.

If you are installing Hadoop for use with the ZetaAnalytics product, Landmark recommends the following:

• create a network user called HADOOPUSER• do not login as root • use the Landmark Hadoop installer, ZetaAnalytics_Hadoop.bin:

this installer is not required, but it streamlines the install process for a faster installation

Example Installation Plans

Components and databases used by ZetaAnalytics are likely to be installed on different servers, though some components may be installed together on the same server. This section describes possible installation scenarios.


5000.1.0.0 5

Minimum Hardware Environment

ZetaAnalytics requires the following server resources:

• 32 – 64GB RAM • 100GB available disk spaceThe smallest hardware configuration that could support the ZetaAnalytics solution is shown below, together with the components to be installed on each machine.

Port Conflict

ZetaAnalyticsTM WITSML Services and EDM AutoSync Server use the same default port number. If you choose to install both on the same machine, you will need to assign one product a different port number.


6 5000.1.0.0

Typical Environment

A minimum hardware configuration would limit the capability of ZetaAnalytics. More typical would be a configuration with components installed on multiple servers. This would provide better performance, the ability to handle larger data volumes, more flexibility in choosing hardware and software and would support larger work groups with more varied roles and responsibilities.


5000.1.0.0 7

ZetaAnalytics services can also be installed and run on multiple servers. For example, the MMS services, FTQS services, the streaming service and the scoring engine could all run on different servers.

Landmark Software Manager

All ZetaAnalytics components are delivered via an electronic delivery system using the Landmark Software Manager (LSM) tool. Helpful LSM links can be found at:

http://css.lgc.com/InfoCenter/index?page=LSMinfo&section=linfo

These instructions assume all software component installation files are downloaded to a temporary location from the LSM in the form of zip files, where they will be unzipped.

Licensing

Landmark’s Application Manager (LAM) is the license system used to control access to Landmark applications.

Check your LAM version

ZetaAnalytics components require a current-generation LAM. If you are using a LAM version earlier than 5000.0, you must un-install the old LAM and install a current version.

ZetaAnalytics Services

FTQS MMS scoring streaming


8 5000.1.0.0

The procedures for installing the LAM client/server and server are detailed in the LAM Guide-Linux, Solaris and Windows (LAM.pdf) which can be found at the Landmark Software Manager site.

If you do not have a previous LAM server available for other Landmark applications, download and install it before installing ZetaAnalytics.

If you previously installed the LAM server for other Landmark applications, place the license.dat file in the \Landmark\LAM directory.

If there is an existing, working license.dat file, remove the file to a temporary location for safekeeping. You may need to edit the existing license file to include the new product access if your new license is not cumulative for all Landmark products. Contact your License Administrator or Landmark’s Support for assistance.

Verify or Add Product LicenseUsing a text editor, open your license.dat file and verify that the correct licenses are available. Several license types are available for specific sets of features in ZetaAnalytics:

• ZETA_DATA_ANALYSIS: Enables access to the Data Analysis components of ZetaAnalytics.

• ZETA_PREDICTIVE_ANALYSIS: Enables access to the Predictive Analytical Model Building components of ZetaAnalytics.

• ZETA_DATA_SERVICES Enables ZetaAnalytics WITSML Services, which reads real-time drilling data and feeds WellSpace (dense database) and EDM.

If the appropriate license type line is not in the file, you will need to obtain a license from Landmark and add it to your license.dat file. After changing the license.dat file, you must restart the Tomcat or JBoss service.

License Checkin and CheckoutThe ZetaAnalytics server uses licenses in three ways:

• Check – When the product starts, it checks the license server for a valid product license. A license is not yet checked out.


5000.1.0.0 9

• Checkout – When an analysis type is selected or a map function is invoked, a product license is checked out.

• Checkin – A checked out license is released when the browser closes or you click the logout icon.

Avoid License Errors

The Back and Refresh buttons in your browser may confuse ZetaAnalytics as it checks the application state and license server. Avoid using Back and Refresh as much as possible and if you encounter license errors, close and re-start the browser.


10 5000.1.0.0


5000.1.0.0 11

INSTALLATION

This chapter describes the ZetaAnalytics installation process. It explains the sequence in which ZetaAnalytics components are installed, and describes infrastructure requirements that you may need to update or configure for use with ZetaAnalytics.

Installation Workflow

This workflow installs all components on a single machine.

STEP 1: INSTALL & CONFIGURE PRE-REQUISITE SOFTWARE

STEP 2: DOWNLOAD INSTALLER

STEP 3: INSTALL

STEP 4: DATABASE SETUP

STEP 5: LDAP SECURITY CONFIGURATION

STEP 6: (OPTIONAL) SERVER INTEGRATION


12 5000.1.0.0

Step 1: Install Pre-Requisite Software

The Zeta installation process assumes the following components are correctly installed and configured:

Data WarehouseA qualified Data Warehouse such as Teradata, Greenplum, or Netezza needs to be available. Initial installation and configuration will be performed by the Data Warehouse vendor. Once up and running, a Zeta user and empty Zeta databases need to be created which will be populated with the Zeta data-model as part of the installation process.

The following users and databases must be created:

• A user called ZADMIN that has full administrator privileges for the database.

• Empty databases called:

• DENSE: This is where the high volume, high density sensor/log data from WITSML is stored. It communicates with the WellSpace service.

• FTQS: This is where contextual data from EDM or other relational databases is stored. It is also where the multi-dimensional cubes (analyses) are stored. It communicates with the FTQS and Streaming Services.

• MMS. This is where details of the Predictive Models you build are stored. It communicates with the MMS service.

• The DENSE, FTQS and MMS databases must be owned by ZADMIN.

Alternative names can be used for the user and databases but we highly recommend you use these names because they are referenced throughout the installation documentation. The process used to create users and databases is different for each qualified system. Please see documentation from the Data Warehouse vendor for detailed instructions.


5000.1.0.0 13

Zeta WITSML ServicesPlease see the Zeta WITSML installation guide for installation and configuration instructions.

EDM AutoSync ServerEDM™ AutoSync Server 5000.1.10.2 must be installed and configured for the desired EDM database. ZetaAnalytics WITSML Services synchronizes well data with EDM via AutoSync. See the EDM™ AutoSync Server Software 5000.1.10.2 Administration Guide for details of the configuration.

Users may synchronize WITSML high frequency high volume data from a WITSML Server with a qualified warehouse.

To use EDM AutoSync Server with ZetaAnalytics, you must edit a config file.

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-moduleclass="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>


14 5000.1.0.0

HadoopAt least one named-node and map-node must be configured to run the model scoring component of the Predictive Analytics module.

If you do not already have an Apache Hadoop cluster installed in your environment, please install it before running the ZetaAnalytics installer, which will prompt you for the name and port number of your Hadoop Name Server and Map Reducer.

If not already available, you will need to install Hadoop on a 64-bit Linux server for use with the ZetaAnalytics product, Landmark recommends the following:

• create a network user called HADOOPUSER• do not login as root when installing Hadoop

Step 2: Download Installer

ZetaAnalytics installation files and documentation are delivered using the Landmark Software Manager tool. The following procedure assumes that the necessary files are downloaded.

There are different installation files for Windows and Linux systems, however both installers follow the same installation workflow.

Step 3: Install

The ZetaAnalytics Server installation package installs all the software needed for the various Zeta services, database configurations, the analytic engine as the browser-based user interface.

Administrator Role

On Windows, run the ZetaAnalytics installer as Administrator. On Linux, run the installer as ‘root’.


5000.1.0.0 15

1. Open the directory where you downloaded the ZetaAnalytics Server installation files and run the file:

ZetaAnalytics.exe (Windows) orZetaAnalytics.bin (Linux)

The Introduction Screen will be displayed.

2. Click Next.


16 5000.1.0.0

The Choose Install Set screen is displayed.

3. Select whether you want the full product installed or you want to customize the install set. Choose Full Install if you plan to run all ZetaAnalytics components from a single computer. Choose Custom if you are setting up an environment with ZetaAnalytics distributed across multiple computers.

These instructions assume that all components will be installed on the same machine, so we will select the Full Install option. If you select the Custom option you will see the following screen.


5000.1.0.0 17

If you select Custom, you must choose which ZetaAnalytics components are to be installed. Components that are checked will be installed. Uncheck components to exclude them from the install.

In the Choose Install Set screen, make sure Full Install is selected, then click Next.

The Choose Install Folder screen is displayed.


18 5000.1.0.0

Landmark recommends using the default destination folder, but you can install the software in a different directory using the Choose button.


5000.1.0.0 19

4. Click Next.

The LAM Configuration screen is displayed.


20 5000.1.0.0

5. Enter the path to your local LAM License file, or the port number and hostname of your LAM Server, then click Next.

The ZetaAnalytics Wellspace Server screen is displayed.

6. Enter connection information to the database that will be used by ZetaAnalytics for the dense model data, then click Next. Incorrect connection or credential information will cause ZetaAnalytics to fail.

• The Username and Password are the credentials that ZetaAnalytics components will use to connect to the database and retrieve data.

• The Host Name can be the domain name of the database appliance, or its IP address.

• The Database Name is the name of the database to which you will write your High Density/High Volume data from your WITSML source. This was set up as part of the Data Warehouse pre-configuration and we highly recommend you use our default name of DENSE.


5000.1.0.0 21

• The Database Schema. For Greenplum and Netezza this should be ZADMIN. For Teradata this is the same as the database name (DENSE).

• Select your Database type from the drop-down menu.

The Autosync Server Connection screen is displayed.


22 5000.1.0.0

7. Enter the domain name or the IP address of the host on which AutoSync Server is running, then click Next.

The MMS Server connection screen is displayed.

Again you should point towards your Data Warehouse that you have previously pre-configured. Use the Username that you created at that stage which owns all the Zeta tables. This should be ZADMIN to avoid confusion. The database you are connecting to here is the Model Management Service (MMS) which will manage all the details of the Predictive Models that you build. The Database Schema will be ZADMIN for Greenplum and Netezza. For Teradata it is the same as the database name (MMS).


5000.1.0.0 23

8. Enter connection information to the database that will be used for the Model Management System, then click Next.

The FTQS Server connection screen is displayed.

Again you should point towards your Data Warehouse that you have previously pre-configured. Use the Username that you created at that stage which owns all the Zeta tables. This should be ZADMIN to avoid confusion. The FTQS database that you are connecting to here contains both the contextual data that comes from EDM and other databases, as well as the multi-dimensional models (Analyses). The Database Schema will be ZADMIN for Greenplum and Netezza. For Teradata it is the same as the database name (FTQS).


24 5000.1.0.0

9. Enter connection information to the database that will be used for the Fact Table (FTQS), then click Next.

The Hadoop Connection screen is displayed.

10. Enter the location of your Hadoop NameNode and the Map Reducer Node, then click Next.

The installer will look for a supported version of the Microsoft C++ Redistributable Library. If it is not found, a dialog will prompt you to install it before continuing. Installing the C++ Redistributable will not interfere with the ZetaAnalytics install process.


5000.1.0.0 25

The Apache Tomcat Service screen is displayed.

11. Enter connection information for the Apache Tomcat Server. This will be different from the Data Warehouse you have been configuring. This is the machine from which the web-services that access the Data Analysis and Predictive Analytics modules will run.

• The username and password are the administrator credentials that Tomcat will use to run the ZetaAnalytics server.

• The Apache Server IPv4 Address is the IP address of the host on which Tomcat runs.

• The connection and command ports are the port numbers on which Apache Tomcat Server is listening. By default these are 8083 for the connection port and 8006 for the command port.

When finished, click Next.


26 5000.1.0.0

The ESRI ArcGis Server screen is displayed.

12. Enter the URL to the ESRI ArcGis Server you wish to use, then click Next.

This server supports the map functions used to select wellbores by location using a map. If you check the box Do not enable ESRI ArcGis support, interactive map features will be disabled in ZetaAnalytics.


5000.1.0.0 27

The Pre-installation Summary screen is displayed.

13. Verify that the information displayed on this screen is accurate, then click Install.

Status messages show the components currently being installed and progress bars show the relative progress of each install step.

14. When the Landmark ZetaAnalytics Server installer completes its installation, click Done.

If errors occurred during the install process, a message will appear in the Install Complete screen. Examine the log file for details. See “Troubleshooting” on page 69.


28 5000.1.0.0

Step 4: Database Setup

After the ZetaAnalytics Server installation is complete a couple of jobs will need to be run from the Zeta ETL application. These jobs will first populate the empty warehouse databases with the Zeta Data Model tables, and then push the initial data into these tables. See “Database Setup” on page 41.

Step 5: LDAP Security Configuration

Before you can start the ZetaAnalytics user interface, you must configure LDAP server information. See “LDAP Security” on page 55.

Step 6: Server Integration

If you are installing ZetaAnalytics in a distributed environment with product components running on separate servers, you must edit XML configuration files to define how the server processes will communicate (IP addresses, port numbers, instances, credentials, etc.). See “Component Integration” on page 57.


5000.1.0.0 29

Un-Configured Install Workflow

You can install ZetaAnalytics as a multi-tier application with each component running on a dedicated server.

For example, you may want some common services installed on the ZetaAnalytics Server machine, but want the FTQS, MMS, Scoring and Streaming services to run on their own servers for performance reasons.

The diagram below shows one possible configuration. It is not the only solution. You could choose to run two services on one machine. You could choose to move additional services off the ZetaAnalytics Server machine.

ZetaAnalytics Server

PROCESSES ON THIS SERVER• Apache Tomcat “LGC-TOMCAT”• LGC ActiveMQ Server• LGC ZetaAnalytics Service Server• LGC Wellspace• LGC Simulator Server Service

FTQS Server

PROCESSES ON THIS SERVER• LGC Fact Table Query Service

Scoring Server

PROCESSES ON THIS SERVER• LGC Scoring Service

MMS Server

PROCESSES ON THIS SERVER• LGC MMS Service

Streaming Server

PROCESSES ON THIS SERVER• LGC Streaming Service

optio

nal

optio

nal


30 5000.1.0.0

This workflow installs components on two or more machines.

Step 1: Setup ZetaAnalytics Server Machine1. Install and configure pre-requisite hardware and software. This

includes infrastructure such as the Teradata Database and Hadoop as well as Landmark components such as ZetaAnalytics WITSML Services and AutoSync Server.

STEP 1: SETUP ZETAANALYTICS SERVER MACHINE

STEP 2: RUN INSTALL ON COMPONENT SERVER MACHINES

STEP 3: EDIT SERVER CONFIGURATION FILES ON EACH COMPONENT SERVER MACHINE

STEP 4: EDIT SERVER CONFIGURATION FILES ON ZETAANALYTICS SERVER MACHINE


5000.1.0.0 31

2. Follow the first three steps in the configured installation workflow (See “Installation Workflow” on page 11.) Stop when you reach the install screen that asks which type of install you want to do.

3. Choose Unconfigured, then click Next.

The Unconfigured option sets up only the web server (Apache Tomcat) and ESRI ArcGis infrastructure.

4. Continue working through the Install screens for Tomcat and ESRI, confirm information on the Installation Summary screen and Finish the install.

5. Configure security on the ZetaAnalytics server machine. See “Step 5: LDAP Security Configuration” on page 28.


32 5000.1.0.0

Step 2: Run Install on Component Server Machines1. Log on to the component server machine.

2. Follow the first three steps in the configured installation workflow (See “Installation Workflow” on page 11.) Stop when you reach the install screen that asks which type of install you want to do.

3. Choose Unconfigured, then click Next.

The Unconfigured option sets up only the web server (Apache Tomcat) and ESRI ArcGis infrastructure.

4. Work through the Install screen for Tomcat as in the configured.

5. On the ESRI ArcGIS screen, select the checkbox Do Not Enable ESRI ArcGIS Support.

6. Confirm information on the Installation Summary screen and Finish the install.


5000.1.0.0 33

Step 3: Edit Server Configuration Files on Each Component Server Machine

Each component service has a bin folder that contains a batch script that sets variables and a batch script to start services. Run the appropriate scripts for the server type you want hosted on a machine.

1. Run the server install script.

2. Start a text editor (such as Notepad) and open the script that will start the service. Change any path information that may be unique for your system.

FTQS Path: Landmark\ZetaAnalytics\ftqs\binScript: InstallFactTableQueryService.bat

MMS Path: Landmark\ZetaAnalytics\mms\binScript: install_mms.bat

Scoring Path: Landmark\ZetaAnalytics\scoring\binScript: install_scoring.bat

Simulator Path: Landmark\ZetaAnalytics\Simulator\binScript: InstallSimulatorService.bat

Streaming Path: Landmark\ZetaAnalytics\streaming_service\binScript: InstallStreamingService.bat

Wellspace Path: Landmark\ZetaAnalytics\Wellspace\binScript: InstallWellSpace.bat

ZetaAnalytics Path: Landmark\ZetaAnalytics\zetaanalytics_service\binScript: InstallZetaAnalyticsService.bat

FTQS Path: Landmark\ZetaAnalytics\ftqs\binScript: InstallFactTableQueryService.bat

MMS Path: Landmark\ZetaAnalytics\mms\binScript: mms.bat

Scoring Path: Landmark\ZetaAnalytics\scoring\binScript: mms.bat

Simulator Path: Landmark\ZetaAnalytics\Simulator\binScript: SimulatorService_Server.bat

Streaming Path: Landmark\ZetaAnalytics\streaming_service\binScript: streaming_service.bat

Wellspace Path: Landmark\ZetaAnalytics\Wellspace\binScript: wellspace_server.bat

ZetaAnalytics Path: Landmark\ZetaAnalytics\zetaanalytics_service\binScript: ZetaAnalyticsService_Server.bat


34 5000.1.0.0

3. Edit XML configuration files for the appropriate service(s). See “Server configuration” on page 55.

4. Run the file to start the appropriate service.

Step 4: Edit Server Configuration Files on ZetaAnalytics Server MachineIP addresses, port numbers and other information needed to establish communication between servers is defined on the ZetaAnalytics server machine. See “Server configuration” on page 55.

1. On the ZetaAnalytics server, edit two files to add IP addresses, database names and any other information needed for the application:

• Landmark\ZetaAnalytics\zetaanalytics_service\config\ zeta_analytics.xml

• Landmark\ZetaAnalytics\apache-tomcat-6.0.35\ webapps\zeta\resources\scripts\app-conf

2. Start the Apache Tomcat service.

FTQS Path: Landmark\ZetaAnalytics\ftqs\configConfig Files: ftqs.xml, hibernate.cfg.xml

MMS Path: Landmark\ZetaAnalytics\mms\configScript: mms.xml, hibernate.cfg.xml

Scoring Path: Landmark\ZetaAnalytics\scoring\configScript: hadoop.properties

Simulator Path: Landmark\ZetaAnalytics\Simulator\configScript: simulator.xml, hibernate.cfg.xml

Streaming Path: Landmark\ZetaAnalytics\streaming_service\configScript: streaming.xml, hibernate.cfg.xml

Wellspace Path: Landmark\ZetaAnalytics\Wellspace\configScript: wellspace.xml, denseModelHibernate.cfg.xml

ZetaAnalytics Path: Landmark\ZetaAnalytics\zetaanalytics_service\configScript: zeta_analytics.xml, hibernate.cfg.xml


5000.1.0.0 35

Starting ZetaAnalytics

To launch the ZetaAnalytics product interface:

1. Open a supported web browser.

2. Enter the full URL to the ZetaAnalytics interface on the server where the produce was installed. This may take a form such as the following:

http://localhost:8083/zeta

http://278.123.72.137:8083/zeta

3. Enter your network user name and password, then click Login.

The ZetaAnalytics home page is displayed. This page lets you choose which module you want to use. Hover over an icon to see which module will be launched. Click to launch the module. Click the Help link at the bottom of the screen to see information about


36 5000.1.0.0

each module. The Predictive Analysis features are available only if a license for the feature has been purchased and installed.

Uninstalling ZetaAnalytics Software

To remove ZetaAnalytics software from the computer:

1. Navigate to the folder containing the uninstaller program. By default, this is: /Program Files/Landmark/ZetaAnalytics/Uninstall_Landmark ZetaAnalytics

2. Run Uninstall Landmark ZetaAnalytics.

The Uninstall Options screen is displayed. If you setup your environment to run components on different machines, you can select Uninstall Specific Features to select only those components to be removed.


5000.1.0.0 37

3. Select Complete Uninstall to remove all installed components, then click Next.

You will be asked whether you wish to keep backup copies of your configuration files.

4. If you want to keep backups, either accept the default location or specify a directory path, then click Uninstall.

Note: Most ZetaAnalytics data files are stored in the data warehouse, but the Model Management System (MMS) stores some data on your host machine. This is what is being retained in the backups. Make a note of the location of your backup


38 5000.1.0.0

directory, you will need it to restore your MMS after a subsequent re-installation.

The uninstaller will remove files and registry keys installed for ZetaAnalytics. Some files or folders will not be removed.

5. When you are prompted to restart the computer, choose Yes.

6. Click Done to close the uninstall program.

The uninstall program will wait 2 minutes before restarting the computer. Use this time to close any open applications.

7. Remove the ZetaAnalytics folder from the installation directory, as well as any subfolders that remain. By default, this is:/Program Files/Landmark/ZetaAnalytics

Restoring the MMS from Backup when Re-InstallingIf you selected the option to backup settings when you uninstalled the ZetaAnalytics software, you can restore your MMS from the backup directory.


5000.1.0.0 39

1. Re-install the ZetaAnalytics software by running the installation program as usual.

2. After the software is successfully installed, go to your backup directory location.

3. Locate the data subfolder.

4. Copy the entire data folder.

5. Navigate to the mms folder in the ZetaAnalytics installation. This is typically:C:\Program Files\Landmark\ZetaAnalytics\mms\

6. Paste the data folder, replacing the default folder.


40 5000.1.0.0


5000.1.0.0 41

DATABASE SETUP

The ZetaAnalytics data model comprises five component databases, each of which is optimized for storing different types of data. Drivers for your data warehouse must be installed in the ZetaAnalytics installation directories and three ETL scripts must be run: one to create the databases, one to setup the schemas and configure the data model, and one to populate the contextual data tables.

Database Setup Workflow

Setup the databases in the following order:

STEP 1: INSTALL DATABASE DRIVERS

STEP 2: RUN SCRIPTS TO CREATE DATABASES AND SCHEMAS

STEP 3: SETUP AND RUN PIPELINE IN ZETA WITSML SERVICES

STEP 4: RUN DEFAULT JOB SCRIPT


42 5000.1.0.0

Step 1: Install Database Drivers

Before you can connect to a database that provides source data to ZetaAnalytics, you must install a driver appropriate to your data warehouse platform. Your database administrator should identify and provide the correct driver. The database driver is a JAR file specific to your data warehouse so there are different drivers for Teradata, Netezza and Greenplum (which uses a Postgres-SQL driver).

Copy the database driver JAR files to the following 9 folders:

C:\Program Files\Landmark\ZetaAnalytics\apache-tomcat-6.0.35\endorsed\

C:\Program Files\Landmark\ZetaAnalytics\ETL\data-integration\libext\JDBC\

C:\Program Files\Landmark\ZetaAnalytics\ftqs\lib\tools\

C:\Program Files\Landmark\ZetaAnalytics\mms\lib\tools\

C:\Program Files\Landmark\ZetaAnalytics\scoring\lib\tools\

C:\Program Files\Landmark\ZetaAnalytics\Simulator\lib\tools\

C:\Program Files\Landmark\ZetaAnalytics\streaming_service\

C:\Program Files\Landmark\ZetaAnalytics\Wellspace\lib\tools\

C:\Program Files\Landmark\ZetaAnalytics\ zetaanalytics_service\lib\tools\

Step 2: Create Databases

The ZetaAnalytics data model comprises five separate component databases, each of which is optimized for storing different types of data.

The five databases are:

• DENSE_SOURCE: This is where the high volume, high density sensor/log data from WITSML is stored.


5000.1.0.0 43

• EDM_SOURCE: This is where low-volume low-density data is stored. It is typically an Oracle database.

• MMS_SOURCE. This is where details of the Predictive Models you build are stored.

• SYSTEM_SOURCE: This is used to create or drop databases and perform user grants. It connects to the data warehouse with elevated rights (such as System or Super User) so it can create users, groups or databases.

• ZA_SOURCE: This points to the FTQS data cube, which is where contextual data from EDM or other relational databases is stored. It is also where the multi-dimensional cubes (analyses) are stored.

By default, EDM_SOURCE points to Oracle and other sources point to Netezza. The data sources must be verified, edited and shared before you do other database setup tasks. They must be owned by the ZADMIN user who has full database administrative privileges.

To create and prepare the databases for ZetaAnalytics, you will:

1. Grant rights to EDM data sources in Oracle.

2. Edit Database connections for each data source.

3. Run the database creation job.

4. Run the default schema creation job.

5. Run the ZA default job.

These steps are described in the following sections.

Grant rights to EDM data source in Oracle

1. Start the Oracle Enterprise Manager Console.

2. Log in as SYSDBA to the database that hosts the EDM source data (and that you will will use to store ZetaAnalytics tables).

3. Create user credentials for a new user named “zadmin”.

The zadmin username will be for the ZetaAnalytics application to use when accessing source data in the EDM database, and to


44 5000.1.0.0

create tables, sessions, triggers, procedures and similar database objects. The SQL commands to create a zadmin user with the appropriate grants are shown here.

4. Verify that the user is created with the appropriate grants.

Edit Database connections for each data source

1. On the server where you installed ZetaAnalytics, navigate to: C:\Program Files\Landmark\ZetaAnalytics\ETL\data-integration\

2. Open Spoon.bat.

The Zeta ETL Tool will open.

3. From the File menu, select Open and navigate to: Landmark\ZetaAnalytics\ETL Scripts\

connect system/Landmark1@HT97W2WK8create user zadmin identified by zadmin;alter user zadmin

default tablespace USERStemporary tablespace TEMPquota 0 on systemquota unlimited on TEMPquota unlimited on USERSquota unlimited on EDMDATA1quota unlimited on EDMDATA2quota unlimited on EDMDATA3quota unlimited on EDMDATA4quota unlimited on EDMIDX1 quota unlimited on EDMIDX2quota unlimited on EDMIDX3quota unlimited on EDMIDX4;

grant create session, create table, create synonym, create public synonym, create view, create sequence, create trigger, create procedure, dba to zadmin;GRANT "EDMROLE" to zadmin;ALTER USER zadmin DEFAULT ROLE ALL;

insert into MD_SITE_USER (USER_ID, GROUP_ID, USER_NAME, SECURITY_LEVEL, US-ER_OR_GROUP)select ((’U’||trim(to_char(user_sequence.nextval, ’0009’)))),MD_SITE_USER.USER_ID, ’zadmin’, ’10’, ’U’from MD_SITE_USERwhere MD_SITE_USER.USER_NAME = ’PUBLICUSERS’;

commit;


5000.1.0.0 45

4. Select the database creation script (ZA_database_creation_job-) corresponding to your Data Warehouse (Greenplum, Netezza or Teradata), then click Open:

5. Change or verify your database connection settings:

• In the Explorer panel, expand the Database connections folder.


46 5000.1.0.0

• Edit the connection information for each data source. Right-click a database icon and select Edit.

In the Database Connection panel, change the Host Name to point to your data warehouse (the IP address where Netezza, Teradata or Greenplum is installed). Change the Connection Type if you are not using Netezza. Verify that all other fields are correct and change if needed.


5000.1.0.0 47

• Click Test to verify that a connection can be established to your database. If errors occur, correct your settings

• Once the Test is successful, go to the Explorer panel, right-click the DENSE_SOURCE folder and choose Share. When the database connections are shared, their names appear in bold.

• Edit, verify, test and share database connections for all five of the data sources used by ZetaAnalytics.


48 5000.1.0.0

Run the database creation job

1. Once the Database connections are correctly defined and the Test is successful, close the Database connection dialog. If you installed ZetaAnalytics using the default settings and folder location, run the ZA_database_creation_job by clicking on the green “Run this job” icon in the menu bar.

This script will create the tables needed for the dense model.

2. If you did not install ZetaAnalytics using the default folder location, you must set the folder location before running the database creation job.

Right-click the Set Folder Location icon and select Edit Job Entry. In the Variables panel, click the Value next to FOLDER_DB and set it to the installation folder you used. Click OK, then run the job.


5000.1.0.0 49

3. If you did not install ZetaAnalytics using the default ZADMIN database user name and the default database schema names (DENSE, MMS and FTQS), then you must modify the CreateDB script for your database type.

• From the File menu in Spoon, select Open and select the CreateDB script for your : Landmark\ZetaAnalytics\ETL Scripts\DATABASE\Create-DB <Greenplum | Netezza | Teradata>

• For each connection, change the <name>, <username> and <password> values.

• Save your changes, then run the CreateDB script.

• close any open ETL scripts

Run the schema creation job

1. Once the databases are created, open the schema creation job (ZA_All_default_schema_creation_job) that corresponds to your data warehouse (Netezza, Greenplum or Teradata).

2. Run the schema creation job.

This script will create the necessary schemas for the dense model, MMS and FTQS.


50 5000.1.0.0

Step 3: Setup and Run Pipeline in ZetaAnalytics WITSML Services

Steps 1 and 2 created your database structures in the data warehouse, but they are not yet populated with any data. Drilling data is written to your dense database by the ZetaAnalytics WITSML Services. This step will probably be done on a different machine than your ZetaAnalytics server (the ZetaAnalytics and ZetaAnalytics WITSML Services products also require different web browsers).

The following high-level workflow describes how to setup and run a pipeline. Detailed information about each of these steps is available in the Help for ZetaAnalytics WITSML Services.

1. Start Internet Explorer 8 and launch the ZetaAnalytics WITSML Services product interface (http://localhost:8080/openwire).

2. Set the connection to the provider (WITSML source).

From the navigation panel (left), expand Provider Connections and select All Provider Connections.

Click New to define the new source. Enter a name, the URL of the provider service, the WITSML verion being used by the provider, and any authentication credentials that the provider may require.

Click Test Connection to verify that the connection parameters are correct. Click OK to close the dialog.

3. Set the Database Connection parameters to point to the target data warehouse for your dense database and to the EDM for your contextual data.

From the navigation panel (left), expand Database Connections and select All Database Connections.

Click New and set the connection to your data warehouse. Specify user name and password credentials to the EDM database.


5000.1.0.0 51

Click Test Connection to verify that the database can be reached. Click Close if the connection test is successful.

4. From the navigation panel (left), expand Admin Utility and select ZetaAnalytics WITSML Services Settings.

You will probably want to check Append Log Curves (click ? to read the Help).

Verify the connector address and click Test Connection. Click Close when the test is successful.

5. Create the pipeline. From the navigation panel (left), expand Pipelines and click the New icon. This starts a New Pipeline Wizard which walks you through the process of naming and defining the pipeline.


52 5000.1.0.0

6. Define which data types are to be moved through your pipeline. This process is called “mapping the log curves” in ZetaAnalytics WITSML Services.

From the navigation panel, expand Pipelines and select All Pipelines, click the name of the pipeline you created in the previous step, then click the Add Mapping button to start mapping your log curves.

See the Help for complete information about Mapping Logs to the Warehouse. Mapping the curves can be a complex process that includes the following steps:


5000.1.0.0 53

7. Start the pipeline. For real-time updates, you will also want to set a schedule. Click the Update Interval button ( )to schedule a recurring transfer.

Step 4: Run Default Job Script

1. On the server where you installed ZetaAnalytics, navigate to: Landmark\ZetaAnalytics\ETL\data-integration\

2. Open Spoon.bat.

The Zeta ETL Tool will open.

3. From the File menu, select Open and select: Landmark\ZetaAnalytics\ETL Scripts\ZA_default_job.kjb

4. Verify that your database connections are still correctly configured.

5. Run the job by clicking on the green “Run this job” icon in the menu bar.


54 5000.1.0.0

6. If you want to update this data regularly click the START icon and chose the pencil icon to open the Job Scheduling dialog:

7. From the Type pull-down, select your update frequency.

8. Set the interval, time or day values, then click OK.


5000.1.0.0 55

SERVER CONFIGURATION

ZetaAnalytics stores configuration information in XML files. Because the product can be distributed across multiple servers, each component has its own set of XML configuration files.

You may want to edit XML configuration files in 4 situations:

• Initial installation: After running the install program, edit the LDAP security configuration (See “LDAP Security” on page 55.)

• Component integration: Edit these files any time you change server names, database names, port numbers, usernames or passwords. You will also need to edit these files when installing on more than one server. (See “Component Integration” on page 57.)

• Performance: Java configuration settings can be tuned to optimize performance. (See “Performance Tuning” on page 66.)

• ESRI maps: Change the default ESRI map server. (See “Change ESRI Map Server” on page 67.)

LDAP Security

ZetaAnalytics supports LDAP security. Before you can log on to use the product, you must edit an XML file to configure the LDAP security settings.

To configure LDAP:

1. Navigate to the directory: \Program Files\Landmark\ ZetaAnalytics\apache-tomcat-6.0.35\webapps\zeta\ WEB-INF\

2. Edit the file: application-ldap-security.xml


56 5000.1.0.0

3. Find the string “searchbase”. Replace each occurrence with a domain component for your LDAP server hostname. For example, replace “searchbase1” with “secserver”, “searchbase2” with “megaoil” and “searchbase3” with “com”. Repeat this process to find and replace the second set of searchbase strings.

4. Find the constructor line for the LDAP server. Replace this with the URL used by your LDAP server. For example:<beans:constructor-arg value=”ldap:secserver.megaoil.com:389” \>

5. Type your user name in the userDn property.

6. Type your password in the password property.

7. Find the constructor line that contains your group role attribute definitions (OU=value). Add your user groups to this line. Also add your domain components.

8. Save the file then restart the web server service.

<beans:bean id=”contextSource”class=”org.springframeworkd.security.dap.DefaultSpringSecurityContextSoure”><beans:constructor-arg value=”ldap://top.domain.com:389” /><beans:property name=”userDn” value=”[email protected]” /><beans:property name=”password” value=”pass1234” /></beans:bean>


5000.1.0.0 57

Component Integration

Settings needed for components to communicate include:

• login credentials• database names• server IP addresses • port numbers XML configuration files are created during installation, but may need periodic updates if you move servers, encounter port conflicts, change user names or passwords or make database updates. Configuration files include:

FTQS:- ftqs.xml- hibernate.cfg

MMS: - mms.xml- hibernate.cfg

Scoring:- hadoop.properties

Simulator:- simulator.xml

Streaming:- service_registry.xml- streaming.xml- hibernate.cfg

Wellspace:- wellspace.xml- denseModelHibernate.cfg

zetaanalytics_service:- zeta_analytics.xml

Mondrian:- web.xml


58 5000.1.0.0

Use a text editor, such as Notepad, to open the configuration files shown in this section, make changes to specify your configuration, then save with the original file name in the original location.

After editing a configuration file, restart the Apache Tomcat or JBoss service. (This will have a name like Apache Tomcat “LGC-TOMCAT”).

FTQS: Fact Table Query ServiceTwo files may need to be edited to maintain FTQS connectivity:

Location: Landmark\ZetaAnalytics\ftqs\config\

• ftqs.xml

• hibernate.cfg

ftqs.xml

Edit this file if you need to change:

• Port number used by the FTQS Service (change this to resolve port conflicts). Look for the line:

• Active MQ connection information including IP address and port number (change this if you run Active MQ on a different server than FTQS). Look for the line:

Backup Config Files

Before editing an XML configuration file, always store a backup copy in a secure location so you can restore a correct working copy.

<portNumber>8183</portNumber>

<activeMqURL>tcp://34.238.62.239:61616</activeMqURL>


5000.1.0.0 59

hibernate.cfg


• Username and password credentials for the Teradata database

• Name of the Teradata database table used for FTQS

• Port number or IP address of the Teradata database server

MMS: Model Management ServiceTwo files may need to be edited to maintain MMS connectivity:

Location: Landmark\ZetaAnalytics\mms\config\

• mms.xml

• hibernate.cfg

ftqs.xml


Port Changes

If you change port numbers in any XML configuration file, you must also change it in zeta_analytics.xml

<property name="hibernate.connection.username">dbc</property><property name="hibernate.connection.password">dbc</property>

<property name="hibernate.default_schema">DB07</property><property name="hibernate.connection.url">jdbc:teradata://387.103.72.137/PORT=1025,DATABASE=DB07</property>

<property name="hibernate.default_schema">DB07</property><property name="hibernate.connection.url">jdbc:teradata://387.103.72.137/PORT=1025,DATABASE=DB07</property>


60 5000.1.0.0

• Port number used by the MMS Service (change this to resolve port conflicts). Look for the line:

hibernate.cfg



• Name of the Teradata database table used for MMS


ScoringThe Model Scoring service uses an Apache Hadoop network. Hadoop has one configuration file that stores its connection details.

Location: Landmark\ZetaAnalytics\scoring\config\

• hadoop.properties

hadoop.properties

Edit the hadoop.properties file if you need to change:



<property name="hibernate.default_schema">MMS_DB</property><property name="hibernate.connection.url">jdbc:teradata://387.103.72.137/PORT=1025,DATABASE=MMS_DB</property>

<property name="hibernate.default_schema">MMS_DB</property><property name="hibernate.connection.url">jdbc:teradata://387.103.72.137/PORT=1025,DATABASE=MMS_DB</property>


5000.1.0.0 61

• Name or port number of the Hadoop Node Server

• Name or port number of the Hadoop Map Reducer

SimulatorOne file may need to be edited to maintain Simulator connectivity:

Location: Landmark\ZetaAnalytics\simulator\config\

• simulator.xml

simulator.xml


• The port number used by the Simulator service

StreamingThree files may need to be edited to maintain Streaming service connectivity:

Location: Landmark\ZetaAnalytics\streaming_service\config\

• service_registry.xml

scoring.output.path=hdfs://wks302262:5380/root/apachehadoopinstall/scoringhd.fs=hdfs://wks302262:5380mapred.job.tracker=wks302262:5381scoring.input.path=input

scoring.output.path=hdfs://wks302262:5380/root/apachehadoopinstall/scoringhd.fs=hdfs://wks302262:5380mapred.job.tracker=wks302262:5381scoring.input.path=input



62 5000.1.0.0

• streaming.xml

• hibernate.cfg

service_registry.xml


• The port numbers used by the Wellspace and/or FTQS service or the IP addresses if you want to split them to run on different servers

streaming.xml


• The port number used by the Streaming service

• The switch that tells ZetaAnalytics to use or not use Hadoop. Hadoop is used for scoring and streaming so it should always be enabled if you are using all product functionality. The only time it makes sense to set the switch to FALSE is if you you are using a Visual-only product license for ZetaAnalytics.

hibernate.cfg



service.WELLSPACE=http://34.238.62.239:8182service.FTQS_SERVICE=http://34.238.62.239:8183


<use-hadoop>true</use-hadoop>



5000.1.0.0 63

• Name of the Teradata database table used for the dense model data


WellspaceTwo files may need to be edited to maintain Wellspace connectivity:

Location: Landmark\ZetaAnalytics\wellspace\config\

• wellspace.xml

• hibernate.cfg

wellspace.xml


• RMI port number (change only to resolve port conflicts). Look for the lines:

• Port number used by the Wellspace Service (change this to resolve port conflicts). Look for the line:

<property name="hibernate.default_schema">DM_DB</property><property name="hibernate.connection.url">jdbc:teradata://387.103.72.137/PORT=1025,DATABASE=DM_DB</property>


<rmi><address>localhost</address><portNumber>1085</portNumber><runLocalRmiRegistry>true</runLocalRmiRegistry>

</rmi>



64 5000.1.0.0

• The location or port number of the AutoSync Server. Look for the lines:

• The cleanup schedule for when ZetaAnalytics deletes orphan records from the database tables. Look for the lines:

denseModelHibernate.cfg



• Name of the Teradata database table storing the dense model data

<autsoync-connections><connection serviceName="AutoSyncServerService"address="134.132.121.107" port="1094"default="true" />

</autsoync-connections>

<orphan-data-cleanup><weekly-event>

<time><hours>03</hours><minutes>15</minutes><seconds>00</seconds>

</time>

<day-of-week>MONDAY</day-of-week><day-of-week>TUESDAY</day-of-week><day-of-week>WEDNESDAY</day-of-week><day-of-week>THURSDAY</day-of-week><day-of-week>FRIDAY</day-of-week><day-of-week>SATURDAY</day-of-week><day-of-week>SUNDAY</day-of-week></weekly-event></orphan-data-cleanup>

Time of day to run cleanup (03:15am)




5000.1.0.0 65


zetaanalytics_serviceOne file may need to be edited to maintain connectivity for the ZetaAnalytis service:

Location: Landmark\ZetaAnalytics\zetaanalytics_service\config\

• zeta_analytics.xml

zeta_analytics.xml


• The port number used by the ZetaAnalytics service

• Port numbers or IP addresses used by any other product component (FTQS, MMS, Simulator service, Scoring service, or Active MQ). If you changed port numbers or IP addresses in another XML configuration file, you must also make the identical change in zeta_analytics.xml.

Search for a second occurrence of any changed IP address or port number. There should be a second occurrence in a <redirectgroup> tag.




66 5000.1.0.0

Performance Tuning

ZetaAnalytics services each have a wrapper.xml file in their respective \conf\ directories.

Edit the wrapper.xml if you are tuning the application to improve performance. You can set two memory parameters:

• Initial Java heap size• Maximum Java heap size

<redirectgroup targetbase="http://34.238.62.239:8179">

<redirectgroup targetbase="http://34.238.62.239:8180">

<config-module class="com.lgc.zeta.server.restlet.ServiceLocatorSettings"><rest>

<ftqsURL>http://34.238.62.239:8183</ftqsURL><mmsURL>http://34.238.62.239:8179</mmsURL><simulatorURL>http://34.238.62.239:8180</simulatorURL><scoringURL>http://34.238.62.239:3000</scoringURL><activeMqURL>tcp://34.238.62.239:61616</activeMqURL>

</rest></config-module>

# Initial Java Heap Size (in MB)wrapper.java.initmemory=256

# Maximum Java Heap Size (in MB)wrapper.java.maxmemory=1024


5000.1.0.0 67

Change ESRI Map Server

If you want to change your ESRI map server, edit one file.

Location: Landmark\ZetaAnalytics\apache-tomcat-6.0.35\webapps\zeta\ resources\scripts\

• app-config.js

Edit the file to:

• Specify the default ArcGIS Server map service for the site collection

• Set the targetselectionBasemap_Config value to the REST URL of the map service you wish to use

• Set a switch to enable or disable the ESRI map functions

var homepageBasemap_Config = "http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer";

var targetselectionBasemap_Config = "http://server.arcgisonline.com/ ArcGIS/rest/services/World_Topo_Map/MapServer";

var isESRISEnabled = true;


68 5000.1.0.0


5000.1.0.0 69

TROUBLESHOOTING

This section explains common problems and solutions.

Installer Errors

Look at any messages that appear when the Install completes. If errors occur, the completion message will look like this.

Examine the log files to determine the cause of the error.

Log Files

There are two types of log files:

• installation logs• run-time logs


70 5000.1.0.0

Installations Logs

Logs are created when the product is installed.

The main log file for installation logging is:Landmark_ZetaAnalytics_InstallLog

The main install log is useful for high-level troubleshooting. It shows all of the configuration inputs you specified during product installation, files installed, summary statistics, and success/fail messages.

Additional logs for specific services include:

• ActiveMQ_service_install• FTQS_service_install• LGC_Scoring_Server_service_install• LGC_ZetaAnalytics_Service_Server_service_install• MMS_service_install• Simulator_service_install• streaming_service_service_install• Tomcat_service_install• WellSpace_service_install


5000.1.0.0 71

Run-time logs

Run-time logs are available for ZetaAnalytics components. Look in these directories for log files:

• Landmark\ZetaAnalytics\curation\logs\• Landmark\ZetaAnalytics\ftqs\logs\• Landmark\ZetaAnalytics\mms\logs\• Landmark\ZetaAnalytics\scoring\logs\• Landmark\ZetaAnalytics\Simulator\logs\• Landmark\ZetaAnalytics\streaming_service\logs\• Landmark\ZetaAnalytics\Wellspace\logs\• Landmark\ZetaAnalytics\zetaanalytics_service\logs\

Port Conflicts

TCP ports are used for component processes to communicate. Errors may indicate a conflict between ZetaAnalytics and other software on your system.

The following table lists port numbers used by ZetaAnalytics components, and the configuration files you may need to edit to resolve conflicts.

Port Purpose In config file...

1025 Teradata database listener port Landmark\ZetaAnalytics\ftqs\config\hibernate.cfg.xml

Landmark\ZetaAnalytics\mms\config\hibernate.cfg.xml

Landmark\ZetaAnalytics\streaming_service\config\hibernate.cfg.xml

Landmark\ZetaAnalytics\wellspace\config\hibernate.cfg.xml

1085 RMI port: communication with ZetaAnalytics WITSML Services

Landmark\ZetaAnalytics\wellspace\config\wellspace.xml

1094 Autosync connection Landmark\ZetaAnalytics\wellspace\config\wellspace.xml


72 5000.1.0.0

Data Display Problems

Problem

When data are not displayed as expected, it can indicate a connection error between software components or to a required database.

8179 MMS server Landmark\ZetaAnalytics\curation\config\curation.xml

Landmark\ZetaAnalytics\mms\config\mms.xml

Landmark\ZetaAnalytics\zetaanalytics_service\config\zeta_analytics.xml

8180 Simulator server Landmark\ZetaAnalytics\curation\config\curation.xml

Landmark\ZetaAnalytics\Simulator\config\simulator.xml


8182 Curation server Landmark\ZetaAnalytics\curation\config\config.xml

Landmark\ZetaAnalytics\wellspace\config\wellspace.xml

8183 FTQS: Fact table query service Landmark\ZetaAnalytics\ftqs\config\ftqs.xml


8184 ZetaAnalytics server Landmark\ZetaAnalytics\zetaanalytics_service\config\zeta_analytics.xml

8185 Streaming service Landmark\ZetaAnalytics\streaming_service\config\streaming.xml

61616 ActiveMQ transport connector for ZetaAnalytics WITSML Server

Landmark\ZetaAnalytics\apache-activemq-5.6.0\conf\activemq.xml

Landmark\ZetaAnalytics\ftqs\config\ftqs.xml


Port Purpose In config file...


5000.1.0.0 73

Solution

Check for:

• port conflicts• user name / password validation changes (expired credentials)• unavailable databases

Symptom: Unavailable database

Solution: Verify Database Names

Most often, the FTQS or MMS database is incorrectly specified in an XML configuration file. See “Server configuration” on page 55.


74 5000.1.0.0

Web Server Unavailable

Problem

Configuration changes require restarting the Tomcat or JBoss service (or specific component services). Occasionally, after restarting services, the application may become unavailable.

Solution

Check any configuration file changes you made. Verify that servers, port numbers, databases, and username and passwords were entered correctly.

Streaming or Scoring Job Status

If response time is unexpectedly slow (or stopped) for either streamed real-time data or for model scoring jobs, you can check the status of the Hadoop server. Status reports are available using a URL such as:

http://wkss030221:53030/jobtracker.jsp

Hadoop name serverHadoop name server listener port


5000.1.0.0 75

Restarting Services

Problems may occasionally occur because required services have stopped or did not restart correctly. This can occur when configuration files are modified. Use the Services administration tool to check the status of services.

Normally, only one service needs to be restarted:Apache Tomcat “LGC-TOMCAT”

If restarting Apache Tomcat “LGC-TOMCAT” does not also restart all other LGC services, you may need to restart the individually. The preferred order for restarting services is:

1. LGC Fact Table Query Service

2. LGC MMS Server

3. LGC Simulator Service Server

4. LGC Wellspace

5. LGC Scoring Server

6. LGC Streaming Service

7. LGC ZetaAnalytics Service Server

8. LGC ActiveMQ Server

9. Apache Tomcat “LGC-TOMCAT”


76 5000.1.0.0


5000.1.0.0 77

APPENDIX: TERADATAADMINISTRATION

Teradata Client

The ZetaAnalytics product requires a Teradata database to be installed and configured. The FTQS, MMS and Dense Model tables used by ZetaAnalytics are stored in the Teradata database.

Teradata databases are administered using a client downloaded from Teradata as part of the Teradata Tools and Utilities package.

Download and install Teradata Tools and Utilities from the Teradata web site.

Specify ODBC Driver

The Teradata Tools and Utilities contains the correct ODBC driver that ZetaAnalytics will use to talk to the database. There may also be dependencies for the ODBC driver and specific installation or configuration steps that are explained in the ODBC Software Installation documentation provided by Teradata.

DBA

This section assumes the Teradata Database will be set up by a skilled database administrator who has been assigned the Teradata Administrator role. This section is not a substitute for training and documentation on Teradata administration.

The DBA may want to grant rights to create, modify and drop database objects to a power user familiar with the real-time drilling data.


78 5000.1.0.0

Verify that the ODBC driver for Teradata is installed correctly.

1. Start Teradata Administrator.

2. Click the User DSN tab. If you have been working with Teradata, the drivers are likely already installed and in use for existing data.

If Teradata drivers are already installed and in use, skip the rest of this task and create the database for ZetaAnalytics.

3. If the Teradata driver does not appear in the list on the User DSN tab, click the Drivers tab. If the driver has been installed but not yet used, it will appear in the list. If it is there, skip the rest of this task and create the database for ZetaAnalytics.

4. Download and install the Teradata ODBC driver from the Teradata web site.

Teradata drivers are already installed


5000.1.0.0 79

5. Click the User DSN tab, then click the Add button.

6. Select Teradata from the Name pane, then click Finish.

7. Choose the database that you created for the ZetaAnalytics analytical data source tables. Select the All Databases & Users radio button, then click OK.

Create a User and Database for the Analytic Data Source Tables

The Teradata Administrator must create a user who will own the databases that must also be created. The Teradata Administrator can do this using query commands or using the Teradata Manager.

8. Start Teradata Manager.

9. From the main window, choose Tools > Create User.

10. In the Create User dialog, assign a user name and password as well as initial space allocations, a default database, and any other


80 5000.1.0.0

fields you need to fully define your database. Uncheck the Fallback checkbox, then click Create.

11. Choose Tools > Create Database.

12. In the Create Database dialog, assign a database name and set up your initial space allocations for the new database. Click Create.I

13. From the main window, choose Tools > Grant / Revoke > Object Rights.

14. In the Grant / Revoke Objects dialog, select the user and database that you created for ZetaAnalytics. Select the checkboxes for all


5000.1.0.0 81

the rights you will grant to the user and database. Click Grant.

If you have not yet created any tables, give the user access at the database level.

After creating the user and database and granting rights, you can run scripts to create the FTQS, MMS and dense model tables used for the ZetaAnalytics analytic data source. See “Database Setup” on page 41.


82 5000.1.0.0

Index ZetaAnalytics Installation Guide

5000.1.0.0 83

INDEXA

Apache Tomcatinstall screen 25see also web server 25

AutoSyncinstall step 21

B

browsersupported 3

C

cleanupdatabase 64

componentsintegration 57required 12

configurationLDAP 55security 55

credentialssetting 57

D

Data Warehouserequirements 4

databasename, setting 57

database requirements 3denseModelHibernate.cfg 64directory, see folder 18display

supported 3download 7

E

EDM AutoSync Server 3EMC Greenplum

requirements 4error

unavailable database 73unavailable server 74

ESRI, seemap 67

F

folderinstall 18

FTQSconfiguration 58install step 23

H

Hadoopdisabling 62install step 24job status 74properties 60requirements 4

hibernate.cfgdense model 64FTQS 59MMS 60streaming 62

I

IBM Netezzarequirements 4

installdownload 14errors 69location 18log 70run 14workflow 11

installationdownload location 7

J

Java heap size 66

L

Landmark Application Manager (LAM) 7Landmark Software Manager (LSM) 7LDAP setup 55license

request 7server 7

INDEX


84 5000.1.0.0

standalone 7license.dat file 8log

install 70run-time 71

M

mapchanging 67ESRI ArcGis install step 26

memoryJava heap size 66

memory requirements 5MMS

configuration 59install step 22

O

orphan recordscleanup 64

P

password, see credentials 57performance

Java memory 66platform requirements 3port

configuration 65prerequisites 3

R

requirements 3

S

scheduledatabase cleanup 64

scoringconfiguration 60job status 74

securityconfiguration 55

serverIP address, setting 57port, setting 57

services, restarting 75simulator

configuration 61

streamingconfiguration 61job status 74

T

Teradata databaserequirements 4

U

username, see credentials 57

W

web serverunavailable 74

web server (HTTP) 3Wellspace

configuration 63workflow

installation 11

Z

ZetaAnalytics WITSML Services 3zetaanalytics_service

configuration 65

Documents

ZetaAnalyticsTM - esd.halliburton.com