Studio 2013

Version 2013.5

Studio Installation and

Configuration Guide

Studio Techlog 2018

Version 2018.1
INSTALLATION AND CONFIGURATION GUIDE
Copyright Notice
Copyright © 2018 Schlumberger. All rights reserved.
This work contains the confidential and proprietary trade secrets of
Schlumberger and may not be copied or stored in an information retrieval
system, transferred, used, distributed, translated or retransmitted in any
form or by any means, electronic or mechanical, in whole or in part, without
the express written permission of the copyright owner.
Trademarks & Service Marks
Schlumberger, the Schlumberger logotype, and other words or symbols used
to identify the products and services described herein are trademarks, trade
names or service marks of Schlumberger and its licensors, or the property
of their respective owners. These marks may not be copied, imitated or
used, in whole or in part, without the express prior written permission of
Schlumberger. In addition, covers, page headers, custom graphics, icons,
and other design elements may be service marks, trademarks, and/or trade
dress of Schlumberger, and may not be copied, imitated, or used, in whole
or in part, without the express prior written permission of Schlumberger.
Other company, product, and service names are the properties of their
respective owners.

Studio ® is a mark of Schlumberger. Techlog ® is a mark of Schlumberger.

An asterisk (*) is used throughout this document to designate other marks
of Schlumberger.

Security Notice
The software described herein is configured to operate with at least the
minimum specifications set out by Schlumberger. You are advised that such
minimum specifications are merely recommendations and not intended to
be limiting to configurations that may be used to operate the software.
Similarly, you are advised that the software should be operated in a secure
environment whether such software is operated across a network, on a
single system and/or on a plurality of systems. It is up to you to configure
and maintain your networks and/or system(s) in a secure manner. If you
have further questions as to recommendations regarding recommended
specifications or security, please feel free to contact your local
Schlumberger representative.

Country of origin: France

May 2018

Schlumberger Private - Customer Use

iv Studio Techlog Installation and Configuration Guide
Schlumberger Private - Customer Use
Contents
1 Information Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Schlumberger Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

About Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Typestyle Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Alert Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Contacting Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Studio Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

3 Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Configuring Studio Techlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Installation and Configuration Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

4 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Studio Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Studio Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Studio Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

5 Studio Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Version Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Studio Manager 2018 Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Contents v

Schlumberger Private - Customer Use

 Accessing Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Downloading the Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Installing Studio Manager 2018 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Updating Studio Manager from 2016.x and 2017.x to 2018.1 . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Updating and Managing Plug-ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Installing the Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
CodeMeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Installing CodeMeter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Schlumberger Licensing Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Installing the Schlumberger Licensing Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Configuring the Studio Manager License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Defining the License Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

6 Studio Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Downloading the Installation Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Installing Studio Server 2018 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Studio Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Studio Server Config File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

7 Studio Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Studio Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Installing the Database on a Fresh Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Upgrading Studio Database from 2016.x and 2017.x to 2018.1 . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Upgrading Repositories from 2016.x and 2017.x to 2018.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Setting Default Studio Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Running the Windows PowerShell Script for Database Configuration . . . . . . . . . . . . . . . . . . 7-14
Running the ValidationManager Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
List of Validation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Validation Manager Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21

8 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

vi Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Uninstalling Studio Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Uninstalling Studio Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Appendix A Licensing Issues, Best Practices and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Licensing Issues and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Best Practices for Setting Up a License Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Appendix B Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Configuring Oracle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Oracle 12.2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Oracle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Database Parameters Using Oracle 12.2.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Configuring SQL Server 2016 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
Windows Server Customizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
SQL Server 2016 Standard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9

Appendix C Configuring IIS 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Configuring IIS 10 with the Recommended Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Configuring IIS 10 with the Recommended Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Configuring HTTP Response Headers for Security Purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
Enabling and Configuring Compression in Studio Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
Configuring Secure Sockets Layer (SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Obtaining a Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Creating HTTPS Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Using the SSL Only Option (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Specifying a URL in Client Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Configuring IIS Ping Maximum Response Time in Studio Server . . . . . . . . . . . . . . . . . . . . . . . . C-14

Appendix D Database Server Standard Accounts for Oracle . . . . . . . . . . . . . . . . . . . . . . . . .D-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Studio Database Accounts Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Fixed Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .D-2
Variable Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Studio Database Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
STUDIO_SYS_ ADMINISTRATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
STUDIO_SYS_
UPGRADE_ROLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
Contents vii

Schlumberger Private - Customer Use

 Studio Database Account Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
STUDIO_SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6
STUDIO_SERVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7

Appendix E Characters Restricted for Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Characters Restricted for Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2

Appendix F Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Glossary Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Data Pump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Default Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Keytab File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Local Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
ORACLE_HOME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Oracle Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3
Oracle SYS Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3
Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3
STUDIO_SERVICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3
STUDIO_SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3
Temporary Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3
TNS_Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-3
TNS Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4

viii Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 1 Information Resources

In This Section

Schlumberger Product Documentation ......................................................... 1-2

About Schlumberger ............................................................................. 1-2
Online Documentation .......................................................................... 1-2
Typestyle Conventions .......................................................................... 1-2
Alert Statements .................................................................................. 1-2
Contacting Schlumberger ............................................................................ 1-3
Technical Support................................................................................. 1-3

Information Resources 1-1

Schlumberger Private - Customer Use

Schlumberger Product Documentation

Schlumberger Product Documentation

About Schlumberger is the leading oilfield services provider, trusted to deliver superior
Schlumberger results and improved E&P performance for oil and gas companies around the world.
Through our well site operations and in our research and engineering facilities, we
develop products, services, and solutions that optimize customer performance in a
safe and environmentally sound manner.

Online Documentation is provided in the following electronic formats on the Schlumberger

Documentation product CD:
• Adobe® Acrobat® PDF files
• Online help
You must have Adobe® Reader® installed to read the PDF files. Adobe Reader
installation programs for common operating systems are available for a free
download from the Adobe Web site at www.adobe.com.

Typestyle The following conventions are observed throughout this guide:

Conventions
• Bold text is used to designate file and folder names, dialog titles, names of
buttons, icons, and menus, and terms that are objects of a user selection.
• Italic text is used for word emphasis, defined terms, and manual titles.
• Monospace text (Courier) is used to show literal text as you would enter it, or
as it would appear onscreen.

Alert Statements The alerting statements are Notes, Cautions, and Warnings. These statements are
formatted in the following style:

• • • • • •
Note: Information that is incidental to the main text flow, or to an important
point or tip provided in addition to the previous statement or instruction.

• • • • • •
Caution: Advises of machine or data error that could occur should the user fail
to take or avoid a specified action.

• • • • • •
Warning: Requires immediate action by the user to prevent actual loss of data
or where an action is irreversible, or when physical damage to the
machine or devices is possible.

1-2 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Contacting Schlumberger

Contacting Schlumberger

Technical Support Schlumberger has sales and support offices around the world. For information on
contacting Schlumberger, please refer to the information below.

Technical Support for SIS software Technical Support Website

Internet www.slb.com

Information Resources 1-3

Schlumberger Private - Customer Use

Contacting Schlumberger

1-4 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 2 Studio

In This Chapter

Introduction............................................................................................... 2-2
Audience ............................................................................................. 2-2
Studio Overview ......................................................................................... 2-3

Studio 2-1
Schlumberger Private - Customer Use
Introduction

Introduction
This chapter provides a quick view of Studio and its capabilities.

Audience This chapter is intended for the user who wants to learn more about Studio. It
describes the Studio environment and the general functionalities.

2-2 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Studio Overview

Studio Overview

The Studio E&P environment empowers a level of usability and productivity that
supports an E&P organization’s quest to streamline and optimize its workflow across
the asset lifecycle, while also capturing vital knowledge to maximize personal and
team productivity. It features a powerful set of tools that allow geoscientists and
engineers to access, review, and use information in the context of their workflows,
providing three key capabilities that increase productivity.
• Find Your Information
Studio provides a fast, powerful and intuitive way to search, identify and consume
information in the context of your project and workflows. Filter multiple
information sources on any value of metadata, display results in a variety of ways,
and either consume the information directly into your working environment or
share your results with others. Find empowers a new level of data discovery,
putting the information you need right where you need it.
• Collaborate with Your Team
Studio promotes collaboration by enabling team members to promote those
elements of their project that are of relevance to the rest of the team or business.
Capturing the status and quality of interpretation as it is published to Studio
ensures integrity and reliability for other team members both now and into the
future. Subscribing to notifications on data of interest, team members can receive
alerts on the work of others that is relevant to their current workflow.
• Manage Your Knowledge
Studio provides a proven, scalable database supported by industry standard
technology (Oracle® and Microsoft® SQL Server®). It is specifically designed to
handle E&P project data as well as the knowledge related to that data, all stored
together in context. This allows users to obtain better retention and reuse of the
generated knowledge.

Studio 2-3
Schlumberger Private - Customer Use
Studio Overview

2-4 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 3 Installation Summary

In This Section

Introduction............................................................................................... 3-2
Audience ............................................................................................. 3-2
Configuring Studio Techlog ......................................................................... 3-3
Installation and Configuration Workflows ..................................................... 3-5

Installation Summary 3-1

Schlumberger Private - Customer Use

Introduction

Introduction
This chapter provides a quick view of the different workflows covered in this
document. See “Installation and Configuration Workflows” on page 3-5 for
information showing where you can find more details related to each step required
in the workflows.

Audience This chapter is intended for the data manager or data administrator who installs and
maintains Studio in a system environment. It describes the workflows for installation
and uninstallation of Studio.

3-2 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring Studio Techlog

Configuring Studio Techlog

Studio Techlog is composed of three components:
• The client on which Techlog or Studio Manager is installed
- Techlog: all collaboration workflows are done in Techlog
- Studio Manager: tool used by data administrators to manage Studio
repositories
• The Studio server: IIS Windows server, which contains all the services managing
the Studio database
• The Studio database: can be Oracle or SQL Server, contains all the Techlog data
All three components need to be installed.

Installation Summary 3-3

Schlumberger Private - Customer Use

Configuring Studio Techlog

The following shows the general workflow for configuring Studio Techlog.

3-4 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Installation and Configuration Workflows

Installation and Configuration Workflows

This section gives information showing where you can find more details related to
each step required in the workflows.

• Review the System Requirements (Details in Chapter 4)

Studio • Configure Windows Server (IIS) (Details in Appendix C)

Server

• Review the System Requirements (Details in Chapter 4)

• Install SQL Server or use preexisting instance (Details in Appendix
Database B)

• Review the System Requirements (Details in Chapter 4)

• Install Oracle Server or use preexisting instance Details in
Database Appendix B)

Review the System Requirements (Details in Chapter 4)

Studio
Manager

Installation Summary 3-5

Schlumberger Private - Customer Use

Installation and Configuration Workflows

Install Studio Server

• Review the System Requirements (Details in Chapter 4)

Prerequisites
• Windows Server (IIS) (Details in Appendix C)

• Install Studio Server

• Define the Server options
Install • Enter name of website, port number, and location of folder for logs
Software

• Install Studio Server

• Define connection information
Install • Enter Provider, Host, Port, and Database name
Software

3-6 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Installation and Configuration Workflows

Install Studio Manager

In Studio Techlog 2018, there is an installation option: the ability to load Studio Manager plug-ins from a
plug-in directory. This loads the default Studio Manager plug-ins or any third-party plug-ins in this directory.
For more details, see Chapter 5, “Studio Manager”.

Review the System Requirements (Details in Chapter 4)

Prerequisites

Install Studio Manager (Details in Chapter 5)

Install
Software

Install Studio Plug-ins (Details in Chapter 5)

Install
Software

Installation Summary 3-7

Schlumberger Private - Customer Use

Installation and Configuration Workflows

Configure Studio for SQL Server or Oracle

After installing the Studio Server, Studio Manager, and the Studio plug-ins, it is required to launch Studio
Manager and configure Studio to either begin a new database installation or upgrade existing databases to a
newer version. This begins by clicking the Open Settings icon in Studio Manager and following the steps
below.

• Launch Studio Manager

• Create a database connection in Studio Manager by clicking the Open
Settings icon, selecting Connections, and inserting the correct name
Configure
Studio and Studio Server URL (test connection by clicking blue question mark )

• Launch Studio Manager

• In Studio Manager, click the Open Settings icon, select Connections,
Configure and click in the Actions tab to Connect and get database information
Studio to configure a new database or upgrade an existing one

• Launch Studio Manager

• Configure logging and licensing options
Configure
• Use Studio Manager to create and manage Users and Studio repositories
Studio

Uninstall Studio Database

Use Studio Manager to uninstall Studio Database (Details in Studio

Uninstall Manager Help)
Software

3-8 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Installation and Configuration Workflows

Uninstall Studio Server

Uninstall Studio Server (Details in Chapter 8)

Uninstall
Software

Uninstall Studio Manager

Uninstall Studio Manager (Details in Chapter 8)

Uninstall
Software

Installation Summary 3-9

Schlumberger Private - Customer Use

Installation and Configuration Workflows

3-10 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 4 System Requirements

In This Chapter

Introduction............................................................................................... 4-2
Audience ............................................................................................. 4-2
Studio Manager .......................................................................................... 4-3
Studio Database ......................................................................................... 4-4
Oracle ................................................................................................. 4-4
SQL Server........................................................................................... 4-5
Studio Server ............................................................................................. 4-6

System Requirements 4-1

Schlumberger Private - Customer Use
Introduction

Introduction
This chapter provides details of the different system requirements needed to install
and configure the Studio products.

Audience This chapter is intended for the administrator and user who need to know the
different system requirements needed for the Studio products.

4-2 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Studio Manager

Studio Manager
Table 4-1 and Table list the minimum and recommended system requirements for
Studio Manager. Any systems not mentioned within the scope of this document will
not be officially supported for use.

Table 4-1 Studio Manager - Windows Client System Requirements

Recommended
Operating system Windows Server 2016 SP1 Standard (64-bit)
Windows 10 Pro or Enterprise (64-bit)
Processor Dual quad-core/six-core processor (quad-core processor
minimum) (best with a fast clock speed and high cache)
Memory 48 GB DDR3 SDRAM (16 GB minimum)
Display Quality of the viewing experience increases with size and
number of monitors
Graphics NVIDIA® Quadro® 6000 (NVIDIA Quadro 4000 minimum)
Primary storage • Fast rotational speed HDD (10K, 15K)
• SSD
Secondary storage Optional

Other Required Software

Microsoft .NET® Framework 4.6.1 and higher

Microsoft Visual C++ Runtime 2010, 2012, 2013, and 2015

(installed silently on a non-Windows Server)
Microsoft System CLR Types For Microsoft SQL Server 2016
(64-bit) (installed silently on a non-Windows Server
machine)
The Backup/Restore scripts provided with Manager require
the specific database clients to be installed on the system
where those scripts are executed.
See Server Requirements for more details about installing
the database clients.

System Requirements 4-3

Schlumberger Private - Customer Use
Studio Database

Studio Database

Oracle

Operating Environment Studio Database is certified for use with a Red Hat® Enterprise Linux® (RHEL)
operating system and must be used with the Oracle® Database Enterprise Edition
12.2.0.1 database.

Table 4-2 Supported Operating Environment

Operating system Version Database

Linux RHEL Server 7.3 (64-bit) Oracle Database
Enterprise Edition
12.2.0.1 (64-bit)

• • • • • •
Note: Linux is the only commercially supported operating system for Studio
Database on Oracle.

Studio Database supporting Techlog does not require a spatial engine to

manage spatial data.

4-4 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Studio Database

System Hardware Studio Database should be installed on a computer with the appropriate hardware
Requirements resources in order to maximize software performance. Table 4-3 contains guidelines
for both minimum and recommended system hardware levels. The Oracle server
may require significant resources, depending on the number and size of the
databases, and the number of simultaneous users. The amount of RAM should be
sized accordingly.
Table 4-3 System Hardware Requirements

Recommended
Processor x64 processor (dual six-core) (x64 processor [dual quad-core]
minimum)
Memory 64 GB or greater (32 GB minimum)

SQL Server

Operating Environment Studio Database for SQL Server is certified for use with SQL Server 2016 SP1
Standard Edition, on Windows Server 2016 Standard (64-bit), and Windows Server
2012 R2 Standard (64-bit).

System Hardware Studio Database should be installed on a computer with the appropriate hardware
Requirements resources to maximize software performance. Table 4-4 contains guidelines for both
minimum and recommended system hardware levels. SQL Server may require
significant resources, depending on the number and size of the databases, and the
number of simultaneous users. The amount of RAM should be sized accordingly.
Table 4-4 System Hardware Requirements

Recommended
Processor x64 processor (dual quad-core) (x64 processor [quad-core]
minimum)
Memory 64 GB or greater (32 minimum)

• • • • • •
Note: Information on memory limitations for Windows Server 2016 can be found
at the following link:
https://msdn.microsoft.com/en-us/library/windows/desktop/
aa366778(v=vs.85).aspx

System Requirements 4-5

Schlumberger Private - Customer Use
Studio Server

Studio Server
Studio Server should be installed on a computer with the appropriate hardware
resources to maximize software performance. Table 4-5 contains guidelines for both
minimum and recommended system requirements.
Table 4-5 Studio Server System Requirements

Recommended
Operating system Windows Server 2016 Standard (64-bit)
Windows Server 2012 R2 Standard (64-bit)
Processor x64 processor (dual six-core) (x64 processor [dual quad-
core] minimum)
Memory 64 GB or greater (48 GB minimum)
Web Server IIS 10

Disk Space† 50 GB

Other Required Software

Microsoft .NET Framework 4.6.1 and higher
Database client dependent on Studio Database:
• Oracle Client 12.2.0.1 with Administrator option
• SQL Server 2016:
- Microsoft ODBC Driver 13 for SQL Server †
- Microsoft Command Lines Utilities 13 for SQL Server †
The ORACLE_HOME variable needs to be set properly and
the $ORACLE_HOME/bin location needs to be included in
the PATH variable.
Microsoft Visual C++ Runtime 2010, 2012, 2013 and 2015
(installed silently on a non-Windows Server machine)

The components can be downloaded from:

SQL Server 2016:
https://www.microsoft.com/en-us/download/details.aspx?id=54279
The following is a download summary of the files that you need:
• ENU\x64\msodbcsql.msi
• ENU\x64\MsSqlCmdLnUtils.msi

4-6 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Studio Server

• • • • • •
Note: The number formats that Windows uses to display information (Region
and Language settings) between the Studio Server machine and client
machines must be the same; different number formats between the Studio
Server and client machines can prevent data transfer. Specifically, the
“Decimal symbol” and the “Digit grouping” settings must be the same
between the Studio Server machine and client machines. In addition, the
language for the Operating System must be English (US) on both the
Studio Server machine and client machines.

System Requirements 4-7

Schlumberger Private - Customer Use
Studio Server

4-8 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 5 Studio Manager
In This Chapter
Introduction............................................................................................... 5-2
Version Compatibility ............................................................................ 5-3
Audience ............................................................................................. 5-3
Studio Manager 2018 Distribution ................................................................ 5-4
Licensing ................................................................................................... 5-5
Accessing Licenses ............................................................................... 5-5
Downloading the Installation Package .......................................................... 5-6
Installing Studio Manager 2018 ................................................................... 5-7
Installation........................................................................................... 5-7
Updating Studio Manager from 2016.x and 2017.x to 2018.1........................5-13
CodeMeter ..........................................................................................5-15
Installing CodeMeter............................................................................5-15
Schlumberger Licensing Tool ................................................................5-16
Installing the Schlumberger Licensing Tool ...........................................5-17
Configuring the Studio Manager License................................................5-17
Defining the License Server Environment ....................................................5-18

Studio Manager 5-1

Schlumberger Private - Customer Use
Introduction

Introduction
Studio Manager comprises a suite of tools for effectively managing the Studio
environment. It consolidates administrative and core data management workflows
supporting Studio Techlog. Using Studio Manager, data managers quickly
understand the state of their Studio environment by using cutting-edge applications
("apps") to ascertain the status of repositories, identify tasks that need to be
performed, and perform the workflows surrounding those tasks.
Studio Manager also shows high-level information in “widgets”, which you can
display or hide.
Studio Manager includes the following key workflows and capabilities:
• Clean and streamlined app-based interface in which all apps are accessible from a
centralized App Gallery that is organized into categories (Browse, Correct,
Administer, and Organize)
• Message Center that keeps data managers informed of data administration and
data transfer issues
• Ability to use match rules, and configure the Studio Database in Oracle and
Microsoft SQL Server
• Administer and centrally manage coordinate systems, unit aliases, users, and
Techlog data

5-2 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Introduction

Version The following shows which versions of Studio Database and Techlog are compatible
Compatibility with Studio Manager 2018.1
• Studio Database 2018.1
• Techlog 2018.1
• Studio Server 2018.1

Audience This chapter is intended for the data manager or data administrator who installs and
maintains Studio Manager in a system environment. It describes the requirements
and procedures for installation and configuration of Studio Manager. You must be a
Windows® Administrator to install Studio Manager.

Studio Manager 5-3

Schlumberger Private - Customer Use
Studio Manager 2018 Distribution

Studio Manager 2018 Distribution

Studio Manager 2018 can be accessed from the Studio Techlog installer, which is
available in DVD format or from the Software Download Center. You can access the
Software Download Center at www.sdc.oilfield.slb.com.

5-4 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Licensing

Licensing
To run Studio Manager 2018, you need valid licenses for this release. The licenses
can be configured either locally on your computer or on a central license server.
Studio Manager 2018 requires Schlumberger Licensing 2018, which is distributed on
the Techlog DVD. Studio Manager version 2018 will not work with Schlumberger
Licensing 2015. The 2018 version of the Schlumberger Licensing tool is backward
compatible with all previous release versions. Schlumberger Licensing 2018 is based
on Flexera™ FlexNet Publisher® to provide a secure licensing solution. See
“Updating Studio Manager from 2016.x and 2017.x to 2018.1” on page 5-13.

Accessing Licenses Studio Manager is a licensed application and has two associated licenses, depending
on features that are intended to be used in your organization:
• License for connection of Studio Manager to Studio Database running on Oracle
• License for connection of Studio Manager to Studio Database running on Microsoft
SQL Server
A suitable database license is checked out upon connecting to a database. To order
licenses, please visit the Ocean store at www.ocean.slb.com.

• • • • • •
Note: For information about the Schlumberger Licensing tool, see the
Schlumberger Licensing User Guide, which can be accessed through the
online Help for the Schlumberger Licensing tool.

Studio Manager 5-5

Schlumberger Private - Customer Use
Downloading the Installation Package

Downloading the Installation Package

The Studio Techlog installer can be obtained via the Software Download Center.

• • • • • •
Note: If you are a new user of the Software Download Center, you must register
before you can download the Studio Techlog installer.

To Download the Studio Techlog installer from the Software Download
Center
1 Go to www.sdc.oilfield.slb.com.
2 Click SIS Software Download Center.
3 Log in to the site.
4 On the Welcome Message page, click Continue.
5 In the Product Group Name list (in the upper-left corner), click Techlog.
6 In the table of Techlog downloads, click the Download icon for the
Techlog20181_Studio2018_x64.zip file.

5-6 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Installing Studio Manager 2018

Installing Studio Manager 2018

Installation This section covers the installation process for Studio Manager, which is installed
using the Studio Techlog installer. The requirement for running the Studio Techlog
installer is Microsoft .NET Framework 4.6.1.

• • • • • •
Note: If you obtained the software from the Software Download Center, you
must unzip the Techlog20181_Studio2018_x64.zip file before being
able to use the Studio Techlog installer.

• • • • • •
Note: All users who run Studio Manager on their workstations must have
read/write permissions to the %ProgramData% folder, usually
C:\ProgramData (used by internal application components).

• • • • • •
Note: Only a Windows Administrator can run the installer program.

 To Install Studio Manager from the Studio Techlog installer

1 Double-click Studio_2018.exe on the Techlog DVD.
The Select Studio Component panel displays.

Studio Manager 5-7

Schlumberger Private - Customer Use
Installing Studio Manager 2018

Fig. 5-1 Select Studio Component Panel

• • • • • •
Note: If you click Documentation, you can view the available release
documents found in the Documentation folder on the Techlog DVD.

2 Select Studio Manager 2018.

The License Terms & Conditions panel displays.
3 Read the license agreement, select I accept the terms in the License
Agreement, and then click Next.
The Prerequisite check panel displays.

5-8 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Installing Studio Manager 2018

Fig. 5-2 Prerequisite check Panel

A check is done to make sure all the prerequisites meet the recommended
requirements for a successful installation. The prerequisite check is done for
the Operating System, Microsoft .NET Framework, Microsoft Visual C++
Runtime, and Microsoft System CLR Types For Microsoft SQL Server.

• • • • • •
Note: Studio Server requires .NET 4.6.1 or higher.

• • • • • •
Note: Visual C++ Runtime and System CLR Types for SQL Server are installed
silently on a non-Windows Server machine and with a prompt on a
Windows Server machine.

Studio Manager 5-9

Schlumberger Private - Customer Use
Installing Studio Manager 2018

During the prerequisite check, a prerequisite is verified by one of the following:

• - Meets the requirement

• - Warning

• - Error

• • • • • •
Note: During the prerequisite check, if any prerequisite is identified as being
different than what is recommended, but will not cause the installation to
fail, a warning will display and you will still be able to proceed with the
installation. However, if an error displays for a prerequisite, you will not be
able to proceed with the installation. You can hover over any icon to
display a tooltip, which gives you additional information.

• • • • • •
Note: If the installed .NET version is older than the required version, an error
displays during the prerequisite check, and you cannot proceed with the
installation. We recommend that you install the required .NET version,
which is available in the installation package.

4 If the requirements for the prerequisites have been met, click Next.
The Install Studio Manager to panel displays.
5 Do the following:

a. Accept the default folder, or click to select the folder where you want to
install Studio Manager.
b. To add a shortcut for Studio Manager 2018 to the desktop, select Add
desktop shortcut.
6 Click Next.
The Ready to install Studio Manager 2018 panel displays.
7 Click Install.
After the Studio Manager installation is finished, the Setup Successful panel
displays.
8 Do the following:
a. If you do not want to install the plug-in or you want to install it later, click
Close.
b. If you want to proceed with the plug-in installation, click Plug-ins.
The Select Plug-In Source Location panel displays.

5-10 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Installing Studio Manager 2018

Fig. 5-3 Select Plug-In Source Location Panel

• • • • • •
Note: You can view the plug-ins and extensions that are currently installed by
selecting Show currently installed Plug-ins and Extensions.

9 Accept the default source location, or click to select an alternate source

location from where you want to install the plug-in.
10 Click Next.
A panel displays, showing the plug-in that is ready to be installed.

• • • • • •
Note: Required plug-ins are selected by default; however, you have the option to
clear the check box for any plug-in you do not want installed.

Studio Manager 5-11

Schlumberger Private - Customer Use
Installing Studio Manager 2018

Fig. 5-4 Select Plug-ins and Extensions Panel

11 Click Next.
The Ready to install Studio Manager Plug-ins and Extensions panel displays.
12 Click Install.
During the installation of a plug-in, the installer gives you status updates. After
the plug-in is installed, a confirmation panel displays, showing how many files
were unzipped during the installation and confirming that the plug-in is
registered. This process is repeated for each plug-in that is installed.
When the installation of the plug-in is finished, you will see a confirmation that
the plug-in has been installed.
13 Click Back if you want to install any plug-ins from other folders or click Close
to exit.

5-12 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Updating Studio Manager from 2016.x and 2017.x to 2018.1

Updating Studio Manager from 2016.x and 2017.x to 2018.1

This section covers updating Studio Manager 2016.x to Studio Manager 2018.1 as
well as updating and managing the plug-ins. The update process is done by using
the Studio Techlog installer.

• • • • • •
Note: Only a Windows Administrator can run the installer program.

 To Update Studio Manager from 2016.x to 2018.1 from the Studio

Techlog installer
1 Double-click Studio 2018.exe on the Techlog DVD.
The Select Studio Component panel displays.
2 Select Studio Manager 2018.
3 Click Upgrade to display the Ready to upgrade Studio Manager 2018 panel.
4 Click Upgrade to update Studio Manager.
After the Studio Manager update is finished, the Successfully Upgraded panel
displays.
5 Click Close to exit.

Updating and To Update Studio Manager Plug-ins from the Studio Techlog installer
Managing Plug-ins
1 From the Select Studio Component panel, select Studio Manager 2018.
2 Click Plug-ins.
The Select Plug-in Source Location panel displays.

• • • • • •
Note: You can view the plug-ins and extensions that are currently installed by
selecting Show currently installed Plug-ins and Extensions.

3 Accept the default source location, or click to select an alternate source

location from where you want to update the plug-in.
4 Click Next.
A panel displays, showing the plug-in that is ready to be updated.

• • • • • •
Note: Required plug-ins are selected by default; however, you have the option to
clear the check box for any plug-in you do not want updated.

5 Click Next.

Studio Manager 5-13

Schlumberger Private - Customer Use
Updating Studio Manager from 2016.x and 2017.x to 2018.1

The Ready to install Studio Manager Plug-ins and Extensions panel displays.
6 Click Install.
When the update of the plug-in is finished, you will see a confirmation that the
plug-in has been updated.
7 Click Back if you want to update any plug-ins from other folders or click Close
to exit.

5-14 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Installing the Licensing

Installing the Licensing

CodeMeter Studio Manager 2017 uses the CodeMeter dongle for license authentication. Before
you insert your CodeMeter dongle into a USB port on your local workstation or on a
central license server, you must install the CodeMeter software. You should use
CodeMeter in the following circumstances:
• If you use a local license (that is, your local workstation is your local license
server), install the CodeMeter dongle, appropriate CodeMeter driver, and the
Schlumberger Licensing tool on your computer.
Installing these licensing tools on your computer is also helpful if your company is
using enterprise license mobility.
• If you use a license on a central license server, the Administrator installs
the CodeMeter dongle, CodeMeter driver, and the Schlumberger Licensing tool on
the server. Individual users do not need to install any licensing hardware or
software on their computers.

Installing Follow the steps in this section to install the CodeMeter version required for this
CodeMeter Studio Manager release, and uninstall previous versions.

 To Install CodeMeter

• • • • • •
Note: CodeMeter automatically installs in your default Program Files directory:
%programfiles%\CodeMeter (usually C:\Program Files).

1 On the Techlog DVD, in the root folder, open the Licensing folder and run
CodeMeterRuntime.exe.
Alternatively, go to the CodeMeter Web site (www.codemeter.com) and
download CodeMeter 6.3 from the web site.
The CodeMeter installation wizard opens.
2 On the Welcome panel, click Next.
3 On the License Agreement panel, read the agreement, select I accept the
license agreement, and then click Next.
4 On the User Information panel, enter your name, your company’s name, and
who will use CodeMeter on your computer, and then click Next.
5 On the Select Features panel, select the features you want to install and then
click Next.
Schlumberger recommends that you accept the default settings.
6 On the Ready to Install panel, click Next to begin the installation.
7 When the installation is complete, on the last panel click Finish.
8 Restart your computer.

Studio Manager 5-15

Schlumberger Private - Customer Use
Installing the Licensing

The CodeMeter icon appears in your Windows taskbar. When you insert
your CodeMeter dongle into the USB port, the icon changes to show that
your computer recognizes the dongle. If you double-click the icon, you can
view information about the dongle.
You are ready to install the Schlumberger Licensing tool.

 To Uninstall Previous Versions of CodeMeter

If you have an older version of CodeMeter installed on your computer, uninstall it
and then install the latest version.
1 If you want to check the version of CodeMeter you are currently using before
uninstalling it, on the Windows toolbar right-click the CodeMeter icon and select
About to open the About CodeMeter window.
2 Remove your CodeMeter dongle from the USB port.
3 Click Start > Control Panel > Programs > Programs and Features >
Uninstall or change a program.
4 On the list of currently installed programs, select CodeMeter Runtime
Kit vx.x.
5 Click Uninstall.

Schlumberger Studio Manager uses FlexNet for licensing. The Schlumberger Licensing tool is a
Licensing Tool simple interface for FlexNet. Using the Schlumberger Licensing Tool to configure and
manage your Studio Manager license is recommended, but you may use FlexNet
tools instead.
After you install CodeMeter on your computer, you must install the Schlumberger
Licensing tool. You will use the Schlumberger Licensing tool to configure your Studio
Manager license. This version of the Schlumberger Licensing tool uses FlexNet.
Install the Schlumberger Licensing tool as follows:
• If you use a local license (that is, your local workstation is your local license
server), install the licensing tool on your computer.
• If you use a license on a central license server, the Administrator installs the
licensing tool on the server. The Schlumberger Licensing tool is not required for
the Administrator to install, configure, and manage the Studio Manager license.
The Administrator may choose to manage Studio Manager licenses with FlexNet
native tools.
• If you use enterprise license mobility, the Administrator must install the
licensing tool on your server for when you are in your office. You must also install
the licensing tool on your laptop for the times you are out of the office.

• • • • • •
Important: Even if you connect to a central license server to run Studio
Manager in the office, you must install the Schlumberger Licensing
tool and a local license on your laptop to run Studio Manager from
your laptop while traveling.

5-16 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Installing the Licensing

Installing the Follow the steps in this section to install the Schlumberger Licensing tool. If you
Schlumberger have a previous version of the licensing tool and want the latest version, uninstall
Licensing Tool the older version and then install the latest version.

• • • • • •
Note: If you use the 2015 version of the Schlumberger Licensing tool when
connecting to Studio Manager 2018, you will receive the following error
message: "License checkout failed. Make sure you're connecting to 2018
license server. 2015 license servers are not supported."

 To Uninstall Previous Versions of the Schlumberger Licensing Tool

1 Click Start > All Programs > Schlumberger > Schlumberger Licensing
> Uninstall Schlumberger Licensing.
A confirmation dialog box confirms your choice.
2 On the confirmation dialog box, click Yes to uninstall.
You are ready to install the latest version of the Schlumberger Licensing tool.

 To Install the Schlumberger Licensing Tool

You must install the Schlumberger Licensing tool from the Techlog DVD. To obtain
the Techlog DVD, contact your local Schlumberger support representative.
1 On the Techlog DVD, open the Licensing folder and run
SchlumbergerLicensingTool_2018.1.exe.
The installation wizard opens.
2 On the Welcome panel, click Next.
3 Complete the following steps on the Destination Folder panel:
a. If you want to change the location of the program files, click Change and
then navigate to a new location. If you are installing on a central license
server, select a folder on the central license server.
b. Click Next.

4 On the Ready to Install panel, click Install.

5 When the installation is complete, on the last panel select Launch
Schlumberger Licensing and then click Finish.
You are ready to configure the Studio Manager license.

Configuring the For information on configuring the Studio Manager license, see the online Help for
Studio Manager the Schlumberger Licensing tool.
License

Studio Manager 5-17

Schlumberger Private - Customer Use
Defining the License Server Environment

Defining the License Server Environment

 To Define the License Server Environment
1 Start Studio Manager, using the following menu command:
Start > All Programs > Schlumberger > Studio Manager 2018 > Studio
Manager 2018

• • • • • •
Note: Studio Manager uses the SLBSLS_LICENSE_FILE license server
environment variable. Other Schlumberger applications may also use this
variable.

The first time that you launch Studio Manager 2018, you may see a message
stating that Studio Manager finds no licenses or that license checkout failed.
The message appears under the following circumstances:
• SLBSLS_LICENSE_FILE variable has not yet been defined.
• The license server contains no Studio Manager licenses.
• The Studio Manager license is not valid.
• You are connecting to a 2015 or older license server. Only a 2018 license
server is supported.

• • • • • •
Note: If the message appears after the first time you open Studio Manager and
have already defined the license server, there may be a problem in
connecting to the license server.

2 On the message, click OK.

A message warns that you are about to change the license server environment
variables.
The Define license server window opens.

5-18 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 Defining the License Server Environment

3 Enter the following information:

On the License server environment variable field, select the address of
your local computer or of the central license server where your license
is stored.
The address must be in the following format:
port@servername
Where:
port is the port number where the license service is running (typically 27000).
You can omit the port number if it is in the default range of 27000 to 27009 and
if your workstation is on the same local network as the license server.
servername is the fully qualified domain name of the server or IP address of the
system where the license was installed and configured.
4 Click OK.

Studio Manager 5-19

Schlumberger Private - Customer Use
Defining the License Server Environment

5-20 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use
 6 Studio Server

In This Chapter

Introduction............................................................................................... 6-2
Audience ............................................................................................. 6-2
Downloading the Installation Package .......................................................... 6-3
Installing Studio Server 2018....................................................................... 6-4
Installation........................................................................................... 6-4
Studio Service Account ..............................................................................6-10
Studio Server Config File ............................................................................6-11

Studio Server 6-1

Schlumberger Private - Customer Use

Installing Studio Server 2018

Introduction
Studio Server is the web-service middle tier that bridges the communication
between client applications and the Studio Database.

Audience This chapter is intended for the web server administrator who installs and maintains
Studio Server in a system environment. It describes the requirements and
procedures for installation and configuration of Studio Server.

6-2 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Downloading the Installation Package

Downloading the Installation Package

To install Studio Server, you need the installation package. You can download the
Studio Techlog installer to access the Studio Server installer, which is a component
of the Studio Techlog installer, from the Software Download Center.

• • • • • •
Note: If you are a new user of the Software Download Center, you must register
before you can download the Studio Techlog installer.

• • • • • •
Note: You may already have this package, if you have installed Studio Manager
2018.

To Download the Studio Techlog installer from the Software Download
Center
1 Go to www.sdc.oilfield.slb.com.
2 Click SIS Software Download Center.
3 Log in to the site.
4 On the Welcome Message page, click Continue.
5 In the Product Group Name list (in the upper-left corner), click Techlog.
6 In the table of Techlog downloads, click the Download icon for the
Techlog20181_Studio2018_x64.zip file.

Studio Server 6-3

Schlumberger Private - Customer Use

Installing Studio Server 2018

Installing Studio Server 2018

Installation This section covers the installation process for Studio Server, which is installed using
the Studio Techlog installer. The requirement for running the Studio Techlog installer
is Microsoft .NET Framework 3.5.

• • • • • •
Note: If you obtained the software from the Software Download Center, you
must unzip the Techlog20181_Studio2018_x64.zip file before being
able to use the Studio Techlog installer.

• • • • • •
Note: Only a Windows Administrator can run the installer program.

• • • • • •
Note: For Windows Server 2016, if not installed, the .NET Framework 3.5 must
be installed.

• • • • • •
Important: If you have already a Studio server installed from a previous
version, make sure that the physical path is different, and copy the
ConfigOverride folder (and content) from the 2016.x or 2017.x
installation in the root folder of the 2018.1 Studio server.

The following lists the prerequisites that are validated during the Studio Server
installation process:
• Windows Server 2016 Standard edition (64-bit) with IIS 10 installed.
- See “Configuring IIS 10 with the Recommended Features” on page C-2
- ASP.NET 4.5
- Common HTTP Features->Static Content = "On"
• Microsoft. NET 4.6.1 and higher
• Microsoft Visual C++ 2010 SP1 (x64) Redistributable Package (will be installed if
not on the machine and the user chooses to install)
• Microsoft Visual C++ 2012 Update 4 (x64) Redistributable Package (will be
installed if not on the machine and the user chooses to install)
• Microsoft Visual C++ 2013 Update 2 (x64) Redistributable Package (will be
installed if not on the machine and the user chooses to install)
• Microsoft Visual C++ 2015 Update (x64) Redistributable Package (will be installed
if not on the machine and the user chooses to install)
• Database client dependent on Studio Database; either:

6-4 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Installing Studio Server 2018

• Oracle Client 12.2.0.1 (with Administrator option).

• SQL Server 2016:
- Microsoft ODBC Driver 13 for SQL Server.
- Microsoft Command Lines Utilities 13 for SQL Server.
The components can be downloaded from the following link:
SQL Server 2016:
https://www.microsoft.com/en-us/download/details.aspx?id=54279
For Oracle - the ORACLE_HOME system variable must be set properly and the
PATH system variable must have $ORACLE_HOME/bin as the first entry. If you
are installing a new Oracle client, you need to reboot your server after the Oracle
installation is complete for the new settings to take effect.
For SQL Server 2016, - Ensure that the following path is part of the environment
variable:
C:\Program Files\Microsoft SQL Server\Client
SDK\ODBC\130\Tools\Binn

Studio Server 6-5

Schlumberger Private - Customer Use

Installing Studio Server 2018

 To Install Studio Server from the Studio Techlog installer

1 Double-click Studio_2018.exe on the Techlog DVD.
The Select Studio Component panel displays.

Fig. 6-5 Select Studio Component Panel

• • • • • •
Note: If you click Documentation, you can view the available release
documents found in the Documentation folder on the Techlog DVD.

2 Select Studio Server 2018.

The License Terms & Conditions panel displays.
3 Read the license agreement, select I accept the terms in the License
Agreement, and then click Next.
The Prerequisite check panel displays.

6-6 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Installing Studio Server 2018

Fig. 6-6 Prerequisite check Panel

A check is done to make sure all the prerequisites meet the recommended
requirements for a successful installation. The prerequisite check is done for
the required Operating System, the required versions of Microsoft .NET
Framework and Microsoft Visual C++ Runtime, and the correct configuration of
Internet Information Services (IIS).
During the prerequisite check, a prerequisite is verified by one of the following:

• - Meets the requirement

• - Warning

• - Error

• • • • • •
Note: During the prerequisite check, if any prerequisite is identified as being
different than what is recommended, but will not cause the installation to
fail, a warning will display and you will still be able to proceed with the
installation. However, if an error displays for a prerequisite, you will not be
Studio Server 6-7

Schlumberger Private - Customer Use

Installing Studio Server 2018

able to proceed with the installation. You can hover over either a warning
icon or an error icon to display a tooltip, which gives you information
about the warning or error condition.

• • • • • •
Note: If the installed .NET version is older than the required version, an error
displays during the prerequisite check, and you cannot proceed with the
installation. We recommend that you install the required .NET version,
which is available in the installation package.

4 If the requirements for the prerequisites have been met, click Next.
The Studio Techlog Server options panel displays.
5 Do the following:
a. Enter the name of the website to be created.
b. Enter the port number to be used.
c. Enter the folder location for the log files.

• • • • • •
Important: Studio Server is installed on a specific port (default=50231) on the
web server. The port number is incremented if the default port is
already in use. For users to access this server, this port must be
added to the Firewall Inbound/Outbound Exception Rules on the
web server in accordance with your security constraints. Failure to
do so will render your Studio Server inaccessible to clients.

6 Click Next.
The Install Studio Techlog Server to panel displays.
7 Select the location where you want to install Studio Server and click Next.
The Database connection information panel displays.
8 Do the following:
a. In the Provider: field, enter the type of database (Oracle or SQL Server) to
be connected.
b. In the Host: field, enter the host name or the IP address of the database
host.
c. In the Port: field, enter the database port number.
d. In the Database name: field, enter the name of the instance.
9 Click Next.
The Database Client Prerequisite check panel displays. A check is done for the
existence of either an Oracle or SQL Server Client.
The database client prerequisite is related to the database selected on the previous
page.

6-8 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Installing Studio Server 2018

Studio Server supports SQL Server 2016, therefore the prerequisites will only check
for the presence of SQL Server 2016.
If this is not the case, an error is shown and you must manually install SQL Server
2016.
10 Click Next.
The Ready to install Studio Techlog Server 2018 panel displays.
11 Click Install.
12 When the installation is finished, a link to Studio Server displays. You can click
this link to verify the Server is accessible.
This page shows various pieces of information on product versions and other
version numbers for Studio Server, as well as important information for the
Oracle/SQL Server Database that can be used for maintenance and monitoring
purposes.
This includes:
• Database — The database for which the corresponding tablespace/file group
listed is for (SQL Server)
• Tablespace/File Group — Name of the tablespace (Oracle) or file group (SQL
Server) being used
• Current Size (GB) — Current size (in GB) of the tablespace/file group
• Max Size (GB) — Maximum size (in GB) of the tablespace/file group
• Free Space (GB) — The amount of the free space (in GB) in a tablespace/file
group
• % Free — The percentage of the free space in a tablespace/file group
• Auto Extend — Indicates if the tablespace/file group is auto extensible
• Data Files — Data files constituting the storage for a tablespace/file group (file
names only)

13 Click Close.

Studio Server 6-9

Schlumberger Private - Customer Use

Installing Studio Server 2018

Studio Service Account

In Studio Manager, the installation of Studio Database supporting Techlog requires
providing account information for the “Studio Service Account name” and “Studio
Service Account password”. This database level account is created during the Studio
Database installation and is the account that is used by Studio Server to connect to
and communicate with Studio Database. The default account name for this is
STUDIO_SERVICE. If this account is deleted or Studio Server is unable to connect to
the database using this account, all Studio functionality will no longer be accessible
from Studio Manager and Techlog.
As a good security practice, Administrators will be required to eventually change the
password of the different accounts used in the system. The following workflow
explains the process to change the STUDIO_SERVICE account password once it
has been changed at the database level.

 To Update the Password for the STUDIO_SERVICE Account

1 Using any text editor, open the StudioSettings.Techlog.json file located in
the <Folder Studio Server is installed to >\ConfigOverride.
2 For the DatabaseUserID setting, do the following:
a. For the value, type studio_service.

• • • • • •
Note: Since the STUDIO_SERVICE account is the default account, if you
defined a different Studio Service account name, then use that account
name instead of STUDIO_SERVICE.

b. Keep the isSecure value as true.

3 For the DatabasePassword setting, do the following:
a. For the value, type the new password.
b. Keep the isSecure value as true.
4 Save the file and exit the text editor.
5 Restart your web server. Once the web server is restarted, the file will change
and the DatabaseUserID and DatabasePassword will be encrypted.

6-10 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Studio Server Config File

Studio Server Config File

The file shown defines the parameters that control the Studio Server Settings. The
file is called StudioSettings.Techlog.json and is located in the <Folder
Studio Server is installed to
>\Config\StudioSettings.Techlog.json.file. This file should never be
updated; only the file, which is discussed below, should be updated.
To update Studio Server Parameters in the above referenced
StudioSettings.Techlog.json file, you need to override this file with the
parameters in the StudioSettings.Techlog.json file located in the <Folder
Studio Server in located in the>\ConfigOverride\
StudioSettings.Techlog.json file, while IIS is shut down. Add the
parameters from the following list of parameters to the
StudioSettings.Techlog.json in the ConfigOverride folder, save the file, and
then, restart IIS.

• • • • • •
Important: Making changes to the StudioSettings.Techlog.json file while
IIS is running may cause the server to hang or crash.

Default Settings of the Override config file

[
{
"Name": "DatabaseUserId",
"Value":
"R8W3emIHEaQiJrZ3xU/4eIPskW2woV+2uwUwffc/rxMVRDRjQ2r/SFeEqvc33G7kY1qY
OdyV/WfXLKy4a2RrJw==",
"IsSecure": true
},
{
"Name": "DatabasePassword",
"Value":
"7jJDUGOLRbOZsYY34J63UlV2dRNptG28N6eJoINO977U2xL8+0MD2qJ8Y+xf3LP2LVK
m83Nq2HIUh1dZSZhJPA==",
"IsSecure": true
}

Studio Server 6-11

Schlumberger Private - Customer Use

Installing Studio Server 2018

6-12 Studio Techlog Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

7 Studio Database

In This Chapter

Introduction............................................................................................... 7-2
Audience ............................................................................................. 7-2
Studio Database ......................................................................................... 7-3
Compatibility .............................................................................................. 7-4
Installing the Database on a Fresh Server Installation ................................... 7-5
Upgrading Studio Database from 2016.x and 2017.x to 2018.1 ...................... 7-8
Upgrading Repositories from 2016.x and 2017.x to 2018.1 ...........................7-11
Setting Default Studio Validation Rules........................................................7-13
Setting Default Studio Validation Rules........................................................7-13
Prerequisites .......................................................................................7-13
Running the Windows PowerShell Script for Database Configuration .......7-14
Running the ValidationManager Script ...................................................7-14
List of Validation Rules.........................................................................7-17
Validation Manager Report .........................................................................7-21

Studio Database 7-1

Schlumberger Private - Customer Use

Introduction

Introduction
Studio Database includes all the database schema required to cover the data model
for the different data types covered by Studio, the database functions, and the
procedures associated with the schema. This chapter provides the different
workflows to configure the Studio Database and the compatibility between the
different versions of Studio Database and Studio Manager.

Audience This chapter is intended for the data administrator or system administrator who
installs and maintains the Studio Database in a system environment.

7-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

Studio Database
The workflows for installing and configuring the Oracle and SQL Server databases
are shown in this section. For information on configuring Studio Database using
Studio Manager, see the Studio Manager online Help. The following workflow
describes the steps to install or upgrade/update your Studio Database.

Studio Database 7-3

Schlumberger Private - Customer Use

Compatibility

Compatibility
The following chart shows which versions of Studio Manager/Studio Server and
Studio Database repositories are compatible.
Table 7-1 Version Compatibility Matrix

Studio
Database 2015.1 2015.2 2015.3 2016.1 2016.2 2017.1 2017.2 2018.2

Studio Manager/
Studio Server
2015.2 Full No No No No No No No
2015.3 Update Full No No No No No No
2015.4 Update Update Full No No No No No
2015.5 Update Update Full No No No No No

2015.6 Update Update Full No No No No No

2015.7 Update Update Full No No No No No

2016.1 Upgrade Upgrade Upgrade Full No No No No

2016.2 Upgrade Upgrade Upgrade Update Full No No No

2017.1 Upgrade Upgrade Upgrade Upgrade Upgrade Full No No
2017.2 Upgrade Upgrade Upgrade Upgrade Upgrade Update Full No
2018.1 No No No Upgrade Upgrade Upgrade Upgrade Full
Full Fully Supported
No Not Supported
Upgrade Using Database Configurator to upgrade your Database (Major
Release)
Update Using Database Configurator to update your Database (Minor
Release)

7-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

Installing the Database on a Fresh Server Installation

Prerequisites • Studio server installed

• Studio manager installed

Procedure 1 Launch Studio Manager and click Open Settings page .

2 In the Connections dialog box > Techlog window, add a new item.
3 Enter a server name and add the full URL of the server.

4 Once the server is listed, use the “test connection” . At this step, the
connection test fails as there is not database installed.

5 Click Connect and get database information to display the Connect

to database dialog box.
6 Enter the user name and password for your System Account and click OK.

If the connection is successful, the installation of database action is available in the

connection window.

7 Use to carry on the process.

Studio Database 7-5

Schlumberger Private - Customer Use

Installing the Database on a Fresh Server Installation

For Oracle database, the service account and the studio_sys are used with their
associated passwords.

• • • • • •
Note: The Backup/Recover folder depends on the installation of Oracle on Linux.

8 For SQL database, the SuperAdmin account is user-defined during the SQL
database creation. Studio_service and the associated passwords are used the
same way as for Oracle.

9 Provide all SQL server database locations which have been set up during SQL
Database creation.
It can take some time to install the database. When it is done, the following
message displays:

7-6 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

Server information is updated in the same Connections dialog box and it is not
possible to install the database. Only the uninstallation is available.
Application log confirms information on the newly installed database and the logs
are available from this window.

Studio Database 7-7

Schlumberger Private - Customer Use

Upgrading Studio Database from 2016.x and 2017.x to 2018.1

Upgrading Studio Database from 2016.x and 2017.x to 2018.1

If you have a Studio Database 2016.x or 2017.x installed, then you will need to
upgrade your database using Studio Manager 2018. The last step to the upgrade is
the migration of 2016 or 2017 repositories to 2018 repositories.

• • • • • •
Note: For the two Oracle database administrator user accounts, SYSTEM and
SYS, only the SYSTEM user can perform the database upgrade.

 To Upgrade Studio Database from 2016.x or 2017.x to 2018.1

After Studio Server 2018.1 has been installed, you will need to create a new
database connection in Studio Manager.

1 Launch Studio Manager and click Open Settings page .

2 In the Connections dialog box, select Click here to add new item, enter
the Name of the connection and the Studio Server URL that was created
during the installation, and then click OK.

• • • • • •
Note: If you try to log in to this server without upgrading the database, you will
receive the following error message: “Server is incompatible with
database. Use database configurator to perform required ‘Upgrade’
operation.”

• • • • • •
Note: IIS needs to be restarted after a database upgrade, especially if the
database credentials are changed.

7-8 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

3 After you have created the connection, click to return to the newly
created connection in the Connections dialog box and click Connect and get

database information to display the Connect to database dialog box.

4 Enter the user name and password for your System Account and click OK.
If the connection is successful, Connect and get database

information changes and Upgrade database displays in the

menu of actions that are available for the selected database and the version of
the database that displays is 2016.X.0.0 or 2017.x.0.0.

5 Click Upgrade database to upgrade the database to 2018.1.

The Upgrade database dialog box displays, showing a summary of the
features that will be available in the upgrade.
6 For an Oracle database, do the following:
a. In the Studio Dictionary password: field, enter the password for the new
2018 Studio Dictionary.
b. In the Studio Service Account name: field, enter the 2016/2017 Studio
Service Account name.
c. In the Studio Service Account password: field, enter the 2016/2017
Studio Service Account password.

• • • • • •
Note: These Studio Service Account values must match the same values used for
the 2016/2017 Studio Service Account.

• • • • • •
Note: These Studio Service Account values are explained in Appendix D.

7 For a SQL Server database, do the following:

a. In the Studio Service Account name: field, enter the 2016/2017 Studio
Service Account name.

Studio Database 7-9

Schlumberger Private - Customer Use

Upgrading Studio Database from 2016.x and 2017.x to 2018.1

8 In the Studio Service Account password: field, enter the 2016/2017 Studio
Service Account password.

• • • • • •
Note: These Studio Service Account values must match the same values used for
the 2016/2017 Studio Service Account.

9 Click OK to start the database upgrade.

a. If the upgrade is successful, the connection information changes and the
version of the database that displays is 2018.1.0.0.
b. If the upgrade is unsuccessful, look at the log files to determine the cause of
the upgrade not completing successfully and then, try again to upgrade the
database to 2018.1.

7-10 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

Upgrading Repositories from 2016.x and 2017.x to 2018.1

After the database has been upgraded to 2017.2, if you have 2015.x or 2016.x
repositories and want to use them in 2017, you will need to upgrade them to 2017.2.
All the repositories are upgraded at once.

 To Upgrade Studio Database Repositories from 2015.x or 2016.x to

2017.2
1 After you see the message confirming the Studio Database upgrade was
successful, click OK to accept the changes and close the Settings dialog box.
The Connect dialog box displays.
2 Do the following:
a. In the Connection: drop-down list, select the database that was upgraded
to 2017.2.
b. In the Repository: drop-down list, select a repository in that database.
c. Click CONNECT.
The App Gallery displays.

3 Click Repositories.
The Repositories app displays, showing the available 2015.x or 2016.x
repositories (in italics) and the 2017 repositories.

4 Click a 2015.x or 2016.x repository to display Upgrade repositories .

Studio Database 7-11

Schlumberger Private - Customer Use

Upgrading Repositories from 2016.x and 2017.x to 2018.1

• • • • • •
Note: You only need to select one repository to upgrade all the 2015.x or 2016.x
repositories.

5 Click Upgrade repositories .

The Upgrade repositories dialog box displays, showing a list of the

repositories that will be upgraded.
6 Click UPGRADE to start the repository upgrade.
After the repository upgrade is complete, you can view the log files for each
repository. The log file of any repository that failed to upgrade will show “Error”
instead of “Information” in the log data.
If there are any repositories that failed to upgrade, fix the issues that caused
the upgrade failures and then, try again to upgrade the repositories that failed
to upgrade. The upgrade process will only run for the repositories that are still
showing 2015.x or 2016.x in the Version column.

7-12 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

Setting Default Studio Validation Rules

Studio Techlog provides a set of validation rules to ensure data integrity, and an
enterprise quality data management, especially in the context of cross-domain
(Petrel*/Techlog) platform workflows. However, for users collaborating only with
Techlog, some rules are not required.
Studio 2016 provides the ability for the Studio administrator to customize a set of
Studio validation rules for Techlog data. The customization is available per each
database instance by turning on and off the rules.
However, the customization has to be planned carefully prior to deploying Studio.
The data sent with the customized validation rules will have less validity against
cross-domain (Petrel/Techlog) platform collaboration workflows. While the rules are
customized, all the repositories in the same instance should be used only for the
purpose of Techlog collaboration workflows. Then, the data will need to be validated
with the default set of Studio validation rules when they are used for Petrel/Techlog
collaboration workflows.
The configuration is done by running a Windows PowerShell® script. The script is
available on the Techlog DVD and in the DBScripts folder, found in the Studio
Manager installation folder, for example, C:\Program
Files\Schlumberger\Studio Manager 2017\Plugins\Techlog\DBScripts.

• • • • • •
Note: If the validation rules need to be updated, changes made through the
ValidationManager script should be done first and then, the Studio for
Techlog repositories should be created.

• • • • • •
Note: The script is only available through the Studio Manager installation. It is
not available through the Studio Server installation.

Prerequisites Before running the script, you need to confirm that you have the correct Windows
PowerShell version installed and the correct settings set. Make sure you have the
following:
• Windows PowerShell version 3.0 or higher
• Windows PowerShell execution policy is RemoteSigned
• The administrator is added as SuperAdmin or Admin into the Studio Techlog
database
• Access to Studio Server
The default for the Windows PowerShell settings for Windows Server 2012 R2 is
version 4.0 and for Windows Server 2016 is version 5.0 and the execution policy is
RemoteSigned. Windows 7 provides Windows PowerShell 2.0 by default.To obtain
PowerShell 3.0 or higher, you can install Windows Management Framework 3.0 or
higher. The Windows Management Framework 3.0 download can be found at the
following link:

Studio Database 7-13

Schlumberger Private - Customer Use

Setting Default Studio Validation Rules

https://www.microsoft.com/en-us/download/details.aspx?id=34595

Running the To run the Windows PowerShell script for database configuation, do the following:
Windows
1 Enter Windows PowerShell in the Search box on the Start menu.
PowerShell Script
for Database 2 Type $PSVersionTable.PSVersion to see the Windows PowerShell
Configuration version.
3 Make sure the number in the Major column is 3 or higher.

4 Type Get-ExecutionPolicy to see the Windows PowerShell execution

policy. By default, Windows Server 2012 R2 sets the execution policy as
RemoteSigned.

5 In Step 4, if the execution policy is Restricted, type Set-

ExecutionPolicy RemoteSigned, and then type Y to confirm the change.

6 Type Get-ExecutionPolicy again to return RemoteSigned, which

verifies the change.

Running the Make sure your login account has Studio administrator rights (SuperAdmin or
ValidationManager Admin). The ValidationManager script, a file named ValidationManager.ps1, is
Script available on the Techlog DVD and in the DBScripts folder, found in the Studio
Manager installation folder, for example, C:\Program
Files\Schlumberger\Studio Manager 2017\Plugins\Techlog\DBScripts.

7-14 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

• • • • • •
Note: The script is only available through the Studio Manager installation. It is
not available through the Studio Server installation.

To run the ValidationManager script, do the following:

1 Type .\ValidationManager.ps1 and then, press Enter.

2 In ServerUri:, type the Studio Server path and the API path, making sure
that you use techlog/2018 as the API path, for example, http://
localhost:50231/techlog/2018.

Studio Database 7-15

Schlumberger Private - Customer Use

Setting Default Studio Validation Rules

The list of rules is shown below.

3 Type the validation rule number to turn the rule on or off and then, press
Enter.
Enter validation rule number to toggle on/off displays.
4 Press Enter to confirm the change you made and the script finishes with the
change.
5 If you type QUIT, the script finishes without any change.
6 Run the script again.
The validation rule that was turned off now becomes red.

7-16 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

List of Validation The available validation rules for the customization are shown in the following table.
Rules The long messages are shown in the Techlog Transfer status window when the data
are invalid. They describe what users need to do to fix the invalid data. The Default
Setting On means the rule is applied when the data are sent to Studio by default.
Table 7-2 Validation Rules

Number Type Short message Long Message On/Off

1 Warning Attempted to send an object that The {2} {1}{6} was previously On
has been previously deleted. deleted from the Repository. Please
ensure that you really intend to add
this {2} back to the Repository.
2 Error Wellhead Location must be correctly Well {1} has Latitude/Longitude On
defined. values but incorrectly defined units.
Units must be dega or an alias of
dega. If in DMS format unit can also
be null.
3 Error Well must be spatially referenced Well {1} must have a CRS and On
(Wellhead, CRS). either valid XY or LAT/LON to be
sent.
4 Error Elevation of the well must have a Well {1} does not have a valid unit On
defined unit. for Elevation. Must be an unit
compatible with the length
dimension (M, FT).

5 Error Total depth of the well must have a Well {1} has values for Total_depth, On
defined unit. but has invalid units.Must be an unit
compatible with the length
dimension (M, FT).

6 Error Water depth of the well must have a Well {1} has values for On
defined unit. Water_depth, but has invalid units.
Must be an unit compatible with the
length dimension (M, FT).
7 Error Well reference must be correctly Well {1} must have a CRS that On
defined (CRS). exists in the CRS Studio catalog and
correctly defined.
8 Error Wellhead location must have Wellhead of Well {1} must be On
correctly defined (X,Y) units. correctly defined. X,Y properties
need to be correctly defined and
with the right units.

Studio Database 7-17

Schlumberger Private - Customer Use

Setting Default Studio Validation Rules

Number Type Short message Long Message On/Off

9 Warning Azimuth reference is not specified The 'Azimuth reference' for the On
for an Index dataset. dataset called '{1}' of the Well {3}
is not specified. This will cause
issues for further collaboration with
Petrel. Please make sure that the
'Azimuth reference' is correctly
defined if you want to share data
with Petrel.
10 Error Azimuth reference is not specified The 'Azimuth reference' property for Off
for an Index dataset. the dataset called '{0}' of the Well
{0} is not specified. This will cause
issues for further collaboration with
Petrel. Please ensure that the
'Azimuth reference' property is
correctly defined if you want to
share data with Petrel.
11 Warning A reference to a non-existent Variable {1} for Dataset {3} and Off
Palette was detected. Well {4} has a reference to Palette
{Palette} that could not be found.
12 Error Variable must have a defined unit. Variable {1} for Dataset {3} and On
Well {4} has undefined units (do
not exist in Studio).
13 Warning Variable has empty unit. Variable {1} for Dataset {3} and On
Well {4} has undefined units (blank
units).
14 Warning Variable has a family attribute that Variable {1} from Dataset {3} from On
does not exists in the Studio Well {4} has a family that is not
repository defined in the Studio Repository.
You should send your Project
families database to the Repository.
15 Error Reference variable must not contain Dataset {1} for Well {3} has an On
missing values invalid reference variable (-9999
value).
16 Reference Reference values should be strictly Reference variable {5} for Dataset On
values increasing or decreasing. {1} and Well {3} is invalid (values
should be should be strictly increasing or
strictly decreasing).
increasing
or
decreasin
g
17 Error Reference values should be strictly Reference variable {0} for Dataset Off
increasing. {0} and Well {0} is invalid (values
should be strictly increasing).
18 Error Reference variables must not have Reference variable '{3}' cannot have On
Format = alphanumeric. data in the alphanumeric format.

7-18 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

Number Type Short message Long Message On/Off

19 Error Wellhead XYs must be correctly The {0} property for Well '{3}', is On
defined. not a valid number.
20 Warning Well does not have an elevation Well '{3}' does not have an On
datum. Elevation_datum defined. This will
cause issues for further
collaboration with Petrel. Please
define an elevation datum if you
want to share data with Petrel.
21 Error UWI must be defined. Well '{3}' must have a UWI. Off
22 Error Elevation of the well must have a Well '{3}' does not have a value for On
correct value. elevation or it is an invalid number.
23 Error Total depth of the well must have a The '{0}' property for well '{3}' does On
correct value. not appear to be a valid number.
24 Error Water depth of the well must have a The '{0}' property for well '{3}' does On
correct value. not appear to be a valid number.
25 Error Wellhead Latitude must be correctly The {0} for Well {3} are not valid On
defined. numbers or do not fall within the
acceptable ranges.
26 Error Wellhead Longitude must be The {0} for Well {3} are not valid On
correctly defined. numbers or do not fall within the
acceptable ranges.
27 Warning SPUD_date of a well is not correctly The {0} for Well '{3}' is invalid or On
defined. not recognised (format=MM/DD/
YYYY). This will cause issues for
further collaboration with Petrel.
Please define the {0} with the
correct format if you want to share
data with Petrel.
28 Warning Completion_date of a well is not The {0} for Well '{3}' is invalid or On
correctly defined. not recognised (format=MM/DD/
YYYY). This will cause issues for
further collaboration with Petrel.
Please define the {0} with the
correct format if you want to share
data with Petrel.
29 Error Data object has incorrect Quality The {2} '{1}' has undefined Quality On
Attribute assigned. Attribute assigned. Attribute Type:
'{AttributeType}' Attribute Value:
'{AttributeValue}'.
{AttributeCompletenessConflict}.

Studio Database 7-19

Schlumberger Private - Customer Use

Setting Default Studio Validation Rules

Number Type Short message Long Message On/Off

30 Error Attempted to update an object that The {2} '{1}' is marked as On
has been previously marked as complete.
complete.
31 Warning Attempted to update an object that The {2} '{1}' is marked as On
has been previously marked as complete.
complete.

7-20 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Upgrading Repositories from 2016.x and 2017.x to 2018.1

Validation Manager Report

The Validation Manager Report option allows the Studio Admin to view the on/off
status of all validation rules per repository.
To run the Validation Manager Report, do the following:
1 Run the Validation Manager script via Windows PowerShell, using the following
command. For details on the prerequisites needed to run the script, see
“Setting Default Studio Validation Rules” on page 7-13.

2 In ServerUri: enter the Studio Server URL for which you want to obtain the
validation report (see the following example).

3 In OutputFile: enter the output file location and file name. The output file
can be either a .txt or .csv file type (see the following example).

4 If the report run is completed without errors, a group of validation rules listed
by repository in the PowerShell output displays and the report file is created in
the file location that you designated (see the following example).

Studio Database 7-21

Schlumberger Private - Customer Use

Validation Manager Report

7-22 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 8 Uninstallation

In This Chapter

Introduction............................................................................................... 8-2
Audience ............................................................................................. 8-2
Uninstalling Studio Manager ........................................................................ 8-3
Uninstalling Studio Server ........................................................................... 8-4

Uninstallation 8-1

Schlumberger Private - Customer Use

Introduction

Introduction
This chapter describes the different workflows used to uninstall the Studio products.

Audience This chapter is intended for the administrator who needs to uninstall any of the
different Studio products.

8-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Uninstalling Studio Manager

Uninstalling Studio Manager

This section covers the uninstallation process for Studio Manager. You can uninstall
Studio Manager from the Control Panel. The plug-ins that were installed with Studio
Manager are uninstalled when Studio Manager is uninstalled.

• • • • • •
Note: Before uninstalling Studio Manager, make sure that it is not open.

 To Uninstall Studio Manager from the Control Panel

1 Click Start > Control Panel > Programs > Programs and Features >
Uninstall or change a program.
2 On the list of currently installed programs, highlight Studio Manager 2018
and click Uninstall at the top of the window.

• • • • • •
Note: A User Account Control message might display. Click Yes to continue.

The Installed Plug-ins and Extensions panel displays.

3 Click Next.
The Ready to uninstall Studio Manager 2018 panel displays.
4 Click Uninstall.
5 When the uninstallation is complete, click Close.

Uninstallation 8-3

Schlumberger Private - Customer Use

Uninstalling Studio Server

Uninstalling Studio Server

This section covers the uninstallation process for Studio Server. You can uninstall
Studio Server from the Control Panel.

 To Uninstall Studio Server from the Control Panel

1 Click Start > Control Panel > Programs > Programs and Features >
Uninstall or change a program.
2 On the list of currently installed programs, highlight Studio Server 2018 and
click Uninstall at the top of the window.

• • • • • •
Note: A User Account Control message might display. Click Yes to continue.

The Ready to uninstall Studio Server 2018 panel displays.

3 Click Uninstall.
4 When the uninstallation is complete, click Close.

8-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 A Licensing Issues, Best Practices and
Solutions
This appendix provides information about issues, best practices, and solutions
related to licensing.

Licensing Issues Studio Manager does not detect license dongle after removal and
and Solutions reinsertion or after the computer wakes from sleep or hibernation
Do the following:
1 As a prerequisite, ensure that this software is installed on your system:
a. Schlumberger Licensing 2018 tool
b. Latest CodeMeter driver
c. Updated dongle firmware
2 Start the Schlumberger Licensing tool.
3 Stop any license server that is running.
4 In Windows, click Start automatically.
5 Click Apply.
6 In the Schlumberger Licensing tool, click File > Advanced options.
7 Make sure that Install CodeMeter detector is enabled.

8 Click OK. A service is installed that detects when a dongle is removed or

inserted.
9 Restart the License Server.
10 Start Studio Manager.

• • • • • •
Note: If you switch between wireless and cable-based connections while Studio
Manager is running or after hibernation, a reconnection with the license
server may fail because of a network conflict.

Studio Manager disconnects from the license server or loses the license on
a regular basis.
Do the following:
1 Upgrade CodeMeter to the latest version (6.60).
2 Swap a new Studio Manager dongle.
3 Update the Studio Manager dongle’s Certified Time.

Licensing Issues, Best Practices and Solutions A-1

Schlumberger Private - Customer Use

 4 Use a different USB port.

A-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

Best Practices for Checking out a license is a frequent task. When many users are running Studio
Setting Up a Manager, the time to connect to a license server and choose the correct license is
License Server significant. To minimize nonproductive time, consider these tips:
• Always make sure that you are using the recommended/latest licensing software.
This includes the Schlumberger licensing utility and CodeMeter driver. For
information about the licensing software, see other information in this guide and
the Schlumberger Licensing User Guide.
• Be sure that you are using the most recent type of dongle. To check, look at the
ID number imprinted on the dongle. Up-to-date dongles have IDs that begin with
2-xxxxxx. If the ID begins with 1-xxxxxx, request a new dongle from your account
manager. The new dongle type is preferred because it delivers performance
improvements.
• Avoid connecting to multiple license servers, if possible. Adding multiple colon
separated license servers to the license selection reads the available licenses from
all connected servers and linearly increases the time to populate the license UI
based on the number of license features served by each server. Using a license
quorum is the exception. When using a quorum, the license selection should
include all three servers separated by a comma, for example,
27000@quorumServer1, 27000@quorumServer2, 27000@quorumServer3.
• When possible, set a Favorite license when starting Studio Manager.
• Always use a static port, for example, [email protected], which optimizes the
communication with the license system.
• Setting TCP_NODELAY. FLEX sends data between the client and server by using
TCP/IP packets. By default, the TCP/IP stack buffers small packets (< 147 bytes in
FLEX), known as Nagle´s algorithm, to coalesce a large number of packets before
sending them across the network. This ACK delay (200 ms) results in artificially
high latency times for small packets (such as most FLEX licensing operations). For
this reason, we recommend disabling the Nagle algorithm by defining the
TCP_NODELAY system setting as a license server environment variable. This
overrides the behavior and reduces the licensing wait period. For more
information, refer to the Flexera documentation.
• Use one license file only. Combining all licenses into one physical file improves
communication with the license server by eliminating the need to open and close
multiple files to read license information.
Validate through the codemeter control center that the certified time is close to
the current time. Navigate to Codemeter control center > File >
Webadmin > Content > CmContainer. If necessary, update the certified
time.

Licensing Issues, Best Practices and Solutions A-3

Schlumberger Private - Customer Use

A-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 B Database Configuration

In This Appendix

Configuring Oracle...................................................................................... B-2

Oracle 12.2.0.1 .................................................................................... B-2
Oracle Configuration ............................................................................. B-3
Database Parameters Using Oracle 12.2.0.1 ........................................... B-7
Configuring SQL Server 2016....................................................................... B-8
Introduction ......................................................................................... B-8
Prerequisites ........................................................................................ B-8
Windows Server Customizations ............................................................ B-8
SQL Server 2016 Standard .................................................................... B-9
Configuring SQL Server 2016................................................................. B-8

Database Configuration B-1

Schlumberger Private - Customer Use

Configuring Oracle

Configuring Oracle

Introduction This section explains how to configure your system to install Studio Database
supporting Techlog in an Oracle environment. Studio Database provides the back-
end infrastructure that allows Techlog users to collaborate and work with very large
amounts of data in a single location, regardless of the data source.

Oracle 12.2.0.1 If you are installing Oracle 12.2.0.1 as a fresh installation in your environment, you
should follow this basic workflow:
1 Install Oracle 12.2.0.1 without creating a database.
2 Create an Oracle database using the parameters and tablespace
recommendations noted in “Storage Configuration” on page B-4.

• • • • • •
Note: For complete details on installing Oracle, refer to the documentation
resources provided with your Oracle software.

Oracle Environment After you have installed Oracle, for the successful installation of Studio Database,
Variables you must set the following Oracle environment variables:
• ORACLE_HOME
• TNS_ADMIN
• PATH
• LD_LIBRARY_PATH
These variables must be set according to Oracle installation procedures so the
database server installation process can access your Oracle home directory and your
TNS configuration.

Disconnecting Make sure that no Database Administrator (DBA) activity, for example, database
Database Connections backup, is conducted at the installation time. You can check the Oracle SYS account
view, V$SESSION, to verify that all users and applications are disconnected. Other
than the connection for the session you use to query V$SESSION, V$SESSION
should show only database background sessions (identified by AUDSID=0 and a
USERNAME of blank).

B-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring Oracle

Oracle
Configuration

Key Configuration Data This section presents a high-level view of the computers involved in local and
Items remote configurations, and correlates key data items from the configuration
program to the physical installation environment.
When configuring, you must specify the following information in the configuration
program:
• Oracle Home — Home directory where the Oracle software is installed.
• TNS Alias — The entry in the tnsnames.ora file that enables the Studio to
connect to the Oracle database. The location of the tnsnames.ora file is
indicated by the TNS Admin directory.

Memory For a default instance creation, it is usually recommended to enable Automatic

Memory Management. Automatic Memory Management can be done via Database
Configuration Assistant (DBCA) during the creation of the instance or by setting the
MEMORY_TARGET in the Initialization Parameter file (initORACLE_SID.ora)
before starting the instance for the first time. For example, if you have 64 GB of OS
RAM, you can set the Oracle MEMORY_TARGET to be 57 GB.
After the system has been tested under its normal workload, then you may need to
change the memory allocation manually. For more information about manual
memory management, click the following link:
Manual Memory Management Reference
For more information about setting Automatic Memory Management via DBCA/
Initialization Parameter file, click the following links:
DBCA Option
Initialization Parameter Option

Tablespaces In addition to the default tablespaces that come with your Oracle installation, Studio
Database requires you to create a tablespace called STUDIO_TABLE and a
temporary tablespace called TEMP.

• • • • • •
Note: You may not need to create the temporary tablespace, TEMP, as it may
already exist.

Database Maintenance When you perform maintenance on the database, access to the database and
tablespace might be blocked during the maintenance. During this period, the home
page for the server might be blank or unresponsive. This is normal behavior, and the
server will be responsive when the database becomes available again.

Database Configuration B-3

Schlumberger Private - Customer Use

Configuring Oracle

Storage Configuration The following tablespace configurations are recommended for Studio Database.
Tablespace Configured with Unlimited MAXSIZE
The tablespace example shown below will create one data file and extend it with an
unlimited maxsize for the file. This means the tablespace will grow until it has
reached the maximum size of disk storage available.
Table B-1 Tablespace Configurationswith Unlimited Maxsize

Tablespace Parameter Value

STUDIO_TABLE Size 4000 MB
Autoextend ON
Autoextend Next Size 40 MB
Autoextend Maxsize UNLIMITED
Autoextend Management LOCAL (Autoallocate)
Autoextend Blocksize 8 KB
Segment Space Management AUTO
TEMP Size 500 MB
Autoextend ON
Autoextend Next Size 640 KB
Autoextend Max Size UNLIMITED
Autoextend Management UNIFORM SIZE 1 MB

To create these tablespaces, use the following SQL commands:

CREATE TABLESPACE STUDIO_TABLE DATAFILE '/oradata/
studio_table1.dbf' SIZE 4000M AUTOEXTEND ON NEXT 40M MAXSIZE
UNLIMITED LOGGING ONLINE EXTENT MANAGEMENT LOCAL AUTOALLOCATE
BLOCKSIZE 8K SEGMENT SPACE MANAGEMENT AUTO;
CREATE TEMPORARY TABLESPACE TEMP TEMPFILE '/oradata/
temp01.dbf' SIZE 500M AUTOEXTEND ON NEXT 640K MAXSIZE
UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
where oradata is the directory where you want to put the data files.
Tablespace Configured with Limited MAXSIZE
Another option is to create a tablespace where multiple data files are created when
AUTOEXTEND is turned off or on, but a MAXSIZE is limited (higher than the original
data file size). This gives you a larger number of data files, and may make it easier
to restore all the data files if a data file is corrupted. Also, a DBA can create the
exact number of data files needed for disk storage allocation (for example, 1 TB Disk
Storage = 20 Large Data File needed to be created).

B-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring Oracle

The following are examples of what the parameters for Small, Medium, and Large
Tablespace could start with.
Table B-2 Tablespace and Data File Sizes (Examples with MAXSIZE Limited)

Tablespace Size Data File Size AutoExtend on Next Maxsize

Small 4000 MB 40 MB 16000 MB
Medium 16000 MB 160 MB 32000 MB
Large 32000 MB 320 MB 48000 MB

To create the tablespaces, you can use the following SQL commands (ALTER
TABLESPACE SQL Statement needs to be used multiple times, depending on the
number of files that need to be created for disk storage allocated at the beginning of
tablespace creation):
CREATE TABLESPACE STUDIO_TABLE DATAFILE '/oradata/
studio_table1.dbf' SIZE 4000M AUTOEXTEND ON NEXT 40M MAXSIZE
16000M LOGGING ONLINE EXTENT MANAGEMENT LOCAL AUTOALLOCATE
BLOCKSIZE 8K SEGMENT SPACE MANAGEMENT AUTO;
ALTER TABLESPACE STUDIO_TABLE ADD DATAFILE '/oradata/
studio_table2.dbf' SIZE 4000M AUTOEXTEND ON NEXT 40M MAXSIZE
16000M;
Where oradata is the directory where you want to put the data files. To create the
Small, Medium, and Large tablespaces, change the SIZE, AUTOEXTEND ON NEXT,
and MAXSIZE parameters in the SQL command above to the respective parameters
in Table B-2.
Temporary Tablespace
The following are examples of the minimum size a DBA could start with. Typically, a
DBA would alter the temporary tablespace size based on how much the workload is
on the server over a certain period of time.
Table B-3 Temporary Tablespace and Data File Sizes

Temporary - Tablespace Size Data File Size AutoExtend on Next

Small 500 MB 640 MB
Medium 2000 MB 160 MB
Large 4000 MB 320 MB

To create the temporary tablespace, use the following SQL command:

CREATE TEMPORARY TABLESPACE TEMP TEMPFILE '/oradata/
temp01.dbf' SIZE 500M AUTOEXTEND ON NEXT 640K MAXSIZE
UNLIMITED EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;
For the Oracle documentation on Tablespace and Data File Management, click the
following links:
Tablespace Management
Temporary Tablespace Management
Data File Management

Database Configuration B-5

Schlumberger Private - Customer Use

Configuring Oracle

Network File System For purposes of repository backup and recovery, during Studio Database
Mounting configuration, you can specify a directory local to the Oracle server, or you can
Specifications mount an external network file system (NFS) directory.
Oracle requires these mount options to ensure that the volume is safe to use, as
incorrectly mounted NFS volumes can result in data corruption issues. In general,
the following conditions are required:
• The mount table can be read to check the mount options.
• The NFS mount is mounted with the "hard" option.
• The mount options include rsize>=32768 and wsize>=32768.

• • • • • •
Note: Studio Database has not been certified on Oracle hardware technologies
such as EXADATA or ASM mounts.

Privileges The privileged account used to install the database via the configurator needs to
have DBA privileges, as well as grant privileges to execute the dbms_lock package.
The following is an example of the commands used in creating a privileged account
(OraStudioAdmin):
create user OraStudioAdmin identified by sft;
grant dba to OraStudioAdmin;
grant execute on dbms_lock to OraStudioAdmin with grant
option;

Accounts The database standard accounts that are created during the installation of Studio
Database are the following: studio_sys, STUDIO DD 2018, and
studio_service. For more information about these accounts, see Appendix D.
Other database accounts, such as the ones created for repositories, are created by
Studio Manager after the database installation is completed.

B-6 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring Oracle

Database The Oracle parameters DB_SECUREFILE and COMPATIBLE must be set to

Parameters Using PREFERRED and at least 12.2.0.1, respectively.
Oracle 12.2.0.1

 To Verify the Parameters Values

1 Connect as SYSDBA.
2 Execute the SHOW PARAMETERS command, as follows:
show parameter db_securefile
Supported value for this parameter is PREFERRED
show parameter compatible
Recommended value for this parameter is at least 12.1.0.2

 To Change the Parameters Values

1 Connect as SYSDBA.
2 Execute the ALTER SYSTEM command, as follows:
ALTER SYSTEM SET DB_SECUREFILE = 'PREFERRED' scope=both;
Recommended value for this parameter is PREFERRED
ALTER SYSTEM SET COMPATIBLE = '12.1.0.2.0' scope=spfile;

Database Configuration B-7

Schlumberger Private - Customer Use

Configuring SQL Server 2016

Configuring SQL Server 2016

Introduction This section explains how to configure your system to install Studio Database in a
SQL Server environment. Studio Database provides the back-end infrastructure that
allows Techlog users to collaborate and work with very large amounts of data in a
single location, regardless of the data source.

Prerequisites Before installing Studio Database 2018.1 on a SQL Server database, you must
configure and complete the installation of a Windows Server 2016 or Windows
Server 2012 R2. Some configuration is required and recommended.
Administrators are responsible for monitoring performance relative to the operating
system database and repository. Performance recommendations are addressed in
“Performance Considerations” on page B-10. Review and configure as needed for
your hardware, software, and network environments. None of the performance
considerations are mandatory to use Studio.

Windows Server
Customizations

Windows Firewall The Windows Firewall must be configured properly to allow remote access to SQL
Server 2016. Ensure that the appropriate ports are open to enable remote access.
See the Microsoft rules documentation at http://go.microsoft.com/fwlink/
?LinkId=94001 for information about ports to open for each feature.

Performance To improve performance, customize the Windows server as follows:

Considerations
• Lock pages in memory
This setting can enhance performance by optimizing how data is loaded into
memory and used by the system. The Lock Pages in Memory Windows policy
option is disabled by default for servers dedicated to a single database instance. It
is recommended that the default value be disabled. For non-dedicated servers, for
example, servers with multiple database instances, or servers that have other
applications installed, Lock Pages in Memory can be enabled to prevent the
system from paging out SQL Server cached data from memory to disks during
periods of high memory requirements. In this case, the Max Server Memory
option must be set for each database instance (see http://msdn.microsoft.com/
en-us/library/ms178067.aspx for more information). This privilege must be
enabled to configure Address Windowing Extensions (AWE).
Use the Windows Group Policy tool (gpedit.msc) to enable this policy for the
account used by SQL Server. You must be a system administrator to change this
policy.
a. Click Start > Run > gpedit.msc.
b. In the Local Group Policy Editor dialog box, expand Computer
Configuration, and then expand Windows Settings.
c. Expand Security Settings, and then expand Local Policies.
d. Select the User Rights Assignment folder. Policies are displayed in the
details pane.
B-8 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring SQL Server 2016

e. Double-click Lock pages in memory.

f. In the Local Security Policy Settings dialog box, click Add.
g. In the Select Users or Groups dialog box, add an account with privileges
to run sqlserver.exe.
• Configure instant file initialization
Enabling this feature will improve performance on Windows Server 2016. The
Studio Database will run without this feature, but performance may be affected.
This feature is only available if the SQL Server (MSSQLSERVER) service account
has been granted SE_MANAGE_VOLUME_NAME. This feature is only available on
Windows Server 2012 R2. Members of the Administrator group have this right and
can grant it to other users by adding them to the Perform Volume
Maintenance Tasks security policy.
a. Click Start > Run > gpedit.msc.
b. In the Local Group Policy Editor dialog box, expand Computer
Configuration, and then expand Windows Settings.
c. Expand Security Settings, and then expand Local Policies.
d. Select the User Rights Assignment folder. Policies are displayed in the
details pane.
e. Double-click Perform Volume Maintenance Tasks.
f. In the Local Security Policy Settings dialog box, click Add.
g. In the Select Users or Groups dialog box, add an account with privileges
to run sqlserver.exe.
h. Click Start > Run > gpupdate /force to immediately apply the
modification in the security policy.

SQL Server 2016 To properly support Studio Database, during the installation of SQL Server 2016
Standard Standard Edition, ensure that you do the following:
• During the feature selection, include the following:
- Database Engine Services
- Client tools connectivity
- Management tools - Basic
- Management tools - Complete (recommended)

• • • • • •
Note: The optional features below Database Engine services (replication, full-
text search, and data quality services) are not required.

Database Configuration B-9

Schlumberger Private - Customer Use

Configuring SQL Server 2016

• During the Server Configuration:

- Set SQL Server Browser to Automatic, otherwise the SQL Server Browser
process will not auto-start.
- Set the Collation/Database Engine to SQL_Latin1_General_CP1_CI_AS.

• • • • • •
Note: SQL_Latin1_General_CP1_CI_AS is the only Collation that is supported.

• During the Database Engine configuration:

- For Authentication Mode, select Mixed Mode authentication.
- Confirm that the Data Directories are correct and can be accessed by the SQL
Server service.

• • • • • •
Note: The maximum value allowed for the .mdb datafile of the modeldb is 20
MB. The installation of Studio Database will fail if you enter a value greater
than 20 MB.

• • • • • •
Note: For complete details on installing SQL Server 2012 Standard Edition SP2,
refer to the documentation resources provided with your SQL Server
software.

Settings
Studio Database requires the following settings in your SQL Server installation to be
enabled before the Studio Database installation:
• Enabling remote connections.
For details on enabling these settings, see the following sections.

Enabling Remote To enable remote connections you need to enable the "Allow remote connections"
Connections parameter in your server properties and to enable TCP/IP protocol for the server
instance.

 To Enable the TCP/IP Protocol in the Server Instance

Using the SQL Server Configuration Manager do the following
1 Expand SQL Server Network Configuration.
2 Select Protocols for <instance_name>.
3 Double-click TCP/IP and select Yes for Enabled.

Performance Customize the following SQL Server features.

Considerations
• Max Degree of Parallelism

B-10 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring SQL Server 2016

The Max Degree of Parallelism option can be used to limit the number of
processors to use in parallel plan execution. Setting this option to a larger value
often causes unwanted resource consumption and performance degradation.
a. Using SQL Server Management Studio, connect to your database engine
service.
b. Right-click on your instance and select Properties.
c. Select Advanced properties.
d. Set the value for Max Degree of Parallelism based on the number of
cores in your server, with a maximum value of 8.
• Presize Database Temporary Data and Log Files
Presize according to the data and size of transactions. The suggested size below
should work for most reasonable transactions sizes.
a. Using SQL Server Management Studio, connect to your database.
b. Expand Database.
c. Expand System Databases.
d. Right-click on the tempdb database and select Properties.
e. Select Files.
f. Set the Initial Size value for tempdev to 5120 with 10 percent of
increment, and the Initial Size value for templog to 1024 with 10 percent
of increment.
• Memory per Query
This controls how much memory is available for each query. Studio Database
makes extensive use of large queries.
a. Using SQL Server Management Studio, connect to your database.
b. Right-click on your instance and select Properties.
c. Select Memory.
d. Set Minimum memory per query to 4 MB.
• Default Fill Factor
Studio Database makes extensive use of indexing in the database. This option
controls how the index grows as amount indexed data increases.
a. Using SQL Server Management Studio, connect to your database.
b. Right-click on your instance and select Properties.
c. Select Database settings.
d. Set Default index fill factor to at least 70.
• Maximum Server Memory
This controls how much overall memory is available for each SQL Server instance.
Settings are suggested, based on a system RAM amount of 64 GB and a single
SQL Server instance in use.
a. Using SQL Server Management Studio, connect to your database.
b. Right-click on your instance and select Properties.

Database Configuration B-11

Schlumberger Private - Customer Use

Configuring SQL Server 2016

c. Select Memory.
d. Set Maximum server memory to 54000 MB.
Repository Customizations
These performance considerations need to be applied to the repository.
Administrators will need to use Studio Manager to create the repository before to
applying these customizations.
The database files and log files must be large enough so that any file growth that
occurs during normal execution doesn't impact the performance of the database. By
default, all newly created repositories will be at the small size of the table below.
The database administrator should adjust the size to match the expected data
volume in the repository. This must be done for each created repository.
1 Using SQL Server Management Studio, connect to your database.
2 Expand the Database folder, right-click on your repository and select
Properties.
3 Select Files, and change the value of the Initial Size parameter according to
the following table. The following settings are suggested for the different
amounts of data. For all cases, it is recommended that you choose an
increment size of 10%.

Size Data File Log File

Small 5120 MB 1024 MB
Medium 20480 MB 20480 MB
Large 102400 MB 20480 MB

B-12 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

C Configuring IIS 10
This appendix explains how to configure your system to install Internet Information
Services (IIS) in order to install the Studio Server. Instructions to install IIS can be
found at:
http://www.iis.net/learn/install/

Configuring IIS 10 C-1

Schlumberger Private - Customer Use

Configuring IIS 10 with the Recommended Features

Configuring IIS 10 with the Recommended Features

1 Click Server Manager > Manage > Add Roles or Features.
2 See the following recommended settings. At the current state of the install,
there will be warnings for the recommended settings shown in Bold. The
installation of the server will work either with or without these recommended
settings shown in Bold. At a minimum, select the following options:
• Web Server
• Common HTTP Features
• Default Document
• Directory Browsing – not needed and a warning will occur
• HTTP Errors
• Static Content
• HTTP Redirection

• Health and Diagnostics

• HTTP Logging
• Custom Logging – not needed and a warning will occur
• Logging Tools
• Request Monitor
• Tracing

• Performance
• Static Content Compression
• Dynamic Content Compression
• Security
• Request Filtering
• Basic Authentication – not needed and a warning will occur
• Windows Authentication

• Application Development
• .NET Extensibility 4.5 – a false warning will occur even if .NET
Extensibility 4.5 exists. Do not install .NET Extensibility 3.5 to
fix the issue.
• ASP.NET 4.5
• ISAPI Extensions
• ISAPI Filters

• Management Tools
• IIS Management Console
• IIS Management Script and Tools
• Management Service
C-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring IIS 10 with the Recommended Features

Fig. C-1 Add Roles and Features Wizard - Part 1

Configuring IIS 10 C-3

Schlumberger Private - Customer Use

Configuring IIS 10 with the Recommended Features

Fig. C-2 Add Roles and Features Wizard - Part 2

3 Verify IIS is installed and running by starting IIS Manager:

a. Click Server Manager > Tools > Internet Information Services (IIS)
Manager.
b. In IIS Manager, select Default Web Site and verify it is running. Notice that
the Start option is to disable and the Stop option is to enable.

• • • • • •
Note: In IIS 8.5, the default value for the Idle Time-out Action setting is set
to Terminate and Studio has been tested on IIS with this default value.
Changing this setting to Suspend may cause problems in Studio Server
and has not been tested. Studio does not recommend changing this
setting.

• • • • • •
Note: As part of the threat modeling process to reduce the risk of security
issues, we recommend following Microsoft’s Security Best Practices for IIS
8, which can be found at the following link:

https://technet.microsoft.com/en-us/library/jj635855.aspx

C-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring IIS 10 with the Recommended Features

Configuring IIS 10 with the Recommended Features

1 Click Server Manager > Manage > Add Roles or Features.
2 See the following recommended settings. At the current state of the install,
there will be warnings for the recommended settings shown in Bold. The
installation of the server will work either with or without these recommended
settings shown in Bold. At a minimum, select the following options:
• Web Server
• Common HTTP Features
• Default Document
• Directory Browsing – not needed and a warning will occur
• HTTP Errors
• Static Content
• HTTP Redirection

• Health and Diagnostics

• HTTP Logging
• Custom Logging – not needed and a warning will occur
• Logging Tools
• Request Monitor
• Tracing

• Performance
• Static Content Compression
• Dynamic Content Compression
• Security
• Request Filtering
• Basic Authentication – not needed and a warning will occur
• Windows Authentication

• Application Development
• .NET Extensibility 4.5 – a false warning will occur even if .NET
Extensibility 4.5 exists. Do not install .NET Extensibility 3.5 to
fix the issue.
• ASP.NET 4.5
• ISAPI Extensions
• ISAPI Filters

• Management Tools
• IIS Management Console
• IIS Management Script and Tools
• Management Service
Configuring IIS 10 C-5

Schlumberger Private - Customer Use

Configuring IIS 10 with the Recommended Features

Fig. C-1 Add Roles and Features Wizard - Part 1

C-6 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring IIS 10 with the Recommended Features

Fig. C-2 Add Roles and Features Wizard - Part 2

3 Verify IIS is installed and running by starting IIS Manager:

a. Click Server Manager > Tools > Internet Information Services (IIS)
Manager.
b. In IIS Manager, select Default Web Site and verify it is running. Notice that
the Start option is to disable and the Stop option is to enable.

• • • • • •
Note: In IIS 10, the default value for the Idle Time-out Action setting is set to
Terminate and Studio has been tested on IIS with this default value.
Changing this setting to Suspend may cause problems in Studio Server
and has not been tested. Studio does not recommend changing this
setting.

• • • • • •
Note: As part of the threat modeling process to reduce the risk of security
issues, we recommend following Microsoft’s Security Best Practices for IIS
10, which can be found at the following link:

https://technet.microsoft.com/en-us/library/jj635855.aspx

Configuring IIS 10 C-7

Schlumberger Private - Customer Use

Configuring HTTP Response Headers for Security Purposes

Configuring HTTP Response Headers for Security Purposes

This is a recommended configuration of IIS.
The HTTP Response Headers need to be changed for security purposes. Extra HTTP
Response Headers need to be added to the Studio Server website. The following
shows the changes needed.

• • • • • •
Note: There might be other HTTP response headers, such as X-Powered-By, that
have already been added to the Studio Server website.

In the Internet Information Services Manager, use the HTTP Response Headers
view to add the following HTTP Response Headers:
• Content-Security-Policy => .default-src ‘self’
• X-Content-Type-Options => nosniff
• X-XSS-Protection => 1; mode=block

C-8 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Enabling and Configuring Compression in Studio Server

Enabling and Configuring Compression in Studio Server

This is an optional configuration of IIS.

• • • • • •
Note: Before Studio Server is installed, make sure that Static Content
Compression and Dynamic Content Compression roles are selected,
as they must be turned on when IIS is installed.

After Studio Server is installed, do the following:

1 In Server Manager, click Tools > Internet Information Services Manager.
2 In IIS Manager, go to the Server level (Feature View) and click Configuration
Editor.

Fig. C-3 Configuration Editor

3 Do the following changes to the system.webServer/httpCompression

settings in the Configuration Editor:
a. Click dynamicTypes.
The Collection Editor - dynamicTypes screen displays.

Configuring IIS 10 C-9

Schlumberger Private - Customer Use

Enabling and Configuring Compression in Studio Server

Fig. C-4 Collection Editor - dynamicTypes Screen

b. Set */* in the mimeType column to True in the enabled column.

c. Go back to the Configuration Editor and click staticTypes.
The Collection Editor - staticTypes screen displays.

C-10 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Enabling and Configuring Compression in Studio Server

Fig. C-5 Collection Editor - staticTypes Screen

d. Set */* in the mimeType column to True in the enabled column.

4 In IIS Manager, select the Feature View of the Studio Web Site.

Fig. C-6 Feature View of Studio Web Site

Configuring IIS 10 C-11

Schlumberger Private - Customer Use

Enabling and Configuring Compression in Studio Server

5 Click Compression.
The Compression screen displays.

Fig. C-7 Compression Screen

6 Select Enable dynamic content compression and Enable static content

compression and click Apply.
7 Restart IIS.

C-12 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring Secure Sockets Layer (SSL)

Configuring Secure Sockets Layer (SSL)

The Studio Server installer creates a new site in the IIS server and creates an HTTP
binding at the specified port. This allows the client application to connect to the
server by using the HTTP protocol. Configuring SSL is an optional step, however, it is
recommended that SSL be enabled on the server for increased security, with client
applications connecting by using HTTPS protocol. This provides the ability to encrypt
data between the client and the server, as well as the client application being able to
confirm the server’s identity.
The following sections provide details on how to configure SSL on Studio Server.

Obtaining a A certificate for the server machine is required to enable SSL. You will need a
Certificate certificate issued by a known certificate authority (CA) or the company’s internal CA
The following IIS manager options can be used to request, install, or create a
certificate:
• To create a request that can be used to request a certificate from a CA, click
Server > Server Certificates > Create Certificate Request
• To install a newly acquired certificate, click Server > Server Certificates >
Complete Certificate Request
If the server is configured with a self-signed certificate, then, a client application,
such as Studio Manager and Techlog will not work and you will receive the following
error message, “Could not establish trust relationship for the SSL/TLS secure
channel. The remote certificate is invalid according to the validation procedure.”
IIS 8.5 also provides the ability to manage certificates in a centralized certificate
store. Refer to the Centralized SSL Certificate Support feature documentation for
details.

Creating HTTPS In IIS Manager, select the Studio site and from the Actions menu, click
Binding Bindings > Add and do the following:
1 For Type, enter https.
2 For Port, use the default 443 port or assign a different unused port number.
3 For SSL certificate, select the required server certificate from the list.

Using the SSL Only To restrict the Studio site to SSL connections only, select the Studio site by clicking
Option (Optional) IIS Manager > SSL Settings > Require SSL.

Specifying a URL in To use SSL connections to the server, specify an https URL in client applications in
Client Applications the following format:
https://server.domain[:port]

Configuring IIS 10 C-13

Schlumberger Private - Customer Use

Configuring IIS Ping Maximum Response Time in Studio Server

Configuring IIS Ping Maximum Response Time in Studio Server

This is an optional configuration of IIS.

• • • • • •
Note: After Studio Server is installed, it may be necessary to increase the IIS
Ping Maximum Response Time setting from the default value of 90
seconds. Studio Server will periodically manage the memory usage on the
server. In certain Studio usage scenarios with a significant number of
simultaneous data transfers, during this memory management operation,
there may be a delay in Studio Server responsiveness. On servers with
higher amounts of RAM installed, this process may cause IIS to reset the
active Studio client connections. To improve the ability of Studio to retain
connectivity during this process, you may need to increase the IIS Ping
Maximum Response Time setting, which controls how long IIS will wait
before resetting the active Studio connections.

After Studio Server is installed, do the following:

1 In Server Manager, click Tools > Internet Information Services Manager.
2 In IIS Manager, select the Application Pools node under the server site
(Connections Pane).
3 Click the Studio application pool item and then, from the Actions pane, click
Advanced Settings.
4 In the Process Model section, go to Ping Maximum Response Time
(seconds) and change the value from 90 to 180. Depending on your particular
Studio Server usage and memory configuration, you may need to increase this
value higher than 180, if needed.
5 Click OK.

C-14 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Configuring IIS Ping Maximum Response Time in Studio Server

Fig. C-8 Advanced Settings Screen

Configuring IIS 10 C-15

Schlumberger Private - Customer Use

Configuring IIS Ping Maximum Response Time in Studio Server

C-16 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 D Database Server Standard Accounts
for Oracle

Overview This appendix describes the privileges provided with all standard accounts for Studio
Database on Oracle databases. This information will enable the Database
Administrator or System Administrator to evaluate potential security threats with
respect to any of the standard accounts (for example, threats due to improper
granting of DBA privileges). Access to those accounts can then be limited to selected
privileged users in the organization.

Database Server Standard Accounts for Oracle D-1

Schlumberger Private - Customer Use

Studio Database Accounts Overview

Studio Database Accounts Overview

The database server uses fixed accounts, variable accounts, and third-party
accounts.
• Fixed accounts are the default accounts provided with standard database server
installations. These account names cannot be changed.
• Variable accounts vary according to the names provided at the time of account
creation (for example, DD1, Proj1). The names of variable accounts used
throughout this document are the names of the account types.

Fixed Accounts

STUDIO_SYS • An internal, or root account created during installation. This account has many
bootstrap procedures to create other accounts and perform administrative
functions, such as managing data dictionaries, repositories, users, and repository
access.
• Should never be used for general data access.
• Password should be kept highly secure.
• Can read and modify data in repository and data dictionary accounts.

STUDIO_DD_2018 • Contains Meta tables that contain data used to generate repositories.
• Contains one version of the database server data model.
• Contains reference tables and some common entities shared by all repositories
created from that data dictionary.
• The data dictionary contains:
- Metadata - Describes the data model used by Repository accounts
- Reference data - For example, Units and Enumerations
- Shared data - Exploration and Production data shared between repositories

Variable Accounts

STUDIO_SERVICE In Studio Manager, the installation of Studio Database supporting Techlog requires
providing account information for the “Studio Service Account name” and “Studio
Service Account password”. This database level account is created during the Studio
Database installation and is the account that is used by Studio Server to connect to
and communicate with Studio Database. The default account name for this is
STUDIO_SERVICE. If this account is deleted or Studio Server is unable to connect to
the database using this account, all Studio functionality will no longer be accessible
from Studio Manager and Techlog.

D-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Studio Database Accounts Overview

Repository This type of account is an organized collection of Exploration and Production (E&P)
related data contained in the database server repository.
• Serves as the main data store for E&P data.
• Users should not log in with this database account, but instead, should log in
using the User account that has been granted access to the repository.

Database Server Standard Accounts for Oracle D-3

Schlumberger Private - Customer Use

Studio Database Roles

Studio Database Roles

STUDIO_SYS_ • CREATE ANY PROCEDURE

ADMINISTRATOR
• CREATE ANY VIEW
• CREATE DATABASE LINK
• CREATE JOB
• DROP ANY PROCEDURE
• DROP ANY VIEW
• EXECUTE ANY PROCEDURE
• GRANT ANY OBJECT PRIVILEGE

STUDIO_SYS_ • GRANT ALTER ANY INDEX

UPGRADE_ROLE
• GRANT ALTER ANY PROCEDURE
• GRANT ALTER ANY ROLE
• GRANT ALTER ANY SEQUENCE
• GRANT ALTER ANY TABLE
• GRANT ALTER ANY TRIGGER
• GRANT ALTER SESSION
• GRANT ALTER USER
• GRANT COMMENT ANY TABLE
• GRANT CREATE ANY INDEX
• GRANT CREATE ANY PROCEDURE
• GRANT CREATE ANY SEQUENCE
• GRANT CREATE ANY SYNONYM
• GRANT CREATE ANY TABLE
• GRANT CREATE ANY TRIGGER
• GRANT CREATE ANY TYPE
• GRANT CREATE ANY VIEW
• GRANT CREATE ROLE
• GRANT CREATE SESSION
• GRANT DELETE ANY TABLE
• GRANT DROP ANY INDEX
• GRANT DROP ANY PROCEDURE
• GRANT DROP ANY ROLE
• GRANT DROP ANY SEQUENCE
• GRANT DROP ANY SYNONYM
D-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Studio Database Roles

• GRANT DROP ANY TABLE

• GRANT DROP ANY TRIGGER
• GRANT DROP ANY TYPE
• GRANT DROP ANY VIEW
• GRANT EXECUTE ANY PROCEDURE
• GRANT GRANT ANY OBJECT PRIVILEGE
• GRANT GRANT ANY ROLE
• GRANT INSERT ANY TABLE
• GRANT SELECT ANY DICTIONARY
• GRANT SELECT ANY SEQUENCE
• GRANT SELECT ANY TABLE
• GRANT UPDATE ANY TABLE

Database Server Standard Accounts for Oracle D-5

Schlumberger Private - Customer Use

Studio Database Account Privileges

Studio Database Account Privileges

STUDIO_SYS • ALTER ANY ROLE

• ALTER ANY TABLE
• ALTER ANY TRIGGER
• ALTER SESSION
• ALTER USER
• CREATE ANY DIRECTORY
• CREATE ANY INDEX
• CREATE ANY LIBRARY
• CREATE ANY PROCEDURE
• CREATE ANY SEQUENCE
• CREATE ANY SYNONYM
• CREATE ANY TABLE
• CREATE ANY TRIGGER
• CREATE ANY VIEW
• CREATE INDEXTYPE
• CREATE OPERATOR
• CREATE PROCEDURE
• CREATE PUBLIC SYNONYM
• CREATE ROLE
• CREATE SEQUENCE
• CREATE SESSION
• CREATE SYNONYM
• CREATE TABLE
• CREATE TRIGGER
• CREATE TYPE
• CREATE USER
• CREATE VIEW
• DELETE ANY TABLE
• DROP ANY DIRECTORY
• DROP ANY INDEX
• DROP ANY LIBRARY
• DROP ANY ROLE
• DROP ANY SYNONYM
• DROP ANY TRIGGER
D-6 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Studio Database Account Privileges

• DROP ANY PROCEDURE

• DROP ANY TABLE
• DROP ANY VIEW
• DROP PUBLIC SYNONYM
• DROP USER
• GRANT ANY OBJECT PRIVILEGE
• GRANT ANY ROLE
• INSERT ANY TABLE
• SELECT ANY DICTIONARY
• SELECT ANY TABLE
• UNLIMITED TABLESPACE
• UPDATE ANY TABLE
• GRANT EXECUTE ON STUDIO_DD_2015.SDSREFERENCE TO STUDIO_SYS;
• GRANT EXECUTE ON STUDIO_DD_2015.SDSSCHEMA TO STUDIO_SYS;
• GRANT EXECUTE ON SYS.DBMS_LOCK TO STUDIO_SYS;
• GRANT EXECUTE, READ, WRITE ON DIRECTORY STUDIO_DP_DIR TO
STUDIO_SYS WITH GRANT OPTION;

Roles STUDIO_SYS_ADMINISTRATOR

STUDIO_SERVICE • CONNECT
• DBA

Database Server Standard Accounts for Oracle D-7

Schlumberger Private - Customer Use

Studio Database Account Privileges

D-8 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 E Characters Restricted for Passwords

Overview This appendix lists codes that are either unusable or not recommended for
passwords.

Characters Restricted for Passwords E-1

Schlumberger Private - Customer Use

Characters Restricted for Passwords

Characters Restricted for Passwords

Description Many European characters are multiple-byte, and in order to have access to the
greatest possible set of European characters, it is recommended that your Oracle
instance be configured to use the Latin-1 character encoding.
Studio Manager can create and use passwords that have US-ASCII letters and
numerals and some punctuation characters. Studio Manager can also support non-
US-ASCII character codes 161 to 180, and 182 to 254.
The following codes are either unusable or not recommended for passwords.
Table E-1 Codes Not Usuable or Recommended for Passwords

Code Character, Description Code Character, Description

0-31 control characters 137 ‰ (per mille sign)
32 space 138 Š (Latin capital letter S with caron)
34 " (quotation mark) 139 ‹ (single left-pointing angle quote mark)
36 $ (dollar sign) 140 Π(Latin capital ligature OE)
37 % (percent sign) 141 reverse line feed (ctrl char)
38 & (ampersand) 142 Ž (Latin capital letter Z with caron)
39 ' (apostrophe) 143 single shift three (ctrl char)
40 ( (left parenthesis) 144 device control string (ctrl char)
41 ) (right parenthesis) 145 ‘ (left single quotation mark)
47 / (solidus) 146 ’ (right single quotation mark)
58 : (colon) 147 “ (left double quotation mark)
59 ; (semicolon) 148 ” (right double quotation mark)
63 ? (question mark) 149 • (bullet)
64 @ (commercial at) 150 – (en dash)
92 \ (reverse solidus) 151 — (em dash)
96 ` (grave accent) 152 ˜ (small tilde)
124 | (vertical line) 153 ™ (trademark sign)
127 delete control character 154 š (Latin small letter S with caron)
128 € (euro sign) 155 › (single right-pointing angle quote mark)
129 control character 156 œ (Latin small ligature OE)
130 ‚ (single low-9 quotation mark) 157 operating system command (ctrl char)
131 ƒ (Latin small letter F with hook) 158 ž (Latin small letter Z with caron)
132 „ (double low-9 quotation mark) 159 Ÿ (Latin capital letter Y with diaeresis)
133 … (horizontal ellipses) 160 no-break space

E-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Characters Restricted for Passwords

Code Character, Description Code Character, Description

134 † (dagger) 181 μ (micro sign)
135 ‡ (double dagger) 255 ÿ (Latin small letter Y with diaeresis)
136 ˆ (modifier letter circumflex accent)

Characters Restricted for Passwords E-3

Schlumberger Private - Customer Use

Characters Restricted for Passwords

E-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 F Glossary

Overview This glossary primarily contains definitions for items that you will encounter during
the installation of Studio Database.

Glossary F-1

Schlumberger Private - Customer Use

Glossary Entries

Glossary Entries

Data Pump Data Pump is a new Oracle option that is faster and more flexible than the "exp"
(export) and "imp" (import) utilities used in previous Oracle versions. Data Pump
uses Oracle directories on the Oracle server to log Data Pump-related files.

Default Tablespace This is a permanent tablespace from the Oracle database that is used as the default
tablespace for user accounts.
If a default tablespace is not specified during database server installation, the Oracle
default tablespace, SYSTEM, is used. However, Oracle recommends that you not use
SYSTEM as the default, so you should specify another option during database server
installation. The Studio Database account STUDIO_SYS and all data dictionaries
always use STUDIO_TABLE as the permanent tablespace.

• • • • • •
Important: Check with your Oracle DBA regarding which tablespace to select
during database server installation.

Keytab File On the Active Directory Enabled Database panel of the installation program,
enter the absolute path to the keytab file on the Oracle server. This should be what
is used for the SQLNET.KERBEROS5_KEYTAB parameter in sqlnet.ora.

Local Installation The process of installing the database server directly to the Oracle server by running
the installation program on the Oracle server.

ORACLE_HOME In the installation program, this is the Oracle home directory location where your
Oracle software is installed. It is not necessarily the location on your Oracle
database server.
For remote installations, this is the value you observe when logged in to the
database server as the UserID under which the Oracle database executes.

F-2 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use

 Glossary Entries

Oracle Instance In the installation program, this is where you specify an Oracle database instance
based on the tnsnames.ora alias. During the database server installation, you will
need to include the following information for the Oracle instance:
• Host—IP address or host name of the computer acting as the host for the Oracle
database
• Port—Assigned port number on the host computer that the database server will
use to communicate with the Oracle database
• Instance—Instance name given to the Oracle database
• TNS Alias—Name used to access the Oracle database. This name can be the
same or different than the database instance name.
When you use SQL*Plus to connect to the database, use the following command
format:
sqlplus <Oracle account>/<password>@tnsalias

Oracle SYS Account This is a database administrator account created during Oracle database creation
(the other is SYSTEM). The SYS account owns most of the data dictionary tables,
while SYSTEM owns the views created on those base tables.

Remote The process of installing the database server to an Oracle server from a remote
Installation workstation.

STUDIO_SERVICE This database level account is created during the Studio Database installation and is
the account that is used by Studio Server to connect to and communicate with
Studio Database. This is the default name for this account, but can be changed
during installation.

STUDIO_SYS An internal, or root account created during installation. This account has many
bootstrap procedures to create other accounts and perform administrative functions,
such as managing data dictionaries, repositories, users, and repository access.

Temporary Oracle uses the temporary tablespace to store transient data that persists only for
Tablespace the duration of a given user session (for example, during a data sorting operation).
The temporary tablespace specified during database server installation is the
temporary tablespace used for all user accounts by default.

TNS_Admin This directory contains the tnsnames.ora file, which contains information (such as
IP address, port number, and service ID) that the database server uses to
communicate with the Oracle database. Although TNS_ADMIN can be placed in any
file location, it typically points to the $ORACLE_HOME/NETWORK/ADMIN directory,
which is maintained by the Oracle DBA.

Glossary F-3

Schlumberger Private - Customer Use

Glossary Entries

TNS Alias This is the identifier used by Oracle to identify a particular database instance. The
TNS alias is resolved using the tnsnames.ora file.

F-4 Studio Installation and Configuration Guide

Schlumberger Private - Customer Use