Aspen Subsurface Science and

Engineering (SSE)

Windows Installation Guide

Version: V14.0.1
Document revised February 2023
Copyright (c) 2023 by Aspen Technology, Inc. All rights reserved.

Aspen Subsurface Science and Engineering (SSE)™, Aspen Epos™ Applications, Aspen GeologTM, Aspen MetteTM,
Aspen OpsLinkTM, Aspen ResviewTM, Aspen Resview AirTM, Aspen RMSTM, Aspen SeisEarthTM, Aspen SKUATM, Aspen
SysdrillTM, Aspen TempestTM, and the aspen leaf are trademarks or registered trademarks of Aspen Technology,
Inc., Bedford, MA.

All other brand and product names are trademarks or registered trademarks of their respective companies.

This document is intended as a guide to using AspenTech's software. This documentation contains AspenTech
proprietary and confidential information and may not be disclosed, used, or copied without the prior consent of
AspenTech or as set forth in the applicable license agreement. Users are solely responsible for the proper use of
the software and the application of the results obtained.

Although AspenTech has tested the software and reviewed the documentation, the sole warranty for the software
may be found in the applicable license agreement between AspenTech and the user. ASPENTECH MAKES NO
WARRANTY OR REPRESENTATION, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS DOCUMENTATION,
ITS QUALITY, PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Aspen Technology, Inc.

20 Crosby Drive
Bedford, MA 01730
USA
Phone: (1) (781) 221-6400
Toll Free: (888) 996-7100
URL: http://www.aspentech.com
Contents
1 Introduction .........................................................................................................5
Aspen SSE Technical Support ............................................................................ 5
Online Technical Support Center .............................................................. 5

2 Overview ..............................................................................................................7
Purpose .......................................................................................................... 7
aspenONE Media .............................................................................................. 7
aspenONE Subsurface Science and Engineering (SSE) Licensing ............................. 7
SLM Licensing ........................................................................................ 8
Aspen SSE Products ......................................................................................... 9
Aspen Epos Applications .......................................................................... 9
Aspen Epos Services ............................................................................... 9
Aspen Geolog ...................................................................................... 10
Aspen METTE ....................................................................................... 10
Aspen OpsLink ..................................................................................... 10
Aspen ResView .................................................................................... 10
Aspen RMS .......................................................................................... 10
Aspen SKUA ........................................................................................ 11
Aspen Sysdrill ...................................................................................... 11
Aspen Tempest .................................................................................... 11
System Requirements ..................................................................................... 11
Hardware and Software Requirements .................................................... 12
General Installation Notes ............................................................................... 13
Product-Specific Installation Notes and Requirements ......................................... 13
Software Developer Kits (SDKs) ............................................................. 13
Aspen Epos Applications ........................................................................ 13
Aspen Epos Services ............................................................................. 13
Aspen Geolog ...................................................................................... 14
Aspen METTE ....................................................................................... 14
Aspen ResView .................................................................................... 14
Aspen RMS .......................................................................................... 14
Aspen Sysdrill ...................................................................................... 14

3 Installing Aspen SSE Products............................................................................15

Installing the Product for the First Time ............................................................ 15
Getting Started .................................................................................... 15
Using the aspenONE Browser ................................................................. 15
Installation Options Sequence ................................................................ 17
Post-Installation Configuration ......................................................................... 29
Aspen Epos Applications ........................................................................ 29
Aspen Epos Services ............................................................................. 29
Aspen Geolog ...................................................................................... 30
Aspen METTE ....................................................................................... 30

Contents iii
 Aspen SKUA ........................................................................................ 30
Aspen Tempest .................................................................................... 30

4 Configuring Aspen SLM.......................................................................................31

Purpose ........................................................................................................ 31
Overview....................................................................................................... 31
Configuring SLM Using the SLM Configuration Wizard ......................................... 31
Accessing the SLM Configuration Wizard ................................................. 32
SLM Configuration Wizard ..................................................................... 33
Configuring SLM Using Environment Variables.................................................... 35
Configuring the Environment Variables (SLM) .......................................... 35
LSDefaultDir Environment Variable ......................................................... 36
LServOpts Environment Variable ............................................................ 37
LServrcCNF Environment Variable .......................................................... 39
LSHost Environment Variable ................................................................. 39

5 Configuring Aspen SSE FlexNet ..........................................................................43

Purpose ........................................................................................................ 43
Overview....................................................................................................... 43
Installing and Configuring a FlexNet License Server ............................................ 43
Linking Applications to FlexNet License Servers .................................................. 44
Aspen SSE FlexNet Environment Variables............................................... 44
Configuring the Environment Variables (Aspen SSE FlexNet)...................... 44
Examples of FlexNet License Server Configuration .................................... 46

6 Configuring Aspen Epos Services .......................................................................49

Services Configuration Wizard Overview ............................................................ 49
Creating a New Configuration vs. Reusing an Existing Configuration ........... 49
Network vs. Local Configuration ............................................................. 50
Configuring Aspen Epos Services ...................................................................... 51
Configuring Crush Dump Functionality for the PNS ................................... 57
Importing Aspen Epos Data from a Previous PNS Segment ........................ 58

7 Configuring Aspen Epos Applications .................................................................59

Configuring the Connection of Aspen Epos Applications to an Aspen Epos PNS Host 59
Configuring Crash Dump Settings ..................................................................... 62

8 Repairing Aspen Subsurface Science and Engineering (SSE) Products ...............65

Overview....................................................................................................... 65

9 Removing Aspen Subsurface Science and Engineering (SSE) Products ..............67

Overview....................................................................................................... 67
Before You Remove ........................................................................................ 67
Removing Aspen Subsurface Science and Engineering (SSE) ............................... 67

iv Contents
1 Introduction

Aspen Subsurface Science and Engineering (SSE) products include end-to-end

geoscience and modeling solutions for optimization across subsurface
engineering and operations. Aspen SSE products empower decision makers to
reduce uncertainty, improve confidence, minimize risk, and support
responsible asset management.
This guide describes how to install Aspen SSE products on Windows operating
systems. For installing Aspen SSE products on a Linux operating system,
please refer to the Aspen Subsurface Science and Engineering (SSE) Linux
Installation Guide.

Aspen SSE Technical Support

Online Technical Support Center
AspenTech customers with a valid license and software maintenance
agreement can access the Aspen Subsurface Science and Engineering (SSE)
portal at: www.aspentech.com/ssesupport.
If you do not have an account, click Request a Login and fill in the form.

Note: Please use your company email address. When the request is
approved, you will then receive an email containing your username and
password, and you will be able activate your account.
The SSE portal allows you to:
 Access current product documentation
 Access online self-paced training
 Search for knowledge base content
 Search for and download application examples
 Search for and download service packs and product updates
 Submit and track technical issues
 Send suggestions
 Report product defects

1 Introduction 5
 To contact customer support for Aspen Subsurface Science and Engineering
(SSE) products, please email sse.support@aspentech.com.

6 1 Introduction
2 Overview

Purpose
This chapter provides an overview of the aspenONE installation process for
Aspen Subsurface Science and Engineering (SSE), including the requirements
for each product in the suite.
This group of products includes Aspen Epos Applications (including Aspen
SeisEarth), Aspen Epos Services, Aspen Geolog, Aspen METTE, Aspen
OpsLink, Aspen ResView, Aspen RMS, Aspen SKUA, Aspen Sysdrill, and Aspen
Tempest. These products were previously distributed by Emerson Electric Co.

aspenONE Media
Unless you have specifically requested a USB drive, you will receive
instructions on how to download the aspenONE media.

Note: The product Release Notes and Installation Guides are included in the
Document sub-folders under each family of products. There is a link to the
Getting Started Guide on the Install Browser.

aspenONE Subsurface Science

and Engineering (SSE)
Licensing
The licensing model used for Aspen Subsurface Science and Engineering
(SSE) products is dependent on your licensing agreement with AspenTech.
During the installation process, you select aspenONE Licensing Token
Mode (based on SLM License Manager) or FlexNet License Manager
Mode on the License Mode Configuration screen of the aspenONE Installer
based on this licensing agreement.
Your selection must be consistent across the entire suite. You cannot select
aspenONE Licensing Token Mode for some Aspen SSE products and

2 Overview 7
 FlexNet License Manager Mode for other Aspen SSE products on the same
machine.
 When aspenONE Licensing Token Mode is selected, installed products
use the SLM License Server. See “SLM Licensing” below for further details.
aspenONE Licensing Token Mode is the default selection. For
information regarding post-installation configuration steps for a client
configuration, please see “Chapter 4: Configuring Aspen SLM.”
Note: See the Software License Manager (SLM) Installation and Reference
Guide for configuration steps for a server.
 When FlexNet License Manager Mode is selected, installed products
use the FlexNet License Server. See “FlexNet Licensing” below for further
details.
Note: See the Aspen SSE FlexNet Installation and Reference Guide for
further details and for information regarding post-installation configuration
steps.

SLM Licensing
If you are using the SLM licensing mode to manage your product entitlement,
you will receive a license file for the SLM Server.

Note: An invoice noting the products for which you are licensed is sent
separately from the software shipment.
Under the SLM licensing model, customers are entitled to install and run any
AspenTech product, as long as they have purchased sufficient tokens.
Software installed under the SLM licensing model requires run-time token-
based license keys.
Before you install products, it is recommended that you install and configure
the SLM License Server.
When you deploy aspenONE V14.0.1, the SLM License Server must be from
V12 or a later aspenONE release. We recommend that you upgrade to the
latest version.
When migrating to a new version of aspenONE, the SLM Server should always
be upgraded first, followed by the SLM clients. This is done to avoid any
potential incompatibility issues. During this transition period, it is possible to
have clients at a lower version than the SLM Server.
For more information about licensing, please see Software License Manager
(SLM) Installation and Reference Guide on the aspenONE media.

FlexNet Licensing
If you select the FlexNet License Manager Mode option on the License
Mode Configuration screen of the aspenONE Installer, Aspen Subsurface
Science and Engineering (SSE) products are licensed and managed by means
of the Flexera FlexNet licensing system.

8 2 Overview
 The Aspen SSE FlexNet License Manager is based on FlexNet 11.16.6. This
manager is designed to remain compatible with older versions of Emerson
E&P and Aspen Subsurface Science and Engineering (SSE).
You can download the Aspen SSE FlexNet License Manager at
www.aspentech.com/ssesupport or request a USB media to AspenTech.

Note: For more information regarding the installation, administration of the

license server and configuration with Aspen SSE FlexNet License Manager, see
the Aspen SSE FlexNet Installation and Reference Guide.
For further information regarding the Flexera FlexNet Licensing system,
please refer to the FlexNet Publisher License Administration Guide from
Flexera Software.

Aspen SSE Products

Aspen Epos Applications
Aspen Epos Applications provide a common working environment for
individuals or teams. The integrated installation of Aspen SeisEarth Seismic
Interpretation; Aspen SKUA Reservoir Modeling; and Aspen Geolog Formation
Evaluation solutions enhances multi-user, multi-disciplinary collaboration
through the shared Aspen Epos infrastructure and database.

Aspen Epos Services

The Aspen Epos PNS and shared Services are a key part of the Aspen Epos
Infrastructure.
 The PNS is the launcher and controller of the Aspen Epos Data Servers
and Utility Servers.
 The Aspen Epos Services provide Aspen Epos with security control and
data access across heterogeneous multi-user networks.
Aspen Epos Applications must be connected to the Aspen Epos Services in
order to operate successfully.
Aspen SKUA and Aspen Geolog have two modes of working: a standalone
mode without Aspen Epos Services, and a mode where they work with the
Aspen Epos Services.
Aspen Epos Services can be configured using a Local or a Network
configuration.
 Local configuration is designed for a single user on a laptop or a
workstation. In this configuration, Aspen Epos Services are installed and
run on the user’s machine; that is, on the same host where Aspen Epos
Applications are running.
 Network configuration is designed for a multi-user environment where
users can share data and work together on projects. In this configuration,
Aspen Epos Services are installed only once on a dedicated host on the
network and will be connected to from multiple remote workstations.

2 Overview 9
 Aspen Geolog
Aspen Geolog is a component of the Aspen Subsurface Science and
Engineering (SSE) Formation Evaluation Suite.
Aspen Geolog is the world's leading well data processing and analysis
software package. Aspen Geolog gives you the freedom to store and process
well bore data easily and efficiently within a flexible and connectible software
environment.
Aspen Geolog incorporates state of the art graphical displays and utilizes the
most advanced analysis techniques for geological modeling through to
complex petrophysical interpretation. Aspen Geolog is a totally integrated
package which consists of various specialized modules.

Aspen METTE
Aspen METTE is a powerful platform for performing life of field
thermohydraulic calculations.
Aspen METTE is an integrated production management solution that provides
operators with flow performance calculations for wells and flow lines,
integrated field modeling for life of field simulation and optimization, and
virtual metering for the allocation of production to wells. Key benefits to
operators include flexible production performance calculations, fast network
simulation and improved life of field integrated flow assurance.
The combination of data from predictive reservoir models, production
modeling and field instrumentation will enable operators to monitor
production continuously and use information from the field when forecasting
future reservoir performance and making operational decisions.

Aspen OpsLink
Aspen OpsLink is a client-server application that provides operating
companies with the ability to make rapid and informed decisions while drilling
to maximize productivity and minimize drilling costs. Fast and flexible access
to real-time WITSML-based MWD and LWD data provides key information
required by asset teams to make these decisions.

Aspen ResView
Aspen ResView provides functionalities for oil and gas field monitoring,
production analysis and optimization, utilizing diverse information sources,
including field databases, and geological and flow models.

Aspen RMS
Aspen RMS is an advanced reservoir management tool that allows users to
derive maximum benefit from building and using 3D reservoir models. It
provides an integrated interdisciplinary perspective to properly manage and
optimize the reservoir’s potential, with the ability to leverage the seismic data

10 2 Overview
 and accommodate complex geologies. The result is faster, more robust, and
more reliable production models, improved decision-making, more justifiable
investments, and enhanced field performance, leading to higher recovery
rates in even complex reservoirs.

Aspen SKUA
Aspen SKUA provides high-definition 3D modeling of the subsurface for
sustainable Earth resource management. Its collaborative platform enables
geoscientists and engineers to integrate, visualize and analyze all subsurface
data, extract insights and build reliable fit-for-purpose 3D models at local and
regional scales.
Geoscientists can use Aspen SKUA to incorporate difficult model structures,
multi-z surfaces, and complex faults such as salt dome, overthrust and
reverse faults. With a simple-to-use, workflow-based interface.
 Aspen SKUA provides a common workspace for easy collaboration and
data sharing.
 Aspen SKUA models more accurately resemble your reservoir because no
data is left out and no interpretation is simplified
 The integration of all interpretation results with the Aspen SKUA increases
stratigraphic and reservoir model accuracy
 With built-in data sharing, multiple scenario processing and audit trail,
Aspen SKUA improves workflows, reduces study time, and creates the
industry’s most accurate models for planning and forecasting.

Aspen Sysdrill
Aspen Sysdrill integrated suite of well planning and drilling software solutions
helps operating and drilling service companies enhance well planning
accuracy, reduce drilling risk and uncertainty, quantify wellbore position and
precision, and improve drilling safety.

Aspen Tempest
Aspen Tempest provides a full range of solutions for preparing and navigating
simulation input, submitting and monitoring runs, visualizing and analyzing
results, performing assisted history matching, and predicting production
uncertainty.

System Requirements
For the most up-to-date hardware and software requirements that must be
met to install AspenTech products, download the platform specification from
the following website:
https://www.aspentech.com/platform-support/

2 Overview 11
 You can also access the online prerequisite viewer. This utility can be used to
review prerequisites prior to installation and can be found at the following
location:
https://support.aspentech.com/aspenone-prerequisites

Hardware and Software Requirements

Hardware and Requirements
Software

CPU x64 architecture Intel or AMD processors (x86_64) with at

least 4 cores recommended.

RAM A minimum of 4GB. Recommended memory is 32GB per

CPU.
Display Resolution 1920 x 1080 minimum recommended. Higher resolutions
may be beneficial.
When using Dual/Multiple monitors, we recommend using
monitors of the same resolution.

Graphic card adapter For applications that provide advanced 3D visualization

and driver (Aspen Epos 3D Canvas, Aspen RMS, and Aspen SKUA), a
3D graphics adapter supporting OpenGL 3.3 is required.
Supported graphic cards are NVIDIA Maxwell and above. The
NVIDIA Quadro series is strongly recommended.
 GPU computing requires an NVIDIA Pascal GPU
architecture or ulterior graphic adapter (such as P5000,
P6000, RTX 5000, RTX A5000…) and video driver
supporting CUDA 11.5 or later.
 3D stereo viewing requires stereo capable display and
appropriate viewing glasses. (Your projection system—
graphics adapter, graphics driver, monitor, or project—is
responsible for rendering the OpenGL information. If
needed, contact Support for assistance.)
 For the graphics driver, we recommend updating to the
latest official version. NVIDIA drivers are available from
www.nvidia.com/Download/index.aspx
Graphic cards from other vendors than NVIDIA may work
but are not officially supported.
With an inadequate 3D graphics adapter, these applications
are not fully functional.
Web Browser To view Help pages and documentation PDF files, we
recommend modern browsers such as Google Chrome,
Microsoft Edge, or Mozilla Firefox.
Internet Explorer is no longer supported.

License Manager Either:

 SLM License Server V12 or later
-or-
 FlexNet license server 11.16.6 or later

12 2 Overview
 General Installation Notes
In order to install Aspen Geolog, Aspen METTE, Aspen ResView, Aspen RMS,
Aspen SKUA, or Aspen Tempest, you must uninstall previous versions of the
applications before installing Aspen SSE V14.0.1.

Product-Specific Installation
Notes and Requirements
This section describes product-specific installation notes and requirements.

Software Developer Kits (SDKs)

AspenTech offers Software Developer Kits (SDKs) for Aspen Epos Applications
and Aspen SKUA. You must first install the corresponding application on the
target machine before installing the associated SDK.
 In order to install the Aspen OpenGeo SDK, you must have Aspen Epos
Applications installed on the same machine. For further details, see the
Aspen OpenGeo SDK for Windows Installation Guide.
 In order to install the Aspen SKUA SDK, you must have Aspen SKUA
installed on the same machine. For further details, see the Aspen SKUA
SDK Installation Guide.

Note: Aspen SDKs are distributed in separate media. You can download this
Media at www.aspentech.com/ssesupport or request a USB media from
AspenTech.

Aspen Epos Applications

Note: Aspen Echos, Aspen EarthStudy 360, and Aspen GeoDepth can only be
installed on Linux operating systems. For details, please see the Aspen
Subsurface Science and Engineering (SSE) Installation Guide.
Aspen SeisEarth MSI is only available when the FlexNet License Manager
Mode is selected.

Aspen Epos Services

For a site with many Aspen Epos users, we recommend allocation of a host
with at least a 1 gigabit Ethernet (GbE) network connection to act as a
dedicated host for running services.

2 Overview 13
 Aspen Geolog
To develop and compile programs using the Aspen Geolog Loglan view, the
Microsoft Visual Studio 2019 (Profession or Enterprise) or compilers with the
Desktop development with C++ option enabled must be installed.

Aspen METTE
For more information regarding configuring Aspen METTE, please see the
following configuration guides:
 Aspen METTE Configuration Guide
 Aspen METTE VFM Configuration Guide

Aspen ResView
You must select the FlexNet License Manager Mode when installing Aspen
ResView. The aspenONE Licensing Token Mode is not supported.

Aspen RMS
Aspen RMS utilizes multi-core, or multi-processor, systems for some multi-
threaded algorithms and operations done on a per grid zone. Significant
performance improvements in processing and visualization may be expected
with multi-core configurations and a higher speed per processor. In addition
to processor choice, the following affect performance:
 Amount of installed RAM
 GPU specifications
 Type of disk drive (hard disk drive, solid state drive, or over network)
NVIDIA Quadro based graphic cards are supported. The suggested profile for
NVIDIA cards, including the Pascal GPU architecture, is Workstation App –
Dynamic Streaming.

Aspen Sysdrill
Aspen Sysdrill cannot work properly with two data services running at the
same time. Use only one data service to ensure the Aspen Sysdrill application
opens correctly.

14 2 Overview
3 Installing Aspen SSE
Products

Installing the Product for the

First Time
Log on using the account name and password of an account in the
Administrators group of the target computer.

Note: Before you begin installation, review the Release Notes and print
copies of the Installation Guides for products that will be installed. Those
documents are included under each product suite folder.

Getting Started

Using the aspenONE Browser

1 To begin your software installation:
o Click on the media download.
-or-
o Insert the aspenONE USB, available on request, into the USB drive.
2 Right Click on the iso file and mount the desired installation media.
3 Browse to the newly mounted DVD drive. Double-click Setup.exe to start
the installation process.
4 Before the Welcome page appears, the User Account Control dialog
box may appear, displaying a message such as: Do you want to allow
this app to make changes to your device?
You must click Yes to continue.
If you do not see this dialog box or something similar, you may have
accessed the installation incorrectly, and in doing so, appropriate settings
may not occur. The consequence is that the applications may not run
correctly, or errors may appear even though the installation seems to
complete successfully. If this dialog box does not appear, cancel the
installation and re-launch setup.exe to start the installation again.

3 Installing Aspen SSE Products 15

 Carefully read the instructions, make your selections, and proceed with
the installation.
The Welcome to aspenONE V14.0.1 Installer screen appears.

The following links are available:

o – Allows you to access the AspenTech Support Center.

o Patents – Allows you to download a document with a list of recent
patents.
o Pre-requisites – This page allows you to review a list of
dependencies and/or prerequisites for the product(s) you plan to
install. You can then use this list to address those prerequisite
requirements before installing.
o Getting Started – Opens a Knowledge Base article describing how
you can get started with aspenONE V14, including the Early Adoption
Program, What’s New, and additional resources.
o Upgrade journey – The Upgrade Journey guides you through the
best practices to plan and execute an AspenTech software upgrade.
Use these guides for a faster, easier software upgrade.
o What’s new? – A list and explanation of new features included in
aspenONE V14.
The Aspen Subsurface Science and Engineering V14.0.1 radio button
is selected.
5 Click Install.

16 3 Installing Aspen SSE Products

 Installation Options Sequence
The following section shows the general sequence of input screens you might
use during the installation. The screens vary depending on the features you
choose to install. You might not see this exact sequence.

Installation Welcome Page

The Welcome to the aspenONE V14.0.1 Installer page provides options
to install or upgrade aspenONE products, configure licensing, and create
install scripts for unattended installations.
The following links are available on the left side of the Welcome page:
 Getting Started Guide – Opens the AspenTech Deployment Solutions Web
site.
 Installation Guides – Opens a folder that contains all the Installation
Guides for the products.
 Release Notes – Opens a folder that contains all the Release Notes for the
products.
 aspenONE Product Documentation – Opens the AspenTech Support
website.
 Unattended Install Notes – Provides instructions on creating an
unattended installation.
 Support Services – Connects to the AspenTech Support website, where
you can find knowledge base articles, tips, and solutions to known
problems.
 AspenTech Home – Connects to the AspenTech Web site.
 Contact Us – Connects to the AspenTech Support Web site, where you can
obtain the latest e-mail and telephone contact information and find the
AspenTech Support location closest to you. You can view hours of
operation for global support and submit your support issues.

3 Installing Aspen SSE Products 17

 The following options are available on the aspenONE Installer Welcome Page:
 Install aspenONE products – Launches the installation process during
which you will select new products to be installed on this computer.
 Upgrade or repair existing products – Repair existing installation
errors.
 Prepare Deployments (For IT Personnel/Deployment Groups) –
Create install scripts and copy media to automate software deployment.
Click Install aspenONE products.

18 3 Installing Aspen SSE Products

 License Terms and Conditions

Select I accept the terms of this agreement and click Next to continue.

3 Installing Aspen SSE Products 19

 Product Selection

Select the products that you want to install and click Next to continue.

Notes:
 Aspen Epos Services are not selected by default because in a multi-user
network environment, only one instance of Aspen Epos Services is
typically installed per network by the Aspen Epos Administrator. In that
case, Aspen Epos Services are installed on a dedicated PNS host and
configured by the administrator, preferably before the individual
installations of Aspen Epos Applications on the user’s local hosts.
Alternatively, if you want to work on your local machine in a single user
environment, you must install and configure Aspen Epos Services along
with Aspen Epos Applications on your local machine.
 For Aspen Epos Applications, Aspen Geolog, and Aspen SKUA, make sure
to select the Documentation check box if you want to install a local copy
of the documentation on your machine. For these products, installing the
documentation is optional. If you select the Documentation option, the
Help documentation is installed into the Aspen Epos Applications, Aspen
Geolog and/or Aspen SKUA installation tree.

20 3 Installing Aspen SSE Products

 File Location (Optional)

Select the File location.

 The default drive for the 64-bit location is C:\Program Files\AspenTech.
 The default drive for the 32-bit location is C:\Program Files
(x86)\AspenTech.

Notes:
 Once the installation of Aspen Subsurface Science and Engineering (SSE)
to the default folder has been completed, this folder cannot be changed,
and the Change Current Destination Folder dialog box no longer
appears. Any further AspenTech installations on the computer are made to
that folder by default.
 Common features are always installed in the Program Files\Common
Files\AspenTech Shared folder regardless of the destination location
selected.
 If the Aspen Geolog installation path contains spaces, the Aspen Geolog
Help will not be accessible unless short names are enabled on the disk
partition. For more information, see Short Names vs. Long Names in the
Microsoft documentation.
After specifying the file location, click Next.

3 Installing Aspen SSE Products 21

 Prerequisite Validation

This screen will only appear if prerequisites are missing. If the prerequisites
window appears, you will see the Install Prerequisites option at the bottom
of the screen
You can install and/or configure some of the product pre-requisites during the
Aspen software installation process – mostly Microsoft Internet Information
Services (IIS). Here is a description of the icons related to installing pre-
requisites.

 - This item can be installed automatically by clicking Install

Prerequisites. This item must be installed before the AspenTech
installation can proceed.

 - This item cannot be installed automatically by clicking Install

Prerequisites. Click the link in the item’s description to open an
AspenTech Support site link that describes how to install this item. This
item must be installed before the AspenTech installation can proceed

 - This item is informational.

To install the prerequisites:
Click Install Prerequisites if you want to install or configure the relevant
prerequisites.

22 3 Installing Aspen SSE Products

 When the Install Prerequisites option is selected, the Install
Prerequisites screen appears. This identifies which prerequisites can be
installed and/or configured.
All options are selected by default. Clear any options that you do not want
installed automatically, and then click Install.
When Install is selected, PowerShell windows appear that perform the install
and/or configuration for the specified prerequisites. When the install and/or
configuration steps are done, the Install Prerequisites window appears
again.
Click x to close the window and return to the installation process.

License Mode Configuration

The licensing model used for Aspen Subsurface Science and Engineering
(SSE) products is dependent on your licensing agreement with AspenTech.
During the installation process, you select aspenONE Licensing Token
Mode (based on SLM License Manager) or FlexNet License Manager
Mode on the License Mode Configuration screen of the aspenONE Installer
based on this licensing agreement.

Note: If you select FlexNet License Manager Mode, you must define the
environmental variables prior to installation. For details, see “Chapter 5:
Configuring Aspen SSE FlexNet.”
Your selection must be consistent across the entire suite. You cannot select
aspenONE Licensing Token Mode for some Aspen SSE products and
FlexNet License Manager Mode for other products on the same machine.

3 Installing Aspen SSE Products 23

 When aspenONE Licensing Token Mode is selected, installed products use
the SLM License Server. For information regarding post-installation
configuration steps for a client configuration, please see “Chapter 4:
Configuring Aspen SLM.”

Note: If you select the incorrect option on this screen and continue with the
installation process, you can repair the install afterward and select the correct
option. For details on repairing your installation, see “Chapter 8: Repairing
Aspen Subsurface Science and Engineering (SSE) Products.”

Specify Product Configuration

During the installation process, you must configure settings for Aspen Geolog
and/or Aspen OpsLink if you have selected these products. These settings are
described below.

Configure Aspen Geolog Settings

The Configure Aspen Geolog Settings screen only appears if you selected
Aspen Geolog on the Product Selection screen.

On the Configure Aspen Geolog Settings screen:

1 If the environment variable PG_SITE is set in your environment, the Site
Directory field is set to this value. If PG_SITE is not set, a default path is
provided. You may need to change the default path to suit your company’s
requirements.

24 3 Installing Aspen SSE Products

 Note: If a geolog_env.tcl file already exists in the bin directory of the
site location specified, the Aspen Geolog Settings section does not
appear on this screen. Go to step 5.
2 If a PNS service is required to access data, select the Server well access
checkbox and enter the PNS host/s where the service is running.
Short names (<host>) or FQDN (Fully Qualified Domain Names) names
(<host>.aspentech.com) can be entered in the PNS_HOST field but
cannot be used at the same time.
3 If direct well access is required and the PG_PROJECTS default location is
not appropriate, click Browse to select the directory where project data is
located. Otherwise, clear the Direct well access check box.
Note: It is valid to have both server and direct well access configured.
4 Select your preferred default unit system.
As a result of data collected on this screen, the environment variables
PG_PROJECTS, PG_UNIT_SYSTEM, and optionally PNS_HOST are set in
the environment file, geolog_env.tcl.
5 Click Next.

Configure Aspen OpsLink Server Port Settings

The Configure Aspen OpsLink Server Port screen only appears if you
selected Aspen OpsLink on the Product Selection screen.

To configure Aspen OpsLink:

1 Choose the help system port and the OpsLink Server Port number that the
Aspen OpsLink Server will listen for Client connections on.

3 Installing Aspen SSE Products 25

 Note:
 If a port number is occupied, a warning message appears. The Single
User Installation check box should be selected if the OpsLink client and
server are to be installed on the same machine and will only be used by a
single user. This option disables the Windows Active Directory/LDAP
permission integration.
 You can install two components for Aspen OpsLink, Client and Services.
Be careful when modifying or repairing the installation. If Aspen OpsLink is
unable to establish a connection to the server, we recommend that you
uninstall both components and add the port number again.
2 Click Next.

Administrator User Credentials (Aspen OpsLink)

1 Specify your username and password.

Note:
 The Administrator User Credentials screen only appears if you selected
Aspen OpsLink on the Product Selection screen. If Aspen OpsLink is
being installed as a single user installation, the username and password
details required to login are the credentials provided during the previous
setup.
 The username and password must not contain spaces. Additionally, the
password must meet complexity requirements properties and contain at
least 7 characters with an uppercase character, lowercase characters and
a base 10 digit (0-9).
2 Click Next.

26 3 Installing Aspen SSE Products

 Verify Your Installation

After verifying the installation list, click Install Now to continue.

Installation Progress
The installation progress screen tracks the install and reports any errors.

3 Installing Aspen SSE Products 27

 During the installation, a progress bar appears. Make sure to wait until the
status of all products reaches 100%.

28 3 Installing Aspen SSE Products

 When the installation is complete, click Finish.

Installation Complete

Once the installation is finished, the Installation Complete screen appears.

Post-Installation Configuration
Post-installation configuration steps for Aspen Subsurface Science and
Engineering (SSE) products are described below.

Aspen Epos Applications

After installation of Aspen Epos Applications is complete, the Aspen Epos
Applications must be connected to Aspen Epos Services on a network
environment. See “Chapter 7: Configuring Aspen Epos Applications” for
further details.

Aspen Epos Services

After installation is complete, Aspen Epos Services must be configured using
the Aspen Epos Services Configuration Wizard. See “Chapter 6: Configuring
Aspen Epos Services”.

3 Installing Aspen SSE Products 29

 Aspen Geolog
 If you selected FlexNet License Manager Mode on the License Mode
Configuration screen, and the geolog_env.tcl file is newly created as
part of this installation, you should edit the file after the installation has
completed and set PRDM_GEO_LICENSE_FILE to the license file name
or the port@host where a license server is running. Alternatively,
configure PRDM_GEO_LICENSE_FILE as a system environment
variable. See “Chapter 5: Configuring Aspen SSE FlexNet” for more
information.
 The Geolog to Petrel connector, Geolog-Link plug-in installation program,
is available in the <geolog installation>\petrel_geolog_link_2019,
\petrel_geolog_link_2020 and \petrel_geolog_link_2021
directories.
The Geolog-Link plug-in Installation Guide and Geolog-Link plug-in User
Guide are also available as PDFs in each of the directories.

Aspen METTE
For more information regarding configuring Aspen METTE, please see the
following configuration guides:
 Aspen METTE Configuration Guide
 Aspen METTE VFM Configuration Guide

Aspen SKUA
Some Aspen SKUA features using third party software require additional
configuration to function properly. To learn more, see the following
installation guide:
 Aspen SKUA V14 Third Parties Installation and Configuration Guide

Aspen Tempest
After installation is complete, please verify the following:
 The Aspen Tempest installation folder is available at the default path
(C:\Program Files\AspenTech\Tempest-VXX), or at the user-
specified installation path, where VXX is the version number.
 The environment variable TEMPEST_DIR has been added, pointing to the
above path.

30 3 Installing Aspen SSE Products

4 Configuring Aspen SLM

Purpose
This chapter describes how to configure SLM License mode.

Note: This chapter is only relevant if you selected aspenONE Licensing

Token Mode (based on SLM License Manager) on the License Mode
Configuration screen of the aspenONE Installer. If you selected FlexNet
License Manager Mode, please see “Chapter 5: Configuring Aspen SSE
FlexNet.”

Overview
You can configure SLM using:
 SLM Configuration Wizard. This is the recommended method.
 The environment variables.

Configuring SLM Using the SLM

Configuration Wizard
The SLM Configuration Wizard guides you through a series of steps that
configure the SLM to generate license keys. The SLM Configuration Wizard is
used to configure the SLM on all computers connecting to an SLM server on a
network or running SLM locally.
The SLM Configuration Wizard Help provides a comprehensive description of
the SLM Configuration Wizard.

Note: The SLM Configuration Wizard makes changes to the registry.

Therefore, to use the SLM Configuration Wizard, you must have permission to
write to the registry. If you do not have permission to write to the registry,
contact your system administrator.

4 Configuring Aspen SLM 31

 Accessing the SLM Configuration Wizard
To start the SLM Configuration Wizard:
 On the Windows desktop, from the Start menu, either:
o Click aspenONE SLM License Manager, and then click
Configuration Wizard.

-or-
o Click Aspen Configuration | aspenONE Manager. On the
aspenONE Manager, click aspenONE SLM License Manager. Then
click Configuration Wizard.

To access the SLM Configuration Wizard Help:

32 4 Configuring Aspen SLM

  From the SLM Configuration Wizard, click Help in the lower left-hand
corner of the window.

SLM Configuration Wizard

Once you have confirmed that the proper license strings are in place, the next
step is to check that your network computer points to your license server.
See the Software License Manager (SLM) Installation and Reference Guide for
more information regarding license strings, which are encrypted alphanumeric
text strings used to define a single licensed feature.
 From the Start menu, select aspenONE SLM License Manager, and then
click Configuration Wizard.

The SLM Configuration Wizard dialog box appears.

To add SLM servers to the Configured Servers list, under Network License
Servers, in the Server Name or IP field, type the name or the IP address
and then click Add Server.
To configure the Advanced Settings:

4 Configuring Aspen SLM 33

 o For Expiration Remainder (days), specify the number of days
before a product license expires that a reminder will be sent to you.
o Select Enable Broadcasting, specify the Interval (min) if you want
SLM to broadcast (search) for licenses on the network.
o Select the Log time zone information check box if you want to log
time zone information in the server log.
o Select the Ignore local keys check box if you want to ignore the local
standalone keys.
o Use the Search Configured Servers for all available buckets at
Runtime to indicate whether you do or do not want to search all
configured servers for all available buckets.
o Select the Log IP addresses check box if you want to log the IP
address in the server log. The log file is saved on the SLM server in the
same directory where the license server is installed.
o When the Resolve server name check box is selected (which is the
default setting), the fully qualified server name is used in the registry.
Customers using an alias for license server names can clear this
setting. The resolve server name is not used in silent installs.

To enable Project Tracking:

o For Project tracking on, select Yes.

34 4 Configuring Aspen SLM

 o Type the Project Name. The project name can be any meaningful
name used to identify the project.
o Type the Department Name associated with the project.
o Type the Location Name where the project takes place.

5 Do one of the following:

o Continue with any additional changes to configuration settings.
o Click Apply Changes.

Configuring SLM Using

Environment Variables
Environment variables can be used to control some of the operations of SLM.
The primary environment variables are:
 LSHost is used to direct the search for a network license to a list of
preferred servers.
 LServOpts is used to set License Server Options including configuration
information, usage logging, and error logging. Alternatively, some of these
options can be set through their own environment variable.

Note: If your computer contains both the registry and the LSHost
environment variables configurations, SLM checks the LSHost environment
variables first.

Configuring the Environment Variables

(SLM)
To add the environment variables for SLM
1 On your computer, open the Control Panel.
2 Click System. On the Settings view, click Advanced system settings.
3 On the System Properties dialog box, click the Advanced tab. On the
Advanced tab, click Environment Variables.
The Environment Variables view appears.
4 Under User or System Variables group, click New.
The New System Variable view appears.
5 In the Variable Name field, type the name of the environment variable
as lshost.
6 In the Variable Value field, type the IP address or hostname of the
server(s).
7 Click OK.
The new environment variable and value is added in the Environment
Variables view.

4 Configuring Aspen SLM 35

 8 If you do not need to set any more variables, click OK to close both
Environment Variables and System Properties views.
9 Reboot the computer to make sure these environment variables take
effect.

Alternatively, access the System Properties dialog box from Start ,

type Edit environment variables and click the result.

Configuring the LSHost File or Environment

Variable
For an SLM Token system, all environment variables must be configured as
system variables. The environment variable or LSHost file is used to instruct
the application where to search for the Token server(s):
 The LSHost file contains a list of the IP address or computer names for
each of the Token servers. When the application searches for the license
information, it proceeds using the following steps:
1 The application starts with the first address on the list of the LSHost
file.
2 If the IP address is not available, the server does not provide the
license requested. The application’s search engine then moves to the next
server on the list.
3 The application’s search engine repeats the previous step until it finds
a server that provides the license requested.
The LSHost file must be placed in the application root directory for each
SLM-protected application. If the application is installed on an application
server, the LSHost file resides on that server.
 The LSHost environment variable contains an IP address or computer
name for a Token server. The environment variable is set on the user’s
computer.

Note: The LSHost environment variable overrides any LSHost files on the
computer. Normally, it is recommended to use LSHost files to avoid
interference with any other vendor security that may also be using LSHost.
Caution: If you have other vendor securities already using the LSHost
environment variable, then consider using an LSHost file for each AspenTech
product or a master LSHost environment variable, which lists the license
servers for both your AspenTech and other vendor products.

LSDefaultDir Environment Variable

You can use the LSDefaultDir environment variable to set the default
location of the license file. AspenTech recommends that the license server’s
default directory not be changed. The default directory is in the same
directory as the license server executable.

36 4 Configuring Aspen SLM

 LServOpts Environment Variable
The LServOpts environment variable is used to set network license server
options.

Notes:
 This variable is set as a system variable and not a local user environment
variable.
 Some of the options that can be set with LServOpts can also be set with a
specific environment variable (which is recommended to be used
whenever possible).

Possible Variable Values of the LServOpts

Variable
Option Description

-s license file Specifies the name and location of the license file. By
default, the license server uses the file, lservrc, in the local
directory. This can also be specified with the LServrc
environment variable.
-e license Specifies the name and location of the optional license
configuration file configuration file. This can also be specified with the
LServrcCNF environment variable.
-l usage log file Enables usage logging by specifying the name and location
of the usage log file (you can not include any spaces in the
path name). A typical log file name is lserv.log. (This is
limited to eight characters.) By default, usage logging is
disabled.
-z usage log file size Specifies the maximum size of the usage file. The default
value for the maximum size of the log file is 5 megabytes.
The size can be specified in bytes, kilobytes, or megabytes.
For example, -z 2000 means 2000 bytes, -z 2k means 2
kilobytes and -z 2m means 2 megabytes. Once the
maximum size of the file is reached, the license server
creates a backup log file (unless the -x option has been
used).
The maximum number of backup files is 9999. However, you
can move existing backup log files to another directory and
the license server begins logging again.

4 Configuring Aspen SLM 37

 Option Description

-x By default, on overflow of the usage log file, the file contents

are moved in to a backup file. New usage records are then
written to the original file until it overflows again. If the -x
option is specified, the file will not be backed up on overflow.
Instead, the license server will simply stop writing further
records to the file.
-smb Specifies the socket buffer multiplier. By default, the socket
buffer multiplier is set to 4. This increases the socket buffer
by a multiple of 4 to 262144 bytes. Increasing the socket
buffer size provides an opportunity for the OS to buffer up
the data/requests while the service is busy processing the
requests, so that the data/requests can be piped in an
orderly fashion to the RMS service. This gives a chance for
the server to respond efficiently, rather than letting the
requests go unanswered and timed out.
-com percentage Commuter licensing uses the same license strings as other
network licenses. To ensure that not all licenses are used up
by commuters, set this option to the percentage of licenses
you want used for commuter licensing. Once that proportion
of license are used up, no more will be made available to
commuters until commuter licenses are returned.
-lfe encryption level Specifies the level of encryption that license transactions are
written to in the license’s server log file. The levels are 1 to
4:
1 - No encryption.
2 - No encryption. Transaction data is readable but
tampering with or deleting an entry can be detected. This is
the default encryption level.
3 - Encrypt usage only. Transaction data is readable except
for license usage data.
4 - Encrypt entire record. All transaction data for the license
s is encrypted.
Level 2 is recommended if you wish to generate any reports
on the usage data. If your contract requires that log files to
be sent to AspenTech, level 2 must be used.
-u group Specifies the name and location of the optional group
reservations file reservations file. By default, the license server uses the
LSReserv file in the current directory. This can also be
specified by the LSReserv environment variable.

Setting the Usage Logging

The following figure displays the New System Variable view containing the
information for a usage log file with a maximum size of 5 megabytes and
level 2 encryption. When typing the path and name of the log file, there can
be NO spaces and quotes are not required.
If you activate the usage logging option, the network license server records
all license requests and writes to this file. The generated usage log file may
be sent to AspenTech using the Auto Upload Tool, and customer can
download various usage reports from AspenTech customer support web site.

38 4 Configuring Aspen SLM

 Note: If you have a large user base, it is advisable to configure the maximum
log file size to a higher value. For example, set it to 7m instead of 5m.
Once this set file size is reached, SLM Server backs up the current usage log
file to another file in the same folder and starts a new log file. If the total
number of files reaches 9999, server will stop logging the usage. For
example, if the trace log file name is trace.log then the first trace log file will
be trace.log.00 and the last trace log file in the series will be
trace.log.9999. You must move the older files to another location for the
server to continue to log the usage. Auto Upload Tool has the ability to
automatically move the files to another location and transmit the log files to
AspenTech.

LServrcCNF Environment Variable

The LServrcCNF environment variable can be used to set the name and
location of the network license server configuration file. This file is used in
setting up user alerts and other options. If LServrcCNF is not used to specify
the configuration file, then the configuration file resides in the same directory
as the license file and has the same base name as the license code file but
with the extension *.cnf.
It is recommended that the default name and location be used for this file. In
most installations, this file is called lservc.cnf. It resides in the license server
default directory.

LSHost Environment Variable

This variable is set on your computer. When the application is activated, it
first tries to identify a standalone license. If there is no standalone license, it
will then attempt to obtain a license by searching for license servers over the
network. This broadcast search is limited to your local network subnet. If the
License Server is located outside the user’s local subnet, then the IP
address/hostname of the server must be specified to the remote network
license server for the Aspen (AspenTech) application(s) to establish a
connection.
For environment variables, there are three ways you can specify the
connection to the proper license server. The following lists the steps
AspenTech applications take to look for a license server:
 If the LSForceHost environment variable is set, the application looks for
the specific license server host listed in that variable. If it cannot find that
computer, an error message appears, and the application closes.

4 Configuring Aspen SLM 39

 # This is a generic lshost file
# Created June 20, 2000

TESTSERV_1
TESTSERV_2:TESTSERV_3:#TESTSERV_4
TESTSERV_5

Note: AspenTech does not recommend using the LSForceHost

environment variable, as it has been proven unreliable during testing.
 If the LSForceHost and LSHost environment variables are not set, then
a check is made for a file with the name lshost in the application root
directory. If this file is found, then the application looks for any of the
license server hosts listed in the file.
The LSHost environment variable naming conventions are:
 Any valid hostname recognized by your network.
 Numeric names (IP address).
Note: If you are using a network system where the DNS is variable, then
you cannot use the IP address for this purpose.
 NO_NET to disable the default network broadcast mechanism from
searching the network for a network license server. With this setting, the
application will only look for a standalone license file.

LSHost Environment Variable

The LSHost environment variable is used to tell the application to search for
one or more license servers.

Note: When using multiple server names on the same line you need to
separate the names, in both the environment variable string and lshost file,
with a colon (:).
When this variable is set, the application attempts to contact each server in
the list beginning with the first license server in the list. If none of the
specified license servers is found, the application stops searching and returns
an error. LSHost disables the network broadcast search for servers.
The lshost file works the same way as the LSHost environment variable.

Tip: The lshost file does not have a file name extension attached to it.
The lshost file must be placed in the application root directory. The following
is an example of a lshost file.
This file searches for TESTSERV_1, TESTSERV_2, TESTSERV_3, and
TESTSERV_5, in that order. Notice that TESTSERV_4 has been commented
out. Anything that follows a pound symbol (#) is treated as a comment.

LSForceHost Environment Variable

The LSForceHost environment variable is used to force the application to
look for a single license server computer. LSForceHost overrides an LSHost

40 4 Configuring Aspen SLM

 environment variable or a lshost file and disables the network broadcast
search for servers.

Note: LSForceHost is used by all Sentinel License Manager protected

products. Therefore, its use could interfere with the security used by other
applications also protected using Sentinel Computer ID dongles. Use
LSForceHost only as a last resort.

4 Configuring Aspen SLM 41

42 4 Configuring Aspen SLM
5 Configuring Aspen SSE
FlexNet

Purpose
This chapter describes how to configure the FlexNet License Manager
Mode.

Note: This chapter is only relevant if you selected FlexNet License

Manager Mode on the License Mode Configuration screen of the
aspenONE Installer. If you purchased an aspenONE Licensing Token Model,
you must install the SLM License Manager. For information on SLM, please
see “Chapter 4: Configuring Aspen SLM.”

Overview
Using the Aspen Subsurface Science and Engineering (SSE) products in the
FlexNet License Manager Mode requires the following:
 A FlexNet license server 11.16.6 or later is installed and configured. The
server can be hosted on the same machine as the applications or another
machine on your network.
 You have configured the end user machines (where the applications are
installed) to use the appropriate FlexNet license servers.

Installing and Configuring a

FlexNet License Server
For installing and configuring a FlexNet License Server, please refer to Aspen
SSE FlexNet Installation and Reference Guide.

5 Configuring Aspen SSE FlexNet 43

 Linking Applications to FlexNet
License Servers
For the Aspen Subsurface Science and Engineering (SSE) products to start,
they must be configured to access a license server. This is done on the
aspenONE installer during the installation process. If you must change the
settings or if you did not define them during installation, you can do so via
the Control Panel on your computer.

Aspen SSE FlexNet Environment Variables

Depending on the applications you purchased, you must define either one of
the environment variables, or both.
Table 1: Environment variables for Aspen SSE products on Windows

If you Set the environment variable To value

purchased
 Aspen METTE GEOMATICLM_LICENSE_FILE Port@ComputerName
 Aspen RMS Server Name or IP address of
 Aspen Tempest the geomaticLM license
 Aspen ResView server.
Default Port=27000
 Aspen Epos PRDM_GEO_LICENSE_FILE Port@ComputerName
 Aspen Geolog Note: This variable must be set Server Name or IP address of
 Aspen OpsLink before installing Aspen SSE the prdm_geo license server.
 Aspen SKUA products. See Figure 1. Default Port=7507
 Aspen Sysdrill

Configuring the Environment Variables

(Aspen SSE FlexNet)
For each user machine, set the GEOMATICLM_LICENSE_FILE and
PRDM_GEO_LICENSE_FILE variables to the adequate server names.
Below is the process to define environment variables globally on a Window
machine.

Note: Aspen Geolog has its own configuration file, where you can also set the
license variable for all users.

To configure the environment variables with the

aspenONE Installer:
When using the aspenONE V14.0.1 Installer, you should define the
environment variables.

44 5 Configuring Aspen SSE FlexNet

 Type the variable value for the FlexNet License Server and click Next to
continue with the installation process.
If the environment variable is already defined, the corresponding value
appears in the text box.

To add or edit the environment variables after installation

using the Control Panel (if necessary):
1 On your computer, open the Control Panel.
2 Click System. On the Settings view, click Advanced system settings.
3 On the System Properties dialog box, click the Advanced tab. On the
Advanced tab, click Environment Variables.
4 Under User or System variables group, click New.
The New System Variable view appears.
5 In the Variable Name field, type the corresponding variable name
(GEOMATICLM_LICENSE_FILE or PRDM_GEO_LICENSE_FILE)
6 In the Variable Value field, type the required value for the product you
are configuring.
7 Click OK.
The new environment variable and value is added in the Environment
Variables view.
4 If you do not need to set any more variables, click OK to close both
Environment Variables and System Properties views.
5 Reboot the computer to make sure these environment variables take
effect.

5 Configuring Aspen SSE FlexNet 45

 Alternatively, access the System Properties dialog box from Start ,
type Edit environment variables and click the result.

Examples of FlexNet License Server

Configuration
Below, we provide a few configuration examples to help you define the
environment variables for using the Aspen Subsurface Science and
Engineering (SSE) products.

Using a FlexNet License Server Configured by

Your Company
Usually, your company has configured license servers. On machines on which
you install the application, you should set up the following environment
variables (examples given for hosts my-lic-serv1 and my-lic-serv2):
Variable Value

GEOMATICLM_LICENSE_FILE 27000@my-lic-serv1

PRDM_GEO_LICENSE_FILE 7507@my-lic-serv2

Note: If you do not know the server values, contact the license administrator
at your company.

Using a FlexNet Server on Your Local Machine

If the license server is configured on the same machine as the applications,
you may use @localhost. This configuration is frequent when you use your
own laptop.
Variable Value

GEOMATICLM_LICENSE_FILE 27000@localhost

PRDM_GEO_LICENSE_FILE 7507@localhost

Using Multiple FlexNet Servers

You can define a list of servers to use with the semi-colon separator on
Windows. If the application cannot reach the first server, it attempts to
connect to the second server, and so on.
Variable Value

GEOMATICLM_LICENSE_FILE @server1;@server2;@server3

PRDM_GEO_LICENSE_FILE @server4;@server5;@server6

46 5 Configuring Aspen SSE FlexNet

 Note: In this example, the port was omitted for simplification. However,
unless the service is defined with no specific port, you must add the port
number in the server address.

5 Configuring Aspen SSE FlexNet 47

48 5 Configuring Aspen SSE FlexNet
6 Configuring Aspen Epos
Services

Services Configuration Wizard

Overview
The Aspen Epos Service Configuration Wizard is designed to configure and
start the Aspen Epos PNS service after the installation of Aspen Epos Services
is completed.
The PNS, which is the main Aspen Epos service, must be configured and
running in order for the Aspen Epos applications to function.
The PNS is the launcher and controller of the Aspen Epos Data Servers and
Utility Servers. The Aspen Epos Services provide Aspen Epos with security
control and data access across heterogeneous multi-user networks.
After the PNS is configured, the Aspen Epos Applications must be connected
to the PNS via the Aspen Epos Applications configuration wizard.
Some basic decisions need to be made during the Services Quick Start
configuration:
 Creating a New Configuration vs. Reusing an Existing Configuration
 Network Configuration vs. Local Configuration

Creating a New Configuration vs. Reusing

an Existing Configuration
 Creating a new configuration: This option creates a new PNS
configuration (PNS segment) in the newly created EposServices-V14
installation tree. If required, you can later import data from a previous
PNS version via the Aspen Epos Services Control Panel >
Administrator tab.
 Reusing an existing configuration: This option uses the previous PNS
Segment data stored in the previous configuration file. The information

6 Configuring Aspen Epos Services 49

 contained in the previous PNS segment (Project/Surveys, Data Paths, and
Aspen Epos Users) is available for use in the newly-configured version.
The previous Aspen Epos Services installation must remain in place.
When reusing a previous configuration, you must run the installation and
the configuration process from the same user that was used for the
previous configuration. Before starting the new configuration, shut down
the previous services on this host by running the
/bin/pns_remove_service command from the previous Services
installation tree.

Network vs. Local Configuration

 Local (Stand Alone) Configuration is designed for using Aspen Epos
Services on the same host where Aspen Epos Applications are running.
This setup is adequate for laptops/workstations of a single user, where no
data sharing among users or co-working is required. Work can be
continued without interruption when the network is switched off/on. Any
user can carry out a single user, single machine installation.
 Network Configuration: In a network installation, Aspen Epos Services
are installed on a dedicated host and will be used from multiple remote
workstations. It allows co-working and data sharing among users. For a
multi-user network environment, the installation procedure should be
carried out by the system administrator or other personnel familiar with
the local systems and network configuration. A network installation
requires additional preparation. See “Data Paths” below.

Data Paths
On a Network configuration, the EposDB allocates disk directories on the
network for the users to store their Aspen Epos data. The directories are
defined per type of data by considering the data size and network
accessibility.
In Aspen Epos Interpretation, Vertical Functions, Pencils, and Well databases
are accessed indirectly by dedicated data servers. The Seismic database is
accessed directly by the applications.
 The indirect data directory should be created/owned by the Epos
Administrator user with Read/Write permissions only for the Epos
Administrator user.
 The direct data directory should also be created/owned by the Epos
Administrator, but with Read/Write permissions for all Aspen Epos
software users.

Note: Table 2 shows each path, what it is used for, and the access mode.
Table 1. Managed Data Path Types

Path Is used for: Access Mode

DB Top level directories of any kind Indirect
of study
INT Separate interpretation data Indirect
areas for projects and surveys

50 6 Configuring Aspen Epos Services

 DRL Top level directories of drilling Indirect
databases
CLT Top level directories of cultural Indirect
databases
GEO Top level directories of geology Indirect
databases
WELL Top level directories of well Indirect
databases
VF Separate vertical function data Indirect
areas for projects and surveys
SCR Seismic data flagged as scratch Direct
APP Application-specific data areas Direct
for projects, surveys, and well
databases
PCL Separate pencil data areas for Direct
survey databases
TRC Seismic data areas for project Direct
and survey databases
SYNC Default location for database Direct
synchronization tools
BCK Default location for database Direct
backups

Configuring Aspen Epos

Services
Follow the steps below to configure Aspen Epos Services.
The configuration wizard should be launched on the dedicated PNS host.
1 Either:
o Click the Windows Start icon and run the Aspen Epos Service Start

Configuration Wizard V14 .

-or-
o Click the Windows Start icon and select the Aspen Epos Services

Control Panel V14 . In the Aspen

Epos Services Control Panel V14, click Configuration Wizard .

6 Configuring Aspen Epos Services 51

 -or-
o From the \AspenTech\EposServices-V14\bin\cli folder, run the
quick_start script.
2 The Configuration Wizard looks for existing configurations and opens:

52 6 Configuring Aspen Epos Services

 3 If a previous configuration was detected, the following dialog box appears:

Select if you want to create a new configuration or reuse the existing

configuration. See “Creating a New Configuration vs. Reusing an
Existing Configuration” above.
Click Next.
4 Either:
o Select Network to configure the Services for a Network environment.
o Select Local if you are configuring a local host.

6 Configuring Aspen Epos Services 53

 Click Next.
5 Enter the PNS host name.
o For network configuration, verify the PNS host name.
o For local configuration, the PNS host name must be set to localhost.

The PNS and other Aspen Epos Services will run on this host. Click Next.

54 6 Configuring Aspen Epos Services

 6 Enter your username and password. Note that the Epos Administrator user
configures the network services. Then click Next.

7 For network configuration, select the Data paths for storing Aspen Epos
Direct and Indirect Data and click Configure. The top directories, Direct
and Indirect are created automatically. You must specify the path up to
this level.
For Local configuration, a single data path applies for all data.

6 Configuring Aspen Epos Services 55

 8 Click Configure. The Aspen Epos Services are configured.

A Configuration Summary appears when configuration is done.

56 6 Configuring Aspen Epos Services

 Next, you must link Aspen Epos Applications to the PNS, see “Chapter 7:
Configuring Aspen Epos Applications”.

Configuring Crush Dump Functionality for

the PNS
Set the crash dump functionality for the server side (PNS) on Windows.

Note: For Windows, there is no automation retention policy for server crash
dump files.
To configure the crash dump for the PNS on Windows:
1 On a PNS host machine, in Advanced System Settings, set the
PG_CRASH_DUMP_MODE variable to 3.
For a description of the environment variable settings, see “Configuring
the Environment Variables (Aspen SSE FlexNet)” on page 44.
2 Restart the PNS server using the Services application.
The PNS server automatically sets the PG_ CRASH_DUMP variable (on
startup) to the PNS reports folder. There is no need to set the PG_
CRASH_DUMP variable for the PNS and data servers.
3 We recommend that if any crash dumps have been generated, archive the
entire crash_dumps directory using an appropriate method, such as 7-
zip, zip, or tar. Send these files to AspenTech Customer Support for
further analysis.

6 Configuring Aspen Epos Services 57

 Importing Aspen Epos Data from a Previous
PNS Segment
If you created a new configuration for the Aspen Epos Services, and you have
a PNS configuration from a previous version, you can import segment settings
from the previous to the new segment. This is performed via the Importing
Segment Settings on the Administrator tab of the Aspen Epos Services
Control Panel. See the Aspen Epos Services Help for more information.

58 6 Configuring Aspen Epos Services

7 Configuring Aspen Epos
Applications

After the installation is complete, the Aspen Epos Applications must be

connected to a running Aspen Epos PNS.
In a network configuration, the Aspen Epos Applications should be connected
to a common Aspen Epos PNS that is configured by the Aspen Epos
Administrator.
On a local installation, the Aspen Epos Applications should be connected to
the local PNS.
In addition, you should define the Crash Dump settings for applications, as
described below.

Note:
 Aspen Epos Applications will not run if they are not connected to an Aspen
Epos PNS host with running services.
 This chapter is not relevant to standalone Aspen SKUA installations; for
example, if you are not intending to use Aspen SKUA with Aspen Epos
services and databases, and have no other Aspen Epos Applications
installed.
 For a network installation, you must prepare the servers before
installation.

Configuring the Connection of

Aspen Epos Applications to an
Aspen Epos PNS Host
Use the Configuration Wizard in the Aspen Epos Control Panel to define
the list of Epos PNS hosts and, for FlexNet License Manager Mode, the
license servers to use.
To configure Aspen Epos Applications:
1 Open the Aspen Epos Applications V14 Control Panel by doing one of the
following:

7 Configuring Aspen Epos Applications 59

 o On the local file system, go to
C:\ProgramFiles\AspenTech\EposApplications-V14\bin and run
PG_epos_config.

-or-
o From Start menu , select the Aspen Epos Application Control

Panel V14.
The Aspen Epos Applications Control Panel appears. Click
Configuration Wizard.

60 7 Configuring Aspen Epos Applications

 The Quick Start dialog box appears.
2 To define the host, do one of the following:
a. If you are working in a network environment, specify the host name
where the network Aspen Epos PNS is running.

b. If you are running on a local configuration, enter localhost as the Host

name.
3 Click Next.
4 Click End to complete the configuration process.

Note: Aspen Epos Applications will not run if they are not connected to an
Aspen Epos host with running services.

7 Configuring Aspen Epos Applications 61

 Configuring Crash Dump
Settings
You can automatically save a call stack when a crash occurs in the Aspen
Epos Applications if you configure the crash dump variables. Crash dumps
help AspenTech to determine the cause of a failure more easily and provide
you a solution more rapidly.
1 On the Epos Applications Control Panel | Administrations tab,
click Runtime Variables.

2 On the Runtime Variables dialog box, press the Ctrl + f keys and
search for the PG_CRASH_DUMP related variables.

62 7 Configuring Aspen Epos Applications

 3 Set the PG_CRASH_DUMP to a valid full path of the directory where
stack dump files will be saved.
4 Accept the defaults of PG_CRASH_DUMP_MODE and
PG_CRASH_DUMP_RETENTION.
5 Click Save. The Crush Dump run time variables are set.
Next time a crash occurs, retrieve the call stack located in the folder you
specified in the PG_CRASH_DUMP variable and send it to AspenTech
Customer Support.
See the Aspen Epos Help (Aspen Epos Infrastructure > Appendix E:
Environment Variables) for more information on these variables.

7 Configuring Aspen Epos Applications 63

64 7 Configuring Aspen Epos Applications
8 Repairing Aspen
Subsurface Science and
Engineering (SSE) Products

Overview
Repairing Aspen Subsurface Science and Engineering (SSE) is performed from
the installation application. The installation program detects what software
has been installed.

When the Welcome screen appears, click Repair existing products. You
are prompted on how to continue.

8 Repairing Aspen Subsurface Science and Engineering (SSE) Products 65

66 8 Repairing Aspen Subsurface Science and Engineering (SSE) Products
9 Removing Aspen
Subsurface Science and
Engineering (SSE) Products

Overview
This chapter provides instructions for removing Aspen Subsurface Science and
Engineering (SSE) products from your computer.

Before You Remove

Before removing any products, close all applications and all subfeature
programs and save any files that you do not want to permanently lose. Pay
particular attention to custom configuration files.

Removing Aspen Subsurface

Science and Engineering (SSE)
To uninstall Aspen Subsurface Science and Engineering (SSE):
1 From the Start menu, click Aspen Configuration | aspenONE
Manager.
The aspenONE Manager window appears.

9 Removing Aspen Subsurface Science and Engineering (SSE) Products 67

 2 On the aspenONE Manager window, click Uninstaller.

68 9 Removing Aspen Subsurface Science and Engineering (SSE) Products

 3 The AspenTech Uninstaller window appears, listing all installed
AspenTech software.
4 On the AspenTech Uninstaller window, select the check boxes for the
products that you wish to uninstall, and then click Uninstall.
The Uninstall Summary screen displays the uninstallation progress.

5 After the Uninstall completed a message appears, click either Reboot

or Close. We recommend rebooting your machine.
The Uninstall Summary screen displays the uninstallation progress.

9 Removing Aspen Subsurface Science and Engineering (SSE) Products 69