DecisionSpace ® Software

Version 5000.0.1
Installation Guide

Contents
Introduction ................................................................................................................... 2

Important Considerations for Installation ................................................................... 4

DecisionSpace® Software Configuration .................................................................... 5

OpenWorks® Software Server Options ....................................................................... 7

DecisionSpace® Software Workstation - Windows .................................................... 9

DecisionSpace® Software Workstation - Linux ........................................................ 24

Installing the DecisionSpace® Software in Silent Mode .......................................... 37

Installing the DecisionSpace Launcher® Software .................................................. 40

Obtaining a License to Run the Software ................................................................. 44

Troubleshooting .......................................................................................................... 46

Trademarks .................................................................................................................. 53

5000.0.1 Installation Guide Page 1 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Introduction
This installation guide provides instructions for installing DecisionSpace® software
version 5000.0.1. It contains the following information:

• Current components in this DecisionSpace software release

• Hardware requirements

• Software requirements

• OpenWorks® software configurations used by the DecisionSpace testing team

• Installation procedures for Windows and Linux operating systems

• Post-installation procedures

• Troubleshooting

Refer to the DecisionSpace® Software Version 5000.0.1 Release Notes for New Function-
ality and Known Problems

The DecisionSpace® Software Version 5000.0.1 Release Notes contain a summary of the new
functionality in this release, as well as software fixes and known problems that impact all
DecisionSpace 5000.0.1 software. In addition, each of the DecisionSpace software has its own
set of Release Notes for issues that are specific to that software.

DecisionSpace Desktop

The Decision Desktop is a common user interface that allows you to access all software
in your workflow. The single interface provides a seamless viewing experience and unifies
common components and functionality across the DecisionSpace® software suite into
one tightly integrated DecisionSpace software environment.

The Desktop has replaced the Session Manager as the first visible user interface. Session
parameters are now configured in the Desktop, and once configured these parameters
remain in effect across sessions. You no longer need to configure session parameters for
each session unless required.

The Desktop provides a launcher that can be configured to start Landmark and other
vendors’ software right in the Desktop. The Launcher can also import existing Command
Menu configuration files of the OpenWorks software for quick configuration.

5000.0.1 Installation Guide Page 2 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

The DecisionSpace® software Desktop runs on Windows 32-bit, Windows 64-bit, and Red
Hat Enterprise Linux 64-bit systems.

DecisionSpace Launcher Software

If you do not have any DecisionSpace software installed on your system, you can use the
DecisionSpace Launcher software to start other Landmark and vendors’ software on a
Red Hat Enterprise Linux 64-bit system. It is a minimal deployment of the DecisionSpace
software that utilizes the software launching capability of the DecisionSpace software
Desktop.

You can utilize the DecisionSpace Launcher software as a common software launch point
rather than command line launch of software from a terminal window. The launcher can
also import existing Command Menu configuration files of the OpenWorks® software for
quick configuration.

The DecisionSpace Launcher software can be downloaded as a stand-alone product from

the Landmark Software Manager (LSM).

5000.0.1 Installation Guide Page 3 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Important Considerations for Installation

• DecisionSpace® software version 5000.0.1 runs on Windows XP 32-bit, Windows 64-
bit, and Red Hat Enterprise Linux 64-bit systems. For more details, refer to the
Release Notes for the individual software.

• DecisionSpace software 5000.0.1 can run in either the OpenWorks® mode, where the
OpenWorks server and client are required, or in non-OpenWorks mode, where data
stores other than an OpenWorks database are accessed.

• DecisionSpace software 5000.0.1 for Windows has been tested with OpenWorks
version 5000.0.0.2 running the Oracle 10g server and client.

Note: You require Oracle 10.2.0.3.0 32-bit for the OpenWorks client, and Oracle
10.2.0.3.0 64-bit for DecisionSpace software installed on Windows 64-bit. For
instructions on installing Oracle 32 and 64-bit, refer to the OpenWorks® Software
Installation Procedures manual for Release 5000.0.0.2.

• DecisionSpace software 5000.0.1 requires the installed OpenWorks 5000.0.0.2 client

to access the OpenWorks project data.

• Instructions for installing or upgrading the OpenWorks 5000.0.0.2 servers and clients
are provided in the OpenWorks® Software Installation Procedures manual for Release
5000.0.0.2.

• Instructions for installing Landmark Software Manager software are provided in the
LAM Installation Procedures manual for Release 5000.0.0. LSM allows you to
download all Landmark products.

5000.0.1 Installation Guide Page 4 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

DecisionSpace® Software Configuration

Windows XP and Linux

The following DecisionSpace version 5000.0.1 software run on the Windows XP and
Linux operating systems:

• AssetView™ software

• Collaborative Well Planning - AssetView™ software

• Collaborative Well Planning - GeoProbe® software - only available on Windows 32-bit

systems.

• PowerGrid™ software - only available on Windows 32-bit and Linux 64-bit systems.

• PowerView® software

• PowerCalculator® software

• Well Seismic Fusion™ software - available only on Linux 64-bit systems.

• 3D Drill View KM™ software

Related Documents

The following Installation Procedures and Release Notes can be accessed from the
DecisionSpace Help menu. The installation procedures provide detailed instructions on
how to install the OpenWorks® software and include the requirements for various
platforms. The release notes summarize new functionality in each software as well as
software fixes and known problems. The LAM Guide provides detailed instructions on how
to install and configure the Landmark license application manager on Windows and Linux
systems.

• AssetView™ Software Release Notes 5000.0.1.0

• DecisionSpace® Software Release Notes 5000.0.1.

• GeoProbe® Software Release Notes 5000.0.0.1

• PowerGrid™ Software Release Notes 5000.0.0.1

• PowerView® Software Release Notes 5000.0.0.1

• OpenWorks® Software Installation Procedures 5000.0.0.2

5000.0.1 Installation Guide Page 5 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

• Collaborative Well Planning Release Notes 5000.0.0.1

• Well Seismic Fusion™ Software Release Notes 5000.0.0.1

• 3D Drill View KM™ Software Release Notes 5000.0.0.1

5000.0.1 Installation Guide Page 6 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

OpenWorks® Software Server Options

DecisionSpace® software version 5000.0.1 has been tested on the OpenWorks
5000.0.0.2 server configuration. DecisionSpace software version 5000.0.1 therefore
requires you to install the OpenWorks 5000.0.0.2 server. For more details, refer to
“DecisionSpace® Software Configuration” on page 5.

The following table lists the software requirements for the OpenWorks 5000.0.0.2 server
installation:

Software Version

Connectivity Software PC only: Hummingbird Exceed 2007

The Exceed Connectivity Secure Shell must also be installed.

Database Server Oracle 10.2.0.3.0 Database Server (Windows, Solaris, or Linux)

OpenWorks Server OpenWorks 5000.0.0.2 Server

License Management LAM 5000.0.0

The installation program and the documentation for LAM 5000.0.0 can be
downloaded from the Landmark Software Manager (LSM). Select Technical
Business Line > Tools > LAM.

Document Viewer Adobe Reader 7.0.8 or later (Adobe Acrobat Reader 5.x or Adobe Reader
6.x also displays PDF documents.)

For information on installing Oracle 10.2.0.3.0, refer to the OpenWorks® Software

Installation Procedures manual for Release 5000.0.0.2.

For information on installing LAM 5000.0.0, refer to the LAM Guide for Release 5000.0.0.

Mobile Workstation

The “mobile workstation” is a Windows XP workstation that runs both the OpenWorks
server and the OpenWorks client on the same laptop. It allows you to run DecisionSpace
software while your laptop is disconnected from the network.

Laptops

DecisionSpace software version 5000.0.1 runs on the Dell Precision M90 with nVidia
Quadro FX 2500M graphics with Windows XP, Service Pack 2.

5000.0.1 Installation Guide Page 7 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Standalone Configuration

• Oracle 10.2.0.3.0 Server and Client

• OpenWorks® software 5000.0.0.2

• GeoDataLoad™ software 5000.0.0.2

• DecisionSpace® software 5000.0.1

• LAM Server

The mobile workstation has the following configuration requirements:

Software Version

Connectivity Software Hummingbird Exceed 2007

Database Server and Oracle 10.2.0.3.0 Database Server

Client

OpenWorks Software OpenWorks 5000.0.0.2 server

Server and Client

License Management LAM 5000.0.0

The installation program and the documentation for LAM 5000.0.0 can be
downloaded from the Landmark Software Manager (LSM). Select Technical
Business Line > Tools > LAM.

Document Viewer Adobe Reader 7.0.8 or later (Adobe Acrobat Reader 5.x or Adobe Reader
6.x also displays PDF documents.)

For information on installing Oracle 10.2.0.3.0, refer to the OpenWorks® Software

Installation Procedures manual for Release 5000.0.0.2.

5000.0.1 Installation Guide Page 8 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

DecisionSpace® Software Workstation - Windows

System Requirements

DecisionSpace software has the following hardware and software requirements for
Windows operating systems.

Hardware Requirements

The following table lists the hardware requirements for Windows workstations running
DecisionSpace software version 5000.0.1. DecisionSpace software runs on the minimum
requirements listed. However, performance may not reach acceptable levels with large or
complex datasets.

Hardware Recommended Configuration

CPU Intel Pentium or Xeon (Minimum CPU tested: Pentium-IV)

Intel EM64T or AMD Opteron (running a 32-bit operating
system)

Memory (RAM) 2 GB or greater

Hard Disk 1 GB is the installation size for the entire DecisionSpace

suite. Refer to page 5 for the list of DecisionSpace soft-
ware.
200 MB is the default cache size in the temporary direc-
tory of the system. For more details, see “DecisionSpace
Software Cache Size” on page 17.

Display Dual monitor in TwinView: 1280 x 1024 per monitor

Color Depth: True Color (32-bit)

Graphics Card See the Graphics Cards section.

Mouse Microsoft-compatible 3-button mouse or 2-button mouse

with scroll wheel configured as the middle mouse button.

Installation Device Drive ESD/LSM

CD/DVD (in case you order the software)

Stereo Shutter Glasses VRex VR Visualizer shutter glasses

(Optional) (www.vrex.com/products/shutter_glasses.shtml)

5000.0.1 Installation Guide Page 9 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Graphics Cards

Workstations

The following graphics cards were tested by the DecisionSpace® Quality Management
team for Windows XP, Service Pack 2. These cards can be expected to perform
adequately.

• Desktop Workstation - nVidia Quadro FX 4500 and nVidia Quadro FX 3450 (PCI
Express Bus). These cards were tested with version 162.62 of the nVidia driver for
Windows XP 32-bit systems.

• DecisionSpace software on laptops - Dell Precision M90 with nVidia Quadro FX

2500M, 512 MB. This card was tested with version 101.19 of the nVidia driver for
Windows XP 32-bit systems.

It is recommended that DecisionSpace software that require high-end cards, such as the
AssetView™ software, run only on the graphic cards listed above.

Other DecisionSpace software may have different requirements for graphics cards. For
detailed information on the graphics cards supported and tested in other DecisionSpace
software, refer to the Release Notes for the individual software. If you run Collaborative
Well Planning or the 3D Drill View KM™ software with the AssetView™ software, refer to
the AssetView™ Software Release Notes. If you run Collaborative Well Planning with the
GeoProbe® software, refer to the GeoProbe® Software Release Notes.

DecisionSpace software does not currently support ATI cards on desktops or laptops.

Software Requirements

The following table lists the software requirements required to run client installations of the
DecisionSpace software version 5000.0.1 on Windows workstations.

Software Version (for PC Client) Required By

Operating Windows XP Professional, Service Pack 2. Decision- All Products

System Space software was tested with the 32-bit version of
Windows XP on computers with either 32-bit or 64-bit
processors.
This release of DecisionSpace software was not
tested on Service Pack 1; however, the release
should operate reliably on Service Pack 1.

Connectivity Hummingbird Exceed 2007 OpenWorks® Software

Software

5000.0.1 Installation Guide Page 10 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Software Version (for PC Client) Required By

Oracle Client Oracle 10.2.0.3.0 OpenWorks® Software

OpenWorks The OpenWorks 5000.0.0.2 client (for connecting to OpenWorks Software

Clienta the OpenWorks 5000.0.0.2 server).

License Man- LAM 5000.0.0 All Products

agement The installation program and the documentation for
LAM 5000.0.0 can be downloaded from the Landmark
Software Manager (LSM). Select Technical Busi-
ness Line > Tools > LAM.

Document Adobe Reader 7.x (Adobe Acrobat Reader 5.x or All Products
Viewer Adobe Reader 6.x also displays PDF documents.)

DIMS DIMS 5000.0.0.1 (32-bit) 3D Drill View KM™ Software

only

EDM EDM 5000.0.0.1 3D Drill View KM™ Software

only

a. The OpenWorks client and its associated software are not required when running in non-Open-
Works mode.

For information on installing Oracle10g Enterprise Client 10.2.0.3.0 and OpenWorks

Client 5000.0.0.2, see the OpenWorks® Software Installation Procedures manual for
Release 5000.0.0.2.

Licensing

To run DecisionSpace® software, a workstation must have the relevant software features
in the license. For a list of features for your software, refer to the Release Notes for the
individual product.

Collaborative Well Planning

To use all the features of the software that are part of Collaborative Well Planning, you
must have a license feature for each of its software and for the OpenWorks software.
Without an OpenWorks license feature, or while running in non-OpenWorks mode,
software that are part of Collaborative Well Planning are only able to manipulate data from
the Wellbore Planner™ (WBP files) and COMPASS™ software. To use the EDM Import
or EDM Export options, refer to the Installing Well Planning section of the Collaborative
Well Planning Release Notes 5000.0.0.1.

5000.0.1 Installation Guide Page 11 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Installation on Windows

Following are procedures for installing the DecisionSpace® software 5000.0.1 on a

Windows workstation.

Pre-installation Step

Before you install the DecisionSpace software on Windows, install the OpenWorks®
5000.0.0.2 client. (See the OpenWorks® Software Installation Procedures manual for
Release 5000.0.0.2.)

Install the DecisionSpace Software

Installing the DecisionSpace software on a system that does not yet have the
DecisionSpace software version 5000.0.1 installed includes installing the following
DecisionSpace software:

• AssetView™ software

• Collaborative Well Planning - AssetView™ software

• Collaborative Well Planning - GeoProbe® software - only available on Windows 32-bit

systems.

• PowerGrid™ software

• PowerView® software

• PowerCalculator® software

• 3D Drill View KM™ software

To install the DecisionSpace software:

1. Log into the client computer with a user account that belongs to the Administrators
group on the DecisionSpace machine.

2. Download the DecisionSpace software from the LSM.

3. Navigate to:

DriveLetter:\Windows\Disk1\InstData\VM\setup.exe

5000.0.1 Installation Guide Page 12 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

4. Double-click the executable file.

The DecisionSpace 5000.0.1 dialog displays.

5. After reading the introduction, click Next.

The Launch Install Guide/Release Notes pane displays.

6. Select the Launch Release Notes and Launch Installation Guide checkboxes.

7. Click Next.

The License Agreement pane displays.

8. Select the I accept the terms of the License Agreement option.

9. Click Next.

The Choose Install Set pane displays.

10. Select each software you want to install.

11. Click Next.

The Choose Install Folder pane appears.

12. Specify where you want the DecisionSpace® software version 5000.0.1 to reside on
your machine.

Ensure that the install directory has at least 1 GB of free space if you want to install
the entire DecisionSpace suite (See page 5 for the list of DecisionSpace software).
You must also ensure that the default drive (usually C:) has at least 400 MB of free
space. The additional space on the default drive is necessary for temporary files
created during the installation.

13. Click Next.

The Desktop icon pane appears.

14. Specify if you want the desktop shortcuts.

15. Click Next.

The Pre-installation Summary pane appears.

16. Validate the information and click Install.

5000.0.1 Installation Guide Page 13 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

The installation process begins.

17. Click Done to close the installation program.

The main DecisionSpace® software installation is now complete.

It is not necessary to restart the system after the installation.

Uninstall the DecisionSpace Software (Optional)

You may want to uninstall the existing version of the DecisionSpace software to free up
disk space.

To uninstall the DecisionSpace software from your system:

1. Log on as a user with administrator privileges.

2. Select Start > Control Panel > Add or Remove Programs.

3. In the Add or Remove Programs dialog, select Landmark DecisionSpace xxx.xx.x

and click Change/Remove.

The DecisionSpace uninstall shield appears.

4. Click Next.

5. Select Complete Uninstall or Uninstall Specific Features.

6. Click Next.

7. Click Done to complete the uninstall process.

You do not need to reboot your system after the uninstall. If you have installed multiple
versions of the DecisionSpace software, uninstall them by navigating to the location
where you installed the DecisionSpace software and double-clicking
UninstallDecisionSpacexxx.xx.x.exe.

Remaining Files

An uninstall of the DecisionSpace software does not uninstall the session management
files that you may have saved when running a session. These files must be manually
deleted.

5000.0.1 Installation Guide Page 14 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Upgrading the DecisionSpace® Software

To upgrade a DecisionSpace software installation in the same location where you had
previously installed it, Landmark recommends that you first uninstall the previous
installation, and then install the current version as described in “Install the DecisionSpace
Software” on page 12.

Post-Installation Notes

This section includes information on the following:

• Removing previously created UI default settings and session files

• Configuring the license file

• Setting environment variables

• Setting the size of the cache, if needed

• Specifying where the output messages and files are stored

• Configuring the Pointing Dispatcher (PD) variables

Removing Previously Created UI Default Settings and Session Files

This section is relevant only if you are upgrading to Release 5000.0.1 from earlier versions
of the DecisionSpace software.

When you use the DecisionSpace software, certain user interface settings (such as entity
color, entity thickness, font size, etc.) and session files are stored on your computer. If
created in earlier versions of the DecisionSpace software, these files may not work well
in Release 5000.0.1 and should be removed. The pertinent files are not removed when
you remove a previous DecisionSpace software installation with the Start > Add or
Remove Programs command.

Files that contain DecisionSpace user interface settings are by default located
at %USERPROFILE%\Landmark\DecisionSpace. Old session files are similarly located
at %USERPROFILE%\Landmark\DecisionSpace\sessions. To delete the old files,

5000.0.1 Installation Guide Page 15 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

remove these two folders. They will be recreated with up-to-date files when the
DecisionSpace® software version 5000.0.1 is used for the first time.

What if you have multiple versions of the DecisionSpace software?

If you are running an older version of the DecisionSpace software and try to load a session
file created by the DecisionSpace software 5000.0.1, you may not receive an error
message, but you may see anomalies in the session itself.

Configuring the DecisionSpace Workstation to Connect to a Valid License File

The DecisionSpace workstation must be able to connect to a license.dat file that has
license keys for the various DecisionSpace software that you want to run. The license.dat
file must be hosted by a FLEXlm license server. Typically, the license server is installed
on the OpenWorks® server, although other configurations are possible.

To configure the DecisionSpace workstation to connect to a valid license.dat file, set up a

LM_LICENSE_FILE variable on the local workstation as follows:

1. Select Start > Control Panel > System. The System Properties dialog box displays.

2. In the Advanced tab, click the Environment Variables button to display the
Environment Variables dialog box.

3. Click the New button in the System Variables group box to display the New System
Variable dialog box.

4. Type LM_LICENSE_FILE in the Variable name text box.

5. Type a string in the Variable value text box. For example, your environment variable
can be as follows:

LM_LICENSE_FILE = \\Server\lam\license.dat

or

LM_LICENSE_FILE = <port>@<Server/IP>

where Server is the system name or IP address of the license server.

If you prefer to install a license server on your local workstation, refer to the OpenWorks®
Software Installation Procedures manual for Release 5000.0.0.2.

5000.0.1 Installation Guide Page 16 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Setting Environment Variables

With the exception of the LM_LICENSE_FILE variable discussed in the preceding

section, you do not need to set any environment variables for default functionality to work
in this release. However, you may want to set certain environment variables to address
specific issues.

LGC_LICENSE_REJECT Environment Variable

The LGC_LICENSE_REJECT environment variable allows you to specify the license

features that the DecisionSpace® software should ignore when launching.

To create the LGC_LICENSE_REJECT variable:

1. Select Start > Control Panel > System. The System Properties dialog box displays.

2. In the Advanced tab, click the Environment Variables button to display the
Environment Variables dialog box.

3. Click the New button in the System Variables group box to display the New System
Variable dialog box.

4. Type LGC_LICENSE_REJECT in the Variable name text box.

5. Type a string in the Variable value text box. The string represents the license features
that the DecisionSpace software should ignore when launching. For example, your
environment variable can be as follows:

LGC_LICENSE_REJECT=LicenseFeatureName1

or

LGC_LICENSE_REJECT=LicenseFeatureName1;LicenseFeatureName2;LicenseFeatur
eName3

where Feature is the name of the license feature that the DecisionSpace software
should ignore when launching. The feature names must be separated by a semi-colon.
For example, the LGC_LICENSE_REJECT variable can be as follows:

LGC_LICENSE_REJECT=PRECISIONTARGET;TRACPLANNER;DRILLVIEW_KM

DecisionSpace Software Cache Size

The settings of the localCache.properties file in com.lgc.ow.seis.localWrite directory

determine the size of the disk cache that DecisonSpace uses in the temporary (tmp or

5000.0.1 Installation Guide Page 17 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

temp) directory on the system. You can change the settings of this file to prevent the
DecisionSpace® software from filling up the system's temporary storage.

As a default, the DecisionSpace software cache is set to 200 MB. However, you may want
to adjust the size of the DecisionSpace software cache depending on the following
factors:

• The size of the system's temporary storage. If the temporary storage becomes filled,
software on the system may not function properly or may not function at all. The size
of the DecisionSpace software cache must always be smaller than the available
temporary storage.

• The demands of other software on the temporary storage.

• The data displayed in the DecisionSpace software. Ideally, the cache should be large
enough to hold all the data you will be using at one time in the DecisionSpace software.

For example, a seismic horizon may need around 20 MB of storage, and if you need to
display 50 horizons at one time, ideally, the cache should be at least 1 GB. However, the
cache may need to be smaller depending on other factors. A smaller cache can adversely
affect performance when manipulating the data.

The default settings of the localCache.properties file are as follows:

• tmpDir, the jvm argument, defines the location of the temporary files on the system. If
tmpDir is set to default, the default temporary directory (tmp or temp) on the
system is used.

• 3d-seismic shared cache is disabled.

• 2d-seismic shared cache is enabled with the size 1500 MB.

• 3d-horizon shared cache is enabled with the size 1500 MB.

Specifying a Directory for DecisionSpace Software Output

When you run the DecisionSpace software, by default, all DecisionSpace software write
their output files to %USERPROFILE%\Landmark\DecisionSpace. Files are written to
folders that correspond to their content type. These folders store sessions, color maps,
runtime messages, error messages, annotation data, image files (jpg, bmp, etc.), and UI
defaults. The files in these folders can become numerous and can occupy significant disk
space.

If you are concerned about the use of disk space

in %USERPROFILE%\Landmark\DecisionSpace, it is recommended that you set
LGC_DATA_HOME to a folder on a disk with more available space. The

5000.0.1 Installation Guide Page 18 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

LGC_DATA_HOME variable can be used to set a different location for the output files of
the DecisionSpace® software. Note that the pre-existing files will not be copied to the new
LGC_DATA_HOME location. This is not fatal but may cause some inconvenience.

To set the LGC_DATA_HOME variable, access the Environment Variables dialog box in
the System Properties dialog box (select Start > Control Panel > System > Advanced >
Environment Variables) and set the variable as follows:

LGC_DATA_HOME C:\DecisionSpace\output_data

About Log Files

The “%USERPROFILE%\ Landmark\DecisionSpace\logs” folder stores runtime

messages and error messages. A typical list of files in this directory is:

ConsoleOutput0.log

ConsoleOutput1.log

ConsoleOutput2.log

ConsoleOutput3.log

ConsoleOutput4.log

ConsoleOutput5.log

ConsoleOutput6.log

output-00.err

output-01.err

The ConsoleOutput[increment].log files contain various types of output messages that

would be printed to the console if it were open.

The output-[increment].err file contains only JAVA output messages.

A new log file is created each time you start a new session with the increment number
increasing by one each time. The number of log files of either type is limited to 10.

Setting Available Memory to the Java Virtual Machine

You can use the LGC_JAVA_XMX variable to allocate memory to the Java Virtual
Machine (JVM) when the default value of 1 GB is insufficient. You can verify whether the
default value of 1 GB is insufficient by looking at the .err log files for a Java out-of-memory
error. The LGC_JAVA_XMX variable specifies how much memory is reserved specifically
for the JVM as opposed to the memory available for non-Java code. Typical upper limits
for Java Xmx on 32-bit Windows systems would be around 1.7 GB or less.

5000.0.1 Installation Guide Page 19 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Changing the LGC_JAVA_XMX variable value may affect the DecisionSpace® software
performance. For example, if your workflow involves large seismic volumes, increasing
the Xmx variable value may increase performance for seismic data but could decrease
performance for other DecisionSpace software. Consult your onsite representative or call
Landmark customer support to change these variable values. To change the Xmx variable
value, the value should be defined in the following form:

768m

where “m” stands for megabytes, “k” for kilobytes, and no letter stands for bytes. If the
LGC_JAVA_XMX value is set too high, you may get an OpenGL error message. If this
occurs, try setting a lower LGC_JAVA_XMX value until the message no longer appears.

The LGC_JAVA_XSS environmental variable is used to set the maximum size of the Java
Virtual Machine's stack. This variable is defaulted to 4 MB. Consult your onsite
representative or call Landmark customer support if you want to change this value.

Configuring the Pointing Dispatcher (OpenWorks® Mode)

When you run the DecisionSpace software in OpenWorks mode, and if you will be using
the Pointing Dispatcher (PD), you may need to set some environment variables.

When you run the DecisionSpace software in OpenWorks mode, you may sometimes use
multiple OpenWorks PD sessions with different instance numbers. To transfer data from
a DecisionSpace software via PD to a particular OpenWorks session, set an environment
variable called OW_INSTANCE_NUMBER that specifies the same instance number as
the OpenWorks PD session.

If all your installed DecisionSpace software are running on the same platform, do not set
the LGC_PD environment variable. If, however, your software are on different platforms,
you need to set the environment variable LGC_PD to the hostname where PD is running
followed by the number of the PD.

For example, you may have three separate machines, one that is your OpenWorks server,
one that has AssetView® software installed, and one that has the OpenWire® software
installed. Usually, the OpenWorks server is configured as the PD server. In this situation,
the other two machines must be configured as PD clients to the PD server.

5000.0.1 Installation Guide Page 20 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

PD is normally session dependent. Setting the environment variables on client and server
machines allows users who are working in the same OpenWorks® project to receive
notifications of database updates.

Project Settings in the OpenWorks and DecisionSpace® Software

For your DecisionSpace software to receive any PD updates from the OpenWorks software, the
Project Status Tool in the OpenWorks project must be set to the same project as the one currently
being used in your DecisionSpace software.

To check the setting, select Programs > Landmark > OpenWorks > Project Administration >
Project Status. In the Project Status Tool window, if the Project text box is set to None
Selected or any project name other than the one currently being used in the DecisionSpace
software, click the List button next to the Project text box to display the Change Project dialog.
Select the project name currently selected in your DecisionSpace software from the Available
Projects list, and click OK. Relaunch the software to see the PD updates.

Configuring the PD Server

The PD server is usually the OpenWorks server. The PD server may be a Windows XP,
a Linux, or a Unix server.

For detailed information about PD, refer to the OpenWorks® Software Online Help.

Windows XP

To configure PD, you must know the host name where PD is running (for example,
wizard) and an open TCP port number (such as 20001).

1. Add the following PD variables to %OWHOME%\conf\lgcenv.cf:

LGC_PD HostName:TCP_PortNum

LGC_PD_SERVICE TCP_PortNum

PD_USE_SESSION_MGR NOThis variable is set to NO.

2. Restart the server.

If the OpenWorks software fails to read the PD environment variables when running PD,
manually set them in the Environment Variables dialog box. To display the Environment
Variables dialog box, select Start > Control Panel > System. Select the Advanced tab
in the System Properties dialog, and then click the Environment Variables button.

Unix or Linux Servers - When using Static PD

5000.0.1 Installation Guide Page 21 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Use the following steps if the Unix server is using Static PD (that is,
PD_USE_SESSION_MGR is set to NO).

To configure PD, you must know the host name where PD is running (for example,
wizard) and an open TCP port number (such as 20001). Enter the following in a
terminal window on the server:

setenv LGC_PD HostName:TCP_PortNum

setenv LGC_PD_SERVICE TCP_PortNum

You do not need to restart the server.

Unix or Linux Servers - When Dynamic PD is set

Use the following steps if the Unix server is using Dynamic PD (that is,
PD_USE_SESSION_MGR is set to YES).

To configure PD, you must know the host name where PD is running (for example,
wizard) and an open TCP port number (such as 20001). Enter the following in a
terminal window on the server:

$OWHOME/bin/pd -sname TCP_PortNum HostName:TCP_PortNum &

You do not need to restart the server.

Configuring the PD Client

For the following steps, the PD client is assumed to be on a Windows XP computer.

To configure PD on the client, you must know the host name where the PD server is
running (for example, wizard) and the TCP port number (such as 20001) that the PD
server is using.

1. Add the following line to %OWHOME%\conf\lgcenv.cf on the client:

LGC_PD HostName:TCP_PortNum

2. Set the LGC_PD variable in the System Properties dialog box in the Environment
Variables dialog box as it was set in lgcenv.cf. To display the Environment Variables
dialog box, select Start > Control Panel > System, select the Advanced tab in the
System Properties dialog, and then click the Environment Variables button.

3. Restart all PD dependent software.

4. To receive PD updates from the OpenWorks database, the PD client must be set to
the same OpenWorks project that is currently being updated. Therefore, before

5000.0.1 Installation Guide Page 22 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

launching a DecisionSpace® software, ensure that you select the appropriate project
in the OpenWorks® Project Status Tool. To open the OpenWorks Project Status Tool,
select Programs > Landmark > OpenWorks > Project Administration > Project
Status.

Installation Information

• The best way to avoid trouble during a DecisionSpace software installation is by

making sure that all hardware and software requirements are met before you begin
running DecisionSpace software. (See page 9 and page 10.) If your hardware is not
up to specification, the DecisionSpace software might still run, but its performance
may be significantly diminished. If you do not meet the software requirements, some
of the DecisionSpace software components will not run at all.

• The DecisionSpace software installer does not support a long directory path. Do not
install to a directory path greater than 25 characters. It is recommended to install to a
directory path with less than 20 characters.

• The DecisionSpace software installer does not support spaces in the directory path.
The installation prevents you from installing to a directory with spaces.

• The DecisionSpace software installer does not support special characters.

• OWSYSSID can be set by default in the background and may not be detected by you
until error messages appear when loading data. To set OWSYSSID, select Programs
> Landmark OpenWorks > Project Administration > Project Status Tool.

5000.0.1 Installation Guide Page 23 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

DecisionSpace® Software Workstation - Linux

DecisionSpace software 5000.0.1 supports Red Hat Linux Enterprise Workstation 5
running with an OpenWorks® 5000.0.0.2 server that has been upgraded to run Oracle
10.2.0.3.0.

Hardware Requirements

The table below lists the hardware requirements for Linux workstations running
DecisionSpace software 5000.0.1.

DecisionSpace software will run on the minimum requirements listed below. However,
performance may not reach acceptable levels with large or complex datasets.

Hardware Recommended Configuration

CPU Intel Pentium or Xeon

Intel EM64T or AMD Opteron (running on a 64-bit operat-
ing system)

Memory (RAM) 2 GB or greater

Hard Disk 1 GB is the installation size for the entire DecisionSpace

suite. Refer to the DecisionSpace Software Configuration
section on page 5 for the list of DecisionSpace software.
200 MB is the default cache size in the temporary directory
of the system. For more details, see “DecisionSpace Soft-
ware Cache Size” on page 31.

Display Dual monitor in TwinView: 1280 x 1024 per monitor

Color Depth: True Color (32-bit)

Graphics Card See “Graphics Cards” on page 24.

Mouse Microsoft-compatible 3-button mouse or 2-button mouse

with scroll wheel where the scroll wheel is configured as
the middle mouse button.

Installation Device Drive ESD/LSM

CD/DVD (in case you order the software)

Stereo Shutter Glasses VRex VR Visualizer shutter glasses

(Optional) (www.vrex.com/products/shutter_glasses.shtml)

Graphics Cards

The following graphics cards were tested by the DecisionSpace Quality Management
team for the Linux workstation. These cards can be expected to perform adequately.

5000.0.1 Installation Guide Page 24 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

DecisionSpace® software Desktop Workstation (Linux 64-bit) - nVidia Quadro FX 4500

and nVidia Quadro FX 3450 (PCI Express Bus). These cards were tested with version
100.14.19 of the nVidia driver for Linux.

It is recommended that DecisionSpace software that require high-end cards, such as the
AssetView™ or Well Seismic Fusion™, run only on the graphic cards listed above.

Other DecisionSpace software may have different requirements for graphics cards. For
detailed information on the graphics cards supported and tested in other DecisionSpace
software, refer to the Release Notes for the individual product. If you run WellPlanning or
the 3D Drill View KM™ software with the AssetView™ software, refer to the AssetView™
Software Release Notes. If you run WellPlanning with the GeoProbe® software, refer to
the GeoProbe® Software Release Notes.

DecisionSpace software does not currently support ATI cards.

Intel EM64T Processor, the nVidia driver, and SWIOTLB

Linux does not currently provide a mechanism for allocating memory with addresses that
fall within the first 4 GB of memory on a computer with Intel's EM64T processor. Some
implementations of the swiotlb kernel parameter set aside a very small amount of memory
for its memory pool (4 MB). Exhaustion of this pool might cause a kernel panic. Panic is
an unrecoverable error detected by the kernel.

To avoid memory problems or a panicked kernel, increase the size of the pool. To
increase the pool, use the following parameter in the kernel command line:

swiotlb=IntegerNumeric

nVidia suggests raising the size of the pool to 32 MB when using its driver. For example,
pass the following value to the kernel:

swiotlb=16384

With kernel 2.6.9, the default size of the pool was raised to 64 MB, and mechanisms for
handling situations when the pool becomes filled have improved.

Note: The information in this section is from the Readme file for the nVidia drivers. For
more information, see the Readme file included with the drivers.

5000.0.1 Installation Guide Page 25 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Software Requirements

Software Version (for PC Client) Required By

Operating System Red Hat Linux Enterprise Workstation 5. All products

DecisionSpace® software was tested with the 64-bit
kernel on computers with 64-bit processors.

Desktop Environment Gnome or KDE All products

Database Client Oracle 10.2.0.3.0 OpenWorks®

Software

OpenWorks Software- OpenWorks 5000.0.0.2 client for connecting to the OpenWorks

Clienta OpenWorks 5000.0.0.2 server. Software

License Management LAM 5000.0.0 All products

The installation program and the documentation for
LAM 5000.0.0 can be downloaded from the Landmark
Software Manager (LSM). Select Technical Busi-
ness Line > Tools > LAM.

Document Viewer Adobe Reader 7.x (Adobe Acrobat Reader 5.x or All products
Adobe Reader 6.x also displays the PDF documents.)

a. The OpenWorks® client and its associated software are not required when running in non-
OpenWorks® mode.

For information on installing Oracle 10.2.0.3.0, OpenWorks Client 5000.0.0.2, and Adobe
Acrobat Reader, see the OpenWorks® Software Installation Procedures manual for
Release 5000.0.0.2.

For information on installing LAM 5000.0.0, refer to the LAM Guide for Release 5000.0.0.

Licensing

Each DecisionSpace software requires that one or more product-specific license keys be
listed in the Landmark license file. For a list of the available license keys, refer to the
Release Notes for the individual product.

Collaborative Well Planning

To be able to use all the features of the software that are part of Collaborative Well
Planning, you must have a license feature for each of its software and for the OpenWorks
software. Without an OpenWorks® license feature, or while running in non-OpenWorks
mode, the software that are part of Collaborative Well Planning are only able to
manipulate data from the Wellbore Planner™ (WBP files) and COMPASS™ software. For

5000.0.1 Installation Guide Page 26 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

information on using EDM™, refer to the Collaborative Well Planning Release Notes
5000.0.0.1.

Installation on Linux

The following section provides procedures for installing the DecisionSpace® software
version 5000.0.1 on a Linux workstation.

Pre-installation Step

Before you install the DecisionSpace software on Linux, install the OpenWorks®
5000.0.0.2 client. (See the OpenWorks® Software Installation Procedures manual for
Release 5000.0.0.2.)

Install the DecisionSpace Software

The following steps explain the installation of the DecisionSpace software on a Linux
system that does not yet have the DecisionSpace software version 5000.0.1 installed. The
installation on Linux currently includes the following DecisionSpace software:

• AssetView™ software

• Collaborative Well Planning - AssetView™ software

• Collaborative Well Planning - GeoProbe® software - only available on Windows 32-bit

systems.

• PowerGrid™ software

• PowerView® software

• PowerCalculator® software

• Well Seismic Fusion™ software - available only on Linux 64-bit systems.

• 3D Drill View KM™ software

5000.0.1 Installation Guide Page 27 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

To install the DecisionSpace® software:

1. Log into the client machine with a Linux user account that has write permissions for
the area where you want to install the DecisionSpace software.

2. Navigate to your home directory or to some other directory where you have execute
write permissions.

3. Download the DecisionSpace Launcher software from the LSM.

or

If you ordered the CD/DVD, mount the CD.

mount /mnt/cdrom

4. Execute the command below that matches your operating system:

/tmp/Disk1/InstData/Linux64/VM/setup.bin(for Linux 64-bit)

/tmp/Disk1/InstData/Solaris/VM/setup.bin(for Solaris)

if you ordered the CD/DVD:

/mnt/tmp/Disk1/InstData/Linux64/VM/setup.bin(for Linux 64-bit)

/mnt/tmp/Disk1/InstData/Solaris/VM/setup.bin(for Solaris)

where, tmp is the download location.

The DecisionSpace 5000.0.1 dialog displays.

Important: Do not execute the install command from within the mounted directory
system. If you do, the installation hangs when you are prompted to eject CD 1.

5. After reading the introduction, click Next.

The Launch Install Guide/Release Notes pane displays.

6. Select the Launch Release Notes and Launch Installation Guide checkboxes.

7. Click Next.

The License Agreement pane displays.

8. Select the I accept the terms of the License Agreement option.

9. Click Next.

The Choose Install Set pane displays.

5000.0.1 Installation Guide Page 28 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

10. Select each software you want to install.

11. Click Next.

The Choose Install Folder pane displays.

12. Specify where you want the DecisionSpace® software version 5000.0.1 to reside on
your machine.

Ensure that the install directory has at least 1 GB of free space if you want to install
the entire DecisionSpace software suite. See page 4 for the list of DecisionSpace
software.

Also, ensure that the default drive (usually the home directory for the user login) has
at least 400 MB of free space. This space on the default drive is necessary for
temporary files created during the installation.

13. Click Next.

The Desktop icon pane displays.

14. Specify if you want the desktop shortcuts.

15. Click Next.

The Pre-installation Summary pane displays.

16. Validate the information and click Install.

The installation process begins.

17. Click Done to close the installation program.

The main DecisionSpace software installation is now complete. See “Post-Installation

Notes” on page 30 for additional installation settings.

It is not necessary to reboot after the installation.

Upgrading the DecisionSpace Software

To upgrade a DecisionSpace software installation in the same location where you had
previously installed it, we would recommend that you first uninstall the previous
installation, and then install the current version as described in “Install the DecisionSpace
Software” on page 27.

5000.0.1 Installation Guide Page 29 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Post-Installation Notes

This section includes information on the following:

• Configuring the workstation to connect to a valid license file

• Setting the size of the cache, if needed

• Specifying a directory for DecisionSpace® software output files

• Selecting KDE as the desktop manager

• Creating a DecisionSpace software launch icon

• Uninstalling the DecisionSpace software

Configuring the Workstation to Connect to a Valid License File

The DecisionSpace software workstation must be able to connect to a license file

(normally license.dat) that has license keys for the various DecisionSpace software that
you want to run. The license.dat file must be hosted by a Landmark License Application
Manager (LAM) server. Typically, the license server is installed on the OpenWorks®
server, although other configurations are possible.

If you have installed DecisionSpace software with the OpenWorks software as an LGC
user, to configure the DecisionSpace software workstation to connect to a valid license
file, set the LM_LICENSE_FILE variable in .lgclogin (depending on the shell type being
used on Linux) as follows:

Variable Definition Initialization File

• setenv LM_LICENSE_FILE /home/landmark/lam/ .lgclogin

license.dat (if you have installed the LAM and the
OpenWorks server locally)
• setenv LM_LICENSE_FILE <port>@<Server/IP> (if
you have installed the OpenWorks server locally or on a
network)
• export LM_LICENSE_FILE=/home/landmark/lam/
license.dat setenv LM_LICENSE_FILE
<port>@<Server/IP> (if you have installed the LAM and the
OpenWorks server locally)
• export LM_LICENSE_FILE=<port>@<Server/IP> (if
you have installed the OpenWorks server locally or on a
network)

where Server is the system name or IP address of the license server.

5000.0.1 Installation Guide Page 30 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

If you have installed DecisionSpace software without the OpenWorks software, you can
set the LM_LICENSE_FILE variable in your login profile files (depending on the shell type
being used on Linux).

To install the license server on your local workstation, see the OpenWorks® Software
Installation Procedures manual for Release 5000.0.0.2 for instructions.

LGC_LICENSE_REJECT environment variable

The LGC_LICENSE_REJECT environment variable allows you to specify the license

feature(s) that the DecisionSpace® software should ignore when launching.

To create the LGC_LICENSE_REJECT variable, do as follows:

1. Open the .lgclogin file located in your Home directory.

2. Set the value of the LGC_LICENSE_REJECT environment variable. The string

represents the license features that the DecisionSpace software should ignore when
launching. For example, your environment variable can be as follows:

setenv LGC_LICENSE_REJECT LicenseFeatureName1

or

setenv LGC_LICENSE_REJECT LicenseFeatureName1:LicenseFeatureName2

where Feature is the name of the license feature that the DecisionSpace software
should ignore when launching. The feature names must be separated by a colon. For
example, the LGC_LICENSE_REJECT variable can be as follows:

setenv LGC_LICENSE_REJECT PRECISIONTARGET:TRACPLANNER:DRILLVIEW_KM

DecisionSpace Software Cache Size

The settings of the localCache.properties file in com.lgc.ow.seis.localWrite

directory determine the size of the disk cache that DecisonSpace uses in the temporary
(tmp or temp) directory on the system. You can change the settings of this file to prevent
the DecisionSpace software from filling up the system's temporary storage.

As a default, the DecisionSpace software cache is set to 200 MB. However, you may want
to adjust the size of the DecisionSpace software cache depending on the following
factors:

• The size of the system's temporary storage. If the temporary storage becomes filled,
software on the system may not function properly or may not function at all. The size
of the DecisionSpace software cache must always be smaller than the available

5000.0.1 Installation Guide Page 31 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

temporary storage.

• The demands of other software on the temporary storage.

• The data displayed in DecisionSpace software. Ideally, the cache should be large
enough to hold all the data you will be using at one time in DecisionSpace software.

For example, a seismic horizon may need around 20 MB of storage, and if you need to
display 50 horizons at one time, ideally, the cache should be at least 1 GB. However, the
cache may need to be smaller depending on other factors. A smaller cache can adversely
affect performance when manipulating the data.

The default settings of the localCache.properties file are as follows:

• tmpDir, the jvm argument, defines the location of the temporary files on the system.
If tmpDir is set to default, the default temporary directory (tmp or temp) on the
system is used.

• 3d-seismic shared cache is disabled.

• 2d-seismic shared cache is enabled with the size 1500 MB.

• 3d-horizon shared cache is enabled with the size 1500 MB.

Specifying a Directory for DecisionSpace® Software Output

When you run DecisionSpace software, by default, all DecisionSpace software write their
output files to %HOME\run. Files are written to folders that correspond to their content
type.

These folders store sessions, color maps, runtime messages, error messages, annotation
data, image files (jpg, bmp, etc.), and UI defaults. The files in these folders can become
numerous and can occupy significant disk space. If you are concerned about the use of
disk space in %HOME\run, we recommend that you set the LGC_DATA_HOME variable
to a folder on a disk with more available space. Note that pre-existing files will not be
copied to the new LGC_DATA_HOME location. This is not fatal but may cause some
inconvenience.

Set the LGC_DATA_HOME variable in your .lgclogin or .lgcprofile file, using a line like the
following:

Variable Definition Initialization File

setenv LGC_DATA_HOME /DecisionSpace/session_data .lgclogin

5000.0.1 Installation Guide Page 32 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Variable Definition Initialization File

LGC_DATA_HOME=/DecisionSpace/session_data .lgcprofile
export LGC_DATA_HOME

Selecting KDE as the Preferred Desktop Manager

Red Hat Linux Workstation 3.0 ships with GNOME as its default desktop manager. If you
want to change your default desktop manager to KDE:

1. Select the “footprint” icon > System Settings > More System Settings > Desktop
Switching Tool.

2. Select KDE.

3. Log out and log back in.

Creating a DecisionSpace® Software Launch Icon

KDE

To place a DecisionSpace software launch icon on your desktop using the KDE window
manager:

1. Right-click on the desktop.

2. Select Create New > Link to Application.

3. In the Properties for Program window, replace the text “Link to Application” with a
name for the icon, (i.e., “Launch DS”)

4. Click the button with the KDE icon.

The icon source button displays.

5. Select the Other icons radio button.

6. Click the Browse button.

7. Navigate to the DecisionSpace software installation directory.

8. Type in “Landmark.ico” in the Location text area.

5000.0.1 Installation Guide Page 33 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

9. Click OK.

The Properties for Program window now displays the Landmark icon.

10. Click on the Execute tab.

11. Click the Browse button.

12. Select Launch.sh in the directory where you installed the DecisionSpace software.

You can also select noOpenWorksLaunch.sh in the directory where you installed the
DecisionSpace® software if you have installed the AssetView™, Nexus™,
PowerView®, and WellPlanning - AssetView™ software.

13. Click OK to finish setting the properties.

The Landmark icon with “Launch DS” text displays. When you double-click the shortcut,
the DecisionSpace software launches.

You can drag the icon on the desktop and drop it on the launch panel bar at the bottom of
the screen to provide access to the DS launcher.

GNOME

To place a DecisionSpace software launch icon on your desktop using the GNOME
window manager:

1. Right-click on the desktop.

2. Select New Launcher.

The Create Launcher dialog box displays.

3. Specify a name for the icon in the Name field, (i.e., “Launch DecisionSpace”).

4. In the Command field, click the Browse button. Navigate to the DecisionSpace
software installation directory and select Launch.sh.

You can also select noOpenWorksLaunch.sh in the directory where you installed
DecisionSpace software, if you have installed AssetView™, PowerView®, and
WellPlanning - AssetView™ software.

5. Set the Type setting to “Application.”

6. Click the Icon button. Navigate to the DecisionSpace software installation directory
and select “Landmark.ico.”

5000.0.1 Installation Guide Page 34 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

7. Click OK.

You should now see an icon with the LGC logo and the text “Launch DecisionSpace.”
When you double-click on the shortcut, the DecisionSpace software launches.

You can drag the icon on the desktop and drop it on the launch panel bar at the bottom of
the screen to provide access to the DS launcher.

Uninstalling the DecisionSpace® Software

The DecisionSpace software installer on Linux does not automatically detect an existing
DecisionSpace software installation and provide an uninstall option.To uninstall the
DecisionSpace software:

1. Navigate to the “UninstallDecisionSpace2003.19.x” directory, which is typically

located in the directory where you installed DecisionSpace software 2003.19.x (such
as /Landmark/DecisionSpace).

2. From this directory, run the UninstallDecisionSpace2003.19.x shell script.

Note: If you installed the DecisionSpace software as a root user, you must uninstall it
as a root user.

The DecisionSpace Uninstall shield starts.

3. Select Complete Uninstall or Uninstall Specific Features. If you select Uninstall

Specific Features, the DecisionSpace software prompts you to select the software to
be uninstalled.

4. Click Next and Done to complete the uninstall process.

Installation Information

• The best way to avoid trouble during a DecisionSpace software installation is to ensure
that all hardware and software requirements are met before you begin running
DecisionSpace software. (See page 26 and page 24.) If your hardware is not up to
specification, DecisionSpace software might still run, but its performance may be
significantly diminished. If you do not meet the software requirements, some of the
DecisionSpace software components will not run at all.

• The DecisionSpace software installer does not support a long directory path. Do not
install to a directory path greater than 25 characters. We recommend installing to a
directory path with less than 20 characters.

• The DecisionSpace software installer does not support special characters.

5000.0.1 Installation Guide Page 35 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

• OWSYSSID can be set by default in the background and may not be detected by you
until error messages appear when loading data. To set OWSYSSID, select
Programs > Landmark > OpenWorks > Project Administration > Project Status.

• If the Linux DecisionSpace software installer aborts during an installation, it may try to
resume the installation process from wherever it failed during the initial installation
attempt. In this case, we recommend that you delete any target folders that were
created before beginning the installation process again.

• If you copy files from your Windows to your Linux system, you may encounter
problems if the files are not converted to UNIX format. For example, a copied but
unedited dir.dat file may cause errors in locating SeisWorks® data. DecisionSpace®
software is sensitive to DOS versus the UNIX/Linux format and will fail silently when
the format is incorrect. This silent failure can result in some data being visible in
DecisionSpace software while other data is not visible.

To resolve this problem, ensure that you have done one of the following for any dir.dat
file copied from your Windows to your Linux system:

• Run dos2unix against the Linux dir.dat file.

• Edit with a UNIX-based editor, and add extra spaces to the nonsys entries in the
dir.dat file.

This should be a standard practice for any text-based configuration files you copy from
Windows to Linux systems.

5000.0.1 Installation Guide Page 36 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Installing the DecisionSpace® Software in Silent Mode

The DecisionSpace installation program provides you an option to install in silent mode
on Windows and Linux. The graphical interface of the installation program does not
display during a silent install. For a silent mode installation, you must create a properties
file and execute a command at the command line. For a silent install:

1. Create a properties file, and save it in any location. For example, the name of your
properties file can be ds.properties.

2. Enter the following script in the properties file:

For Windows

INSTALLER_UI=silent

USER_INSTALL_DIR=TargetDirectory

CHOSEN_INSTALL_FEATURE_LIST=FeatureList

SHORTCUT_DESKTOP=1

SHORTCUT_DESKTOP_NOOW=1

SHORTCUT_START_MENU=1

SHORTCUT_START_MENU_NOOW=1

For Linux

INSTALLER_UI=silent

USER_INSTALL_DIR=TargetDirectory

CHOSEN_INSTALL_FEATURE_LIST=FeatureList

SHORTCUT_DESKTOP=1

SHORTCUT_DESKTOP_NOOW=1

where

• TargetDirectory is the full path to the base folder where you want the software
installed

• FeatureList is the list of software for the installation program to install

• SHORTCUT_DESKTOP allows you to create an icon on the desktop to launch the

DecisionSpace software in the OpenWorks® mode. Set the value to 1 to create the
icon and to 0 to not to create the icon.

• SHORTCUT_DESKTOP_NOOW creates an icon on the desktop in the non-OpenWorks

mode. Set the value to 1 to create the icon and to 0 to not to create the icon.

5000.0.1 Installation Guide Page 37 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

• SHORTCUT_START_MENU creates an icon on the Window’s Start menu to launch

DecisionSpace® software in the OpenWorks® mode. Set the value to 1 to create the
icon and to 0 to not to create the icon.

• SHORTCUT_START_MENU_NOOW creates an icon on the Window’s Start menu to

launch DecisionSpace software in the non-OpenWorks mode. Set the value to 1 to
create the icon and to 0 to not to create the icon.

Note: On Windows, the TargetDirectory path must be defined using forward slashes
(/) to delineate the directories. For example:

USER_INSTALL_DIR=C:/Landmark/DecisionSpace5000.0.1

FeatureList must have one of the following forms:

ApplicationName

or

ApplicationName1,ApplicationName2, ApplicationName3

If you are installing more than one software, each name must be separated by a
comma. Use the following names to specify the software you want to install:

AV AssetView™ software

KM 3D Drill View KM™ software

PC PowerCalculator® software

PG PowerGrid™ software

PV PowerView® software

WPAV WellPlanning - AssetView™ software

WPGP WellPlanning - GeoProbe® software

WSF Well Seismic Fusion™ software

Windows

1. Go to Start > Run.

The Run dialog appears.

5000.0.1 Installation Guide Page 38 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

2. In the Run dialog, click the Browse button and navigate to the setup.exe file.
Double-click the file. It will be located at:

DriveLetter\Windows\Disk1\InstData\VM\setup.exe

3. To the path to the executable file in the Open field, append the following:

-f path_to_properties_file

where path_to_properties_file means the full path to the properties file you had saved
earlier.

As an example, a full installation execution string might look like the following:

DriveLetter/Landmark/DecisionSpace/setup.exe –f C:\temp\ds.properties

4. Select OK from the Run dialog to begin the installation in the silent mode.

Linux

1. Open a terminal session and navigate to the setup.bin file. It will be located at:

/Landmark/DecisionSpace/setup.bin

2. Execute the setup.bin file.

3. Append the following to the path of the executable file:

–f /temp/ds.properties

where path_to_properties_file means the full path to the properties file you have saved
earlier.

As an example, a full installation execution string might look like the following:

DriveLetter/Landmark/DecisionSpace/setup.exe –f C:/temp/ds.properties

The installation begins in the silent mode.

5000.0.1 Installation Guide Page 39 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Installing the DecisionSpace Launcher® Software

DecisionSpace Launcher software 5000.0.1 supports Red Hat Linux Enterprise
Workstation 5.

Hardware Requirements

The table below lists the hardware requirements for Linux workstations running
DecisionSpace Launcher software 5000.0.1.

DecisionSpace Launcher software will run on the minimum requirements listed below.
However, performance may not reach acceptable levels with large or complex datasets.

Hardware Recommended Configuration

CPU Intel Pentium or Xeon

Intel EM64T or AMD Opteron (running on a 64-bit operat-
ing system)

Memory (RAM) 2 GB or greater

Hard Disk 200 MB is the installation size for the DecisionSpace

Launcher® software.

Display Dual monitor in TwinView: 1280 x 1024 per monitor

Color Depth: True Color (32-bit)

Mouse Microsoft-compatible 3-button mouse or 2-button mouse

with scroll wheel.

Installation Device Drive ESD/LSM

CD/DVD (in case you order the software)

5000.0.1 Installation Guide Page 40 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Software Requirements

Software Version (for PC Client) Required By

Operating System Red Hat Linux Enterprise Workstation 5. All products

DecisionSpace® software was tested with the 64-bit
kernel on computers with 64-bit processors.

Document Viewer Adobe Reader 7.x (Adobe Acrobat Reader 5.x or All products
Adobe Reader 6.x also displays the PDF documents.)

For information on installing Oracle 10.2.0.3.0, OpenWorks® Client 5000.0.0.2, and

Adobe Acrobat Reader, see the OpenWorks® Software Installation Procedures manual
for Release 5000.0.0.2.

For information on installing LAM 5000.0.0, refer to the LAM Guide for Release 5000.0.0.

To install the DecisionSpace Launcher software on a Linux system:

1. Log into the client machine with a Linux user account that has write permissions for
the area where you want to install DecisionSpace software.

2. Navigate to your home directory or to some other directory where you have execute
write permissions.

3. Download the DecisionSpace Launcher software from the LSM.

or

If you ordered the CD/DVD, mount the CD, if necessary.

mount /mnt/cdrom

4. Execute the command below:

/tmp/Disk1/InstData/Linux64/VM/setup.bin

or

/mnt/tmp/Disk1/InstData/Linux64/VM/setup.bin (in case you ordered CD/

DVD)

where, tmp is the download location.

The DecisionSpace Launcher 5000.0.1 window displays.

Important: Do not execute the install command from within the mounted directory

5000.0.1 Installation Guide Page 41 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

system. If you do, the installation hangs when you are prompted to eject CD 1.

5. After reading the introduction, click Next.

The License Agreement pane displays.

6. Select the I accept the terms of the License Agreement option.

7. Click Next.

The Choose Install Folder pane displays.

8. Specify where you want DecisionSpace Launcher® software version 5000.0.1 to

reside on your machine.

9. Click Next.

The Desktop Shortcut pane displays.

10. Select the Create Desktop Shortcut checkbox.

The Pre-installation Summary pane displays.

11. Validate the information and click Install.

The installation process begins.

12. Click Done to close the installation program.

Uninstalling the DecisionSpace Launcher Software

The DecisionSpace Launcher software installer on Linux does not automatically detect an
existing DecisionSpace software installation and provide an uninstall option.To uninstall
the DecisionSpace Launcher software:

1. Navigate to the “Uninstall_DecisionSpace5000.0.1” directory, which is typically

located in the directory where you installed the DecisionSpace Launcher software
(such as /Landmark/DecisionSpace).

2. From this directory, run the Uninstall_DecisionSpace5000.0.1 shell script.

Note: If you installed the DecisionSpace software as a root user, you must uninstall it
as a root user.

The Uninstall DecisionSpace 5000.0.1 dialog displays.

5000.0.1 Installation Guide Page 42 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

3. Click Next.

The Uninstall Option pane displays.

4. Select Complete Uninstall or Uninstall Specific Features. If you select Uninstall

Specific Features, the DecisionSpace® software prompts you to select the software to
be uninstalled.

5. Click Next.

The uninstallation process begins.

6. Click Done to complete the uninstall process.

5000.0.1 Installation Guide Page 43 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Obtaining a License to Run the Software

Before running DecisionSpace® software, you must obtain a license file from Landmark
Graphics Corporation. Request the license file from:

http://www.halliburton.com/customersupport/Licensemanagement

If you have any questions, call your Landmark Customer Services Representative, or see:

http://www.halliburton.com

You must have the hostid of the system where the license.dat file will reside to request a
license. To obtain the hostid, enter the following:

Operating System Command

SUN/Solaris and Linux hostid

Systems

IBM/AIX Systems uname -m

SIG/IRIX Systems /etc/sysinfo -s

Windows Systems ipconfig /allfrom a Command

Prompt window

Installing the Software License

Upon receiving the license request, a Landmark representative generates and returns
your license. The license contains information such as:

• Product name

• Version

• Expiration date

• Number of copies

• Encrypted key

For example, a license for five copies of the Well Seismic Fusion™ software is similar to
the line below:

FEATURE WSFUSION licsrv 5000.0.1 10-nov-2008 5

AKEY42AAD7898675309F VENDOR_STRING="Ewing Oil”

5000.0.1 Installation Guide Page 44 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Once you receive your license, add your license.dat file to your system and restart the
license manager. After the license manager has been restarted, you are able to use your
newly installed software.

For more information on managing the LAM, refer to the LAM Guide for Release 5000.0.0.

5000.0.1 Installation Guide Page 45 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Troubleshooting

Increasing the Granularity of Error Messages

Caution

Instructions below tell you how to edit the configuration file to increase the diagnostic level
of the DecisionSpace® software. This reconfiguration should be used for support purposes
only and should not be done unless instructed to do so by Landmark representatives. If
you do increase the diagnostic level, ensure that you change it back to the normal usage
before running DecisionSpace software, as running the software at the increased level
substantially reduces performance.

When a program is executed, any prints and diagnostics are sent to a log file,
ConsoleOutput<Increment>.log on Windows, and DecisionSpace5000.0-
<Increment> on Linux, where Increment is a number from 0 to 9. To avoid accumulating
too many files and taking up too much space, the number of files is limited to 10. A new
log file is created each time you start a new session with the increment number increasing
by one each time up to 9 and then repeating at 0 by overwriting the existing file.

On Windows, these files are stored in:

C:\Documents and Settings\username\Landmark\DecisionSpace\logs

or

%USERPROFILE%\Landmark\DecisionSpace\logs

On Linux, they are stored in:

$HOME/run

You can identify the most recent files in Windows Explorer by viewing the file details
(select View > Details), or by using the -tr options for the ls command in Linux.

You can increase the diagnostic level to get more messages to help Landmark support
and onsite consultants diagnose problems. To increase the diagnostic level when
instructed to do so:

1. Open the configuration file logging.properties in a text editor. On Windows,

the file is typically located at:

C:\Landmark\DecisionSpace5000.0.1\modules\dsinfra\config\logging
.properties

On Linux, the location of the DecisionSpace installation is user-specified, so the file

will be located at:

5000.0.1 Installation Guide Page 46 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Install_path/DecisionSpace5000.0.1/modules/dsinfra/config/
logging.properties

2. Find the Default Global Logging Level line. The line is similar to the following:

# Default Global Logging Level

.level= xxx where xxx is CONFIG by default

Change it to:

# Default Global Logging Level

com.lgc.level= FINEST

3. Save the edited file.

Now, whenever you run DecisionSpace® software, more detailed diagnostic

messages are generated.

REMEMBER: When you are not trying to diagnose a problem, do not leave this
diagnostic setting set to FINEST . This setting substantially decreases performance.
To return the diagnostic level to normal usage, re-edit the logging.properties file
to:

com.lgc.level=CONFIG

Issues Accessing OpenWorks® Databases

An OpenWorks or DecisionSpace client may encounter problems accessing an

OpenWorks database when the alias for the system identifier (SID) of the database has
changed or when the alias for the SID includes a domain name (such as
DatabaseName.company.com).

Access problems can be exacerbated in an environment where some SID aliases include
a domain name and others do not, or in an environment where SID aliases include domain
names, and Unix (or Linux) and Windows clients are accessing those databases. In this
last case, if the same tnsnames.ora is placed on each client, some clients may be able
to access some databases and some may not be able to access other databases.

The cause of these access problems are partially associated with not using the Landmark-
recommended format for SIDs and are associated with how the OpenWorks software
uses and stores those names.

5000.0.1 Installation Guide Page 47 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

How the OpenWorks® Software for Windows Uses SID Aliases

The OpenWorks software in Windows uses aliases for SIDs differently from the
OpenWorks software in the Unix or Linux operating systems. As the OpenWorks software
for Windows reads tnsnames.ora, it strips the domain portion of an alias from each SID
listed in the file. The OpenWorks software in other operating systems does not strip the
domain name from the SID alias.

In the OpenWorks software version 2003.12.0.0, the OW_TNS_STRIP environment

variable was established for the OpenWorks software running in Windows. If the variable
is set to zero, the OpenWorks software leaves the domain name in the SID alias, or if it is
set to one, the OpenWorks software strips the domain portion of the alias as in previous
versions of the OpenWorks software in Windows.

This environment variable is not included in some initialization files for a user on a system.
It is included in a file in the installation of the OpenWorks software in Windows. The file is
lgcenv.cf. It has no effect in the OpenWorks software on any operating system, except
Windows. This file is located in %OWHOME%/conf. The variable can have the following
settings:

OW_TNS_STRIP 0Prevents OpenWorks in Windows from stripping domain names from

SID aliases.

OW_TNS_STRIP 1Allows OpenWorks in Windows to strip domain names from SID

aliases.

If this variable is not set in lgcenv.cf, the OpenWorks software in Windows acts as if
the variable has been set to one.

Storage Of SID Aliases in an OpenWorks Server

The OpenWorks server stores the alias of the SID for the OpenWorks database in the
database itself. From a client perspective, the SID alias of an OpenWorks database is
stored in tnsnames.ora. For a client to access an OpenWorks database, the alias
stored in the OpenWorks database and tnsnames.ora must match.

The Oracle user can check the value of the SID alias by entering the following at an
SQL*Plus prompt:

select node_db_name from ow_sys_project;

For example, to check the SID alias, the Oracle user enters the following:

[oracle10g@name admin]$ sqlplus owsys/owsys@SID_Name

Response from SQL*Plus

SQL> select node_db_name from ow_sys_project;

5000.0.1 Installation Guide Page 48 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

NODE_DB_NAME

----------------------------------------------------------------

SID_Name

SQL> exit

Response from SQL*Plus

[oracle10g@name admin]$

Recommendations

To access OpenWorks® databases, it is recommended that:

• When naming OpenWorks SIDs on a local network, all the SID aliases should use the
same format. For example, a format could be:

• An alias with the format indicated in the OpenWorks® Software Installation

Procedures manual (InstallProcedures.PDF), where identifiers are composed of
letters and numbers only, begin with a letter, and are four to eight characters.

or

• An alias composed of the database name and a domain name (for example,
DatabaseName.Company.com).

• The alias of a SID in tnsnames.ora must be the value of NODE_DB_NAME in the

OW_SYS_PROJECT table.

• If the name of a database changes, the database administrator must change the name
in tnsnames.ora on each client accessing the database and the name must match
the value of NODE_DB_NAME in the OW_SYS_PROJECT table.

• If the clients on Windows access databases with SID aliases that include a domain
name, the OW_TNS_STRIP variable must be entered in %OWHOME%/conf/
lgcenv.cf, and must be set to zero. For example:

OW_TNS_STRIP 0

• If the SIDs accessed from a particular client have aliases with more than one domain
name, comment out or delete a line similar to the following in sqlnet.ora :

names.default_domain = DomainName

To comment out the line, enter a pound sign ( # ) at the beginning of the line:

# names.default_domain = DomainName

5000.0.1 Installation Guide Page 49 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Changing the SID Alias in an OpenWorks® Database

To change the SID alias in an OpenWorks database, the Oracle user must enter the
following at an SQL*Plus prompt:

update ow_sys_project set node_db_name='OldName' where

node_db_name='NewName';

For example, do as follows:

[oracle10g@name admin]$ sqlplus owsys/owsys@SID_Name

Response from SQL*Plus

SQL> update ow_sys_project set node_db_name='OldName' where

node_db_name='NewName';

Response from SQL*Plus

SQL> exit

Response from SQL*Plus

[oracle10g@name admin]$

REMEMBER: After changing a SID in the database, check tnsnames.ora of each

client to ensure that the client refers to the same name as is stored in the database.

Issues with the Firewall in Windows XP Service Pack 2

When Service Pack 2 is first installed in Windows XP, the Windows Firewall is on by
default. Some of its default settings conflict with the seamless running of DecisionSpace®
software, its help files, and other Landmark software.

Listed below are issues that have been encountered as of this writing:

• To use Hummingbird Exceed to display DecisionSpace software or the OpenWorks

software, both Hummingbird Exceed and PDBIN must be unblocked. On the first
attempt to start one of the software or modules, you may need to try to run it two or
three times before it will run. After that, the software or module (and the others) starts
immediately.

• When starting DecisionSpace software for the first time, unblock Java.

• If Microsoft NetMeeting is used as a collaboration tool, it must be unblocked.

• After the Windows FireWall is installed, the defaults for Internet Explorer (the default
viewer for help files in Windows) do not allow seamless browsing of help files.
Specifically, the execution or viewing of files stored in a local file system (files with an
file:///xxx URL) is blocked when initially accessed.

5000.0.1 Installation Guide Page 50 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

For seamless viewing of these files, change the browser's default behavior. Do as
follows in Internet Explorer:

1. Select Tools > Internet Options. The Internet Options dialog displays.

2. Select the Advanced tab.

3. In the Settings list box, scroll down to the Security section.

4. Check the Allow Active Content To Run In Files On My Computer box.

5. Click OK in the Internet Options dialog.

This procedure opens the browser to potential security threats. Landmark can
guarantee that viewing its help files poses no risk; however, this solution may not be
in accord with a company’s security requirements.

Without allowing general access to all active content files, currently no other general
solution allows trusted content files to run as this procedure does.

• OpenWorks scripts (such as NTOrauser.sh) may lose their association with a shell
in which to run the script. The scripts must be associated with Sh.EXE
through ...\nutcroot\mksnt\sh.PIF .

Setting the Amount of Memory Available to the Java Virtual Machine

You can use the LGC_JAVA_XMX variable to allocate memory to the Java Virtual
Machine (JVM) when the default value of 5 GB on 64-bit Linux systems is insufficient. You
can verify whether the default values are insufficient by looking at the .err log files for a
Java out of memory error.

5000.0.1 Installation Guide Page 51 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Consult your onsite representative or call Landmark support to change these variable
values.

About Error Files

In addition to the files in the $HOME/Landmark/DecisionSpace directory, a set of error files is

written to the $HOME/run directory. This folder stores runtime messages and error messages. A
typical list of files in this directory would be:

DecisionSpace5000.0-0.err

DecisionSpace5000.0-1.err

DecisionSpace5000.0-2.err

DecisionSpace5000.0-3.err

DecisionSpace5000.0-4.err

DecisionSpace5000.0-5.err

DecisionSpace5000.0-6.err

DecisionSpace5000.0-7.err

DecisionSpace5000.0-8.err

DecisionSpace5000.0-9.err

output-00.err

output-01.err

The DecisionSpace5000.0-Number.err files contain various types of output messages that would
be printed to the console if it were open. The output-[increment].err file contains only JAVA output
messages. A new .err file is created each time you start a new session with the increment number
increasing by one each time. The number of error files of either type is limited to 10.

5000.0.1 Installation Guide Page 52 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

Trademarks

3D Drill View, 3D Drill View KM, 3DFS, 3D Surveillance, 3DView, Active Field Surveillance, Active Reservoir Surveillance,
ADC, Advanced Data Transfer, ARIES, ARIES DecisionSuite, AssetConnect, Asset Decision Solutions, Asset Development
Center, AssetDirector, Asset Journal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver,
AssetObserver Advisor, Asset Performance, AssetPlanner, AssetSolver, AssetSolver Online, AssetView, BLITZPAK, CasingLife,
CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot,
Decision Management System, DecisionSpace, DecisionsSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace
AssetPlanner, DecisionSpace AssetSolver, DecisionSpace AssetView 2D, DecisionSpace AssetView 3D, DecisionSpace Atomic
Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace for Production, DecisionSpace Infrastructure,
DecisionSpace Nexus, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir, DecisionSpace
TracPlanner, DecisionSpace Well Seismic Fusion, DecisionSpace WellSolver, DecisionSuite, DepthTeam, Depth Team,
DepthTeam Explorer, Depth Team Explorer, DepthTeam Express, Depth Team Express, DepthTeam Extreme, Depth Team
Extreme, DepthTeam Interpreter, Depth Team Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS,
Discovery, Discovery Asset, Discovery FrameBuilder, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth
Model, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, EDT, eLandmark, Engineer’s
Data Model, Engineer's Desktop, Engineer’s Link, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker,
FastTrack, FG+, FieldPlan, Field Scenario Planner, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration
System, GeoLink, GeoProbe GF DataServer, GES, GES97, GESXplorer, GMAplus, GMI Imager, GRIDGENR, Handheld Field
Operator, HHFO, I2 Enterprise, iDIMS, IsoMap, iWellFile, i Wellfile, KnowledgeSource, Landmark, Landmark Decision Center,
Landmark & Design, Landmark Logo and Design, Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep,
Make Great Decisions, MathPack, MIMIC, MIMIC+, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks,
OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Development Kit, OpenWorks Well File,
OpenWorks Production, PAL, Parallel-VIP, PetroBank, PetroBank Explorer, PetroBank Master Data Store, PetroWorks,
PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack,
PostStack ESP, PostStack Family, PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, Power
Interpretation, PowerJournal, PowerModel, PowerView, PrecisionTarget, Presgraf, PRIZM, Production Asset Manager,
Production, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D,
ProMAX 3D, ProMAX 3DPSDM, ProMax 4D, ProMax Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick,
Quick+, QUICKDIF, QuickWell, QuickWell+, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real
Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production
Surveillance, Real Time Surveillance, Real-Time View, Reference Data Manager, Reservoir Framework Builder, RESev, ResMap,
RightTime, RTOC, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D,
SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks PowerView,
SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio,
SimResults, SimResults+, SimResults+3D, SIVA+, SLAM, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap,
StrataModel, StrataSim, StrataWorks, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf &
Connect, SynTool, SystemStart, SystemStart for Clients, SystemStart for Servers, System Start for Servers, SystemStart for
Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, The Engineer’s Desktop, Total Drilling Performance, TOW/cs, TOW/
cs Revenue Interface, TracPlanner, TracPlanner Xpress, Trend Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-
COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM,
WavX, Web Editor, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, Well Cost, WELLPLAN, Well Seismic
Fusion, WellSolver, WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!, and Z-MAP Plus are
trademarks, registered trademarks or service marks of Landmark Graphics Corporation.

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

5000.0.1 Installation Guide Page 53 of 54 June 2008

Landmark DecisionSpace® Software Version 5000.0.1

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

<DecisionSpace>\help\com\lgc\dspx\Third_Party.pdf

5000.0.1 Installation Guide Page 54 of 54 June 2008