GeoSoftware Installation Guide

GeoSoftware Launcher 9.0

Jason Workbench 9.0

PowerLog Enterprise 9.0

EarthModel FT 9.0

PowerLog 9.0

Copyright © 2015 CGG April 2015

 CGG GeoSoftware
As the leading provider of seismic inversion and reservoir characterization products and
services, CGG GeoSoftware has offices worldwide. Please see our Web site jason.Jason.com
for office locations and contact information. For general information, please send a request to
[email protected].

Copyright © 2009-2015 CGG

All rights reserved.

No part of this documentation may be reproduced, stored in a retrieval system, or transmitted in any form or by
any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from
CGG.
CGG assumes no responsibility or liabilities direct or indirect for any errors or inaccuracies that may appear in
this document or from the use of the information in this document with the software products described herein.
The software described in this document is furnished under a separate license agreement and may only be used or
copied in accordance with the terms of such license.
Usage rights for this material are governed by the terms of customer’s written license agreements with CGG.

Trademarks

3D Grid/CPG Builder™, 3DiQ™, EarthModel®, EarthModel® FT™, EPlus™, FracRat™, FunctionMod™,

GeoSoftware Database™, GeoSoftware Launcher™, GeoSoftware Suite™, InverMod®, InverTrace®,
InverTrace®Basic™, InverTrace®Plus™, Jason™, Jason Geoscience Workbench®, Jason STS™, Jason
Workbench™, Largo™, PowerBench®, PowerLog®, PowerLog® Enterprise™, PowerLog® Frac™, Rock Physics
Module™, RockMod®, RockScale®, RockTrace®, Statmin™, StatMod®, StatMod® MC™, VelMod™, and
Wavelets™ are trademarks of Jason and may not be used without permission.
All names of other companies, products, and services are the property of their respective owners.
 Third-party software

PowerLog uses WinWrap® Basic, Copyright 1993-2009 Polar Engineering and Consulting, http://
www.winwrap.com/.
Baker Hughes Inc. (BHI) is the source of the software used in PowerLog for laminated sand-shale analysis and
the owner of all rights thereto. The Baker software is used under license from BHI, but neither BHI nor Jason
guarantee the reproducibility or accuracy of answers derived from its use.
 v

CONTENTS

CHAPTER 1 Preparing to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
GeoSoftware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Jason Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
EarthModel FT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
PowerLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Requirements for MCPU installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Compatibility with earlier versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Product compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

CHAPTER 2 Installing on Linux (Jason Workbench) . . . . . . . . . . . . . . . . . . . . 13

Creating the product installation account & directory . . . . . . . . . . . . . . 14
Installing the Jason Workbench software . . . . . . . . . . . . . . . . . . . . . . . 15
Installing the license file & configuring the license manager . . . . . . . . . 15
Local license server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Database services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Remote license server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Making the Jason launcher available to users . . . . . . . . . . . . . . . . . . . . 21
Defining local settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Local cache directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Global spool directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Site-wide CGM previewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Customizing local defaults (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Default color scales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Templates for viewers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Automating printing of scaled plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

CHAPTER 3 Local Installation on Windows (GeoSoftware, Jason Workbench, . .

EMFT, PowerLog) 29
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Windows installer & the license server . . . . . . . . . . . . . . . . . . . . . . 29
Default installation directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Contents
vi

Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
MCPU workers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing the applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
PowerLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
GeoSoftware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuring the Petra link (PowerLog) . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuration for Petra Versions Prior to 4.0 . . . . . . . . . . . . . . . . . . 39
Configuration for Petra 4.0 and above . . . . . . . . . . . . . . . . . . . . . . . 39
Installing Petrel plug-ins (Jason Workbench, EMFT) . . . . . . . . . . . . . . 42
Using the plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Licensing & plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Uninstalling the plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Installing the OpenSpirit Satellite (EMFT) . . . . . . . . . . . . . . . . . . . . . . . 45
Setting up the cache directory (Jason Workbench) . . . . . . . . . . . . . . . . 46
Customizing the default color scales (Jason Workbench) . . . . . . . . . . . 47
Uninstalling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
PowerLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
GeoSoftware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

CHAPTER 4 Network Installation on Windows (GeoSoftware and PowerLog) . 51

Verifying the license server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Confirming the database (AMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Verifying the database (network share) . . . . . . . . . . . . . . . . . . . . . . . . . 54

CHAPTER 5 Configuring the GeoSoftware and PowerLog installation . . . . . . . 57

Creating user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Creating standard data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Creating default & predefined screens . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Scheduling database backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

CHAPTER 6 Configuring the MCPU Environment (Jason Workbench). . . . . . . 63

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Linux installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Using SSH (without a password) for MCPU . . . . . . . . . . . . . . . . . . 67
Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Setting up password-less SSH . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Using an external scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Windows installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Implementation details (Linux & Windows) . . . . . . . . . . . . . . . . . . . . . . 71
How workers are located . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Active user (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
RSH daemon (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

GeoSoftware Installation Guide

 vii

Checking PVM (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

About PVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

CHAPTER 7 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Licensing basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
License file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Types of licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Requesting a license file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
For a Linux machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
For a Windows machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Windows keyless license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Windows dongle license (PowerLog only) . . . . . . . . . . . . . . . . . 79
Configuring the license manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
On Linux workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
On Windows workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Automated configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Manual configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Manually configuring the license service (Windows) . . . . . . . . . . . . . . . 83
Setting the license variable (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . 85
Network installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Local installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Setting the variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Sharing the license between different release versions (Linux) . . . . . . . 86
Stopping/starting the license manager . . . . . . . . . . . . . . . . . . . . . . . . . 87
On Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
On Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Frequently asked questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

CHAPTER 8 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
License problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Checking the license log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Obtaining additional diagnostic information . . . . . . . . . . . . . . . . . . . 94
On Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
On Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Linux: Dealing with license problems . . . . . . . . . . . . . . . . . . . . . . . 95
Troubleshooting checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
FlexNet error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
System is not LSB compliant. . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
No “eth0” network card is found.. . . . . . . . . . . . . . . . . . . . . . . . . 98
User is invalid. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
License file is corrupt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Contents
viii

Licenses are still in use after a crash. . . . . . . . . . . . . . . . . . . . 100

Lockfile is not removed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Hostname in license file is wrong. . . . . . . . . . . . . . . . . . . . . . . 100
Windows: Dealing with license problems . . . . . . . . . . . . . . . . . . . 101
Cannot find license file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Cannot connect to license server system.
The desired vendor daemon is down. . . . . . . . . . . . . . . . . . . . 102
License server machine is down or not responding.. . . . . . . . . 103
Some or all features that should be available are not available. . .
103
License expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Windows: Dongle license problems . . . . . . . . . . . . . . . . . . . . . . . . 104
USB dongle not plugged in or dongle driver not working. . . . . 105
Dongle ID does not match host ID in license file. . . . . . . . . . . . 106
Some or all features that should be available are not available. . .
106
Linux or Windows: Additional information . . . . . . . . . . . . . . . . . . . 107
Users cannot connect to license server . . . . . . . . . . . . . . . . . . 107
Administrator cannot release a checked out license . . . . . . . . 107
Contacting support with license problems . . . . . . . . . . . . . . . . . . . 107
Database problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Cannot connect to remote database via AMS . . . . . . . . . . . . . . . . 109
1. Check that essential services are running. . . . . . . . . . . . . . . 109
2. Check that the database exists. . . . . . . . . . . . . . . . . . . . . . . 110
3. Disable the firewall temporarily. . . . . . . . . . . . . . . . . . . . . . . 111
4. Test the local connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Database lock server not running . . . . . . . . . . . . . . . . . . . . . . . . . 113
Other problems connecting to database . . . . . . . . . . . . . . . . . . . . 113
Jason Workbench problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3D View hangs (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
3D View does not display SHF files (Window and Linux) . . . . . . . 115
PowerLog problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
PowerLog 2 no longer works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Petra link does not work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Petra license issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Petra server and client out of sync . . . . . . . . . . . . . . . . . . . . . . 118
Other problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

GeoSoftware Installation Guide

 1

CHAPTER 1

Preparing to Install
In this guide, you will find instructions for the following

• PowerLog® 9.0 without the GeoSoftware Launcher™

• GeoSoftware that consists of the following Jason products:

• GeoSoftware Launcher 9.0

• Jason Workbench™ 9.0
• PowerLog® Enterprise™ 9.0
• EarthModel® FT™ 9.0

GeoSoftware provides an integrated environment for oil field

evaluation and development. It bundles well log appraisal tools with a
well database, data management tools, and QC views. The database and
tools can be shared by a family of Jason software products, making it
easy for colleagues in different disciplines to collaborate based on a
common set of well curve interpretations.

Key features include the following:

• A sophisticated database designed for storing all types of well data.

• Dynamic sharing of well data among various GeoSoftware

applications.

• Sharing of well projects by multiple applications and by multiple

users.

• Ability to assign various levels of access to users.

• Ability to import and export data in industry-standard well data

formats.

• Ability to capture and restore product configurations and views in

session files.

Chapter 1: Preparing to Install

2

• Ability to group, explore, and share curve interpretations in an

efficient manner.

• A full suite of database management tools.

You can install the GeoSoftware Launcher with either all of the Jason
products or with any combination of software. For example, you can
install only Jason Workbench or both PowerLog and EarthModel FT.

This chapter contains information about system requirements and other

factors you need to consider as you plan your installation. Please read it
carefully before attempting to install the software.

The following conventions are used throughout this guide:

Conventions Used in this Guide
Notation Description
terminal This font is used for user input, program output, or error
messages. Example: tar xv
<user> Identifies a generic element that must be replaced by the value
appropriate for your installation.
<topdir> On Windows only—Refers to the top-level CGG directory
under which are found subdirectories for each installed
application and a common subdirectory containing license
management tools and files shared by all Jason applications.
For example, C:\Program Files\CGG\GeoSoftware 9.0\.
<instdir> Refers to the directory where the Jason application currently
under discussion is installed. For example, C:\Program
Files\CGG\GeoSoftware 9.0\.

GeoSoftware Installation Guide

 System requirements 3

System requirements

Before installing any Jason software, make sure that your system meets
the minimum requirements outlined below. If you plan to install
multiple products on a machine, the minimum requirements will be the
combination of those listed for each product.

GeoSoftware

GeoSoftware can be installed only on Windows (64-bit) machines.

Optionally, you can install the application on a server and run it from
clients via remote desktop access. You also have the option of setting
up an MCPU network for processing large, computation-intensive jobs.
GeoSoftware
Item Requirement
operating system On Windows, only the 64-bit version is supported with Windows 7
(Professional and Enterprise), latest service packs installed
processor • dual core for working with small datasets up to 100,000 traces
• 4 cores for datasets up to 1M traces
• 8 cores for datasets up to 4M traces
hard drives SATA-II hard drive with enough space for your data
disk space 10 GB of free disk space recommended for installation since the installer
uncompresses files and generates temporary files.
The installed software will occupy about 4 GB of disk space.
• 2 GB for interpreting small datasets up to 100,000 traces
memory • 16 GB for interpreting datasets up to 1M traces
• 64 GB for interpreting datasets up to 4M traces
• Minimum (supports interpretation on small datasets up to 100,000 traces):
512 MB NVIDIA OpenGL 4.0 capable video card with at least 48 shader
cores
• Medium (supports interpretation on datasets up to 1M traces):
2 GB NVIDIA OpenGL 4.0 capable video card with at least 256 shader
graphics card cores
• Large (supports interpretation on datasets up to 4M traces):
4GB NVIDIA OpenGL 4.0 capable video card with at least 1536 shader
cores
Important: Version 330 or later of the NVIDIA driver is required. You can
download the driver from www.nvidia.com.

Chapter 1: Preparing to Install

4 System requirements

GeoSoftware
Item Requirement
Dual monitors are recommended. On Linux, configure the X-server to use
monitors NVIDIA’s TwinView architecture (this is the default). Xinerama is not
supported because it causes performance issues in the viewers.
HP Remote Graphics Software (RGS), version 6 or later.
RGS allows users to access and share the desktop of a remote machine where
the Jason software is installed. It supports the graphics-intensive 3D View.
remote desktop access Note: No Machine (NX) and ThinAnywhere are not sufficient for displaying
(optional) the 3D View and are no longer supported. Jason software is not certified for
any X-emulators such as Hummingbird Exceed/Exceed 3D or CygWin-X.
The Windows 7 remote desktop client does not support hardware-accelerated
graphics, and are not supported.
Adobe Reader is required for displaying online documentation including the
PDF viewer release notes. If it is not already installed on your system, download it from
www.adobe.com and set it as your default PDF viewer.

Jason Workbench

Jason Workbench can be installed on Linux (64-bit) or Windows

(64-bit) machines. Optionally, you can install the application on a
server and run it from clients via remote desktop access. You also have
the option of setting up a MCPU network for processing large,
computation-intensive jobs.
Jason Workbench
Item Requirement
On Linux x64, the following operating systems are supported:
• SUSE Linux Enterprise Server 11, with latest updates
• Red Hat Linux Enterprise Server (CentOS) 4, 5, or 6, with latest updates
operating system
The 32-bit compatibility libraries and perl4 core modules must be installed.
On Windows, only the 64-bit version is supported:
Windows 7 (Professional and Enterprise), with latest service packs installed
processor • dual core for working with small datasets up to 100,000 traces
• 4 cores for datasets up to 1M traces
• 8 cores for datasets up to 4M traces
hard drives SATA-II hard drive with enough space for your data
disk space 10 GB of free disk space recommended for installation since the installer
uncompresses files and generates temporary files.
The installed software will occupy about 4 GB of disk space.
• 2 GB for interpreting small datasets up to 100,000 traces
memory • 16 GB for interpreting datasets up to 1M traces
• 64 GB for interpreting datasets up to 4M traces

GeoSoftware Installation Guide

 System requirements 5

Jason Workbench (Continued)

Item Requirement
• Minimum (supports interpretation on small datasets up to 100,000 traces):
512 MB NVIDIA OpenGL 4.0 capable video card with at least 48 shader
cores
• Medium (supports interpretation on datasets up to 1M traces):
2 GB NVIDIA OpenGL 4.0 capable video card with at least 256 shader
graphics card cores
• Large (supports interpretation on datasets up to 4M traces):
4GB NVIDIA OpenGL 4.0 capable video card with at least 1536 shader
cores
Important: Version 330 or later of the NVIDIA driver is required. You can
download the driver from www.nvidia.com.
Dual monitors are recommended. On Linux, configure the X-server to use
monitors NVIDIA’s TwinView architecture (this is the default). Xinerama is not
supported because it causes performance issues in the viewers.
HP Remote Graphics Software (RGS), version 6 or later.
RGS allows users to access and share the desktop of a remote machine where
the Jason software is installed. It supports the graphics-intensive 3D View.
remote desktop access Note: No Machine (NX) and ThinAnywhere are not sufficient for displaying
(optional) the 3D View and are no longer supported. Jason software is not certified for
any X-emulators such as Hummingbird Exceed/Exceed 3D or CygWin-X.
The Windows 7 remote desktop client does not support hardware-accelerated
graphics, and are not supported.
Adobe Reader is required for displaying online documentation including the
PDF viewer release notes. If it is not already installed on your system, download it from
www.adobe.com and set it as your default PDF viewer.

Additionally, consider the following requirements that are specific to

the Jason processing modules:
Jason Workbench Processing
Item Requirement

• InverTrace® Basic™, InverTrace® Plus™, and RockTrace®: 2 GB per core

memory
• StatMod®MC™ and RockMod®: 2.0 GB per core
Processing is done by CPU, not GPU. So the type of graphics card is
graphics card
irrelevant for the processor modules.

Chapter 1: Preparing to Install

6 System requirements

EarthModel FT

EarthModel FT is available only for Windows (64-bit).

EarthModel FT
Item Requirement
operating system Only the 64-bit Windows version is supported:
Windows 7 (Professional and Enterprise), with latest service packs installed
processor Single-core processor is sufficient. Multi-core processor will speed execution
of some algorithms, for example, the new fault-building algorithms
(Minimum Energy and Minimum Energy Curved), the new truncation code,
and the new calculator code.
hard drives SATA-II hard drive with enough space for your data
disk space 10 GB of free disk space recommended for installation since the installer
uncompresses files and generates temporary files.
The installed software will occupy about 1 GB of disk space. EMFT projects
will require additional disk space. A good guideline is 10 GB for small
projects, 100 GB for mid-size projects, and >100 GB for large projects.
For 64-bit systems, the recommendation is 4-8 GB for small projects,
memory
24-64 GB for mid-sized projects,64+ GB for large projects.
512 MB NVIDIA OpenGL 4.0 capable video card with at least 48 shader
cores.
graphics card
Note: An issue has been found with newer NVIDIA versions. For the 9.0
release, only the 331 release is supported.
Adobe Reader is required for displaying online documentation including the
PDF viewer release notes. If it is not already installed on your system, download it from
www.adobe.com and set it as your default PDF viewer.
HP Remote Graphics Software (RGS), version 6 or later.
remote desktop access
RGS allows users to access and share the desktop of a remote machine where
(optional)
the Jason software is installed. It supports the graphics-intensive 3D View.

GeoSoftware Installation Guide

 System requirements 7

PowerLog

PowerLog can only be installed on a 64-bit Windows machine. It is not

available on Linux. All components (application, database, license
server) can be installed on the same machine; or for a multi-user,
network installation you can install the database and license server on
remote machines.
PowerLog
Item Requirement
operating system Only the following 64-bit versions of Windows are supported.
• Windows 7 (Professional and Enterprise), with latest service packs installed
processor at least 1.5 GHz, dual core
hard drives SATA-II hard drive with enough space for your data
disk space 10 GB of free disk space recommended for installation since the installer
uncompresses files and generates temporary files.
The installed software will occupy about 1 GB of disk space.
memory 4 GB
graphics card A graphics card with at least 512 MB of video memory
Adobe Reader is required for displaying online documentation including the
PDF viewer release notes. If it is not already installed on your system, download it from
www.adobe.com and set it as your default PDF viewer.
HP Remote Graphics Software (RGS), version 6 or later.
remote desktop access
RGS allows users to access and share the desktop of a remote machine where
(optional)
the Jason software is installed. It supports the graphics-intensive 3D View.

Chapter 1: Preparing to Install

8 Requirements for MCPU installation

Requirements for MCPU installation

With the Jason Workbench, computation-intensive jobs can be run on a

heterogeneous network of 64-bit computers as if they were running on
a single large, parallel computer. This capability applies to
InverTrace®Basic™, InverTrace®Plus™, RockTrace®, StatMod® MC™
and RockMod®, all of which can be run in parallel mode. In this way
large computational problems can be solved more cost effectively by
using the aggregate power and memory of many computers.

For this type of configuration, you need a special MCPU license. You
can have a mixture of Linux and Windows machines cooperating on the
same task. For efficient use, the machines should be of comparable
specifications. They should have the same amount of memory per
thread (core or CPU), and the CPUs should be of roughly equal
performance. All must have 64-bit operating systems
MCPU Hardware Recommendations
Hardware Recommendation
Network The worker nodes access their input data over the network
(using NFS or CIFS) and, therefore, benefit from having a
high-speed, low-latency network (GigE or better).
Memory The maximum amount of data a worker process can handle
is determined for the whole process. Therefore, the lowest
amount of memory available on any one of the workers will
determine the maximum amount available for each process.
Having six workers with 2 GB available and two workers
with 1 GB will usually lead to a longer overall runtime than
having only six workers with 2 GB of memory.
CPU A good rule of thumb is that the speed difference between
the fastest and slowest CPU should be less than 50%.

GeoSoftware Installation Guide

 License 9

License

A single license file is issued to cover all the Jason software products
and modules you purchase. You must obtain a Jason license file for this
release. Earlier Jason licenses will not support the new versions of the
software. However, the Jason 9.0 license is backward compatible and
will support previous releases.

For instructions on requesting a license file, see page 78 in the

“Licensing” chapter.

Tip: Although you can install the products before you obtain your license file,
having the file when you run the installer will make the installation process
quicker and, in some cases, will automate some of the configuration tasks.

Installers

Several installers are available:

• GeoSoftware Suite (64-bit for Windows)

• PowerLog without the GeoSoftware Launcher (64-bit for Windows)
• Jason Workbench (64-bit for Linux)

Contact your local Jason support representative to request the installer

that is appropriate for your system. Your representative will supply a
DVD with the software or explain options for downloading an installer
from the Web.

Chapter 1: Preparing to Install

10 Compatibility with earlier versions

Compatibility with earlier versions

You can preserve existing Jason installations by installing the latest

software version in a different directory. This approach may assist in a
smoother migration to the new version. However, data compatibility
across software versions varies somewhat by product.

Important: We recommend that you make backups of your projects before using
them in the newly installed version of the software.

Product compatibility

Backward compatibility is summarized below:

• GeoSoftware projects—With the 9.0 release, projects are stored as

GeoSoftware projects, which are not backward compatible. The
Jason Workbench portion of a GeoSoftware project is located in the
JASON__DATA subdirectory. This project is backward compatible.

• Jason Workbench—Jason Workbench 9.0 is fully compatible with

Jason Workbench 8.4, with a few exceptions mentioned below

• Jason Workbench projects—Jason projects can be used on Linux

and Windows machines as long as the file names are supported
on both platforms. To be safe, use only alphanumeric characters
and underscores when naming files. Do not use spaces or special
characters.

• Cartographical degrees—Jason 9.0 projects that use the new

type, Cartographical degrees, cannot be opened using JGW 8.4.2
because JGW 8.4 does not know this unit. To remedy this, you
need to copy the file jgw/etc/units.txt from the 9.0 install
tree to the same location in the 8.4 tree.

• RockMod/StatMod MC—RockMod/StatMod MC session files

generated in 9.0 may not work in 8v4. Session files generated in
8.4 will work correctly in 9.0.

• EarthModel FT—EMFT projects created prior to 9.0 are not

changed by the upgrade process and can still be used by the
previous EMFT version. New EMFT projects cannot be used by
previous versions of EMFT.

GeoSoftware Installation Guide

 Compatibility with earlier versions 11

• PowerLog—PowerLog 9.0 introduces database schema changes; so

you have to upgrade all existing databases for use with PowerLog
9.0. Once you upgrade, you cannot use it with previous versions of
the software. (Whenever a new release includes a schema change,
you will be prompted to upgrade the database when you launch
PowerLog and try to connect to that database.)

Chapter 1: Preparing to Install

12 Compatibility with earlier versions

GeoSoftware Installation Guide

 13

CHAPTER 2

Installing on Linux (Jason Workbench)

This chapter describes how to install and configure the Jason
Workbench on Linux machines. The main steps are outlined below and
described in detail in later sections of this chapter.

1 Create the product installation account and directory.

2 Install the Jason Workbench software.

3 Install the license file and configure the license manager.

4 Make the Jason launcher available to users.

5 Define local settings.

6 Customize local defaults (color scales, viewer default displays).

7 Automate printing of scaled plots.

If you plan to use the machine in an MCPU network, please review the
MCPU requirements (page 63) before beginning the Jason Workbench
installation.

Chapter 2: Installing on Linux (Jason Workbench)

14 Creating the product installation account & directory

Creating the product installation account & directory

The Jason Workbench modules can be made available to all

workstations on your network by exporting the applicable partition.
Please ensure that the path to the software installation is the same on all
machines, preferably by using the automounter.

We also recommend that you create a user account with the name jason
and use that account to install the software. This approach has the
following advantages:

• avoids potential security risks, which may occur when the software
is installed as root,

• allows patches to be installed without the need for the root password

To create the installation directory, do as follows:

1 Switch to the root account by typing: su root

2 Check for available disk partitions and space: df -k

3 Decide where to install the Jason software (at least 4 GB of disk

space is required), and create a directory on the selected partition:
mkdir jason.

4 Create a user jason, and grant him access to the directory you just
made.

useradd jason
passwd jason <password>
chown -R jason <jason_dir>

Tip: Alternatively, you can use this command to create the user jason and make the
jason directory his home directory:
useradd -d <path_jason_dir> jason

5 Log in as the user jason to proceed with the installation procedure.

GeoSoftware Installation Guide

 Installing the Jason Workbench software 15

Installing the Jason Workbench software

Now that you have created an account to install the product and a
directory where it will reside, you are ready to run the install script.

1 If you obtained the installation software on DVD, mount the DVD.

Note: Ensure that the DVD has been mounted with execute permission. RHES5 by
default mounts DVDs with no execute permission. If you get a “permission
denied” error when you try to run the install script, this message usually
indicates that the DVD has not been mounted with execute permission. Use
this command: mount -o remount -o exec /mnt/dvd

You can run the install script as either the root (superuser) or as the
jason user (if you have write permission in the destination
directory.)

2 Run the install script using one of these methods.

• Change to the DVD directory, and enter this command:

(Note the leading ./)

• If you have downloaded the Linux installer, type

tar xf geosoftware9.0.tar
cd geosoftware9.0
./install

3 To start the installer, type O (for OK).

4 Specify the directory where you want to install the software.

When the installation is completed, you are prompted to install the

license file.

Installing the license file & configuring the license

manager

The next task is to configure licensing, using either the local machine
as the license server or a remote license server.

Chapter 2: Installing on Linux (Jason Workbench)

16 Installing the license file & configuring the license manager

Local license server

During the installation, license management tools were installed in

<instdir>/license. Now, you’ll copy your license file to that directory,
run the jgsetup script, and enable the license manager.

1 Save the license file you received via email from Jason as
license.dat.

2 Copy license.dat to the license directory:

cp license.dat <instdir>/license

3 Change to <instdir> and run the configuration script:

./jgsetup

4 Select the appropriate option to configure the installation:

• You have Jason Workbench 8.4 RAP installed.—Select option 1,

Configure using a previous installation. When prompted, specify
the path to your Jason Workbench 8.4 RAP installation.

• You do not have a previous version of Jason Workbench

installed.—Select option 6, Configure the installation.

Both options 1 and 6 set the path to the license daemons in the
license.dat file and update the full directory path to the current
installation in several configuration files. Option 1 also copies
the license file and other configuration settings from your
previous installation to your new installation.

Because GeoSoftware 9.0 uses an objectivity database to store well

data, you next need to enable database services.

Database services

1 On each machine where you want to install such a database, install

the database services.

• Log in to these machines as root.

• Change to <instdir> and run the configuration script:

./jgsetup

GeoSoftware Installation Guide

 Installing the license file & configuring the license manager 17

• Selection option 7.

Next, you will enable the license manager.

2 Stop and then restart the license manager daemon:

• Change to the license directory:

cd <instdir>/license

• Enter these commands:

./jlmdown -c license.dat
./jasonstartjlm -c license.dat

• Check the license manager log file to ensure the license manager
has started correctly:
more /tmp/jasonlicense.log

• Also, you can check to see if the daemons lmgrd and jasonlm are
running by entering this command:
ps -ef | grep jason

3 Configure the license manager to start automatically whenever the

system is rebooted. Use either of the following methods:

• Edit the script <instdir>/etc/jasonlm to reflect your setup.

• Create a startup script. You need root privileges to do this.

– Type vi /etc/rc5.d/S85lmgrd.jason.

– Add the following lines:

Chapter 2: Installing on Linux (Jason Workbench)

18 Installing the license file & configuring the license manager

#!/bin/sh
#
# Start Jason license manager demon
#
if [ -f <instdir>/license/jasonstartjlm ]
then
<instdir>/license/jasonstartjlm \
-c <instdir>/license/license.dat \
-l /tmp/jasonlicense.log -u jason &
fi

– Note that with option -1 you can change the name and
location of the log file to align with your installation
environment. Option -u allows you to the run the license
manager as a user who does not have root privileges; we
recommend doing this to prevent possible security leaks.

4 Test the installation:

• Log in as the user jason.

• Run the setup script: <instdir>/jgsetup.

• Select option 2, Test the Jason installation.

Some informational messages are displayed in the window, and

the Jason launcher is started.

• Select Help > Release Notes.

• Open a viewer, for example, by selecting Views > Section View.

• If these tests were successful, select Project > Exit to close the
launcher.

Remote license server

To use a license server that is installed on a remote machine (either

Linux or Windows), you can use either of these methods:

• Set the environment variable JASONLM_LICENSE_FILE to point

to the remote license server.

GeoSoftware Installation Guide

 Installing the license file & configuring the license manager 19

setenv JASONLM_LICENSE_FILE <port#>@<hostname>

The port number is optional; if you do not specify a port, one of the
FlexNet default ports (27000 - 27009) will be used. Hostname is the
name of the machine where the license server resides.

This solution is temporary if you set the variable in an xterm and

run the Jason application from that same xterm. For a permanent
solution, set the variable in the user’s profile.

• Copy the license file from the remote server and paste it in
<instdir>/license on the Linux client. The SERVER line in the
license file specifies the remote license server. There should be no
Jason license server running on the local machine.

After implementing either of these methods, continue with the

configuration of the Jason installation on the local Linux machine, as
follows:

1 If you are using option 1 above (setting the environment variable),

place a dummy license.dat file in <instdir>/license.

The configuration script looks for a license file on the local

machine. So you need a dummy license.dat in the license directory;
this file can be empty.

2 Change to <instdir> and run the configuration script:

./jgsetup

3 Select the appropriate option to configure the installation:

• You have Jason Workbench 8.4 RAP installed.—Select option 1,

Configure using a previous installation. When prompted, specify
the path to your Jason Workbench 8.4 RAP installation.

• You do not have Jason Workbench 8.4 RAP installed.—Select

option 6, Configure the installation.

Both options 1 and 6 set the path to the license daemons in the
license.dat file and update the full directory path to the current
installation in several configuration files. Option 1 also copies
the license file and other configuration settings from your
previous installation to your new installation.

Chapter 2: Installing on Linux (Jason Workbench)

20 Installing the license file & configuring the license manager

4 Select option 2 to test the installation.

• When the Jason launcher opens, select Help > Release Notes.

• Open a viewer, for example, by selecting Views > Section View.

• If these tests were successful, select Project > Exit to close the
launcher.

Important: If you use a separate, central license server (which does not have Jason
software installed) and you are upgrading from Jason Workbench 8.2 or an
older version, you need to update the license daemons on the license server.
Copy new versions of jasonlm.exe and lmgrd.exe from a machine where you
install the Jason products to the license server.

GeoSoftware Installation Guide

 Making the Jason launcher available to users 21

Making the Jason launcher available to users

To make it easy for users to start the Jason launcher, you will add a new
command, jason. This command can be run with or without an
argument:

• jason with no argument starts the launcher and opens the Select
Project window so that user can select the project to work in.

• jason <project_directory> starts the launcher and opens

the specified project.

Several methods of adding this new command are possible:

• The recommended way is to create a symbolic link to an executable

directory that is available in everyone’s search path. The advantage
is that only one, globally accessible directory requires maintaining.
Use the following commands:

cd /usr/local/bin
ln -s <instdir>/jason .

• Alternatively, you can quickly enable the command jason for a

specific user without the need of having root privileges. You simply
run the setup script to update the user’s .login or .profile file.

cd <instdir>jgsetup
Select option 3, Make Jason available to the users.

• Finally, you can define an alias jason in a global login script.

Chapter 2: Installing on Linux (Jason Workbench)

22 Defining local settings

Defining local settings

When a user starts the application, the runtime environment is

initialized. You can customized the runtime environment, specifying
the location for the cache directory, spool directory, etc. These settings
are stored in the file <instdir>/local/bin/machind/jwclient.csh and are
applied globally.

However, you can also define local settings for each user. These are
stored in $HOME/jwclient.csh and take precedence over the global
settings.

Procedure

Most of the options you need to define can be set using the jgsetup
script. A few require that you manually edit the settings file.

1 Change to the <instdir>, and type ./jgsetup.

2 Select option 5, Define local settings.

3 When prompted, enter the full paths for each of the following:

• local cache directory (page 23)

• global spool directory (page 23)
• external CGM previewer (page 24)

4 Exit jgsetup.

5 Browser—To use a browser other than Firefox for displaying the

Jason Workbench help, do as follows:

• Open the file <instdir>/local/bin/machind/jwclient.csh.

• Locate the following line: setenv JG_BROWSER Firefox.

• Insert a # at the beginning of that linen and add a new line:

#setenv JG_BROWSER Firefox

setenv JG_BROWSER <your_webbrowser>

6 GeoFrame link—If the GeoFrame links fails to start with an error

that IESX data communication cannot be started, the timeout period
may be too short (the default is 15 seconds). Try this:

GeoSoftware Installation Guide

 Defining local settings 23

• Edit the appropriate jwclient.csh file (either the global file or an

individual user’s file).

• Add the following line:

setenv JG_SERVER_SLEEP_TIME 999

where 999 is the timeout in seconds.

Local cache directory

To enhance performance of 3D View, representations of the models that

are displayed are stored locally on disk. When setting the default cache
directory, be sure to specify a local file system that has at least 1 GB of
free space. This default appears as the suggested choice when a user
opens 3D View for the first time and is prompted to specify the cache
directory.

Important: Do NOT use /tmp as this directory is used by the operating system and
many other applications to store temporary files; if /tmp fills up, the OS will no
longer be able to function correctly.

As an example, if most workstations have a free partition called /space,

you could set the default cache directory to /space/$USER. When a
user starts 3D View, the system will prompt him to set the cache
directory and suggest /space/<username>. If the user accepts the
default, the system will use that as the cache directory for that user (and
create it in case it does not yet exist).

The location of the cache directory is stored in the file /usr/tmp/

jason_cache_dir.<username>.

Note: All files in the cache directory that have not been modified in the last seven
days are removed automatically when 3D View is started.

Global spool directory

By default, Jason Workbench stores hardcopy files in each user’s home

directory, $HOME/JASON_PLOTS. However, by setting the global
spool directory option, you can define one site-wide directory that
functions as a central repository for hardcopy files.

Chapter 2: Installing on Linux (Jason Workbench)

24 Defining local settings

For example, you might define a global directory

/volume/JASON_PLOTS and set the global spool directory to
/volume/Jason_Plots/$USER. The system will try to create this
directory automatically when a user starts Jason Workbench. If the
directory cannot be created, a JASON_PLOTS directory will be created
in the project directory.

Site-wide CGM previewer

You can specify an external viewer that will be used site-wide to

preview CGM files when a scaled plot is being made. The CGM
previewer is called automatically as the last argument in the command
for displaying the CGM file.

If this setting is left blank, the user will be asked which previewer to
use.

GeoSoftware Installation Guide

 Customizing local defaults (optional) 25

Customizing local defaults (optional)

The default color scales applied for the various data types and the way
data is displayed by default in the various viewers are controlled by
system parameter files. You can edit and save these files so that the
system will then operate with your preferred settings.

Note: The environment variables used below can only be defined correctly within the
Jason Workbench environment. Select System > Unix Terminal Window
from the Jason launcher to get access to that environment (a regular terminal
will not work).

All default files are stored in $JWSYS and its subdirectories. You can
copy these files to the $JG_LOCAL_ETC directory and make all the
changes you wish. The Jason modules use the defaults from the files in
$JG_LOCAL_ETC first, and (if no default file can be found) check for
these files in $JWSYS next.

Default color scales

As an example, the $JWSYS/colorscales directory contains a file called

class_mapping.ri, which defines the mapping of data classes to color
scales. For a given data type, the file is read until a class containing the
type is found. The associated scale is then used as default for that type.
Hence, classes must be ordered from specific to general; the class “all”
must be present, and must be the last class in the file:

Chapter 2: Installing on Linux (Jason Workbench)

26 Customizing local defaults (optional)

class_mapping:dict[5]=
{
class:string="none";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="waves";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="time_frequency";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="depth_frequency";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="_class_all";
color_scale:string="rainbow.shs";
};

Templates for viewers

When users want to start a new session, all modules that work with
sessions (except 3D View) check for a template file named empty. If
present, the settings in that file are applied when the user clicks the
New button in the module. New empty files can be created and stored
in $JG_LOCAL_ETC. Please contact Jason customer support if you
would like more information on this option.

GeoSoftware Installation Guide

 Automating printing of scaled plots 27

Automating printing of scaled plots

When a user creates a scaled plot, it is passed to the jwplot script. This
script, located in <instdir>/local/bin/machind/jwplot allows you to
automate the submission of the plot file to the printing queue.

The arguments to jwplot are as follows:

Device type = hardcopy device type

Device key = hardcopy device key
Plot file = hardcopy file name

The script <instdir>/local/etc/jwhcpl.cfg lists all available printers and

can be adapted to your environment. The format is

line 1: Description e.g.: A0 Plotter in room 923

line 2: Device-driver e.g.: CGM
line 3: ASCII-key of device e.g.: CGM_VERSA1
line 4: (Not used)
line 5: (Not used)

where:

The Description for each printer is presented to the user so that he

can select the plotter of his choice.

The Device-driver specifies what type of output is desired, CGM or

postscript.

The ASCII-key of device will be passed to the jwplot script as the

second argument, so that you can direct the plot file to the
appropriate print queue.

Please contact Jason customer support if you would like more

information on this option.

Chapter 2: Installing on Linux (Jason Workbench)

28 Automating printing of scaled plots

GeoSoftware Installation Guide

 29

CHAPTER 3

Local Installation on Windows (GeoSoftware,

Jason Workbench, EMFT, PowerLog)
GeoSoftware, Jason Workbench, EarthModel FT, and PowerLog can
all be installed locally on Windows machines (64-bit). In this scenario,
the application is installed on the machine where it will be run. In the
case of PowerLog, the database is also installed on the local machine.
The license server can be either local or remote.

Before you begin

This section contains useful information about the installer and the
installation process. Please read it before launching the installer.

Windows installer & the license server

In addition to the Jason products you select, the Windows installer

always installs the FlexNet license manager software in
<topdir>\common\license. Depending on the content of your license
file, the installer may also perform other functions:

• If the host ID listed in the license file is the same as that of the local
machine, the installer will configure a license service, copy the
license file to <topdir>\common\license, and set the environment
variable JASONLM_LICENSE_FILE to point to the license file on
the local machine.

• If the host ID in the license file is not the same as that of the local
machine, the installer assumes the host ID refers to a remote license
server and sets the variable JASONLM_LICENSE_FILE to point to
the license file on that host. No local license service is configured.

• If you have a dongle license (supported for PowerLog only), no

license server is required, and no license service is configured.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

30 Before you begin

Thus, it is advantageous to obtain your license file before installing the

Jason products. If you do install without a license file, you may have to
do some manual configuration later (page 83).

Default installation directories

The default installation directories for the applications, database, and

sample project are listed in the table below. You can specify different
directories during the installation. After the installation, you can also
create additional databases in the same or different directories.
Default Installation Directories on Windows
Platform Directory

Applications

Windows 7 C:\Program Files\CGG\GeoSoftware 9.0<application_name_version>

Database

Windows 7 C:\Users\<user>\AppData\Roaming\CGG\DB\
Sample Project

Windows 7 C:\Users\<user>\AppData\Roaming\CGG\Amberjack 9v0

Note that on Windows the default DB installation directory is under the

<user> who is doing the installation; so others cannot access that
directory. If you want different levels of access, be sure to specify a
different directory; do not accept the default.

Note: To access the database, a user not only must have access to the DB directory
but also must have a user account for the DB (which is created by the database
administrator).

GeoSoftware Installation Guide

 Before you begin 31

Installing on Windows

On Windows, run the installer with an account that has administrator

privileges.

If you attempt to install GeoSoftware 9.0 with an account that does not
have administrator privileges, you are prompted to supply credentials
for such an account. From that point on, the installer configures
everything for this user. Specifically, the default location for creating
the wells database is set to the administrator’s directory, not to yours.
Do not accept the default; specify the directory you want.

MCPU workers

If you are installing Jason Workbench and plan to use the machine as an
MCPU worker, please review the MCPU requirements (page 63)
before beginning the installation.

During the local installation, you will need to enable MCPU on this
machine and list the hosts that will be allowed to send jobs to it.

With MCPU enabled, the installation directory is automatically set to

the default location: C:\Program Files\CGG\GeoSoftware 9.0. You
cannot change it.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

32 Installing the applications

Installing the applications

You can install PowerLog without the GeoSoftware launcher or you

can install the GeoSoftware Suite with any combination of
applications. For example, you can install the GeoSoftware Suite with
only PowerLog and EarthModel FT.

PowerLog

Perform the following steps to install PowerLog by itself and without

the GeoSoftware Launcher. You can install PowerLog Frac, PowerLog
with all features, or both versions of PowerLog.

Important: Install all available Windows updates. The installer may fail if the
necessary updates are not in place.

Note: If you install PowerLog as a standalone application and without the

GeoSoftware Launcher, you will need to uninstall that application before you
can install additional Jason software. You would then reinstall PowerLog and
other applications, with the GeoSoftware Suite installer
GeoSoftwareSuite9.0.exe.

1 Double-click the setup executable to launch the installer:

SAPWL9.0x64.exe.

The installer checks for Microsoft.net Framework 3.5 on your

computer. If it is not found, the installer installs it, and you are
prompted to reboot. If the installer does not reappear automatically
after the reboot, double-click SAPWL9.0x64.exe to restart it.

2 Follow the on-screen instructions to install the software.

Note: If you want to install only server components, you can install Database
Management without installing PowerLog.

GeoSoftware Installation Guide

 Installing the applications 33

3 Custom Setup—On the Custom Setup page, select the products and
features you want to install:

Component Description
Local License Server Installs the license manager and configures a license service for
PowerLog products. This option is always selected; the installer
determines whether to configure a local license server based on
the contents of your license file (page 29). If you use dongle
licensing, no license server is installed.
Database Management 9.0 Installs a database server and Database Management. Used for
network installations of PowerLog or to install Database
Management on another machine.
PowerLog 9.0 Installs the PowerLog application.
GeoPlus Petra I/O Installs the Petra link for transferring data to/from Petra projects.
This option appears only if Petra is installed on the machine.
Sample Project Creates a sample project in the database. If you have a Sample
Project already installed, you need to delete it from Windows
Explorer.

4 PowerLog Runtime Options—Determine which versions of

PowerLog you want to install. You can install either one or all of
them.

• PowerLog Full—PowerLog with all of the features available. If

you install PowerLog Full without the proper license, you will
be unable to use all menu options because of a licensing
agreement.

• PowerLog Frac—PowerLog with only the features necessary to

run FracRat and to execute a pressure-pumping workflow. This
can be installed with a license for the full version of PowerLog.

5 Database folder—Specify the location where you want the database

created.

• The installer will not overwrite or delete an existing database

named sample.fjdb. If you want to install a new database,
change to a different directory or delete the existing database
from Windows Explorer.

• The full path, including database filename, cannot exceed 200

characters.

• The default directory is accessible only to you. If you want to

allow others access, specify a different directory.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

34 Installing the applications

• If you want to login with your Windows ID and bypass the

PowerLog login, select the checkbox Automatically login into
database/project with current Windows user ID. Your
password is not stored within PowerLog; only your login name
is saved.

6 All Products: License file—Specify where you copied license.lic on

your machine.

The installer will copy the license file to this directory:

<topdir>\common\license. If you do not yet have a license file,
continue with the installation, copy the license file to that directory
when you get it, and then set the environment variable
JASONLM_LICENSE_FILE (page 85).

Tip: If you do not yet have your license file and do plan to use a local license server,
you can get the installer to configure a license service and set the
JASONLM_LICENSE_FILE by entering the default path to the license file:
<topdir>\common\license. Later when you get the license file, simply copy it
to this directory.

7 Click Install.

8 Test the installation by launching each PowerLog application you

installed:

• Click Start > All Programs > CGG GeoSoftware > PowerLog
9.0 and select the application.

• When you launch PowerLog for the first time, log in as

Administrator (no password) even if you had selected the
option to login with your Windows ID.

Note: If you installed PowerLog with a user account that does not have administrator
privileges, you get a message stating that the active database is not set. Simply
click the Database button in the login dialog box; then click Connect to a
different DB on this computer and specify the location where you created the
database.

GeoSoftware

Perform the following steps to install the GeoSoftware Suite. You can
install any combination of applications that you want.

GeoSoftware Installation Guide

 Installing the applications 35

Note: Before you can install additional Jason software, you must uninstall PowerLog
if it were installed as a standalone application and without the GeoSoftware
launcher. You can reinstall PowerLog, along with other applications, with
GeoSoftware Suite installer.

Important: Install all available Windows updates. The installer may fail if the
necessary updates are not in place.

1 Double-click the setup executable to launch the installer:

GeoSoftwareSuite9.0.exe.

The installer checks for Microsoft.net Framework 3.5 on your

computer. If it is not found, the installer installs it, and you are
prompted to reboot. If the installer does not reappear automatically
after the reboot, double-click GeoSoftwareSuite9.0.exe to restart it.

2 Follow the on-screen instructions to install the software.

3 Setup Type—Select between Complete and Custom setup.

4 Custom Setup—On the Custom Setup page, select the products and
features you want to install:

Component Description
GeoSoftware 9.0.0 Installs the GeoSoftware Suite of applications.
EarthModel FT 9.0.0 Installs the EarthModel FT application.
Jason Workbench 9.0.0 Installs the Jason Workbench application.
PowerLog 9.0.0 Installs the PowerLog application.
Database Management 9.0.0 Installs a database server and Database Management. Used for
network installations of PowerLog or to install server
components on another machine. It automatically installs on
your machine.
Project Management 9.0.0 Installs Project Management that manages GeoSoftware
projects. Used for backing up, fixing, and restoring projects. It
automatically installs on your machine.
Sample GeoSoftware Project 9.0.0 Creates a sample project associated with the sample database. If
you have a sample project already installed, you need to delete it
from Windows Explorer.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

36 Installing the applications

5 Enable MCPU—This page always appears when you are installing

on a 64-bit system. The MCPU feature is used only with Jason
Workbench and requires a special license.

• If you are not going to be using a network of machines to

process computationally intensive jobs, click Next.

• If you want to enable a MCPU environment, do as follows:

– Check Enable MCPU for this installation.

– Click Add Host, and list the machines that will be allowed to
send jobs to this worker (that is, the MCPU masters). Use the
true machine names, not the alias names.

Note: If you choose to not install the Sample GeoSoftware Project, the installation
screens will not be displayed for the database folder or sample GeoSoftware
project.

6 Database folder—Specify the location where you want the database

created.

• The installer will not overwrite or delete an existing database

named sample.fjdb. If you want to install a new database,
change to a different directory or delete the existing database
from Windows Explorer.

• The full path, including database initiation filename, cannot

exceed 200 characters.

• The default directory is accessible only to you. If you want to

allow others access, specify a different directory.

• If you want to login with your Windows ID and bypass the

PowerLog login, select the checkbox Automatically login into
database/project with current Windows user ID. Your
password is not stored within PowerLog; only your login name
is saved.

7 GeoSoftware Sample Project—Specify the location where you want

the sample project installed.

• The installer will not overwrite or delete an existing project. If

you want to install a new database, change to a different
directory or delete the existing project from Windows Explorer.

GeoSoftware Installation Guide

 Installing the applications 37

• The default directory is accessible only to you. If you want to

allow others access, specify a different directory.

8 All Products: License file—Specify where you copied license.lic on

your machine.

The installer will copy the license file to this directory:

<topdir>\common\license. If you do not yet have a license file,
continue with the installation, copy the license file to that directory
when you get it, and then set the environment variable
JASONLM_LICENSE_FILE (page 85).

Tip: If you do not yet have your license file and do plan to use a local license server,
you can get the installer to configure a license service and set the
JASONLM_LICENSE_FILE by entering the default path to the license file:
<topdir>\common\license. Later when you get the license file, simply copy it
to this directory.

9 Click Install.

10 Test the installation by launching each application you installed:

• Click All Programs > CGG GeoSoftware > GeoSoftware

Launcher 9.0.

• Open each application from the launcher.

• When you launch GeoSoftware for the first time, log in as

Administrator (no password) even if you had selected to login
with your Windows ID.

Note: If you installed PowerLog with a user account that does not have administrator
privileges, you get a message stating that the active database is not set. Simply
click the Database button in the login dialog box; then click Connect to a
different DB on this computer and specify the location where you created the
database.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

38 Installing the applications

11 Complete additional setup tasks for each product you have installed:

EarthModel FT Optional—Install the Petrel plug-in (page 42).

Optional—Install the OpenSpirit Satellite (page 45).
Jason Optional—Install the Petrel plug-in (page 42).
Workbench
Optional—Change the location of the cache directory for
3D View (page 46).
If the machine is part of a MCPU environment, complete
the MCPU configuration (page 63)
Optional—Customize which color scales are applied when
displaying various types of data (page 47).
PowerLog If you installed the Petra link locally, but the Petra server
resides on a remote machine, copy pserver.exe to the Petra
server installation directory and register the executable
manually.
If you are installing PowerLog 9.0 for the first time, create
database user accounts (page 57).
Optional—Schedule automatic database backups
(page 62).

Important: If you use a separate, central license server (which does not have Jason
software installed) and you are upgrading from Jason Workbench 8.2 or an
older version, you need to update the license daemons on the license server.
Run the installer on the license server machine, and select only Local License
Server for installation.

GeoSoftware Installation Guide

 Configuring the Petra link (PowerLog) 39

Configuring the Petra link (PowerLog)

PowerLog 9.0 installs the PetraPortal as part of the installation process,

however, the interface between the PowerLog and Petra installations
may need to be manually configured.

For information regarding Petra installation procedures, refer to

documentation by the Petra distributor.

Configuration for Petra Versions Prior to 4.0

To communicate with Petra databases before the 4.0 version, the

pserver.exe must be installed in the Petra installation directory as done
previously. Now, however, two versions of pserver.exe are required in
the Petra installation directory: 32-bit and 64-bit. This is because
previous versions of PowerLog are 32-bit and PowerLog 9.0 is 64-bit.

The pserver.exe files can be found as follows:

• The 64-bit version is located in the bin folder of the PowerLog

installation directory.

• The 32-bit version is located in the bin\win32 folder of the

PowerLog installation directory.

You must copy the same pserver.exe to the Petra installation directory
as the same bitness as the Petra installation components. All Petra
installations before 4.0 are 32-bit even when the target host is 64-bit.
This bitness issue is the only operational difference in PowerLog 9.0
installations as compared to earlier installations.

Configuration for Petra 4.0 and above

Pserver.exe is not required for installations of Petra 4.0 and above.

Only PetraPortal.config is required. There is no automated mechanism;
the configuration file must be manually added via text editing.

Below is an example of a PetraPortal.config file that is very similar to

the installed PowerLog 9.0 component.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

40 Configuring the Petra link (PowerLog)

The only time the PetraPortal.config file needs to be modified is when

the following occurs:

• The PowerLog user intends to employ the PetraPortal in her

workflow.

• The PetraPortal will communicate with an installation of Petra 4.0

or higher.

• An endpoint is changed.

GeoSoftware Installation Guide

 Configuring the Petra link (PowerLog) 41

• A new endpoint needs to be added.

Note: Our Petra test bed does not support enough licenses to test a multiple endpoint
configuration.

There are only two fields in the PetraPortal.config file example that are
critical to modifying an endpoint:

• address
• servicePrincipalName

To change the address of an endpoint, replace 172.17.130.139:8000

with the host address and designated port number of the
PetraDBService to which PowerLog’s PetraPortal will connect.

PetraDBService is an optional Petra installation component. In order

for PowerLog’s PetraPortal to function, the PetraDBService must be
installed on the host where Petra is installed.

To change the servicePrincipalName in the above PetraPortal.config

example, replace DAL-PETRA01.int.Jason.com with the applicable
host name that corresponds to 172.17.130.139 in the example above.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

42 Installing Petrel plug-ins (Jason Workbench, EMFT)

Installing Petrel plug-ins (Jason Workbench, EMFT)

Plug-ins are available for both Jason Workbench and EMFT that allow
the exchange of data between the Jason application and a local Petrel
installation. Installers for these plug-ins are separate from the
GeoSoftware Suite installer and can be found on the DVD (in the
“petrel” folder) or obtained from your local Jason support
representative.

1 Launch Petrel.

2 Select Help > Ocean Plug-in Manager.

3 Locate the appropriate installer for the Petrel version you have:

Filename For Petrel

EMFT_PetrelPlug2012.pip 2012 64-bit
EMFT_PetrelPlug2013.pip 2013 64-bit
EMFT_PetrelPlug2014.pip 2014 64-bit
JGW_PetrelPlugin2012.pip 2012 64-bit
JGW_PetrelPlugin2013.pip 2013 64-bit
JGW_PetrelPlugin2014.pip 2014 64-bit

4 Double-click the .pip file to launch the installer, and select Install.

Using the plug-in

The plug-in appears as a set of processes in Petrel. Detailed instructions

for running the plug-in can be found in the EMFT and Jason
Workbench online help. The basic steps are summarized below.

1 Launch Petrel.

2 Open the Petrel project you want to export data from or import data
to.

GeoSoftware Installation Guide

 Installing Petrel plug-ins (Jason Workbench, EMFT) 43

3 In the Processes panel, expand the EMFT Plugins node or Jason

Workbench Plugins node, and select the desired action, export or
import.

Note: The Jason Workbench-Petrel plug-in is not loaded unless a valid Jason license
is detected. The EMFT-Petrel plug-in does not require a Jason license.

Licensing & plug-ins

You do not need a Jason license to run the installer and install the Petrel
plug-in. Nor do you need a license to run the EMFT-Petrel plug-in.
However, a Jason license is required to run the Jason Workbench-Petrel
plug-in; and if one is not detected, the plug-in is not loaded when Petrel
is launched. Of course, to examine or use the imported data within
EMFT or Jason Workbench you must have the appropriate Jason
license.

Here are three possible scenarios to consider:

• EMFT plug-in—A Jason license is not required. The plug-in is run

from within Petrel and can be used to import data from an existing
EMFT project or to export data to and create a new EMFT project.
Conceivably, a user could run the EMFT plug-in on one machine,
perform an export, and give the exported EMFT project to another
user who has EMFT installed.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

44 Installing Petrel plug-ins (Jason Workbench, EMFT)

• Jason Workbench plug-in on a machine where Jason Workbench is

installed—This is the usual case. The JASONLM_LICENSE_FILE
environment variable points to a license on the local machine, the
license is detected when you launch Petrel, and the plug-in is loaded
into Petrel.

• Jason Workbench plug-in on a machine where Jason Workbench is

not installed—This situation occurs when you are working in an
environment where Petrel is installed on one machine and Jason
Workbench projects are accessible via the network. Set the
JASONLM_LICENSE_FILE variable on the Petrel machine and
point it to a valid Jason license server.

Uninstalling the plug-in

Follow the instructions below to uninstall the Petrel plug-in. It will be

listed as Jason Plugin Petrel <version> or EMFT Plugin Petrel
<version>.

1 Launch Petrel.

2 Select Help > Ocean Plug-in Manager.

3 Click on the Jason or EMFT plug-in you want to remove, and select
Uninstall.

GeoSoftware Installation Guide

 Installing the OpenSpirit Satellite (EMFT) 45

Installing the OpenSpirit Satellite (EMFT)

If you want to import project data from third-party data sources using
an OpenSpirit 3.2 server, you must install the OpenSpirit 3.2 satellite
and configure it to connect to an OpenSpirit 3.2 server. You must also
apply a Microsoft Visual Studio 2010 C++ hotfix.

EMFT 4.4 runs with the OpenSpirit 3.2 server and satellite only. It does
not run with previous versions of the OpenSpirit server and satellite
(since they are no longer supported by OpenSpirit).

You must have the following information to install the satellite:

• host ID of the OpenSpirit 3.2 server

• port used by OpenSpirit 3.2 on the server
• path to the local executable of the browser to be used by the
OpenSpirit satellite

The files for installing the OpenSpirit satellite are located in a separate
OpenSpirit directory, which can be found on the GeoSoftware Suite
installation DVD or obtained from your local Jason support
representative.

1 Locate the Windows version of the OpenSpirit Installer-v3.2.2.md5

installer.

The installer name is OSP322rt_Win.exe. This installer can install

the OpenSpirit satellite on either 32-bit or 64-bit systems.

2 Launch the OpenSpirit v3.2.2 Runtime Installation wizard.

3 Follow the on-screen instructions to install the satellite.

4 Click Done to close the OpenSpirit v3.2 Runtime Installation

wizard.

5 Locate the DevKit_3.2_HF01-runtime.zip, which will be included

in the OpenSpirit installer directory.

This .zip file contains a hotfix that applies Microsoft Visual Studio
2010 C++ support to the TIBCO OpenSpirit v3.2.3 Windows
Runtime. It includes 32-bit and 64-bit libraries.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

46 Setting up the cache directory (Jason Workbench)

6 Read the contents of the RUNME_RUNTIME.txt file that also

appears in the OpenSpirit installer directory.

This file describes the purpose and install procedure for the contents
of the .zip file.

7 Unzip the DevKit_3.2_HF01-runtime.zip into the top level folder of

the OpenSpirit v3.2.3 Windows Runtime installation that you
performed in step 3 (above).

Setting up the cache directory (Jason Workbench)

To enhance performance of 3D View, representations of the models that

are displayed are stored locally on disk. When you install Jason
Workbench, a cache directory for this purpose is in the following
location: C:\ProgramData\Jason\view3d_cache

You may want to change the cache location to another drive rather than
risk filling up the C drive. The drive you designate must be local,
although it can be an attached external drive. It should have at least
1 GB of free space. We recommend using a fast drive, such as an SSD.

The procedure is as follows:

1 Set the environment variable JG_CACHEDIR to the directory you

prefer.

• In the Start menu, right-click Computer and select Properties.

• Click Advanced system settings.
• In the Advanced tab, click Environment Variables.
• Under System Variables, click New.
• Enter the variable name and the desired directory.

2 Open 3D View.

3 Select Tools > Set Cache Directories.

4 Define the location for the main cache directory.

Subdirectories for each project are created when you work with the
project in 3D View. Optionally, you can create project cache directories
in other locations (not under the main cache directory) by checking
Override in the Cache Directories dialog box and setting the path.

GeoSoftware Installation Guide

 Customizing the default color scales (Jason Workbench) 47

Note: All files in the cache directory that have not been modified in the last seven
days are removed automatically when 3D View is started.

Customizing the default color scales (Jason Workbench)

The color scales that are used by default when data are displayed in a
Jason Workbench viewer are defined in the class-mapping.ri file, which
is located in <instdir>\etc\colorscales. You can edit this file to set your
own custom defaults.

Keep in mind how the file is implemented: For a given data type, the
file is read until a class containing the type is found. The associated
scale is then used as default for that type. Hence, classes must be
ordered from specific to general; the class “all” must be present, and
must be the last class in the file. A simplified example is shown below.

class_mapping:dict[5]=
{
class:string="none";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="waves";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="time_frequency";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="depth_frequency";
color_scale:string="red_white_dkblue.shs";
},
{
class:string="_class_all";
color_scale:string="rainbow.shs";
};

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

48 Uninstalling

Uninstalling

There are two methods to uninstall Jason applications, depending on

what you are uninstalling. You can uninstall a version of PowerLog
without the launcher or you can uninstall all or part of the GeoSoftware
Suite.

PowerLog

Follow this procedure if you are uninstalling PowerLog without the

launcher. You can uninstall or modify PowerLog, Database
Management, and License Tools.

Use the Windows Programs and Features option to uninstall all or

part of the GeoSoftware Suite.

• To uninstall all of PowerLog, right-click PowerLog 9.0 Standalone

from the list of installed programs, and click Uninstall.

• To uninstall the individual PowerLog application or features, do as

follows:

– Double-click PowerLog 9.0 Standalone from the list of

installed programs, and click Uninstall.

– Click Change.

– In the Program Maintenance page of the installer, select

Modify.

– In the Custom Setup page, deselect the program and features

you want to uninstall.

– Click Install.

GeoSoftware

Use the Windows Programs and Features option to uninstall all or

part of the GeoSoftware Suite. A single listing, CGG GeoSoftware
Suite encompasses all Jason applications.

• To uninstall all Jason applications, right-click GeoSoftware Suite

9.0 from the list of installed programs, and click Uninstall.

GeoSoftware Installation Guide

 Uninstalling 49

• To uninstall individual Jason applications, do as follows:

– Double-click GeoSoftware Suite 9.0 from the list of installed

programs, and click Uninstall.

– Click Change.

– In the Program Maintenance page of the installer, select

Modify.

– In the Custom Setup page, deselect the programs and features

you want to uninstall.

– Click Install.

Chapter 3: Local Installation on Windows (GeoSoftware, Jason Workbench, EMFT, PowerLog)

50 Uninstalling

GeoSoftware Installation Guide

 51

CHAPTER 4

Network Installation on Windows

(GeoSoftware and PowerLog)
Both GeoSoftware and PowerLog can be run in a distributed
configuration, with GeoSoftware or PowerLog on the local machine
and the other components on remote machines.

In this multi-user scenario, the license server is installed on one

computer, the database is installed on another computer, and the
application is installed on multiple client machines. All clients must
have network access to the machines hosting the license server and the
database. You need not use this database, however, and can easily
connect to the database on the remote host.

In addition, a single database lock server is installed to manage

concurrent access to objects in the database by granting or refusing
locks to requesting applications. Obtaining a lock prevents multiple
concurrent transactions from performing incompatible operations on
the same data. The database lock server is usually installed on the same
computer as the database; however, if you are using network shares, the
lock server and database may be installed on different machines.

On Windows 7, you will need to log on and run the installer with a user
account that has administrator privileges. If you attempt to install either
GeoSoftware or PowerLog with an account that does not have
administrator privileges, you are prompted to supply credentials for
such an account. From that point on, the installer configures everything
for this user. Specifically, the default location for creating the
GeoSoftware or PowerLog database is set to the administrator’s
directory, not to yours. Do not accept the default; specify the directory
you want.

Chapter 4: Network Installation on Windows (GeoSoftware and PowerLog)

52 Verifying the license server

Verifying the license server

After you have installed either GeoSoftware or PowerLog, you will

want to verify the license server was installed. Perform the following
steps on the machine that will host the license server.

1 Check the license server:

• Double-click lmtools.exe, which is found in

\Program Files\CGG GeoSoftware 9.0\license.

• Select the service called JasonFLEXnetService.

• Click the Server Status tab.

• Click Perform Status Enquiry and check the report.

2 If the license service is not running properly, try the following:

• Check that license.lic was copied to \Program Files\CGG

GeoSoftware 9.0\license. If not, copy it there manually.

• Open the license.lic file and make sure the SERVER line
specifies the current machine.

• In the lmtools utility, click the Start/Stop/Reread tab, and stop

and then restart the license service.

GeoSoftware Installation Guide

 Confirming the database (AMS) 53

Confirming the database (AMS)

Both GeoSoftware and PowerLog support a multi-user environment in

which users access a shared database across a network and can work on
the same data simultaneously. By default, access to the remote database
is provided via Objectivity's Advanced Multithreaded Server (AMS).
Conventional network shares are supported, but not recommended.

For AMS to work, the database lock server must reside on the same
machine as the database. The lock server is installed when you install
the database software. Database Management is also installed with the
database; you do not need a GeoSoftware or PowerLog license to run
Database Management.

Important: The full path to the database, including the name of the database
initiation file, cannot exceed 200 characters.

To confirm the database (AMS) has been installed, perform the

following steps on the machine that will host the database.

1 To verify that the project manager was installed successfully, launch

Project Management.

• From the Start menu, select All Programs > CGG

GeoSoftware> Tools > Project Management.

• Close the dialog box.

2 To verify that the database was created successfully, launch

Database Management.

• From the Start menu, select All Programs > CGG

GeoSoftware> Tools > Database Management.

• From the Create & Manage DB tab, click Show Info.

3 Create a user account for each person who will be using the
database. See page 57.

Note: An Administrator account with no password is provided simply to get you

started. For security reasons, you should immediately assign a password to this
account See page 57 for instructions.

Chapter 4: Network Installation on Windows (GeoSoftware and PowerLog)

54 Verifying the database (network share)

Verifying the database (network share)

By default, connection to a remote database is provided via

Objectivity’s Advanced Multithreaded Server (AMS). However, if you
wish, you can host the database on a Windows shared directory or an
embedded network-attached storage (NAS) device. Some additional
setup is required for this approach, and some degradation in
performance can be expected.

Because an NAS device usually runs on an embedded operating system

and does not allow installation of software, the database lock server
must be installed on another machine. The drawback of this
arrangement is that if the machine with the lock server is not running,
no one can access the database.

Important: The full path to the database, including the name of the database
initiation file, cannot exceed 200 characters.

To create a database on a network share, do as follows:

1 Create a shared directory on a Windows machine or NAS device.

2 Set permissions for users to access the shared directory.

3 Install either PowerLog without the launcher or the GeoSoftware

Suite.

4 On the machine where the lock server is installed, set the

environment variable FJ_ALLOW_NETWORK_SHARE to 1.

• Right-click Computer in the Start menu, and select Properties.

• Click Advanced system settings.
• In the Advanced tab, click Environment Variables.
• Under System Variables, click New.
• Enter the variable name and a value of 1.

GeoSoftware Installation Guide

 Verifying the database (network share) 55

5 Configure the database lock server:

As installed, the lock server typically runs under the local account
of the machine administrator. To access a database on a network
share, the lock server must run under a network account with full
read-write permissions.

• Open Administrative Tools in the Control Panel, and select

Services.

• Right-click the ools-13 service and select Properties.

• In the Properties dialog box, click the Log On tab.

• Select This account and provide the credentials of a user with

read-write permissions for the shared directory.

6 On the machine where the lock server is installed, launch Database

Management, and do as follows:

• In the Create and Select tab, click Create a database, and

create a database on the network share. The full path, including
database initiation filename, cannot exceed 200 characters.

• In the Manage Users and Projects tab, create a user account for
each person who will be using the database. See page 57.

For more information on Windows shares and Windows services,

consult Microsoft’s online documentation for your particular operating
system.

Chapter 4: Network Installation on Windows (GeoSoftware and PowerLog)

56 Verifying the database (network share)

GeoSoftware Installation Guide

 57

CHAPTER 5

Configuring the GeoSoftware and PowerLog

installation
If you are installing either GeoSoftware of PowerLog 9.0 for the first
time, there are a few configuration tasks you need to perform. These
can be grouped into four categories:

• creating user accounts

• creating data all users can access (for example, curve alias tables)
• creating default and predefined screens for all users
• scheduling automatic database backups

Creating user accounts

An Administrator account (no password) is provided to get you started.

For security reasons, you should immediately assign a password to this
account. You also need to create a user account for each person who
will be using the database. Letting multiple people log into a project
with the same user account is not advisable and could degrade
performance.

Tip: If you plan to create default or predefined screens for formatting computation
modules and viewers, you may want to wait to create new users until after the
screens are ready. Global default and predefined screens are automatically
promulgated to new users the first time they log into GeoSoftware or
PowerLog.

Chapter 5: Configuring the GeoSoftware and PowerLog installation

58 Creating user accounts

1 Select Start > All Programs > CGG GeoSoftware > Database
Management.

2 Assign a password to the Administrator account:

• Click the Users and Project Management tab.

• Click Manage Users.
• Log in as Administrator (no password).
• In the list of users, double-click Administrator.
• Enter and confirm a password for this account.

3 Click Add User.

A row is add to the table.

4 Enter a User Name for the account. Optionally, also enter the user's
Full Name and a Description.

5 Set authentication controls by choosing either of these options:

• Use OS User Name to Log in—If this option is checked, the

user's operating system login is used for authentication when he
launches GeoSoftware. He is not asked to enter a GeoSoftware
user name and password.

• Password—If you did not select the OS user name option, set an
initial password for the user. He will be asked to enter his user
name and password when he launches GeoSoftware.

6 Grant the user access to one or more projects, using either of these
techniques:

• Same role in all projects—Click the checkbox for the user; then
select Set <desired_role> role for all projects from the dropdown
list at the bottom of the dialog box.

• Different roles in different projects—Select the project from the

dropdown list at the top of the dialog box; then double-click in
the Project role field to select the role.

• The following roles are supported:

None—User does not even see the project in lists of available

projects. This is the default setting.

GeoSoftware Installation Guide

 Creating user accounts 59

Browser— User has read-only access; he can view project data

but cannot create or edit data.

Interpreter—User has read-write access; he can view, create,

and edit project data. He cannot edit data associated with another
user (such as top picks).

Manager—User has read-write access to all project data,

including all data associated with individual users. He can grant
other users access to the project.

7 Check Access to Current User's Data to allow the user to see the
user settings you have created (curve alias tables, curve settings
tables, color maps, fill patterns, etc.).

8 Check Admin if you want the new account to be a database

administrator.

See the online help for more information. Project roles are briefly
described below:

• Project manager—Has read/write access to all project data. Can edit

user data (such as top picks) created by anyone.

• Interpreter—Can view, edit, and create project data. Can edit user
data only if he created it.

• Browser—Can only view project data. Can create only limited types
of user data (such as curve alias tables).

Chapter 5: Configuring the GeoSoftware and PowerLog installation

60 Creating standard data

Creating standard data

In GeoSoftware and PowerLog, certain types of data are associated

with the user who creates them, including curve alias tables, default
settings for displaying curves, color maps, and fill patterns. If you want
to provide company standards for these data types, you can create them
as an administrator and then distribute them to all users via the User
Settings Explorer. See the online help for instructions.

Creating default & predefined screens

Several default screens and predefined screens are supplied when you
install PowerLog, and these screens are available to GeoSoftware and
PowerLog users. Several default screens and predefined screens are
supplied when you install PowerLog.

In PowerLog, screens are templates that store the setup for a

computation module such as MathPack or for a viewer such as Logplot.
Default screens are applied when a user opens a module for the first
time for a given well. Predefined screens are a library of screens that
users can apply at their discretion.

You can add to or edit these screens and promulgate your changes or
additions to all users, as described below.

1 Launch PowerLog and log in as Administrator.

2 Create default screens:

• For each template, set up the module or viewer as you want it.
• Select Screens > Save Screen or File > Save Screen.
• Save the screen to the Global Defaults folder and name it
Default.

All default screens must be named “Default.” They are

distinguished by the module type. There can be only one default
screen for each module.

GeoSoftware Installation Guide

 Creating default & predefined screens 61

3 Create predefined screens:

• For each template, set up the module or viewer as you want it.

• Save the screen to the Predefined Screens folder. You can name
it whatever you like.

4 Distribute the screens you just made to all users:

• Distribution to new users is automatic. When a new user logs

onto PowerLog for the first time, all screens in the Global
Defaults and Predefined Screens folders are copied to his
personal Default Screens and Predefined Screens folders (under
Users).

• Distribution to existing users requires that you export the new

screens from the global folders and import them into the user’s
personal folders.

– Select File > Screens Explorer.

– Click View Multi-User to display all users’ folders.

– Select the new screens in Global Defaults; right-click and

select Export Screens.

– Select the new screens in Predefined Screens; right-click and

select Export Screens.

– Give users the exported files, and tell them to import the
screens into their personal Default Screens and Predefined
Screens folders.

Chapter 5: Configuring the GeoSoftware and PowerLog installation

62 Scheduling database backups

Scheduling database backups

You can schedule automatic backups of the database using the

DatabaseManagementCmd executable and the Windows Task
Scheduler.

DatabaseManagementCmd.exe is located in the Jason binaries

directory. (The default location is C:\Program Files\CGG
GeoSoftware 9.0\bin.) The command syntax is

databasemanagementcmd -database <“DB_path”> -user <user_name>

-password <password> -backup <backup_directory>

where
DB_path = full path to the database initiation file, in quotes
user_name = name of a user with Administrative privileges on the
specified database
password = password for the specified user. To indicate an empty
password, use double quotes: “ ”
backup_directory = directory where the backup should be stored. The directory
should already exist.

As an example, to back up the database C:\DB\Sample.fjdb to

C:\Backups as user Administrator (no password), you would use the
following command:

databasemanagementcmd -database “C:\DB\Sample.fjdb”

-user Adminstrator -password “” -backup C:\Backups

To execute the backup command at a regular interval, create a task that

defines the time trigger for this executable action. See the Task
Scheduler documentation for information: http://msdn.microsoft.com/
en-us/library/aa383614%28v=vs.85%29.aspx.

GeoSoftware Installation Guide

 63

CHAPTER 6

Configuring the MCPU Environment (Jason

Workbench)
The Jason Workbench can be run in a MCPU environment, thus
enabling large computational jobs to be processed quickly by using the
aggregate power and memory of many computers. The heterogeneous
network of computers functions as if it were a single large parallel
computer. The MCPU worker nodes are used to process
InverTraceBasic, InverTracePlus, RockTrace, StatMod MC, and
RockMod jobs, all of which can be run in parallel mode.

Jason’s implementation of MCPU is based on PVM (Parallel Virtual

Machine) (http://www.epm.ornl.gov/pvm/pvm_home.html). A native
scheduler is provided; however, you can also chose to use the IBM
Platform LSF external scheduler.

Requirements

Review the following requirements and recommendations before

configuring your MCPU environment:

• A special MCPU license is required.

• Any combination of Linux and Windows machines can be used.

• The speed difference between the fastest and slowest CPU in the
network should be less than 50%.

• The maximum amount of memory available for any process is

determined by the worker machine with the least amount of
memory. Having six workers with 2 GB available and two workers
with 1 GB will usually lead to a longer overall runtime than having
only six workers with 2 GB of memory.

Chapter 6: Configuring the MCPU Environment (Jason Workbench)

64 Linux installation

• The worker nodes access their input data over the network (using
NFS or CIFS) and, therefore, benefit from having a high-speed,
low-latency network (GigE or better).

For additional information, see the Jason Workbench online help,

which has a section on MCPU, data location, and setup.

Linux installation

The steps required to make MCPU available on your Linux

workstations are as follows:

1 Check that ALL computers you want to use in the MCPU network
meet the following requirements:

• The user must have an identical home directory, login shell,

user ID, and group ID on each computer.

• The home directory must be accessible by the same directory

path and must be on the same physical disk.

• The Jason Workbench software installation must be accessible

by the same directory path and must be on the same physical
disk.

• The Jason Workbench project data directory must be accessible

by the same directory path and must be on the same physical
disk.

• Name resolving needs to be set up for your network. That is, for
all hosts you want to use as master or workers, the nslookup
command should return the correct IP address.

The best way to satisfy all these requirements is by using NIS

(yellow pages) in combination with the automounter. Please see the
applicable sections of your OS documentation for more
information.

Note: Do NOT use /net/<hostname>/ to access remote directories. If it is used,

performance and operational problems will occur.

GeoSoftware Installation Guide

 Linux installation 65

2 For machines with RedHat Linux, edit the /etc/hosts file to avoid
problems with IP addresses.

• The hostname on a default RedHat installation is assigned to the

IP address 127.0.0.1. Any IP address that starts with 127.0.0 will
cause problems with the Jason Workbench software.

• To correct this hostname assignment, edit /etc/hosts:

– Remove the hostname from the line that starts with

127.0.0.1.

– Add the actual hostname association (unless you are using

DHCP).

– If there are other entries starting with 127.0.0.X remove the

hostname from those as well.

An example /etc/hosts file is shown below:

# Do not remove the following line, or various programs

# that require network functionality might will fail.
127.0.0.1 localhost.localdomain localhost
192.168.0.23 jason

Note: If your MCPU network consists of a mixture of Linux and Windows machines,
you must use remote shell (RSH) without a password for machine-to-machine
communication. Instructions for setting up remote shell follow.

However, if your MCPU network consists only of Linux machines, you can
use secure shell (SSH) without a password. And since SSH offers greater
security, using it when you can is preferable. See page 67 for instructions.

3 Enable all users to use remote shell without a password to start a

process on any of the MCPU workers:

• Create (or edit) the file .rhosts in the user's home directory. All
hosts to be connected from should be listed, one host per line.
Use the official hostnames, not aliases. An example of a .rhosts
file is shown below:

linux_ws1
linux_ws2
+

Chapter 6: Configuring the MCPU Environment (Jason Workbench)

66 Linux installation

• Disable access for other users:

chmod 600 .rhosts

• Ensure that the file is owned by this user:

ls -l .rhosts

• If necessary, change the owner:

chown <username> .rhosts

Note: The latest versions of RedHat and SuSE do not include the rsh client and server
packages by default. If these packages have not already been installed on your
machine, install them before proceeding to the next step.

4 Enable the RSH daemon on all hosts:

• On RedHat Linux, log in as root and enter these commands:

chkconfig rsh on
chkconfig rlogin on
/etc/init.d/xinetd restart

• On SuSE Linux, do as follows:

– Start yast.

– Select System Administration > Network configuration >

Configure network services.

– Enable xinetd, rsh, and rlogin services.

5 Test that remote shell is configured and operating correctly:

• Log in as a typical Jason user to a system where you want to

launch the MCPU job. Ensure that the .rhosts file is correctly
configured as outlined above.

• Run the following test: rsh <xxx> uptime

where <xxx> is one of the remote hosts on the list. This should
return the uptime of host <xxx> without asking for a password.

6 Verify that the installation is correctly configured:

• Start Jason Workbench, and select System > Unix Terminal

Window.
• Type: pvm -verify

GeoSoftware Installation Guide

 Linux installation 67

Using SSH (without a password) for MCPU

Remote shell (RSH) has inherent security weaknesses. Secure shell

(SSH) offers much of the same functionality but over a much more
secure communication channel and can use public/private keys instead
of passwords.

This section describes how to get SSH to use “password-less” logins

for your MCPU processing. This method is built into the Linux
infrastructure and is not a feature of the Jason software. Consequently,
Jason does not provide customer support for SSH-related issues.

Prerequisite

SSH must be installed on all machines that are to be used for MCPU.
Running PVM with SSH for Windows workers is not supported.

Setting up password-less SSH

To set up password-less SSH, do as follows:

1 Log in as the user who needs to run MCPU.

2 In ~/.ssh create a key pair if not already present.Type:

ssh-keygen -t dsa

3 When asked to supply filenames for the key pair, accept the
defaults.

4 When asked for a passphrase, leave the line empty and press return.
Do the same when asked for the phrase again.

Two new files are created: ~/.ssh/id_dsa and ~/.ssh/id_dsa.pub. The

first file is the private key; this should not be given to anyone (set
the permissions to 700). The second is the public part.

5 Log on the remote host using SSH, and do as follows:

• Change to the .ssh directory.

• Copy the contents of the public key into the authorized_keys2

file. If this file does not exist, create it.

• Exit from the remote login.

Chapter 6: Configuring the MCPU Environment (Jason Workbench)

68 Linux installation

6 Log on the remote machine again. This time you will not be asked
for a password.

7 Configure Jason Workbench for password-less SSH:

• Set the environment variable PVM_RSH to contain the full path

to SSH (for instance, setenv PVM_RSH /usr/bin/ssh).
This can be done in the users’ login scripts, rather than having to
set it each time.

• Run Jason Workbench and use as normal.

More information on SSH and password-less logins (including key

generation) can be found at these Web sites:

http://www.linuxjournal.com/node/4413

http://www-jcsu.jesus.cam.ac.uk/jcn/documentation/misc/
passwordless_ssh.html

Using an external scheduler

Jason’s implementation of PVM includes a native scheduler for

efficiently allocating processing tasks to workers. However, on Linux,
you can use an external scheduler to manage MCPU jobs.

The only external scheduler currently supported is the IBM Platform

LSF. When you use the LSF scheduler for batch jobs, you can specify
the number of processors needed for the job and choose the LSF queue
to which the job should be added. Thus, you are defining the priority of
the job.

LSF batch jobs are submitted by the customizable scripts

ParallelBatchPreSchedule and ParallelBatchPostSchedule, which can
be found in <instdir>/bin/machind. LSF in turn searches for the
appropriate machines to process the job. Which worker machines are
selected depends a lot on how you have configured your LSF cluster.

To enable all your users to use LSF as their external scheduler, do as

follows:

1 Open the file <instdir>/local/bin/machind/jwclient.csh.

2 Locate the following line: #unsetenv JG_USE_LSF.

GeoSoftware Installation Guide

 Linux installation 69

3 Beneath that line insert the following line:

setenv JG_USE_LSF true

On an individual basis, each user can enable LSF by setting the

environment variable JG_USE_LSF to true before launching Jason
Workbench.

Note: This discussion assumes that LSF has been correctly set up and configured for
your users. Setting up LSF is beyond the scope of this document.

Chapter 6: Configuring the MCPU Environment (Jason Workbench)

70 Windows installation

Windows installation

The steps required to make MCPU available on your Windows

workstations are as follows:

1 Ensure that name resolving is set up for your network. That is, for
all hosts you plan to use as MCPU masters or workers, the nslookup
command should return the correct IP address.

2 On all Windows machines to be used as MCPU workers, set up a

mapped drive to the network share where the project data directory
resides. This drive should be mapped to the same drive letter on all
workers.

3 Install Jason Workbench on each machine that will be used as an

MCPU worker. During the installation, do as follows:

• Select Enable MCPU option for this installation.

• Click Add Hosts and list the machines that can send jobs to this
MCPU worker (that is, list the acceptable MCPU masters). Use
the true machine names, not the alias names.

• Proceed with the installation as usual.

The list of master hosts that can access this worker machine is kept in
the C:\Windows\rhosts file. You can manually edit this file to grant
additional hosts access to this computer. Add new hosts, one line per
host.

Tip: You can set up all MCPU workers to use the same rhosts file. That way, you
have only one file to maintain to grant hosts access to all workers. See the
Jason Workbench online help for details.

Note: Due to the Windows security model, MCPU workers can only be started for
active users; that is, if a user wants to run workers on a Windows machine, he
needs to be logged in on that machine.

GeoSoftware Installation Guide

 Implementation details (Linux & Windows) 71

Implementation details (Linux & Windows)

This section contains information about how MCPU jobs are initiated
and processed.

How workers are located

When a user sets up an MCPU job, he can select from a list of available
worker hosts and, optionally, add additional worker hosts.

To create the list of available hosts, Jason Workbench tries to connect

to all computers listed as workers in the file <instdir>/local/etc/
pvm.hostfile. If a machine cannot be reached, a warning message is
given.

Next, on each host, the system checks if a pvm daemon is running for
the current user; if not, a pvm daemon is started.The system then tries
to connect to the pvm daemon.

Active user (Windows)

Due to the Windows security model, MCPU workers can only be

started for active users. That is, if a user wants to run workers on a
Windows machine, he must be logged in on that machine.

RSH daemon (Windows)

MCPU on Windows makes use of a Windows version of the RSH

daemon. This RSH daemon has been modified such that it can only be
used to start Jason MCPU jobs.

The RSH daemon is started when a user logs on to the computer and
stopped when the user logs off. The RSH daemon logs status
information is recorded in a file called C:\Windows\rshd.log

Note: This daemon is installed only when you choose the MCPU option during the
installation process. If this option is not chosen, MCPU will not work for this
computer.

Chapter 6: Configuring the MCPU Environment (Jason Workbench)

72 Implementation details (Linux & Windows)

Checking PVM (Linux)

If a user experiences problems when running with a Linux master and

Linux workers, you can check that PVM is correctly configured as
follows:

1 Log in as that user.

2 Start Jason Workbench, and select System> Open UNIX Terminal

Window.

Opening the terminal window from within Jason Workbench sets

the correct environment.

3 Type: pvm -verify

If PVM is not correctly configured, instructions on how to solve the

problem are displayed.

About PVM

The Jason Workbench installation contains the latest PVM distribution

(3.4.6), which is installed in <instdir>/3rdparty/Pvm3.

GeoSoftware Installation Guide

 73

CHAPTER 7

Licensing
Jason issues a single license file that covers all the Jason software
products and modules included in your contract with the company.
When you install a Jason product, the license manager software
(FlexNet 11.10) is also installed. On Linux systems, you have to do
some configuration of the license manager. On Windows systems,
configuration of the license manager is automated in most cases.

This chapter provides some background on Jason licensing and

provides instructions for requesting a license file, configuring the
license service, and starting/stopping the license manager. For
information on dealing with license problems, see page 91 in the
“Troubleshooting” chapter.

Important: The Jason license manager will not conflict with other applications that
use FlexNet and should be used for managing the Jason license. We strongly
recommend that you do NOT merge the Jason license file with other license
files.

Chapter 7: Licensing
74 Licensing basics

Licensing basics

This section defines key licensing terms and presents an example of a

Jason license file.

Terminology

Components of the license management system and terms used in this

chapter are described in the following table:

Component/Term Descriptions
license file An encoded file that tells the license manager how many copies of each Jason
module can be run at one time. It identifies the machine where the license manager
resides by hostname and host ID, the port number to be used in communicating
with the license manager, and the expiration date of the license.
Jason license files are named either license.dat (Linux) or license.lic (Windows).
license key A line in the license file that specifies how many instances of a particular module
or feature can be run simultaneously. All the license keys together with the host
information comprise the license file.
license server A machine that runs the FlexNet license manager services and serves licenses to
client machines.
license manager Software that keeps track of how many licenses are in use and grants or denies
license requests when a user tries to start the software. Jason uses FlexNet 11.10
license management software.
license daemon A process that runs on the computer whenever the license manager is running.
Jason has two daemons, jasonlm and lmgrd.

License file

Although you may have purchased a perpetual license, Jason issues

license keys for a maximum duration of one year. A new license file is
automatically sent to your company one month before the expiration
date of the current license.

Among other reasons, the one-year limitation on license files is

imposed to allow customers to change the license server periodically as
systems are upgraded without Jason personnel having to come on-site
to move the license.

GeoSoftware Installation Guide

 Licensing basics 75

As an example, a simplified Jason license file is shown below.

Example: Portion of a Jason license file

Chapter 7: Licensing
76 Licensing basics

The important points to note are these:

• SERVER line states the hostname and host ID of the machine where
the FlexNet license manager resides. The port number through
which the modules communicate with the license manager daemon
can also specified; or, if omitted as in this example, a default
FlexNet port (27000 to 27009) is used. The license files must be
installed on the machine indicated on the server line.

• DAEMON line specifies the name and path of the license daemon.
On Linux machines, the correct path is inserted in the license file
when you run the jgsetup script. On Windows machines, the path
can be omitted when the daemon is placed in the same directory as
the lmgrd.exe file (as is done by the Jason installer). You can edit
the path in the license file if necessary.

• INCREMENT lines contain the digital signatures for a licensed

feature or package. Information is listed in this order: (1) feature or
package name, (2) vendor daemon, (3) feature version, (4)
expiration date, (5) number of seats, and the digital signatures. For
PowerLog modules only, and the additional keyword BORROW is
included and indicates the number of hours license borrowing is
allowed.

• PACKAGE lines list all the features that are licensed under a
package name.

• Lines beginning with # are comments and are ignored by FlexNet.

If necessary, you can change the following:

• hostname on the SERVER line (but NOT the host ID)

• port number on the SERVER line
• path to the daemon on the DAEMON line

Important: Never set back the system date. The Jason license manager will detect
the change and prevent the Jason software from running. Even when you reset
the system date to the correct date, the software may not run. In that case you
may have to reload the complete operating system.

GeoSoftware Installation Guide

 Types of licenses 77

Types of licenses

Three types of licenses are available for use with Jason software. Some
require a license server; others do not. A license server is a machine
that runs FlexNet license manager services and serves licenses to client
machines. The license manager keeps track of how many licenses are in
use and grants or denies license requests.

• Keyless licenses, also referred to as floating or network licenses, are

used in combination with a FlexNet license manager. Licenses are
available to all client machines configured on the same network as
the license server.

For a single-user environment where the license is to be used on

only one machine, the license manager and Jason application must
be installed on the same machine.

• Security key licenses, also referred to as dongle or node-locked

licenses, are supported only for PowerLog. Dongle licenses are
locked to a particular dongle ID. If the dongle is plugged in, the
dongle driver is successfully installed, and a valid license is present,
you can launch PowerLog.

For a single-user environment, PowerLog supports the SafeNet

Sentinel SuperPro USB port dongle (black or purple dongle). No
FlexNet license manager or license service is required.

For a multi-user environment, PowerLog supports the. FlexID USB

port dongle (small green dongle). A FlexNet license manager is
required to serve licenses to the client machines. The license file
stipulates how many clients can access PowerLog features
simultaneously.

• Evaluation licenses are locked to a particular host ID, which can be

either a composite ID or a MAC address. These are single-user
licenses that expire after 30 days. A license manager is not required;
neither is a dongle.

Chapter 7: Licensing
78 Requesting a license file

Requesting a license file

You must obtain a Jason 9.0 license file for this release. Earlier Jason
licenses will not support the new versions of the software. However,
the Jason 9.0 license is backward compatible and will support previous
releases.The only exception is PowerLog 3.4.2. If you have a
PowerLog 3.4.0 license and do not run any other Jason software, you
can upgrade to PowerLog 3.4.2 without obtaining a new license.

All Jason products can be run with keyless licenses (also referred to as
floating or network licenses), which are used in combination with a
FlexNet license manager. To request a license file, you must provide
the hostname and host ID of the machine that will serve as the license
manager.

Security key licenses (dongle licenses) are also supported for

PowerLog only. If you use dongle licensing for PowerLog, the
dongle ID is specified in the license file. Hostname and host ID are not
required.

For a Linux machine

To request a license for a Linux workstation, do as follows:

1 Determine the hostname and host ID of the machine that serves as

the license manager, using any of these techniques:

• Enter the following commands:

hostname -s
/sbin/ifconfig -a

The second command returns the hardware address (HWaddr) of

the machine. Remove the colons from the HWaddr to provide
the host ID. For example, a HWaddr of 00:40:05:16:E5:25
becomes a host ID of 00400516E525.

• If you have an earlier version of Jason Workbench installed,

change to the license directory, and enter this command:

./jlmhostinfo

GeoSoftware Installation Guide

 Requesting a license file 79

• If you have already run the installer to install the new version, do
as follows:

– Change to the Jason Workbench installation directory: cd

<instdir>
– Enter this command: ./jgsetup
– Select option 4, Query license manager host
information.

2 Send an email with the hostname and host ID to

[email protected].

For a Windows machine

The procedure is slightly different, depending on whether you plan to

keyless licensing (supported for all Jason products) or dongle licensing
(supported only for PowerLog).

Windows keyless license

Follow these instructions if you plan to use keyless licensing.

1 Locate a copy of JasonPreInstall.exe, which can be found on the

installation DVD or obtained from your local Jason support
representative.

2 Run JasonPreInstall.exe on the machine where you plan to install

PowerLog.

3 Email the output file, JasonPreInstallOutput.txt, to

[email protected] to request a license file.

Windows dongle license (PowerLog only)

Follow these instructions if the only Jason product you are installing is
PowerLog and you plan to use a security key.

1 If you are a new PowerLog customer, the following applies:

• A dongle is shipped to you when you purchase the software.

• When you receive the dongle, email [email protected] to

request a license file.

Chapter 7: Licensing
80 Requesting a license file

2 If you are an existing PowerLog customer, the following applies:

• If you are currently using a parallel port dongle, request a USB

port dongle from Jason. Parallel port keys are no longer
supported.

• When you are ready to upgrade to PowerLog 3.4, email

[email protected]. Include a copy of your PowerLog 3.x
or 2.x license.

3 Make sure that you have installed the latest version of the dongle
driver before plugging in the dongle. You can get drivers from the
following sources:

• Rainbow Sentinel SuperPro USB port dongle:

http://www2.safenet-inc.com/support/tech/latestdriver.asp

• FlexID USB port dongle:

Can be downloaded from the Jason FTP site. Contact your local
Jason support representative for information.

GeoSoftware Installation Guide

 Configuring the license manager 81

Configuring the license manager

Your license file is sent to you by email. The procedure for installing
the license file and configuring the license manager varies for the
different operating systems.

Important: If you use a separate, central license server (which does not have Jason
software installed) and you are upgrading from Jason Workbench 8.2 or an
older version, you need to update the license daemons on the license server.

On Linux—Copy new versions of jasonlm.exe and lmgrd.exe from a machine

where you installed the Jason products to the license server.

On Windows—Run the installer on the license server machine, and select only
Local License Server for installation.

On Linux workstations

When you run the install script to install Jason Workbench, the license
manager software is installed in <instdir>/license. You can then install
the license file and enable the license manager as outlined below. For
detailed instructions, see page 15 in the chapter “Installing on Linux
(Jason Workbench).”

1 Rename the license file you receive via email license.dat.

2 Copy license.dat to <instdir>/license.

3 Run the setup script <instdir>/jgsetup, and select option 1,

Configure the installation.

Running this script sets the path to the license daemons in the
license.dat file.

4 Stop and then restart the license manager daemon.

Chapter 7: Licensing
82 Configuring the license manager

On Windows workstations

The Windows installer always installs the FlexNet license manager

software in <topdir>\common\license. Depending on the content of
your license file, the installer may also perform other functions:

• If the host ID listed in the license file is the same as that of the local
machine, the installer will configure a license service, copy the
license file to <topdir>\common\license, and set the environment
variable JASONLM_LICENSE_FILE.

• If the host ID in the license file is not the same as that of the local
machine, the installer assumes the host ID refers to a remote license
server and sets the variable JASONLM_LICENSE_FILE to point to
that host ID. No local license service is configured.

• If you have a dongle license (supported for PowerLog only), no

license server is required, and no license service is configured.

Thus, it is advantageous to obtain your license file before installing the

Jason products.

Automated configuration

If you have the license file when you run the Windows installer, all you
need to is as follows:

1 Copy the license.lic file you receive via email to any directory on
the local machine.

2 Run the installer, and specify where license.lic is located.

Note: If you plan to use a remote license server, the same license.lic file should be
copied to the machine hosting the license server and to each client machine
that will use that license server. Alternatively, you can manually set the
environment variable JASONLM_LICENSE_FILE on each client and set it to
point to the remote license server. (page 85).

GeoSoftware Installation Guide

 Manually configuring the license service (Windows) 83

Manual configuration

If you install without having a license file, you will have to do some
manual configuration later.

For a local license server, do as follows:

1 Copy license.lic to <topdir>\common\license.

2 Configure the license service (page 83).

3 Set the environment variable JASONLM_LICENSE_FILE to point

to C:\<topdir>\common\license\license.lic (page 85).

For a remote license server, set the variable

JASONLM_LICENSE_FILE on your local machine to point to the
remote license server: port#@hostname (page 85).

Manually configuring the license service (Windows)

If you installed the Jason software before obtaining your license file,
the license manager tools were installed in <topdir>\common\license,
but you have to manually configure the license service.

You have to have administrator privileges to configure the license

services and save your changes.

1 Launch the lmtools utility using one of these methods

• Select Start > All Programs > CGG GeoSoftware > License
Manager.

• Right-click the License Manager icon (Start > All Programs >
CGG GeoSoftware > License Manager), and select Run as
Administrator.

2 Stop the license manager (in case it is running):

• Click the Start/Stop/Reread tab.

• Check Force Server Shutdown.
• Click Stop Server.

Chapter 7: Licensing
84 Manually configuring the license service (Windows)

3 In the Config Services tab, set the following parameters:

• Service Name—Select JasonFLEXnetService from the

dropdown list or type the name in the field to create it.

• Path to the lmgrd.exe file—Set to

<topdir>\common\license\lmgrd.exe.

• Path to the license file—Set to

<topdir>\common\license\license.lic.

• Path to the debug log file—Set the path to the log file. We
recommend using <topdir>\common\license\license.log.

• Check Start Server at Power Up.

• Check Use Services.

• Click Save Service.

4 In the Start/Stop/Reread tab, click Start Server.

The local license service should now be running. You can check by
examining the log file.

5 In the Config Services tab, click View Log. After checking the log
file, click Close Log to close the file.

6 Close the lmtools utility.

GeoSoftware Installation Guide

 Setting the license variable (Windows) 85

Setting the license variable (Windows)

Normally, the variable JASONLM_LICENSE_FILE is set

automatically when you install Jason software. However, there are
some situations where you need to set this variable manually.

Network installation

If you are using a remote license server, you can copy the license.lic
file from the server to every client machine before installing the Jason
software on the client. During the installation, the environment variable
JASONLM_LICENSE_FILE will then be set automatically to point to
the license server (which is named in the license file).

Alternatively, you can manually set the variable on each client machine
without copying the physical license file to the clients:

JASONLM_LICENSE_FILE=<port#>@<hostname>

The port number is optional; however, the symbol @ is always

required. If you do not specify a port, one of the FlexNet default ports
(27000 - 27009) will be used. Hostname is the name of the machine
where the license server resides.

Local installation

For a local installation, you need to set JASONLM_LICENSE_FILE

manually if you did not have a license file when you installed the
software. (Copy the file to <topdir>\common\license when you get it.)
Also, if you use dongle licensing, you should set this variable to avoid
possible confusion with the license file FlexNet accesses for other
applications.

If you have a dongle license or evaluation license, set the variable as

the full path to the license file, for example, C:\Program Files\CGG
\GeoSoftware 9.0\license\license.lic. For other types of licenses, set
the variable to @localhost.

Chapter 7: Licensing
86 Sharing the license between different release versions (Linux)

Setting the variable

To set an environment variable, do as follows:

1 Right-click the Computer icon on the desktop or My Computer in

the Start menu, and select Properties.

2 On Windows, click Advanced system settings in the left pane; then

click the Advanced tab.

3 In the Advanced tab, click Environment Variables.

4 Under System Variables, click New.

Sharing the license between different release versions

(Linux)

In most cases you will want to support multiple versions of the Jason
Workbench software. To enable this, do as follows:

1 Install the license manager for the latest version as described on

page 81.

2 Update the references in the system boot script to the latest version.

3 Copy the new license.dat file into the license directory of the
previous installations. (Overwrite the old license.dat file.)

Note: The license manager should be started only from the new Jason installation
directory.

GeoSoftware Installation Guide

 Stopping/starting the license manager 87

Stopping/starting the license manager

When properly configured, the Jason license manager starts

automatically whenever the system is rebooted. There may be times,
however, when you need to manually stop and then restart the license
manager (for example, to cause it to read a new license file).

On Linux

On Linux workstations, the license manager startup and shutdown

scripts are found in the <instdir>/license directory. The license manager
daemons are located in <instdir>/bin/linux_ia32.

Stopping. To stop the license manager, change to <instdir>/license,

and enter this command:

./jlmdown -c license.dat

Starting. To restart the license manager, enter this command from the
license directory:

./jasonstartjlm -c license.dat

Optionally, you can use two additional arguments with this command:

-u <user> Starts the license managers as <user>, not

root. This improves system security and is
highly recommended.
-l <logfile> Specifies the location of the log file. If this
argument is omitted, the default is used,
/tmp/jasonlicense.log.

Chapter 7: Licensing
88 Stopping/starting the license manager

Checking. Check the license manager log file to ensure the license
manager has started correctly:

more /tmp/jason/license.log

Also, you can check to see if the daemons lmgrd and jasonlm are
running by entering this command:

ps -ef | grep jason

On Windows

On Windows workstations, the license manager tools are installed in

<topdir>\common\license and can be launched from the Start menu.
The license manager daemons are also found in this directory.

You have to have administrator privileges to stop/start the license

manager.

1 Launch the lmtools utility using one of the methods:

• Select Start > All Programs > CGG GeoSoftware > License
Manager.

• Right-click License Manager and select Run as

Administrator.

2 In the Start/Stop/Reread tab, do as follows:

• Make sure JasonFLEXnetService is highlighted.

• Check Force Server Shutdown.
• Click Stop Server.

3 To restart the license manager, click Start Server.

Messages in the status bar will indicate when the license manager is
successfully stopped and started. You can also check the log file by
clicking View Log on the Config Services tab.

GeoSoftware Installation Guide

 Frequently asked questions 89

Frequently asked questions

Some common questions about licensing are discussed in this section.

Question: Does Jason support redundant license servers?

Yes, you can request a license file for three license servers.

Question: Do I have to put all my FlexNet licenses into one license file?

No, FlexNet does not require the merging of license files, and, in fact,
merging is not recommended. Keeping the license files separate offers
several advantages:

1 maintenance of one vendor’s license management system will not

impact other applications

2 smaller files are easier to maintain

3 you can use the latest FlexNet daemons that are more secure, less
CPU-intensive, and more reliable

If a system manager still wishes to store all the license management

files in one place, they can be symbolically linked back to their
respective software installations.

Question: How is the host ID obtained?

The host ID comes from the network address on the network adapter. A
network card must be installed in order to run FlexNet and use the
Jason software.

Chapter 7: Licensing
90 Frequently asked questions

GeoSoftware Installation Guide

 91

CHAPTER 8

Troubleshooting
This chapter provides some guidance for resolving problems related to
licensing, connecting to the database, or running the individual
products.

License problems

Some problems with licensing are relatively easy to diagnose and

resolve; others are not. If the techniques described in this section do not
solve your problem or if you feel uncomfortable debugging the license
server system yourself, contact Jason customer support for assistance.

Checking the license log file

Whenever you have problems with licensing, the first thing to do is to

check the log file. It will provide information about errors encountered
and possible causes of those errors. For instance, the log will indicate if
the host ID of the license server and the host ID specified in the license
file do not match or if the license file has expired.

The default locations for the Jason license log file are as follows:

• Linux: /tmp/jasonlicense.log
• Windows: <topdir>\common\license

Note, however, that on Linux, the license file can be written to a

different location by using the -l flag when you start the license
manager manually with the jasonstartjlm script; for example:

jasonstartjlm -l /home/fred/licensetest.log

On Windows, you can use the lmtools utility to display the log file.
Select Start > All Programs > CGG GeoSoftware > License
Manager, and click View Log in the Config Services tab.

Chapter 8: Troubleshooting
92 License problems

Excerpts from two license log files are shown below. The first is a log
file without errors.

FlexNet lmgrd version

number

path to license file

jasonlm version number.

Should not be significantly
different from lmgrd
version.

license server name

list of supported license

features

OUT and IN lines indicate

successful feature
check-outs and check-ins.

Example of a license log file without errors

GeoSoftware Installation Guide

 License problems 93

In the next example, the log gives useful information about a problem
that occurred. In this case, a system administrator did not use the
FlexNet facilities to shut down the license manager, thus leaving the
jasonlm daemon running. When someone else tried to launch a Jason
application, the software did not start and no error message was
displayed.

Excerpts from a license log file with errors

Chapter 8: Troubleshooting
94 License problems

Obtaining additional diagnostic information

In addition to the log file that is written on the license server, you can
generate a file with diagnostic information that is written to the
machine where the Jason application is installed. You may want to do
this, for example, if you are using a remote license server.

Set the environment variable FLEXLM_DIAGNOSTICS on the

machine where the Jason application is installed before you attempt to
start the application and check out a license. Setting this variable to
level 3 gives information about failed checkouts.

Important: Once you have finished debugging, remember to unset the

FLEXLM_DIAGNOSTICS variable to avoid degradation of performance.

On Linux

Enter this command, and then start Jason Workbench from that same
xterm:

setenv FLEXLM_DIAGNOSTICS 3

The diagnostic output goes to stderr and is written to the directory

$HOME/JASON_LOGS. Filenames for these files include the word
“startup.”

On Windows

To set the environment variable, select Start, right-click

My Computer, and select Properties. Then, in the Advanced tab, click
Environment Variables.

The output is a file called flexpid.log, where pid is the process

identifier for the Jason process (Jason Workbench, EMFT, or
PowerLog). Depending on how you start the application, the
flexpid.log file is written to one of these locations:

• Desktop—if you start the application by double-clicking on its

desktop icon

• C:\Windows\System32—if you start the application from the

Windows Start menu

GeoSoftware Installation Guide

 License problems 95

• Directory where the executable is located—if you start the

application from that directory by double-clicking on the .exe file

For additional information, see the FlexNet user guide, which can be
accessed from the Jason Workbench online help.

Linux: Dealing with license problems

A checklist for diagnosing license problems on Linux systems is

provided below. along with a list of some common FlexNet error codes.
Also, some possible reasons why the license manager will not start are
discussed.

Troubleshooting checklist

The fastest way to get the license manager started is to clean out all the
existing files and daemons and restart the system. Use this checklist
when a Jason installation that was running is no longer working, for
example, after a version upgrade or after a system crash.

1 Inspect the log file /tmp/jasonlicense.log to ensure that both jasonlm

and lmgrd started properly (page 91).

2 Make sure the hostname and host ID in the license file match the
system where you are trying to start the license manager.

3 Shut down the license manager:

cd <instdir>\license
jlmdown -c license.dat

4 Remove any /usr/tmp/lockjasonlm or ~/.flexlmrc files.

5 Start the license manager:

cd <instdir>\license
jasonstartjlm -c license.dat

6 Inspect the license log file.

7 Start the Jason launcher.

8 If your Jason license manager is started by a script when the license

server is rebooted, is that script up to date?

Chapter 8: Troubleshooting
96 License problems

9 If you are concatenating the Jason license file with license files
from other vendors, are you running the highest version of the
FlexNet software so that all the programs will behave properly?
(Jason requires FlexNet 11.10.)

FlexNet error codes

Some common FlexNet error codes and how to resolve them on Linux
systems are described in the table below. For a full list of error codes,
see the FlexNet user guide, which can be accessed from the Jason
Workbench online help.
Common FlexNet Error Codes
Code Error Description Cause/Solution
-1 Cannot find license file C: The path to the license file is incorrect in the Jason startup script, or
the path to the daemon is incorrect in the license file.
S1:Run jgsetup to ensure that the paths to the installation and daemon
are correct.
S2: Check the file ~/JASON_LOGS/jlmcheck.log. This file records
what happens when the user starts an application that tries to connect to
the license manager.
-2 Invalid license file syntax C: License file is corrupt.
S1: Check that the file does not contain ^M characters at the end of
each line, which can result from doing an FTP transfer through a
non-UNIX/LINUX system.
S2: Request a replacement license file from [email protected].
-3 No license server system C: A license server is running, but it’s not the Jason license server.
for this feature Usually this means the Jason license server has not been configured.
S: Configure the Jason license server.
-5 No such feature exists C: The license file that the license server is using is different from the
one the Jason software is using. This can happen when there are several
users and the Jason Workbench installation is moved or when multiple
versions of Jason Workbench are installed.
S: Make sure the license file in <instdir>/license is the same as the one
specified in the user’s JASONLM_LICENSE_FILE variable.
-8 Invalid license key C: The license key and the data for the feature do not match. This
problem is usually caused by alteration of the license file. Or it may
result from problems with the user’s .flexlmrc file.
S1: Use the license file that you got from Jason as is. Do not try to copy
lines into an existing file.
S2: A .flexlmrc file is created when the user starts the Jason launcher
for the first time; it enables subsequent startups to proceed more
quickly. You can safely delete this file; it will be automatically
regenerated during the next successful startup of the Jason launcher.

GeoSoftware Installation Guide

 License problems 97

Common FlexNet Error Codes (Continued)

Code Error Description Cause/Solution
-9 Invalid host C: The hostname in the license file and the hostname of the machine
where the license manager is trying to start do not match.
S1: If you are running Jason Workbench on a remote machine, make
sure you are logged into the correct host.
S2: If there is a typo in the hostname in the license file, you can edit it
to match the correct name. Do not attempt to edit the host ID, however,
as this will invalidate the license.
-14 Cannot find SERVER C: The lookup for the hostname on the SERVER line in the license file
hostname in network failed. This problem often happens when NIS or DNS is down or when
database the hosts file is incorrect.
S: Workaround: Edit the license file to use the IP address (e.g.,
123.456.789.123) instead of the hostname.
-15 Cannot connect to license C: Check for any of these possible causes: (1) the license server
server. (lgmrd.exe) has not been started yet, (2) the wrong license file is being
used, (3) the variable JASONLM_LICENSE_FILE = port@host is
incorrectly set, or (4) the port or hostname in the license file has been
changed.
-18 License server does not C: The requested functionality is not enabled by your license.
support this feature
-21 License file does not C: Trying to run a new major version of the Jason software with an
support this version older license file can cause this error.
S: Request a new license from [email protected].
-37 Duplicate selection C: You (or someone else) are currently using version 5 or earlier of
mismatch for this feature Jason Workbench.
-54 No FEATURESET line C: You may get this error if you try to use an old license.dat file with a
in license file newer version of the software. Beginning with Jason Workbench 5,
Jason license files must include FEATURESET lines (now called
PACKAGE lines) that list all the features that are licensed under a
given feature set name or package name.
S: Request a new license from [email protected].
-55 Incorrect FEATURESET C: FEATURESET (or PACKAGE) lines are paired with corresponding
line in license file INCREMENT lines where the license key for that particular set of
features is provided. If you attempt to add or remove lines from the
license file, it will lose its self-consistency and give this error.
S: Use the license file you got from Jason as is. Do not try to copy lines
into an existing file.

Chapter 8: Troubleshooting
98 License problems

System is not LSB compliant.

FlexNet 11.10 assumes you are running on a LSB 3.0 compatible Linux
distribution. All Linux distributions for which Jason software is
certified are LSB 3.0 compliant or can be made so by installing an
additional package.

Specifically, the license manager requires the file /lib/ld-lsb.so.3 to be

present on the system. An error message about LSB compliance
indicates that this file is not found on the system where you wish to run
the license manager.

To fix this problem, install the relevant packages for your system:
redhat-lsb for Red Hat systems, suse-lsb (or simply lsb) for OpenSuse
systems. Alternatively you can create the missing file manually. This
file is just a symbolic link to /lib/ld-linux.so.2.

No “eth0” network card is found.

The FlexNet license manager looks for the network card labeled “eth0”
on Linux. If no eth0 card is found, the license manager will return an
error like this in the license log:

SERVER line says 001122334455, hostid is

000000000000

where 001122334455 is the host ID of your computer.

Remap your network cards so that a specific one will always appear as
eth0. The instructions may vary depending on the operating system. On
Red Hat systems, the following should work:

1 Edit your “70-persistent-net.rules” file as follows:

vi /etc/udev/rules.d/70-persistent-net.rules

2 Locate the current mapping of the network card (e.g., “eth1”) and
change this to “eth0”:

NAME="eth0"

3 Reboot the computer.

Once the network card is mapped to eth0 you should be able to activate
the software normally.

GeoSoftware Installation Guide

 License problems 99

User is invalid.

With the jasonlmstart command, you can specify a user account for
running the license manager, for example,

jasonlmstart -u fred

However, if you get errors in the log file like “user fred does not
exist” or “user fred is not a valid user,” either fred does not
exist on your system or fred does not have a valid Linux shell.

Try to start license manager without the -u argument in the command

(in which case root is used); or use a different user instead. Please
contact your system administrator for details.

License file is corrupt.

To determine if license.dat has been corrupted, run the lmchsum utility.

This utility compares the features encoded for each license key with the
encrypted code for that feature.

cd <instdir>/license
jlmutil lmcksum -c license.dat

The program will respond with something similar to the following:

lmutil - Copyright (C) 1989-1994 Globetrotter Software, Inc.

lmcksum: using license file "license.dat"

214: SERVER lief 8093abcdc392 1790

246: DAEMON jasonlm
/pa/jason/8.3/bin/linux_ia32/jasond
/pa/jason/8.3/license/license.opt
13: FEATURESET jasonlm 27F5B249DC688916
OK: 173: INCREMENT jgw_environment jasonlm 8.300 07-jul-2011 10
1CB8FCFD646B3EC7B4C2 SUPERSEDE SUITE_DUP_GROUP=UHD
vendor_info=startdate:13-jul-2011 ISSUED=13-jul-2011 ck=173
SN=1
OK: 111: INCREMENT jgw_environment_plus jasonlm 8.300 07-jul-2011 10
2CF8BCBDFA7AD384C887 SUPERSEDE SUITE_DUP_GROUP=UHD
vendor_info=startdate:13-jul-2011 ISSUED=13-jul-2011 ck=111
SN=2
OK: 42: INCREMENT JasonCore jasonlm 8.300 07-jul-2011 10
7CB86C3D59136153C88E SUPERSEDE SUITE_DUP_GROUP=UHD
vendor_info=startdate:13-jul-2011 ISSUED=13-jul-2011 ck=42
SN=3

If there is a line that does not begin with OK, the file may be corrupted.

Chapter 8: Troubleshooting
100 License problems

Licenses are still in use after a crash.

When a workstation crashes, the license manager may not release the
licenses that were in use. This is a known issue with FlexNet. If nothing
is done, it will take about a day before the licenses are freed. To resolve
this problem quicker, manually restart the license manager.

Lockfile is not removed.

When the Jason launcher is started for the first time (or after the license
manager was shut down) and run on the same host as the license
manager, the system will start the Jason license manager automatically.
A lockfile /usr/tmp/lockjasonlm is created and owned by the user who
started the Jason launcher.

Occasionally this lockfile is not properly removed after a system or

license manager shutdown. If someone else now tries to start the
license manager, the system may complain about incorrect permissions.
The solution is to remove the lockfile manually.

Hostname in license file is wrong.

If your workstation has both an official hostname and an alias, the

hostname -s command may return the alias, which is then used in
generating the license file. When you try to run the application, you get
an error message. To resolve this problem, edit the hostname in the
license file.

GeoSoftware Installation Guide

 License problems 101

Windows: Dealing with license problems

On Windows, the first indication of a license problem typically occurs

when you try to start a Jason application and get this message box:

You can try to point the application to a valid license server or valid
license file or click Cancel to display more information about the error
condition. Some of those conditions are discussed below.

Chapter 8: Troubleshooting
102 License problems

Cannot find license file.

If you are trying to connect to a remote license server, do as follows:

1 Check if the variable JASONLM_LICENSE_FILE is pointing to

the correct license server (for example, it is set to @bigserver).

2 Check if the license.lic file in <topdir>\common\license is pointing

to the correct license server.

Note: When using a remote license server, you do not have to have a license.lic file
on the local machine, provided the variable JASONLM_LICENSE_FILE is
correctly set to the remote server.

3 Try again to start the application.

4 If you get the same error, check the network connectivity. Can you
ping the server machine?

5 If a firewall is set up on the server machine, make sure that both

lmgrd.exe and jasonlm.exe are allowed to communicate with other
computers on the network.

If you are trying to connect to a license server on the local machine, do

as follows:

1 Check if there is a license.lic file in <topdir>\common\license.

2 If the JASONLM_LICENSE_FILE variable is set, it should be set

to @localhost or to C:<topdir>\common\license\license.lic.

Cannot connect to license server system.

The desired vendor daemon is down.

These two error messages indicate different problems, but the remedies
are similar. The first message means that although it is possible to
connect to the server machine, FlexNet (lmgrd) is not running on that
machine. The second message indicates that a connection to the server
has been established (lmgrd is up and running), bu the vendor daemon
(jasonlm) is not running.

GeoSoftware Installation Guide

 License problems 103

Look for and correct these possible causes:

• The Jason license service is not started on the server machine. Use
lmtools to make sure the service is configured correctly, using the
correct license file, and started. If the Jason service is running.
examine the license log file.

• A firewall on the server is blocking incoming FlexNet license

requests. Make sure that the server firewall allows connections to
both lmgrd.exe and jasonlm.exe.

• The license file is installed on the wrong server. The license server
log file will indicate if the server host ID or name is not identical to
the one listed in the license file. If the names do not match, you can
edit the hostname in the license file. If the host IDs don't match, you
either have to install the license on the server specified in the file or
request a new license file.

• If the message reads “Cannot connect to license server system,”

there may be a network connectivity problem preventing the client
from communicating with the server. Try pinging the server
machine to verify that it is visible from the client. If the ping
succeeds, you can rule out this possible cause. If the ping fails, it
does not mean anything; the server may be configured to ignore
ping requests.

License server machine is down or not responding.

The error occurs if either the license file in <topdir>\common\license

or JASONLM_LICENSE_FILE points to a non-existent server. Make
sure the server name is spelled correctly and try pinging the server
machine to verify the client machine can connect to it.

Some or all features that should be available are not available.

The error can occur if the wrong license server or wrong license file is
being used.

1 Select Help > About from the PowerLog main menu.

2 Look for the license server host ID in the About box.

3 Check the license file that is located on the machine with the
host ID reported in the About box.

Chapter 8: Troubleshooting
104 License problems

4 Check the license log on that machine to verify if there are OUT,
IN, or DENIED lines in log file, indicating that you requested
license features from the server.

If there are no such lines, you are probably looking at the wrong
license server.

5 Does the log file corresponding to the correct license file include the
following line:

15:58:02 (lmgrd) The license server manager

(lmgrd) is already serving all vendors,
exiting.

It so, it means that you already have a license server set up on that
machine that serves Jason licenses. Locate the other service using
lmtools, and either disable it, merge the two license files, or replace
the old license file with your most recent one.

License expired

FlexNet caches the location of all license files it has used. Perhaps it is
looking at an older Jason license that has expired. Check the registry
for obsolete Jason licenses; the key is JASONLM_LICENSE_FILE.
Call support for help.

Windows: Dongle license problems

Dongle licenses (licenses that are locked to a particular security key

ID) are supported only for PowerLog. A dongle license file has no
SERVER or DAEMON lines because, with this type of license,
PowerLog does not connect to a FlexNet server. Because there is no
license server, there is no license log file.

Some of the problems you might encounter with a dongle license are
described below.

GeoSoftware Installation Guide

 License problems 105

USB dongle not plugged in or dongle driver not working.

The plug ID in the error message indicates the license file was
generated for a USB dongle.

1 Make sure the dongle (in this case, #1317) is plugged into the
machine. If it is, you probably have a problem with the dongle
driver.

2 Open the device manager window to verify that the USB SafeNet
dongle is recognized by the system. If it is not, reinstall the dongle
driver.

Chapter 8: Troubleshooting
106 License problems

Dongle ID does not match host ID in license file.

The host ID specified in the license file (1256) does not match the
serial number of the dongle that is currently plugged in (1317).

Some or all features that should be available are not available.

There can be two reasons why some features are not available: The
USB dongle is programmed to support only a restricted set of features,
or the license file may not include everything the you expect.

1 Check the license file, and verify its correctness.

2 If the license file is correct, contact Jason customer support. We can

send you a tool to check how the dongle has been programmed.

GeoSoftware Installation Guide

 License problems 107

Linux or Windows: Additional information

The following information applies to both Linux and Windows

installations.

Users cannot connect to license server

A firewall on the license server could be blocking the FlexNet calls.

• Try disabling the firewall briefly to see if this is what is causing the
problem.

• Set the firewall to allow these applications to communicate with the

outside: lmgrd.exe and jasonlm.exe.

• Open port 27000. This is the default port used by FlexNet. The
Jason applications assume that this is the port being used. You can
use a different port; however, to do so, you would need to change
the port number in the license file to match the port open in the
firewall.

Administrator cannot release a checked out license

If a user checks out a license and then forgets the application running
(for example, when he leaves the office), the license is locked and
unavailable to other users. A system administrator cannot release the
license using the license management software. The only recourse is to
log onto the user’s machine and close the application to free the license.

Contacting support with license problems

If you cannot resolve the licensing problems yourself, contact Jason

customer support. Please send copies of the license server log file and
your license file. Be prepared to answer the following questions:

• What kind of machine is the license manager running on? What is

the version of the operating system?

• What machine and operating system is the Jason software running

on?

• What error or warning messages appear in the license log file? Did
the server start correctly? Look for a message such as:
server xyz started for: feature1 feature2.

Chapter 8: Troubleshooting
108 License problems

• On Linux systems, what is the output from running jlmstat -a?

• Are you running other products that are also licensed by FlexNet?
Are you using a combined license file or separate license files?

• Are you using redundant servers (multiple SERVER lines in your

license file)?

GeoSoftware Installation Guide

 Database problems 109

Database problems

A few troubleshooting tips are listed below.

Cannot connect to remote database via AMS

If the application fails while trying to connect to a networked database

using the Advanced Multithreaded Server (AMS), here are some
techniques you can use to diagnose and resolve the problem.

1. Check that essential services are running.

During application startup, the software attempts to connect to the

AMS service and lock server running on the database server. If those
services cannot be contacted, you may get an error message similar to
one of these:

Determine if the services are running and, if necessary, start them, as

follows:

1 On the database server, open the Control Panel, and double-click

Administrative Tools, then Services.

2 Search the list of services for ooams-3 and ools-13.

Chapter 8: Troubleshooting
110 Database problems

The status for both services should be Started, and the startup type
should be Automatic.

3 If the services are not running, start them manually. Right-click the
service name, and select Start.

Note: Services must be started with an account that has administrative privilege and
read/write permissions to the drives where databases are hosted on the
database server. To specify which account should be used for starting services,
right-click the service and select Properties.

4 Try connecting from the client machine again.

2. Check that the database exists.

If the database cannot be located, you may receive an error message

similar to this:

1 On the database server, browse to determine if the database path in

the error message is the actual location of the database.

GeoSoftware Installation Guide

 Database problems 111

2 If the path in the error message is incorrect, try using the correct
path to connect from the client machine.

3 If the client still cannot connect, has the database been moved or the
directory where it resides renamed? If so, do as follows to update
internal references in the database:

• On the database server, select Start > All Programs > CGG
GeoSoftware> Tools > Database Management 9.0.

• Click Install DB moved from another machine or folder.

4 Try connecting to the database from the client machine.

3. Disable the firewall temporarily.

If the services are started, the path is correct, but the client machine still
cannot connect to the database server, perhaps the firewall is blocking
access.

1 Turn off the firewall on both the client machine and the database
host:

• Open the Control Panel, and double-click Windows Firewall.

• Click Turn Windows Firewall on or off in the left pane.
• Select Turn off Windows Firewall.
• Click OK.

2 Try connecting to the database from the client machine.

3 If the connection succeeds, perform the following steps on both the

client and the server:

• Reopen the Windows Firewall dialog box.

• Click Turn Windows Firewall on or off in the left pane.

• Select Turn on Windows Firewall.

• Click OK.

Chapter 8: Troubleshooting
112 Database problems

• Click Allow a program or feature through Windows Firewall

in the left pane.

• Click Allow another program.

• Click Browse and locate ooams.exe. The default location is

C:\ProgramFiles\CGG GeoSoftware 9.0\bin.

• Repeat these steps to add ools.exe as an exception to the

firewall.

4 Now, with the firewall enabled again, try connecting to the database
from the client machine.

4. Test the local connection.

If connection from the client is still failing, try connecting to the

database locally from the database server.

1 On the database server, select Start > All Programs > > CGG
GeoSoftware > Tools > Database Management 9.0.

2 Click Connect to DB on this computer.

3 Once the database has been located and listed in the dialog box as
the active DB, click Log on.

4 If the login succeeds, then a communication problem between the

client and server is likely. Try pinging the database server from the
client machine.

5 If the login fails, try to determine if the cause lies with this
particular database or with the system.

• Create a new database.

• Connect to the new database locally from the database server.
• Try to connect to the new database from the client machine.

If you are still unable to identify and rectify the cause of the problem,
contact Jason customer support for assistance.

GeoSoftware Installation Guide

 Database problems 113

Database lock server not running

Whether you are connecting to a remote database via AMS or the

database is on a network share, the database lock server must be
running. If you get an error message stating the lock server is not
running, restart it as follows:

1 On the machine hosting the lock server, open the Control Panel,
and double-click Administrative Tools, then Services.

2 Search the list of services for ools-13.

3 Select the ools-13 service, and click Restart the service. (If the
service is already stopped, click Start the service.)

4 Launch PowerLog 9.0.

5 If the application will still not run, check your firewall settings to
make sure that ools-13 can communicate with other machines.

Other problems connecting to database

Cannot connect to database, firewall problem. For users to
connect to a database on another computer, the firewall on the database
server must allow access to the port used by the Objectivity lock server
process. By default, the lock server process uses port 6780, but a
different port can be assigned.

Chapter 8: Troubleshooting
114 Database problems

Cannot connect to database, insufficient permissions.

Because a journal file is written when a user accesses the database and
deleted when he logs off, the user must have adequate permissions for
the directory where the database resides. The simplest approach is to
grant each user Full Control of the directory. This option includes all
the required permissions: read, write, and delete. Note that membership
in the Administrators group is not sufficient; permissions must be
granted to each user account individually or to another group (not
Administrators) to which the user belongs.

GeoSoftware Installation Guide

 Jason Workbench problems 115

Jason Workbench problems

Some problems that can occasionally occur with the Jason Workbench
are discussed below.

3D View hangs (Windows)

On a system with dual graphics processing units (integrated GPU and

NVIDIA GPU), the 3D View will hang if the low-power, non-NVIDIA
GPU is used.

Due to technical issues with dual graphics technology, we cannot

guarantee proper functioning of the 3D View application on this type of
hardware, and as such, do not support this hardware.

3D View does not display SHF files (Window and Linux)

There is an issue with newer NVIDIA drivers that causes SHF files to
not display correctly. Because of this, only the 331 version of NVIDIA
drivers is supported.

For detailed information, refer to the NVIDIA website:

http://www.nvidia.co.uk/download/driverResults.aspx/74184/en-uk

http://www.nvidia.co.uk/download/driverResults.aspx/71782/en-uk

http://www.nvidia.co.uk/download/driverResults.aspx/76779/en-uk

Chapter 8: Troubleshooting
116 PowerLog problems

PowerLog problems

Some installation-related problems that may occur with PowerLog are

discussed below. For information on other PowerLog issues, see the
PowerLog release notes and online help.

PowerLog 2 no longer works

PowerLog 2 and later versions of PowerLog can coexist on the same

machine. However, you need separate license files and separate license
services for each application. (If you use dongle licensing, no license
service is required.)

You should have made a copy of your existing PowerLog license

components and license file before upgrading to a later version of
PowerLog (as instructed on page 11). If, after completing the upgrade,
PowerLog 2 no longer starts without problems, you need to configure
the license service for PowerLog 2 as follows.

1 Launch lmtools.exe from the folder where you placed the backup of
your PowerLog 3.x license components, for example,
C:\PetcomFlexNet.

2 In the Configure Services tab, do as follows:

• Enter a new service name, for example, PetcomFlexNetService.

• Specify the path to the lmgrd.exe executable,

C:\PetcomFLEXlm\lmgrd.exe.

• Specify the path to the license file,

C:\PetcomFLEXlm\license.lic.

• Enter a name for the log file,

C:\PetcomFLEXlm\petcom_log.txt.

• Check Start Server at Power Up and Use Services.

• Click Save Service.

3 In the Start/Stop/Reread tab, click Start Server.

4 Start PowerLog 2.

5 Close the lmtools utility.

GeoSoftware Installation Guide

 PowerLog problems 117

Petra link does not work

Some issues that could possibly affect operation of the Petra link are
described below.

Petra license issues

For the Petra link to work, your Petra license must allow data transfer
between Petra and other applications.

Petra bitlock (standalone) license. When you try to open the

Petra link from within PowerLog, the following dialog box appears:

If API User is not enabled, you cannot transfer data. To have the API
switch turned on, send a request to [email protected] and
include the bitlock serial number. There is no fee for enabling this
option.

Chapter 8: Troubleshooting
118 PowerLog problems

Petra network license. With network licenses, you need a

PETRADATAACCESS license in your geoplus.lic file, and a keyword
in the Petra.ini file has to be uncommented.

1 To uncomment the keyword, open the Petra.ini file, and remove the
semicolon and space at the beginning of the FLEXLMDATALIC
line:

[NETLOGIN]
;
; to enable network flexlm licensing use the
following
; two keywords. Needed is the Port and machine
hostname
; where flexlm is running.
;
FLEXLM=ENABLED
FLEXLMLICPATH=27001@Hostname
; FLEXLMDATALIC=YES

2 Launch Petra.

If you receive an error message, your geoplus.lic file does not

contain the PETRADATAACESS feature. Contact
[email protected] to request it. There is a fee for this feature.

Petra server and client out of sync

The Petra link operates via pserver.exe, which serves as a bridge

between PowerLog 3.x and the Petra libraries. Any time Petra changes
its libraries or Jason adds functionality to the Petra link, a new version
of pserver.exe is provided.

When PowerLog is installed, pserver.exe is installed on the Petra server

and registered on the Petra client as a COM component. All clients
must be running the same version of PowerLog in order to access data
from the Petra installation via pserver.exe. Check the PowerLog
version on each client machine, and, where necessary, upgrade
PowerLog to the newer version.

GeoSoftware Installation Guide

 PowerLog problems 119

Other problems

A few other considerations are listed below.

Multiple user access. Multiple users can be working in the same

project simultaneously; however, it is not advisable to log into the same
project with the same user account from multiple instances of
PowerLog. Create separate user accounts.

Windows themes. Running with a theme that has continuously

changing images can degrade PowerLog performance. Instead, use a
single image or color as your theme.

Chapter 8: Troubleshooting
120 PowerLog problems

GeoSoftware Installation Guide