installation guide 2020 - schlumberger

Installation guide 2020.2

Copyright Notice

Copyright © 2020 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 retrievalsystem, 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 and Service MarksSchlumberger, the Schlumberger logotype, and other words or symbols used to identify the products and services described herein are eithertrademarks, trade names or service marks of Schlumberger and its licensors, or are the property of their respective owners. These marks may notbe 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 becopied, imitated, or used, in whole or in part, without the express prior written permission of Schlumberger. Other company, product, and servicenames are the properties of their respective owners.

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

Security NoticeThe software described herein is configured to operate with at least the minimum specifications set out by Schlumberger. You are advised thatsuch minimum specifications are merely recommendations and not intended to be limiting to configurations that may be used to operate thesoftware. Similarly, you are advised that the software should be operated in a secure environment whether such software is operated across anetwork, 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 securemanner. If you have further questions as to recommendations regarding recommended specifications or security, please feel free to contact yourlocal Schlumberger representative.

OVERVIEWDistribution............................................................................................................................................................................................................. 3

REQUIREMENTSSystem requirements............................................................................................................................................................................................4

Operating systems..........................................................................................................................................................................................4Other required software................................................................................................................................................................................4

Licensing.................................................................................................................................................................................................................8Support for 4K (and higher resolution) monitors............................................................................................................................................14Ergonomics and alternative input devices......................................................................................................................................................15Recommended tested hardware solutions.....................................................................................................................................................15Petrel Geophysics recommendations..............................................................................................................................................................16Network storage recommendation.................................................................................................................................................................. 17Remote visualization support............................................................................................................................................................................ 17

Schlumberger IaaS (Infrastructure as a Service)...................................................................................................................................17

INSTALLATIONPre-requisites...................................................................................................................................................................................................... 19Download the installation package..................................................................................................................................................................19Install Petrel......................................................................................................................................................................................................... 19Run the installation executable from the command line.............................................................................................................................. 20Deploy Petrel without using the installation executable..............................................................................................................................20INTERSECT Connector....................................................................................................................................................................................... 20

Configuring the default INTERSECT Connector.......................................................................................................................................20Default SLB plugins.............................................................................................................................................................................................21Deploying Petrel on a network shared disk....................................................................................................................................................21Petrel Coordinate System Manager.................................................................................................................................................................24Uninstall Petrel.................................................................................................................................................................................................... 26

PLUG-INSInstalling and uninstalling plug-ins.................................................................................................................................................................. 27Plug-in licenses................................................................................................................................................................................................... 27Plug-in Manager..................................................................................................................................................................................................27Deploy plug-ins from a network shared folder...............................................................................................................................................28Change the default location of the [plug-ins home] directory.....................................................................................................................30Plug-in troubleshooting......................................................................................................................................................................................31

Access denied during plug-in installation................................................................................................................................................31Petrel Startup Optimization option................................................................................................................................................................... 31

ENHANCED SUMMARY FILE FORMATConversion-related worksteps in Petrel..........................................................................................................................................................33Technical details................................................................................................................................................................................................. 33General considerations......................................................................................................................................................................................36

Best practice guidelines............................................................................................................................................................................. 36Performance considerations......................................................................................................................................................................36

STUDIO DATABASE CONFIGURATIONThird-party software configuration..................................................................................................................................................................37

Single sign on................................................................................................................................................................................................37Connecting to the database.............................................................................................................................................................................. 37Automatic connection to a Studio repository.................................................................................................................................................37Enable the Remember password feature........................................................................................................................................................38

TABLE OF CONTENTS

i

Change the configuration for custom coordinate systems..........................................................................................................................38

SUPPORT INFORMATIONUser assistance...................................................................................................................................................................................................40Contact Schlumberger....................................................................................................................................................................................... 40

TABLE OF CONTENTS

ii

Overview

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

Distribution

The Petrel 2020 release is available by download using the appropriate links on the Software Integrated Solutions (SIS)Support Portal. A user account is required on the portal. If you do not already have a user account, you can register toaccess the portal at https://www.software.slb.com.

The full set of Petrel 2020 documentation, and documentation for any prior Petrel release, can be downloaded from the Software Integrated Solutions (SIS) Support Portal.

The Ocean* Store provides Petrel plug-ins at ocean.slb.com

OVERVIEW

3

HTTPS://WWW.SOFTWARE.SLB.COM/SUPPORT/PRODUCT/PETREL


HTTPS://WWW.SOFTWARE.SLB.COM/SUPPORT


HTTPS://WWW.OCEAN.SLB.COM/

Requirements

System requirements

Minimum Preferred

Processor Quad-core processor (best with a fast clockspeed and high cache)

Dual 4 to 8 core processor (best with a fastclock speed and high cache)

Memory 16 GB RAM (32+ GB recommended) 64 GB RAM

Display The quality of the viewing experience increases with the size and number of monitors

Graphics desktop NVIDIA® Quadro® P4000 or NVIDIA QuadroP2000

NVIDIA Quadro P6000 or P5000

Graphics mobile NVIDIA Quadro P3000 or NVIDIA Quadro M2200 NVIDIA Quadro P5000 or P4000

Primary storage Fast rotational speed HDD (10K, 15K RPM) orSSD

PCIe based Flash or SSD

Secondary storage Optional SSD or Fast rotational speed HDD (10K, 15K)

• The Petrel interface is optimized for horizontal resolutions from 1280 and higher and for vertical resolutions from 1024and higher.

• Support for VR (virtual reality) has been removed from Petrel 2017 onward.• Windows 10 updates - Microsoft® supports semi-annual update channel (includes .NET®) - future Petrel versions will

be supported on the current channel update at the Petrel release date.• Schlumberger continually tests the latest hardware available from major suppliers. In an attempt to minimize

unexpected problems and costs, Schlumberger often uses branded solutions such as those offered by HP®, Dell®,Lenovo®, Intel®, and NVIDIA.

Operating systems

Microsoft Windows 10 Professional or Enterprise Edition (64-bit)

Other required software

Microsoft .NET Framework 4.7.2 or newer (Tech Alert #6858030)

Processors

Processor speed improves performance for these types of tasks:

• Large calculation tasks, such as volume size, seismic attribute generation, property modeling, and upscaling.• Adding information to the graphics card.

For general Petrel use, a processor that meets the minimum recommendations is sufficient. For better performance, usethe best available configuration.

Several modules can benefit from multi-core processors.

Geophysics

Feature Parallel Background

Seismic read access of ZGY Yes Yes

INSTALLATION GUIDE 2020.2

4


Volume attribute computation Yes Yes

Prefetch to cache 3D seismic data Yes Yes

Local 3D horizon - read access for Yes Yes

Multiresolution computation for viz

• Horizons for seismic 3D• Seismic 2D lines

Yes Yes

Seismic 3D realization from any source - ZGY/SEGY/RAW

Yes Yes

Seismic 3D read access for 3D viz using slicerenderer - SEGY/RAW

Yes Yes

Seismic 3D export to SEG-Y Yes No

Decompression of compressed ZGY Yes Yes

Prefetch to cache SEG-Y No Yes

Prefetch to cache RAW seismic No Yes

3D seismic interpretation No Yes

Seismic interpretation min/max queries Yes No

Seismic histogram scan Yes Yes

Seismic copy local No Yes

Make compressed ZGY Yes No

Ocean prestack seismic access Yes Yes

Geology and Modeling


Data analysis No Yes

Facies and Petrophysical modeling Yes No

Geometrical modeling (including seismicsampling)

Yes No

3D grid volumetrics Yes No

Surface volumetrics Yes No

Gridding


Structural gridding Yes No

Grid refinement process Yes No

REQUIREMENTS

System requirements 5


Mesh skin extraction for 3D grid propertyvisualization

Yes Yes

Petrel Modeling recommendations

Several modeling algorithms in Petrel take advantage of multi-core processing. Increasing the number of processorsimproves the runtime of these algorithms. This current trend of converting algorithms to run in parallel will continue,based on algorithm runtime.

Memory (RAM)

To run Petrel efficiently, Schlumberger requires at least 16 GB of RAM and recommends at least 32 GB (64 GB forGeophysics workflows and Structural Modeling). The total system memory must be greater than the memory used by theapplication. This ensures that your operating system has dedicated RAM so that you do not need use your page file (diskmemory).

To estimate the required system size, follow these guidelines:

• For small- to medium-sized data sets (<5 GB): 32 GB of memory.• For large data sets (large 3D seismic volumes, regional seismic models, large structural models with many horizons, or

large simulation [ECLIPSE] runs): 64 to 192+ GB of RAM.

Graphics cards

Your graphics card must meet these requirements:

• Run Pixel Shader 2.0 or later.• Be OpenGL compatible.

For a better visualization experience, use a high-end graphics card and a good monitor (such as a 27‒30-inch LCD monitoror Ultra High Definition 4K monitors).

Level Card Dedicated RAM GPU cores

Workstation, ultra-high end NVIDIA Quadro P6000 24 GB 3840

NVIDIA Quadro P5000 16 GB 2560

Workstation, high end NVIDIA Quadro P5000 16 GB 2560

Workstation, mid-range NVIDIA Quadro P4000 8 GB 1792

Mobile workstation, ultra-high end NVIDIA Quadro P5000 16 GB 2048

Mobile workstation, high end NVIDIA Quadro P4000 8 GB 1792

Mobile workstation, mid-range NVIDIA Quadro P3000 6 GB 1280

NOTE: NVIDIA Quadro RTX GPUs are also recommended and supported for use with Petrel.

Petrel is certified and supported on NVIDIA Quadro graphics cards only. Integrated graphics cards are notrecommended.

From Petrel 2017 onward, NVIDIA Quadro FX graphics cards are no longer supported.


6

Selecting the right graphics card

Petrel automatically manages graphics card memory for most data types and windows. Choosing the right graphics cardoptimizes Petrel visualization performance. Petrel enables rendering and computation on the graphics card for many dataobjects, such as seismic, well data, surfaces, point, and polygons. Therefore, it is important to scale your graphics cardtowards the expected needs.

The table below provides a basic overview and recommendation for selected data types.

Data type Size Recommend graphicscards

Recommended GPUmemory and cores

Recommended RAM

Seismic 1 GB P2000 or better

M2200 or better

Memory: 4 GB+

GPU cores: 700+

16 GB+

>10 GB P5000 Memory: 8 GB+

GPU cores: 1500+

64 GB+

>50 GB P6000 Memory: 12 GB+

GPU cores: 3000+

128 GB+

Wells 1000 P2000 or better

M2200 or better

Memory: 4 GB+

GPU cores: 700+

16 GB+

>10000 P5000 Memory: 8 GB+

GPU cores: 1500+

32 GB+

>250000 P6000 Memory: 12 GB+

GPU cores: 3000+

64 GB+

Surfaces (cells) or points >1 mill P2000 or better

M2200 or better

Memory: 4 GB+

GPU cores: 700+

16 GB+

>10 mill P5000 Memory: 8 GB+

GPU cores: 1500+

32 GB+


GPU cores: 3000+

64 GB+

3D grids (cells) >1 mill P2000 or better

M2200 or better

Memory: 4 GB+

GPU cores: 700+

16 GB+


GPU cores: 1500+

32 GB+


GPU cores: 3000+

64 GB+

NOTE: The option Workstation App - Dynamic Streaming in the NVIDIA Control Panel under 3D settings > Manage3D settings is set by default through the application to ensure optimal performance for Petrel, whenvisualizing data in the 2D or 3D windows.

REQUIREMENTS

System requirements 7

NVIDIA tested drivers

Release 441.66 is the latest recommended and tested official driver from NVIDIA for both workstations and mobileworkstations. Schlumberger recommends upgrading to the latest official drivers from your PC vendor's home page ordirectly from NVIDIA.

Testing shows that NVIDIA drivers 430.64 and later fix many critical issues that support Petrel. Accordingly, release 430.64is the minimum required driver for NVIDIA graphics cards.

Starting with driver Release 430, the following Kepler generation notebook GPUs are no longer supported: QuadroK5000M, Quadro K5100M, Quadro K4000M, Quadro K4100M, Quadro K3000M, Quadro K3100M, Quadro K2000M, QuadroK2100M, Quadro K1000M, Quadro K1100M, Quadro K610M, Quadro K510M and Quadro K500M.

NVIDIA SLI™ technology currently does not benefit Petrel. However, this technology could be an advantage if you areusing a large, high-resolution monitor such as 30-inch LCD monitors.

Disable NVIDIA Optimus

The NVIDIA Optimus feature is incompatible with Petrel.

1. Reboot the system.2. Access the BIOS settings.3. Go to the video section.4. Disable Optimus.5. Reboot the system.

Read more about NVIDIA's Optimus Technology here.

Hyperthreading

Hyperthreading is an option that does not improve Petrel performance. Whether the option is ON or OFF has no impact onPetrel. If the option is turned ON for other reasons, be aware that this affects how Windows reports CPU utilization.

LicensingPetrel uses a combination of FlexeraTM FlexNet Publisher® licensing and a WIBU® CodeMeter® dongle to provide asecure licensing solution. This requires a continuous connection to a USB-based CodeMeter dongle that serves licensesthrough a remote- or local-license server. To use a local license, you must have the Schlumberger Licensing tool andCodeMeter runtime installed. Both of these tools come with Petrel.

NOTE: The 2020.1 (recommended) or 2017 version of the Schlumberger Licensing tool is required. This version isfully backward compatible with previous Petrel versions and does not require new license files. For moreinformation, please see the Schlumberger Licensing User Guide.

As a minimum, Petrel requires a core module license. Petrel supports the following core module licenses:

• Geoscience core• Reservoir engineering core• Combined core (combines Geoscience core and Reservoir engineering core)• Shale core• Geophysics core• Data and results viewer core• Ocean framework (enables Ocean development)

Each core module license enables a different set of Petrel features.

Core module licenses are offered in two types:


8

http://www.nvidia.com/object/optimus_technology.html

• License bundle• Stack on start

(The Shale core is available as a license bundle only.)

Petrel supports either license type in a standalone mode or mixing license types from multiple or a single license serverprovided through multiple or a single license file.

NOTE: When choosing your license type and license feature sets, consult your local SIS Account Manager or SISServices team for guidance on an optimal configuration.

For information about the Schlumberger Licensing Tool, refer to the Schlumberger Licensing User Guide,located in the installation folder of the Petrel installation files (for example, C:\Program Files\Schlumberger\Petrel 20xx\Help).

Licensing terminology

License bundles(packages)

A license bundle is a physical license. It must contain a Petrel core license and it may containoptional Petrel module licenses. Checking out a bundled license feature checks out all the licensesthat the bundle contains.

In the Petrel E&P Software Platform - License selection dialog box, by default, license packages arelisted under Core licenses as Bundle + #.

Stack on start(SOS)

A stack on start (SOS) license consists of individual licenses for each Petrel module. SOS licensescan be part of the same license file or exist as separate license files.

In the Petrel E&P Software Platform - License selection dialog box, Petrel core module SOS licensesare listed under Core licenses. All other Petrel modules are listed under Petrel modules. If multipleservers are connected, licenses are summed.

Profiles A profile is a user-defined selection of licenses. This feature in Petrel allows you to check out apreselected set of licenses at startup.

License feature A license feature, as used in FlexNet, is the actual licensed module or bundle of modules (in the caseof bundled Petrel licenses).

Module A module is a set of Petrel functionality that is usually tied to a license feature. Petrel modules arelisted in the Petrel modules section of the License UI. There are dependencies between Petrelmodules that are automatically honored during selection.

Expiry date Each license bundle has an expiry date that defines when the license expires. All features that arepart of the bundle expire on the same expiry date defined in the license file.

Each stack on start feature (increment) has an expiry date that defines when the feature licenseexpires. Stack on start increments may have different expiry dates.

Petrel shows an expiration warning before the license expires.

Maintenancedate

The maintenance date defines when the current maintenance contract must be renewed to obtainaccess to new Petrel releases. The maintenance date consists of a month and year. After themaintenance date passes, Petrel versions released after this date do not work until the maintenancedate is renewed.

Each license bundle and SOS license feature has a maintenance date.

REQUIREMENTS

Licensing 9

License selection

You can use the License selection dialog box to manage all aspects of license selection independently of the license typeor server. In addition, you can use the License selection dialog box to create and maintain user-defined license profiles tomatch individual end-user profiles or workflows. For more details about using the License selection dialog box, refer tothe relevant section in the Petrel online Help.

Color-coded information, warning, and error messages are captured and displayed at the bottom of the License selectiontab. Multiple messages are stacked based on priority. For an overview of all messages, refer to the Message log pane inthe License selection tab.

License bundles

When you use licensing bundling, you must check out the entire package bundle. Bundles must contain a Petrel coremodule. Individual modules cannot be selected or deselected from the bundle. Typically, you will have one or morepackage bundles with one or more seats of each package bundle. Checking out a bundled license enables all thefunctionality licensed by the modules that are part of the bundle.

For example, suppose you have purchased a single Petrel user license that consists of a Geoscience core, a Reservoirengineering core, and a set of Petrel modules (for example, Seismic interpretation, Facies modeling, etc.). Once thelicense file is generated by Schlumberger Information Solutions and installed at your site, when you log in to Petrel, theLicense selection dialog box opens.

If additional Ocean licenses are available, they are listed under the Ocean modules section and can be selected ordeselected as needed.

Stack on start

When you start Petrel with a stack on start license file, you can choose the Petrel core and module licenses that youwant to use. Your selections become the stack of modules checked out and used during your Petrel session. The modulesremain checked out throughout the session until you log off.

In the License selection dialog box, the dependencies between Petrel core licenses and Petrel modules are explicitlymapped. This ensures that you can select valid module combinations only.

If additional Ocean licenses are available, they are listed under the Ocean modules section. These licenses can beselected or deselected as needed.

You can select and deselect stack on start licenses as needed during your Petrel session. The Petrel modules node alsoprovides a right-click Select All option for quickly selecting all listed module licenses.

Mixing bundles and stack on start licensing

Petrel 2020 supports the ability to connect to servers that provide both stack on start and bundled licenses. This allowsyou to mix bundles and stack on start licenses.

Any additional Ocean licenses that are available are listed under the Ocean modules section. You can select or deselectthese licenses as needed.

Mixing stack on start licenses with bundled licenses allows you to select basic bundles and extend them with specificfeatures that may be available in fewer quantities.

Checking out SOS licenses at Petrel runtime

Petrel 2020 provides the option to check out functional SOS license modules while Petrel is running. This enables easyaccess to additional functionality needed for the workflow at hand and avoids to exit and restart Petrel to selectadditional functional license modules.


10

NOTE: • A prerequisite for checking out additional licenses at Petrel runtime is that license modules must to be oftype Stack on Start (SOS). License modules that are part of bundle licenses are not available for runtimecheckout. The same applies to Ocean Plug-in licenses, which will be enabled with a later Petrel release.

• It is not possible to connect additional license servers while Petrel is running. Additional licenses canonly be added from the servers connected at startup.

To check out additional license at runtime, click File > License modules and click the boxes for further licenses in theLicense status dialog box. Already selected licenses are marked and disabled (shown in gray text).

License profiles

The license profiles feature replaces previous functionality that provided names for packages. To create a profile, selectthe combination of licenses that you need and save the selected combination as a profile with a name.

Saved profiles are listed under Profiles.

You can also perform these profile-related actions:

• Select a profile as a favorite that denotes the profile with a yellow star. To remove the favorite, open Petrel and clickFile > License modules.

• Save a new profile• Rename a profile• Delete a profile

Configuring global Petrel license profiles

Petrel supports global license profiles. To set up a global license profile add a path to the following setting in thePetrelConfiguration.xml file, which is located in:

%appdata%\Schlumberger\Petrel\2020

REQUIREMENTS

Licensing 11

In the PetrelConfiguration.xml file, locate the following parameter:

<GlobalLicenseProfileFilePath Value="" />

Insert the full path and filename to your global license profile file, i.e.

<GlobalLicenseProfileFilePath Value="D:\Global Petrel Profiles\Profiles2020.xml"/>

When using a global license profile the options to save, create, delete or favorite profiles are grayed out. Global licenseprofiles supersede any local Profiles.xml file.

To create a global license profile launch Petrel and save all license configurations using the options in the License UI.This creates a file named Profiles.xml in %appdata%\Schlumberger\Petrel\20xxUse this file as your global license profiles file, copy it to the desired location and update the path for the setting in thePetrelConfiguration.xml file.

Copy profiles between Petrel installations

Use this method to copy profiles between Petrel installations:

1. Go to %appdata%Schlumberger/Petrel/Petrel 20xx.2. Copy the Profiles.xml file and paste it in the %appdata%Schlumberger/Petrel/Petrel 20xx directory of

the new installation.

NOTE: If the profiles are not available from the license server, the License UI shows a warning message in themessage log to let you know that the Profile could not be loaded because no licenses are available on thecurrent server.

Tooltips

You can view detailed information about the functionality provided by a Petrel module in the License selection dialog boxby hovering over the item.

This helps you to decide whether the module contains the features for the work to be executed and thus helps you tomake the right selections.

License module expiry dates can be visualized in the tooltip by enabling the Show expiry date in license descriptionoption in the license settings tab of the license selection dialog box.

Customers are able to add custom description to the license module tooltip using a custom description xml file enabledthrough a PetrelConfiguration.xml file. See the Petrel Help Center to learn how to enable this option.

License information inside Petrel

To access license information within Petrel, select File > License modules. The dialog provides this license featureinformation for the licenses in the currently available profiles. Select a profile and then select the license module in thelist shown in the right pane.

• Feature name• Expiry date• Days left• Server ID

In addition the License module dialog to inspect the current selection and check out additional licenses for this selection.


12

NOTE: Upon starting Petrel the next time, licenses added at runtime are not preserved in the current selection ofprofile.

Setting up the license server environment

Different license server environments are supported for different requirements. Petrel supports local servers, remoteservers, and Quorum server configurations. Remote servers or Quorum server configurations are also supported onvirtual windows systems using a USB network connector. However, any mentioned solution requires a dongle.

License servers can host both bundle and stack on start licenses simultaneously.

NOTE: Detailed information about setting up license servers, quorum servers, and troubleshooting can be found inthe Schlumberger Licensing User Guide, located in the Documentation folder of the downloaded andextracted installation files. For more advanced license server configurations involving virtual or quorumsetups, it is recommended to involve SIS services to help design a tailored system providing maximumperformance and minimum IT maintenance. Contact your local account manager for more information.

Connecting license servers

• Local license server environment

When using a local dongle, the local system must be configured to serve as a license server. In this case, theSchlumberger licensing utility and the CodeMeter dongle software must be installed. Both are distributed with Petreland can be found in the unzipped Petrel installation directory. These tools require Admin privilege to install. Toachieve maximum performance, make sure the recommended versions of Schlumberger licensing software isinstalled.

• Remote license server environment

When building a remote license server environment, it is important to consider that network latency impacts thelicense checkout time. Thus, it is critical that remote servers, independently of whether they are physical, virtual, or aQuorum setup, are well connected within the network. When serving a large number of users (500+ licenses), Quorumconfigurations usually offer better performance than single servers. However, specific knowledge and testing of thenetwork infrastructure should always be considered and performed for larger license server setups.

Best practices for setting up a license server

Checking out a license is a frequent task. When many users are running Petrel, the time to connect to a license serverand select the correct license is significant. To have minimum nonproductive time, these tips may be considered:

• Always make sure the recommended/latest licensing software is used. This includes the Schlumberger licensingutility and CodeMeter driver. For information about the licensing software, refer to the Petrel Installation Guide andSchlumberger Licensing User Guide.

• Be sure that you are using the most recent type of dongle. To check, look at ID number imprinted on the dongle. Up-to-date dongles have IDs that begin with2-xxxxxx. If the ID begins with 1-xxxxxx, contact your account manager torequest a new dongle. The new dongle type delivers performance improvements over the old type and shouldtherefore be preferred.

• Avoid connecting to multiple license servers, if possible. Adding multiple colon-separated license servers to thelicense selection reads the available licenses from all connected servers and linearly increases the time to populatethe license UI based on the number of license features served by each server. Using a license quorum is theexception. When using a quorum, the license selection should include all 3 servers separated by a comma, forexample, 27000@quorumServer1, 27000@quorumServer2, 27000@quorumServer3.

• Where possible, use Favorites. Favorite license packages can be created in the license UI by saving licenseselections as license profiles and denote one as a favorite using the Favorite option.

REQUIREMENTS

Licensing 13

• Always use a static port, for example, [email protected], which optimizes the communication with the licensesystem.

• Set TCP_NODELAY. FLEX sends data between the client and server using TCP/IP packets. By default, the TCP/IP stackbuffers small packets (< 147 bytes in FLEX), known as Nagle´s algorithm, to coalesce a large number of packets beforesending them across the network. This ACK delay (200 ms) results in artificially high latency times for small packetssuch as most FLEX licensing operations. For this reason, we recommend disabling the Nagle algorithm by defining theTCP_NODELAY system setting as a license server environment variable to overcome this behavior, and reduce thelicensing wait period. For more information read the Flexera documentation.

• Use one license file only. Combining all licenses into one physical file improves communication with the license serverand 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 toCodemeter control center > File > Webadmin > Content > CmContainer and if necessary, update the certified time.

Licensing issues and solutions

Petrel does not detect license dongle after removal and reinsertion or after the computer wakes from sleep orhibernation

Follow these steps:

1. As a prerequisite, ensure that this software is installed on your system:

• Schlumberger Licensing Tool 2017 or 2020.1 (recommended).• Latest CodeMeter drivers• Updated dongle firmware

2. Start the Schlumberger Licensing Tool.3. Stop any license server that is running.4. In Windows, select Start automatically.5. Click Apply.6. In Petrel, select File > Advanced options.7. Make sure that the Install CodeMeter detector check box is selected.8. Click OK.

A service is installed to detect when a dongle is removed or inserted.9. Restart the License Server.10. Start Petrel.

NOTE: If you switch between wireless and cable-based connections while Petrel is running or after hibernation, areconnection with the license server may fail because of a network conflict.

Petrel disconnects from the license server or loses the license on a regular basis

Follow these steps:

1. Upgrade CodeMeter to the latest version.2. Swap a new Petrel dongle.3. Update Petrel dongle Certified Time.4. Use a different USB port.

Support for 4K (and higher resolution) monitors4K (and higher resolution) monitors can be used with Petrel with low, medium, and high DPI settings, ranging from 100%to 200% DPI. The advised display setting using 4K resolution (3840 x 2160) is 150-175% DPI. In this scenario, most PetrelUIs scale proportionally and consistently.


14

NOTE: To set 175%, click Set custom text size (DPI), make your selection and sign out/sign in.

Petrel has a few UIs that are still unable to handle high display scaling correctly. An alternative, if this is an issue, is toreduce the resolution to 3K (2560 x 1440) in combination with 100% or 125% DPI. In that scenario, all UIs should workcorrectly.

NOTE: In Windows 10, the Display settings dialog box has an option for dynamic display scaling. This is simply amonitor magnifier, and everything on the screen will be scaled. The scaling approach is sub-optimal. Signout/Sign in is strongly recommended for the best display scaling quality and experience.

NOTE: 4K monitors have a significantly higher number of pixels which require sufficient graphics card support.

NOTE: In a multi-monitor setup, the best results are achieved where all the monitors have the same resolution(different scaling has no detrimental effect, for example, a 4K laptop @250% + a 4K 32" monitor @150%).

Ergonomics and alternative input devicesPetrel ribbons and other features are designed to improve the overall ergonomics. Data-centered workflows aresupported through tools like Petrel Search, window toolbars, tool palettes, inspectors, object players, context menus andmini-toolbars. Furthermore, global and in-context keyboard shortcuts are available for direct action. Finally, ribbons canbe navigated via key tips (invoked with the keyboard ALT key).

We are aware that people can have ergonomic issues, and that there are products out there, which can help to reducesuch issues. Many of these products may work with Petrel, although we cannot guarantee that they will.

One product that has worked with Petrel is the 3Dconnexion Space Mouse joystick (www.3dconnexion.com). Petrel hasbuilt-in support for space mouse joystick control of the 3D Window camera movements. See Schlumberger CustomerCare Center for more info: CCC Knowledge Article kb6948320 .

Petrel should in principle work with any Microsoft Windows compatible input device. Below are some examples of otherdevices that may work with Petrel. Others may also work with Petrel.

Wacom Cintiq 27QHD pen and touch display (http://www.wacom.com)

• Pressure sensitive pen• Remote control with customizable buttons• Screen can be tilted

Evoluent Vertical Mouse (https://evoluent.com)

• Ninety degree rotation of the hand position• Right-handed and left-handed versions

Sun-Flex ProTouch touch and button pad (http://www.sun-flex.com/en/products/protouch/)

• Placed in front of the keyboard• Standard mouse features (mouse buttons and cursor control)

Recommended tested hardware solutionsSchlumberger regularly tests hardware from a variety of vendors.

The tables below list a sampling of the hardware products used in the Petrel commercialization cycle. For detailedinformation about the laptops and workstations listed here, contact the SIS organization.

REQUIREMENTS

Ergonomics and alternative input devices 15

HTTP://WWW.3DCONNEXION.COM

HTTPS://WWW.SOFTWARE.SLB.COM/SUPPORT/LIBRARY/KBARTICLES/KB6948320

HTTP://WWW.WACOM.COM

HTTPS://EVOLUENT.COM/

HTTP://WWW.SUN-FLEX.COM/EN/PRODUCTS/PROTOUCH/

NOTE: Schlumberger routinely tests the latest hardware available from major suppliers. To minimize unexpectedproblems and costs, contact your Schlumberger sales representative.

Most hardware vendors offer highly customizable options of each workstation model. To ensure that yourworkstation selection meets Petrel system requirements, note the individual workstation specificationsinstead of relying on a model number. As a general rule, the hardware used should not be more than twoyears older than the Petrel version running on it.

Tested laptops

High-end laptops Mid-range laptops

• Dell 7740/7540• HP Zbook 17/15• Lenovo P73/P53

• Dell 5540• HP Zbook Studio• Lenovo P53s

Tested workstations

High-end workstations Mid-range workstations

• Dell T7920/T7820• HP Z8/Z6• Lenovo P920/P720

• Dell T5820• HP Z4• Lenovo P520

Additionally, smaller platforms (desktop and laptop) in the 'workstation' ranges from the above manufacturers haveshown to perform well in light geoscience workflows or with very small datasets:

• HP Z1 all-in-one workstation series• HP Z240 desktop workstation series• Lenovo P310 desktop workstation series• Dell 3510 mobile workstation

NOTE: Although the hardware listed here has been tested, it is not certified for use by Schlumberger. Problemsbeyond the control of Schlumberger (for example, driver bugs, BIOS bugs, operating system limitations) mayaffect individual experiences.

Petrel Geophysics recommendationsIf you use the Geophysics module to view large 2D lines and 3D surveys and if you use the volume rendering feature,Schlumberger recommends that you use:

• A high-end graphics card with at least 4 GB memory• As much memory as your hardware and operating system permits and at least 32 GB RAM

Graphics cards

Levels Graphics card

High NVIDIA Quadro P6000 or P5000

Medium NVIDIA Quadro P5000 or P4000

Minimum NVIDIA Quadro P4000


16

For better performance, use multiples of serial-attached SCSI (SAS) 15K RPM, SSDs or PCIe based flash. Consider:

• Storage capacity (for example, 500 GB)• Rotational speed (for example, 15K RPM)• Interface (SATA, SAS, PCIe)

Setup scenarios

Scenario Operating system RAM Graphics cardRAM

Seismic texturecache

Seismic cache

Seismicinterpretation

64-bit system(Windows 10)

32 to 96 GB 1.5 to 4 GB 768 MB to 3 GBdepending ongraphics RAM

Up to 180 GB,depending on RAM

Seismic andgeobodyinterpretation

64-bit system(Windows 10)

32 to 192 GB 4 to 8 GB 2 to 4 GB Up to 180 GB,depending on RAM

Network storage recommendationPetrel projects and associated data may be stored on a network drive on a central file server. Often, access to theseprojects could become a performance issue due to network congestion or as a result of using an inadequate Windowsnetwork protocol.

To efficiently access project data stored on a network shared drive use Windows SMB3 network protocol. This protocolis available by default for Windows 10. Your network storage system must be able to support this protocol. Contact yourstorage provider if you need assistance.

The combination of the 64-bit Windows operating system with the SMB3 protocol can significantly enhance ReferenceProject workflows and access to Petrel data, in general.

Remote visualization supportMany organizations are moving to a centralized application delivery model using thin-client technology. Petrel can beused in this way if the environment is properly configured to meet application and workflow requirements.

Schlumberger IaaS (Infrastructure as a Service) is the SIS-supported solution for E&P application centralization andprovides a full, dedicated infrastructure designed to provide optimal performance for SIS Platform technologies. Thesolution provides an end-to-end service option for customers.

Other solutions may work as well, but are not supported. For customers implementing an internally developed convergedinfrastructure solution, we recommend validation of the specific solution through our Validation Framework service. Thisservice helps define baseline performance characteristics and expectations of the environment. Please contact youraccount manager for further information on the validation framework service.

Schlumberger IaaS (Infrastructure as a Service)

Schlumberger IaaS provides a full E&P computing environment as a converged infrastructure, including systems, storageand networks. Extensive validation testing has been conducted to ensure the solution provides optimal performance* forSIS Platform technologies. The converged infrastructure approach means that the entire solution can be delivered as amanaged service, taking the E&P workload off the shoulders of the internal IT organization.

A full Schlumberger IaaS solution can be defined through a simple requirements assessment process and delivered to thecustomer pre-loaded with standard virtual images and Schlumberger software, including Petrel.

If you are seeking to deploy Petrel in a centralized architecture, please contact your account manager for furtherinformation.

REQUIREMENTS

Network storage recommendation 17

NOTE: Bandwidth, latency and network quality can impact the quality and performance of visualizationtechnologies.


18

Installation

Pre-requisitesPetrel is a complete package installation. Installation requires:

• A workstation that is running a supported operative system.• At least 5 GB of free disk space in the installation directory to install Petrel• 3 GB on the C: drive for system files• Administrator rights on the local system

You can install this version of Petrel on a system that already has previous versions of Petrel. However, if you want thisversion of Petrel only, you must uninstall the older versions.

NOTE: If you plan to install a future version of Petrel that includes plug-ins such as Production or Drilling, refer tothe plug-in release notes for an installation overview and steps on verifying the installation.

Download the installation packageThe Petrel installation package is available on DVD or by download from the Software Download Center.

NOTE: If you are a new user to the Software Download Center, you must register before you can downloadproducts.

1. Go to the Schlumberger Software Download Center.2. Click SIS.3. Log in to the site.4. On the Welcome Message page, click Continue.5. In the Products list on the left side of the page, click Petrel.

6. In the list of packages, locate the Petrel package that you want to download and click .

You can download a full version or you can download a specific upgrade, extension, or plug-in.

Install Petrel1. Insert the DVD or navigate to the location where you downloaded the installation files.2. In the DVD browser, from the root folder, run PetrelPlatformInstaller.exe.

The License Terms & Conditions panel appears.3. On the License agreement panel, read the agreement, select I accept the terms in the license agreement, and then

click Next.4. On the Prerequisite Check panel, inspect warnings or errors by hovering over the icon and then click Next.

For optimal performance, all checks should show a green check mark.5. On the Destination Folder panel, accept the default folder, or click Change to select the folder where you want to

install Petrel, and then click Install.

NOTE: You must install Petrel on a local drive (a drive that is locally installed on your system), or refer to deployPetrel on a network shared disk.

INSTALLATION

Pre-requisites 19

https://www.sdc.oilfield.slb.com/

6. When the installation completes, click Finish.

Run the installation executable from the command lineYou can execute PetrelPlatformInstaller.exe from the Windows command line. The executable program supports theseoptions:

Option Description

/? or /Help Lists available commands

/InstallFolder="C:\CustomInstallPath\" Identify the directory name for the installation

/Silent /Install Install with no UI

/Silent /Uninstall Uninstall with no UI

A log file is automatically created for each installation and stored in the user’s %TEMP% directory.

Deploy Petrel without using the installation executableInstalling Petrel without using PetrelPlatformInstaller.exe is possible but not recommended and can lead to a corruptedinstallation if attempted. Please contact your account manager for more information before creating a custom installer.

INTERSECT ConnectorYou do not need to choose the INTERSECT connector version during Petrel installation. Instead, multiple INTERSECTconnectors will be installed simultaneously and you can select the INTERSECT connector you want to use in Petrel byaccessing File > Options > Select INTERSECT Connector. Switching the connector only takes effect when Petrel isrestarted. Petrel stores the selection details in the following file: %APPDATA%\Schlumberger\Petrel\20xx\IntersectConnector.xml

Configuring the default INTERSECT Connector

By default, the latest commercial version of INTERSECT Connector is active the first time Petrel is started. Systemadministrators can define a different default INTERSECT connector prior to roll-out. This can be configured by creating anIntersectConnector.xml file in Extensions\Schlumberger\INTERSECT subdirectory of the Petrel installation directory. Forexample:

C:\Program Files\Schlumberger\Petrel 20xx\Extensions\Schlumberger\INTERSECT\IntersectConnector.xml

The xml file must contain the following:

<IntersectConnector><intersect>INTERSECT version</intersect><iscommercial>True/False</iscommercial><override>True/False</override></IntersectConnector>

For example, to define 2018.1 INTERSECT Connector as the default, you can specify the following:

<IntersectConnector><intersect>2018.1</intersect><iscommercial>True</iscommercial><override>False</override></IntersectConnector>


20

override =True/False: If set to False, the users will not be able to change the INTERSECT connector throughthe Select INTERSECT Connector dialog box in Petrel.

iscommercial = True/False: Petrel will always attempt to load the latest commercial connector correspondingto the specified INTERSECT version. The iscommercial setting controls the behavior when no matching commercialconnector is found, and a matching pre-commercial connector is available. If set to True, the pre-commercial connectorwill not be loaded. If set to False, the pre-commercial connector will be loaded.

Default SLB pluginsThe Petrel Installer now installs any plugins that reside in the Plugins folder of the Petrel distribution (you can add othersto this folder).

It will install each in turn and write the plugin install log in %temp% alongside the main installer log. If the plugin installfails, an error message is displayed in the installer GUI.

The plugins appear in the Plug-in Manager; however, they cannot be disabled or uninstalled from the Plug-in Manager.

All these plugins can be disabled using the command line format:

C:\Program Files\Schlumberger\Petrel 20xx>PluginManager.exe /disable /allusers ‘PluginID’ Petrel.exe

Where 'PluginID' can be found using the command line format:

C:\Program Files\Schlumberger\Petrel 20xx>PluginManager.exe /list Petrel.exe

'PluginID' is the second attribute in any line returned by the list command - examples highlighted below:

All the plugins can be uninstalled from Control Panel under 'Uninstall a program'. All the plugins can also be uninstalledusing the command line format:

C:\Program Files\Schlumberger\Petrel> 20xx>PluginManager.exe /uninstall /allusers ‘PluginID’ Petrel.exe

MSI packages for the default plugins are available in the Plugins folder of the Petrel distribution for those runningscripted installations (see also Knowledge Base Content ID 6969918).

Deploying Petrel on a network shared diskDeploying Petrel on a network shared disk offers these advantages:

INSTALLATION

Default SLB plugins 21

HTTPS://WWW.SOFTWARE.SLB.COM/SUPPORT/LIBRARY/KBARTICLES/KB6969918

• Easy and efficient deployment of Petrel• Single configuration file for all Petrel users• Transparent configuration and installation of updates for all Petrel users

Deploying Petrel on a network shared disk reduces the management burden for system administrators. They can install,configure, and maintain the application in one location only.

Also, the system administrator can configure a single Petrel configuration file to standardize license packages andspecific Petrel settings for all Petrel users. For detailed information, refer to Create a global configuration file tostandardize system settings and Deploy plug-ins from a network shared folder.

Deploy Petrel

Before beginning this procedure, you must be familiar with installing Petrel and you must already have access to afunctional Petrel license.

NOTE: A system administrator must perform this procedure. Petrel users cannot launch Petrel directly from thenetwork path where the distribution resides. Petrel users must map the network shared folder on their localworkstation.

NOTE: When running Petrel from a network shared disk performance is affected depending on network latency.Network shared installations cannot benefit from the Petrel startup optimization and caching, which has animpact on the Petrel startup performance.

1. From the workstation, install Petrel.2. Copy the entire installation folder where Petrel was installed (for example, C:\Program Files\Schlumberger

\Petrel 20xx) from the local workstation to a folder on the network shared disk (for example, P:\GlobalPetrel\Petrel 20xx).

3. On each workstation that will run Petrel, complete these steps:a. Go to the location on the shared disk where Petrel was copied and create a shortcut for the Petrel executable.

Place the shortcut on the desktop.b. Install all the applications from the RuntimeEnvironment folder (which is located in the Petrel Installation folder) if

they are not already installed on the workstation:

• NDP452-KB2901907-x86-x64-AIIOS-ENU.exe• Windows6.1-KB2533623-x64.msu• vcredist_x64.exe• vcredist_x86.exe• vcredist_2008_ATL_x86.exe• SQLSysClrTypes.msi (only to connect to Studio Database on SQL server)

4. Execute the caspol.exe command to configure the runtime security policy for the machine. Here is an example of ascript you can modify for your use.

%windir%\Microsoft.NET\Framework64\v4.0.30319\caspol.exe -quiet -machine -reset %windir%\Microsoft.NET\Framework64\v4.0.30319\caspol.exe -quiet -enterprise -reset %windir%\Microsoft.NET\Framework64\v4.0.30319\caspol.exe -quiet -machine -addgroup 1 -url "file://\\your.server.com\Global Petrel\Petrel2020\*" FullTrust -name "Petrel_fulltrust" -description "Allow exe and dll from directory on Network drive to run with full .NET trust, necessary for calling native code."


22

%windir%\Microsoft.NET\Framework64\v4.0.30319\caspol.exe -quiet -enterprise -addgroup 1 -url "file://\\your.server.com\Global Petrel\Petrel2020\*" FullTrust -name "Petrel_fulltrust" -description "Allow exe and dll from directory on Network drive to run with full .NET trust, necessary for calling native code."

Modify \\your.server.com\Global Petrel\Petrel2020\ for your own environment.

Executing the caspol command updates system security at the machine and enterprise policy level. This allows .exeand .dll files on the shared folder to run Petrel with full .NET trust.

Resetting the policies removes existing policies that may have been configured at the site. Use caution when youreset a policy

5. Launch Petrel from the shortcut that you created.6. Define the license server environment.

Create a global configuration file to standardize system settings

If you want to standardize Petrel system settings for multiple users, create a global configuration file. Petrel stores theuser system settings in the PetrelConfiguration.xml file. The first time you run Petrel and exit, the file is created in thefolder named %APPDATA%\Schlumberger\Petrel\20xx.

For Windows 10, the application data and settings folder is C:\Users\<username> \AppData\Roaming\Schlumberger\Petrel\20xx.

The PetrelConfiguration.xml file contains this information:

• Settings configured in the Select license package window, such as package name and favorite package• Settings configured using File > System > System settings.

NOTE: If you change these settings, the changes are stored in the PetrelConfiguration.xml file each time you exitPetrel.

For more information, refer to System settings in the Help Center.

To create a global configuration file:

1. Open Petrel.2. Configure your license packages in the Select license package dialog box.3. Configure your system settings in Petrel.4. Close Petrel.

Your PetrelConfiguration.xml file is updated with the settings that you selected, and it is ready to be distributedglobally.

5. Copy the PetrelConfiguration.xml file to a shared disk drive that all users can access, and set it to read only.

Remove these lines from the global configuration file:

<UseGlobalSettingsFile Value="True"/><GlobalSettingsFile Value=""/>

6. To enable Petrel users to use the global configuration file, you need to set their local configuration file to point to theglobal PetrelConfiguration.xml file.

INSTALLATION

Deploying Petrel on a network shared disk 23

Make a copy of the PetrelConfiguration.xml file created in Step 5 and remove everything from the file except theselines:

<?xml version="1.0" encoding="us-ascii" standalone="no" ?><Configuration><SystemSettings><UseGlobalSettingsFile Value="True"/><GlobalSettingsFile Value="E:\PetrelConfiguration.xml"/></SystemSettings> </Configuration>

NOTE: For the GlobalSettingsFile Value, replace E:\PetrelConfiguration.xml with the path to the shared folder whereyou place your global configuration file.

Copy the new PetrelConfiguration.xml file to the %APPDATA% folder on all Petrel user machines. Typically, you copy thenew PetrelConfiguration.xml file to this default folder on Windows, which is C:\users\<username>\AppData\Roaming.

When Petrel starts, Petrel uses the settings defined in the global configuration file (PetrelConfiguration.xml). Aftercompletion of the first Petrel run, a new PetrelConfiguration.xml file is created (if it does not exist) in the user data andsettings location. This file is identical to the global configuration file. It allows individual users to personalize their ownPetrel environment for an individual session without modifying anyone else’s settings. The settings in the globalconfiguration file overwrite the personalized settings when Petrel is restarted.

Users can also select the global configuration file in the Define license server environment window. Refer to DeployingPetrel on a network shared disk for more information about selecting the global configuration file.

Lines can be deleted from the global configuration file, and only settings that correspond to the remaining lines in theglobal configuration file can be controlled globally. The user can control settings that do not have corresponding lines inthe global configuration file.

Petrel Coordinate System ManagerInstalling Petrel also installs the Petrel Coordinate System Manager. The Petrel Coordinate System Manager enables youto manage and customize the Petrel Coordinate Reference System catalog.

A geodetic expert can use the Petrel Coordinate System Manager to manage and customize the enterprise and extensioncatalogs used by Petrel. These catalogs provide the coordinate reference systems that are available in Petrel in theCoordinate reference system selection dialog box. From the Coordinate reference system selection dialog box, a Petreluser can select the appropriate coordinate reference system for a Petrel project.

If the default catalog has not been changed, Petrel can be upgraded directly from Petrel 2010.1 to this version of Petrel.

If the default catalog has been customized or replaced, a migration must be performed in order to make thecustomizations available in this version of Petrel.

For more information about the Petrel Coordinate System Manager, refer to the Petrel Coordinate System Manager OnlineHelp.

Migrate 2015.1 catalog files

If you used Petrel Coordinate System Manager 2015.x to customize the enterprise or extension catalog, you can migratethese catalogs to the 2016 catalogs that are used by Petrel Coordinate System Manager 2016 and onward.

• If you stored the 2015.1 enterprise or extension catalog in the default location %APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration\2015.1, the software migrates the catalogs for you.

• If you stored the 2015.1 catalogs in another location, for example, on a shared network drive, or if you want to migrateolder catalogs, for example, 2013.1 catalogs, you must manually enter the catalog locations in the


24

CoordinateCatalogConfiguration.xml file before you can open Petrel Coordinate System Manager 2020 or theCoordinate reference system selection dialog box in Petrel 2020.

1. Navigate to the xml directory in your Petrel 2020 installation directory and open theCoordinateCatalogConfiguration.xml file. For example, C:\Program Files\Schlumberger\Petrel 2020\xml.

2. Locate the section  and update the default enterpriseand extension catalog file locations. For example, if you migrate 2015.1 catalogs, enter the location of the 2015.1catalog files.a. To update the enterprise catalog file location, update this value with catalog file location:

<Catalog name="CopyFromEnterpriseCatalog"> <value>%APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration\2015.1\CoordinateCatalogEnterprise.ctl</value></Catalog>

b. To update the extension catalog file location, update this value with the catalog file location:

<Catalog name="CopyFromUserdefinedExtensionCatalog"><value>%APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration \2015.1\CoordinateCatalogExtensions.ctl</value></Catalog>

3. Save and close the configuration file.4. Migrate the catalogs by performing one of these actions:

• Launch Petrel Coordinate System Manager.• Launch Petrel and open an existing Petrel project or create a new one.

Re-migrate catalog files from older versions

Catalog files from previous versions (prior to 2015.1) are not automatically migrated. You must manually migrate them bymodifying the CoordinateCatalogConfiguration.xml file (refer to Migrate 2015.1 catalog files).

However, as an example, if you opened the Petrel Coordinate System Manager or the Coordinate reference systemselection dialog box in Petrel before you migrated your older catalog files, for example, your 2013.1 catalog files, you canuse this procedure to re-migrate your older catalog files to 2020.x.

NOTE: You can also use this remigration procedure if you opened Petrel Coordinate System Manager or theCoordinate reference system selection dialog box before you modified theCoordinateCatalogConfiguration.xml file with the location of your older catalog files stored on a networkshared drive.

1. Delete the default location for the 2020.x catalog files that are used by Petrel Coordinate System Manager 2020.x:%APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration\2020.x

2. Navigate to the xml directory in your Petrel 2020.x installation directory and open theCoordinateCatalogConfiguration.xml file. For example, C:\Program Files\Schlumberger\Petrel 2020\xml.

3. Locate the section  and update the default enterpriseand extension catalog file locations.a. To update the enterprise catalog file location, update this value with the location of your catalog file from an older

version, for example, 2013.1:

<Catalog name="CopyFromEnterpriseCatalog"> <value>%APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration \2013.1\CoordinateCatalogEnterprise.ctl</

INSTALLATION

Petrel Coordinate System Manager 25

value></Catalog>

b. To update the extension catalog file location, update this value with the location of your catalog file from an olderversion, for example, 2013.1:

<Catalog name="CopyFromUserdefinedExtensionCatalog"><value>%APPDATA%\Schlumberger\Petrel\CRSCatalogConfiguration\2013.1\CoordinateCatalogExtensions.ctl</value></Catalog>

4. Save and close the configuration file.5. Migrate the catalogs by performing one of these actions:

• Launch Petrel Coordinate System Manager 2020.x.• Launch Petrel 2020.x and open an existing Petrel project or create a new one.

Uninstall Petrel

NOTE: The installer detects installed Ocean plug-ins and uninstalls the plug-ins before uninstalling Petrel.

If Ocean plug-ins were installed on a shared network disk, you may need to uninstall each plug-in separatelybefore uninstalling Petrel, depending on how the plug-ins were initially installed.

1. From the Start menu, open the Control Panel, then click Uninstall a program.2. In the list of currently installed programs, select the Petrel application, and then click Uninstall.


26

Plug-ins

The Ocean Plug-in Manager enables you to access, organize, and manage plug-ins within Petrel. Plug-ins can come froma variety of sources. They may be:

• Distributed from the Ocean Store• Developed internally within your company• Developed as third-party plug-ins

The Ocean Plug-in Manager uses a Petrel plug-in installer package (.pip) for packaging and distributing plug-ins. You donot need to run an installer application to install or uninstall a plug-in.

From the Ocean Plug-in Manager, you can access plug-ins from two locations:

• Plug-ins published in the Ocean Store• Plug-ins developed by your own organization and available on your network

The information in this chapter is for system administrators. This chapter tells you how to customize the deployment ofplug-ins and how to customize the Ocean Plug-in Manager interface to enable or disable features.

Installing and uninstalling plug-ins

Ocean for Petrel is a public, open API that sits on top of Petrel. You can use Ocean for Petrel to develop plug-ins thatextend Petrel capabilities.

Each plug-in includes its own installer and targets a specific version of Petrel. When a plug-in is installed, it registersitself to let Petrel know that it exists and also to provide information on how it can be uninstalled. If the plug-in isuninstalled, it unregisters itself from Petrel.

If you uninstall Petrel, Petrel checks for plug-ins and prompts you to uninstall the registered plug-ins. Uninstalling all plug-ins is recommended if you uninstall Petrel.

Plug-in licenses

When you order a Petrel plug-in from the Ocean Store, full instructions for installing and activating the plug-in license areincluded in the email that is sent to you. You can also find this information on the Ocean Store’s Help page.

Plug-in ManagerThe Petrel.exe.config configuration file contains the Ocean Plug-in Manager settings. You can find Petrel.exe.config in thePetrel installation folder. For example:

C:\Program Files\Schlumberger\Petrel 20xx\Petrel.exe.config

NOTE: Back up the Petrel.exe.config file before editing.

Customize the Plug-in Manager interface

1. If Petrel is open, close it.

2. Open the Petrel.exe.config file.3. Find the <configSections> tag and add this section, if it is not there:

<sectionGroup name="applicationSettings" type="System. Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0,

PLUG-INS

Plug-in Manager 27

HTTP://WWW.OCEAN.SLB.COM

Culture=neutral, PublicKeyToken=b77a5c561934e089"><section name="Slb.Ocean.Petrel.PluginManagerUiElements.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/></sectionGroup>

This code enables configuration settings under a separate <application Settings> tag.4. Inside the <configuration> tag, on the same level as the <configSections> tag, add this section if it is not

there:

<applicationSettings> <Slb.Ocean.Petrel.PluginManagerUiElements.Properties.Settings> </Slb.Ocean.Petrel.PluginManagerUiElements.Properties.Settings></applicationSettings>

5. Inside the <Slb.Ocean.Petrel.PluginManagerUiElements. Properties.Settings> tag, add thesettings you want to modify. Use this format:

<setting name="SettingName" serializeAs="Type"> <value>Value</value></setting>

For example:

<setting name="StoreTabEnabled" serializeAs="String"><value>True</value></setting>

6. Use this same format to change these additional Plug-in Manager settings:

• StoreTabEnabled: Set as True if you want the Plug-in Manager’s Store section enabled.• SecurityTabEnabled: Set as True if you want the Plug-in Manager’s Security section enabled and visible.• CorporateTabEnabled: Set as True if you want the Plug-in Manager’s Corporate section enabled and visible.• InstallPluginButtonEnabled: Set as True if you want the Install Plug-ins feature enabled in the Plug-in

Manager. This feature is available only for plug-ins packaged with a Petrel plug-in installer package (.pip file).• UpdatePluginButtonEnabled: Set as True if you want the Update Plug-in feature enabled from the Plug-in

Manager.• AddTrustedPublisherButtonEnabled: Set as True if you want the Add Trusted Publisher feature

enabled.• RemoveTrustedPublisherButtonEnabled: Set as True if you want the Remove Trusted Publisher

feature enabled.• ChangeSecurityLevelEnabled: Set as True if you want the Change Security Level feature enabled.

7. Save the file.

Deploy plug-ins from a network shared folderThe Ocean Store is the designated website where scientists and engineers can access and download plug-ins to usewith Petrel. Plug-ins developed by other companies for their internal use are not available in the Ocean Store.

A system administrator can use the Ocean Plug-in Manager to configure the internal source for plug-ins (for example,network shared folders) to distribute and deploy plug-ins within Petrel. These plug-ins are available in the Corporatesection of the Ocean Plug-in Manager.


28

NOTE: The Ocean Plug-in Manager cannot browse plug-ins directly from the network path where the plug-insreside. Petrel users must map to the network shared folder on their local workstation.

1. If Petrel is open, close Petrel.2. Open the Petrel.exe.config file.3. Find the <configSections> tag and add this section, if it is not there:

<sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"><section name="Slb.Ocean.Petrel.PluginManagerUiElements. Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false"/></sectionGroup>

This enables the configuration settings under a separate <applicationSettings> tag.4. In the <configuration> tag, on the same level as the <configSections> tag, add this section if it is not

there:

<applicationSettings><Slb.Ocean.Petrel.PluginManagerUiElements.Properties.Settings></Slb.Ocean.Petrel.PluginManagerUiElements.Properties.Settings></applicationSettings>

5. In the <Slb.Ocean.Petrel.PluginManagerUiElements. Properties.Settings> tag, make surethat this setting is set to True:

<setting name="CorporateTabEnabled" serializeAs="String"> <value>True</value></setting>

6. In the <Slb.Ocean.Petrel.PluginManagerUiElements. Properties.Settings> tag, add thissection if it is not there:

<setting name="LocalStoreDirectories" serializeAs="Xml"><value><ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> </ArrayOfString></value></setting>

7. Inside the <ArrayOfString> tag, add the folder locations where Ocean plug-ins can be located. You can add asmany locations as you need. For example:

<string>H:\Corporate Plug-ins</string><string>D:\My Developed Plug-ins</string><string>I:\Asset Team Plug-ins</string><string>\\myServer\MyFolder</string>

PLUG-INS

Deploy plug-ins from a network shared folder 29

NOTE: • Deploy your Ocean plug-in PIP files or assembly files into subfolders of the root folder configured inPetrel.exe.config.

• Use PIP files for faster resolution of the plug-in list in the Corporate tab.• Plug-ins that are already installed locally will not show up in the Corporate tab.• You can use this procedure to set a local folder (for example, C:\my developed plug-ins) as the

location of the plug-ins directory.

8. Find the <runtime> tag and add this section:

<loadFromRemoteSources enabled="true" />

NOTE: Refer to this Microsoft Knowledge Base article for more information about this setting.

9. Save the file.10. From a DOS shell, run the caspol command to configure the machine’s runtime security policy. This command

enables your system to trust the execution of .exe and .dll files from a network shared folder.a. Change to this directory:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319b. From this location, run caspol.exe:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319> caspol.exe -quiet -machine -addgroup 1 -url "\\myServer\MyFolder\*" FullTrust -name "Petrel_fulltrust” -description "Allow_exe_and_dll_to_run_with_full_.NET_trust"

You can run the caspol.exe command from a DOS shell, but make sure that you change \\myServer\MyFolder\* tothe location where your plugin assemblies are. This location must be accessible when you execute the caspolcommand.

The caspol command updates your system security at the machine policy level. You can find the security policyupdates at:

• %WINDIR%\Microsoft.NET\Framework64\version directory\config\Security.config

• %WINDIR%\Microsoft.NET\Framework64\version directory\config\Security.config.cch

NOTE: Do not open these files you unless you are familiar with them. Incorrect changes to these files couldmake your system unstable.

11. Repeat step 10 for each network shared folder that you want Ocean Plug-in Manager to browse for plug-ins.

Change the default location of the [plug-ins home] directoryPlug-ins are usually deployed or installed in a directory under [Petrel Home] called \Extensions (for example, C:\Programs Files\Schlumberger\Petrel\ 20xx\Extensions). This folder is considered the default[Plug-ins Home] directory.

1. If Petrel is open, close Petrel.


30

HTTP://MSDN.MICROSOFT.COM/ENUS/LIBRARY/DD409252(VS.100).ASPX

2. Open the PluginManagerSettings.xml file.

Find the <DefaultDirectory> tag (for example, <DefaultDirectory Name="Default"Location="C:\Program Files\Schlumberger\ Petrel 20xx\Extensions\" />).

3. Enter the address for the new [Plug-ins Home] location (for example, <DefaultDirectoryName="Default" Location="D:\My Documents\ My Plug-ins\" />).

NOTE: • You must have read/write access to the new [Plug-in Home] directory.• The [Plug-in Home] directory may be located on a network shared folder. The system

administrator must execute the caspol.exe command to configure the machine runtime security policy(refer to Deploy plug-ins from a network shared folder for more details).

4. Save the file.

NOTE: Plug-ins that use installers for deployment may be deployed under [Petrel Home]\extensions. Onlyplug-ins deployed or installed from the Plug-in Manager are guaranteed to be deployed automatically in thecustomized [Plug-in Home].

Plug-in troubleshooting

Access denied during plug-in installation

If you try to install a plug-in into a restricted location on your computer, the Plug-in Manager displays an Access Deniedmessage.

Plug-ins are usually deployed or installed in this directory:

[Petrel Home]\Extensions

For example:

C:\Programs Files\Schlumberger\Petrel 20xx\Extensions

The [Petrel Home]\extensions directory is the default [Plug-ins Home] directory. If you receive anAccess Denied message while installing a plug-in, the access to [Petrel Home] and/or [Plug-ins Home] ismost likely restricted.

To allow the Plug-in Manager to install plug-ins, change the default [Plug-ins Home] directory as described in Change the default location of the [plug-ins home] directory.

Petrel Startup Optimization optionThe Startup Optimization setting runs a native image generator (Ngen) tool that improves the performance of managedapplications. The installation process enables this setting by default.

Ngen is a Native image generator tool that improves performance of managed applications. Ngen.exe creates nativeimages (files containing compiled processor-specific machine code) and installs them into the native image cache onyour local computer. The runtime executable uses these images from cache instead of using the just-in-time (JIT)compiler to compile the original assembly.

Ngen compilation is on by default. After Petrel is installed and your system is idle, Ngen begins to create native imagesand store them in a hidden directory (C:\Windows\assembly\NativeImages_v4.0.30319_64). This processis transparent; the system controls when to create the native images and when to use them.

PLUG-INS

Plug-in troubleshooting 31

Never delete this directory. It contains many files; some belong to Petrel (these are identified by an .slb extension) andothers belong to other applications. The files are removed when Petrel is uninstalled.

Install Ngen manually

1. Open a Command prompt and change to the Petrel installation directory. (Usually, this directory is C:\ProgramFiles\Schlumberger\Petrel 20xx).

2. At the Command prompt, enter ngenrun.bat install.

To uninstall, enter ngenrun.bat uninstall.

Both the install and uninstall process take several minutes.

Ngen significantly increases Petrel startup time. However, you must evaluate your own situation with your IT staff; incertain situations, startup optimization must be turned off.


32

Enhanced summary file format

The simulator output for summary results in the form of *.(F)SMSPEC and *.A/Sxxx files reflects the way the simulatorsolves the mathematical equations for increasing time. Accessing the data for a particular summary vector–usually forplotting against time–requires the entire data set. This access pattern is poorly supported by the simulator outputmentioned previously, more so if the data is located on a network drive. In effect, accessing summary data often results inhigh access times over network connections. This is the primary motivation behind the introduction of a new, enhancedfile format for storing summary data from Petrel 2017 onward. Requesting summary data in this new file format results ingreatly increased access speed over network connections.

The recommended workflow is to make the conversion to the enhanced summary file format part of the simulationsubmission job rather than through Petrel.

Conversion-related worksteps in Petrel

When you load a Petrel project, whether it is a legacy project or not, Petrel checks whether conversion is needed. If so,the conversion process to the new file format is started in the background without impeding Petrel itself. Names ofindividual cases being converted appear in red font with the addition (summary conversion being active...) as seen in thefigure:

NOTE: If the data is stored on a network location, do not access summary data for a case during the conversion.Although you can access the data, you do not benefit from increased summary data performance until theend of the conversion.

If you decide not to use the enhanced summary file format for a particular case, open its settings dialog by right-clickingthe case. Then select the Results import tab and clear the Use enhanced summary file format check box.

Generally, Petrel ensures that the enhanced summary file format is being used and kept up-to-date. However, you havethe option to enforce conversion by right-clicking on a simulation case, case folder, or case collection and selectingConvert summary data into enhanced summary file format on the popup menu.

If this option is disabled (displayed with gray text), Petrel either has not found any summary data for the case or the optionselection has been cleared in the Results import tab on the case.

The message log displays several messages that explain the process.

Technical detailsConversion into the enhanced summary file format can occur in one of two ways:

• As part for the simulation submission workflow: After successfully completing the simulation, the conversion to theenhanced file format is triggered as a port-processing step before the results are loaded back into Petrel. This is therecommended workflow because it hides the conversion time.

• When importing the deck into Petrel or loading the results: Petrel checks whether conversion is needed. In this case,the conversion takes place on the machine where Petrel is installed. Although the conversion is done withoutimpeding Petrel, it is not recommended that you allow Petrel to do the conversion because it can be expensive interms of resources needed (time and memory).

Preferred workflow for conversion

Conversion from the simulator output for the summary results into the enhanced summary file format may take aconsiderable amount of time, depending on the size of the summary data, network speed, and the load on the machinePetrel is running. Therefore, you are advised to make the conversion process part of the simulation submission system.This section describes three different method for making the conversion part of the recommended post-simulationworkflow.

ENHANCED SUMMARY FILE FORMAT

Technical details 33

ECLRun >= 2012

First consider ECLRun 2012, the first version of ECLRun aware of this new file format. If you submit a simulation run viaECLRun 2012, it triggers the simulation data conversion after successful completion of the simulation run. That means bythe time the results are read back into Petrel, the enhanced summary file is already created so Petrel does not need tocreate it. You benefit from the advantages of this new file format immediately.

You can control certain aspects of the conversion by editing the PetrelConfiguration.xml file.

NOTE: Before changing this file, close all instances of Petrel; otherwise, you will lose your changes when you closePetrel.

Open the file and find the section <SimulationCommands> . It should look like this:

<SimulationCommands>

<Command Name="ECLIPSE 100"><Submit>eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q %QUEUE%] [--username %USERID%] [--passwd %PASSWORD%] [%OPTIONS%] eclipse %DATAFILE%</Submit><Fetch>eclrun.exe [--passwd %PASSWORD%] check %DATAFILE%</Fetch><Kill>eclrun.exe [--passwd %PASSWORD%] kill %DATAFILE%</Kill></Command>

<Command Name="ECLIPSE 300"><Submit>eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q %QUEUE%] [--username %USERID%] [--passwd %PASSWORD%] [%OPTIONS%] e300 %DATAFILE%</Submit><Fetch>eclrun.exe [--passwd %PASSWORD%] check %DATAFILE%</Fetch><Kill>eclrun.exe [--passwd %PASSWORD%] kill %DATAFILE%</Kill></Command>

<Command Name="FrontSim"><Submit>eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q %QUEUE%] [--username %USERID%] [--passwd %PASSWORD%] [%OPTIONS%] frontsim %DATAFILE%</Submit><Fetch>eclrun.exe [--passwd %PASSWORD%] check %DATAFILE%</Fetch><Kill>eclrun.exe [--passwd %PASSWORD%] kill %DATAFILE%</Kill></Command>

</SimulationCommands>

The options are:

• hdf-converter-version• summary-conversion

Suppose you are using ECLRun 2012 and you must support submissions from both Petrel 2012 and Petrel 2014. By default,ECLRun starts the newest converter it finds. It decides this based on the file system structure, for example \ecl\2012.1\,\ecl\2012 etc. If you do not tell ECLRun explicitly to start the 2012 converter for submission from Petrel 2014, the convertedsummary file is rejected by Petrel 2014 and regenerated locally into the new file format. This can be time-consuming. To


34

avoid this, append the submission string of the Submit xml tag with [- - hdf-converter-version 2012.1]for all the simulators E100, E300, and Frontsim for the 2012 PetrelConfiguration.xml file. For example:

eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q %QUEUE%] [--username %USERID%] [--passwd %PASSWORD%] [%OPTIONS%] [--hdf-converter-version 2012.1] e300 %DATAFILE%

To suppress conversion into the new summary file format altogether, use [- - summary-conversion=no]. Forexample:

eclrun.exe [-v %VERSION%] [-s %SERVER%] [-q %QUEUE%] [--username %USERID%] [--passwd %PASSWORD%] [%OPTIONS%] [--summary-conversion=no] e300 %DATAFILE%

The location of the xml file is system-dependent. For Windows 10, the default location is: C:\Users\UsernName\AppData\Roaming\Schlumberger\Petrel\Petrel- version\

Pre-2012 ECLRun

In this case, ECLRun is unaware of the enhanced summary file format. To complete the conversion automatically at theend of the simulation run, use the stand-alone converter utility. Contact Schlumberger support to obtain the version youneed. Once the converter is properly installed, ensure it runs after the end of a successful simulation before thesimulation results are read back into Petrel. Refer to Standalone enhanced summary converter utility for additional detailsfor using the converter.

NOTE: If you have changed PetrelConfiguration.xml to include the hdf options, you should break simulationsubmissions from within Petrel 2014 with older ECLRun versions in case you should decide to downgrade.

Custom remote submission systems

For successful summary conversion, obtain the stand-alone converter from Schlumberger support. Supported systemsinclude Microsoft Windows and various Linux versions. Contact your system administrator for setup instructions. Refer to Standalone enhanced summary converter utility for additional details for using the converter.

Standalone enhanced summary converter utility

The Windows version of the stand-alone converter is installed with the Petrel installation. The executable is namedConvertSummaryData2DataBase.exe and is located in the same location as the Petrel application file petrel.exe.

NOTE: Usually, the simulation run happens on a cluster. One way to make the summary conversion part of thesubmission workflow is to install the stand-alone converter on the same machine that runs the simulation.For this, you must obtain either the Windows or Linux version of the converter from Schlumberger support.

The converter accepts two mandatory command line options:

• Either a directory or a path to a specific (F)SMSPEC file• The directory for storing temporary files

If the first argument is a directory, the converter recursively looks for (F)SMSPEC files in that directory and converts thecorresponding summary data into the new file format. In the case of a specific (F)SMSPEC file, only its summary data isconverted. The second argument could, for example, be C:\TEMP for Windows and /tmp for Linux.

Examples for Windows include:

ENHANCED SUMMARY FILE FORMAT

Technical details 35

• ConvertSummaryData2DataBase.exe C:\Users\hawaii\maui.SMSPEC C:\TEMP• ConvertSummaryData2DataBase.exe C:\Users\hawaii\maui C:\Users\foo\AppData\Local\Temp• ConvertSummaryData2DataBase.exe C:\Users\hawaii\maui %TEMP%

Linux examples include:

• ConvertSummaryData2DataBase.exe /home/hawaii\maui.SMSPEC /tmp• ConvertSummaryData2DataBase.exe /home/hawaii /users/maui/tmp• ConvertSummaryData2DataBase.exe /home/hawaii $TMPDIR

If you see errors loading shared libraries when trying to run the Linux hdf converter, you might need add the path to theshared libraries installed with ECLRun to your LD_LIBRARY_PATH environment variable. When using shell csh, this couldlook like:

$ setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/path/to/shared/libraries

To make this persistent, you must add this command to the shell config file, for example .cshrc for csh.

General considerationsThis page lists general comments about behavior, resources, and performance for the enhanced summary file format.

Best practice guidelines

• While Petrel is using the enhanced summary file (extension .h5), the file cannot be modified or deleted outside ofPetrel. This ensures that the data Petrel works with and that the user sees are in sync with the data on the disk. If youstill need to remove or change the file, you must first remove the simulation results for the particular case withinPetrel (right-click the simulation case and select Remove simulation results).

• When a project loads, Petrel warns you if any of the enhanced summary files are read-only. This might become anissue after a simulation run. In this case, when the simulation results are pulled back, Petrel cannot update theenhanced summary file returned by the simulation submission. To prevent the display of incorrect summary results,Petrel falls back to the standard summary files *.(F)SMSPEC and *.A/Sxxxx. A warning is written to the message log.

• If the option Convert summary data into enhanced summary file format (which appears after right-clicking a case) isgrayed out, either:

• Petrel has not found any summary data for this case or• The option to use the enhanced summary file format has been cleared on the Results import tab on the case

• When summary data is loaded into Petrel, the old-style summary data is in sync with the summary data in the newenhanced summary file. To keep them in sync, the converter writes the new keyword TIMESTMP (documented in theEclipse File Format Reference Manual) into the (F)SMSPEC file. This means, for conversion to work reliably, that the(F)SMSPEC file cannot be read-only.

Performance considerations

Performance can be an issue if you are working with large summary data sets. In any case, the enhanced summary fileshould be generated as part of the simulation run so it is available to Petrel by the time the results come back from remotesubmission. Performance considerations include:

• The bigger the summary data files, the longer the conversion takes.• Make sure you have sufficient main memory. Conversion is faster if more memory is available. Roughly, make sure

your #physical RAM = 2*size of summary files.• If the project data is located on a network location, a fast network connection pays off• You should request only the summary data and report steps you really need. The more data you request, the slower

the conversion and import into Petrel.• If a large amount of physical memory is available, consider setting the environment variable

SLB_FAST_SUMMARY_READER on the machine that does the enhanced file format conversion. This can speed upconversion considerably.


36

Studio Database configuration

Third-party software configuration

Single sign on

Configuring the Single Sign On authentication against Active Directory consists of three main procedures:

• Configure the Active Directory service account.• Configure the Oracle database server.• Configure the client.

To configure the client:

1. Create a krb5.conf file.2. Create Oracle net parameters (sqlnet.ora):

• Add the following parameters to the sqlnet.ora file:

SQLNET.AUTHENTICATION_SERVICES=(KERBEROS5PRE,NONE)• Add KERBEROS5 to any other authentication services that you are using.

SQLNET.KERBEROS5_CONF=c:\oracle\network\krb5\krb5.conf• This parameter points to the krb5.conf file.

SQLNET.KERBEROS5_CONF_MIT=TRUESQLNET.KERBEROS5_CC_NAME=OSMSFT://

3. Create an environment variable named TNS_ADMIN with a path that points to the location of the sqlnet.ora file.

Connecting to the databaseThe first time you log in to Studio, you must have a connection to the database.

For instructions about connecting to the database, refer to the appropriate documentation for your role:

• Database user: Open the Petrel Help Center. Navigate to Studio > Studio Database > Accessing Studio Database >Managing Database Connections > Creating a Connection to a Database.

• Database administrator: Open the Online Help in Studio Manager.

Automatic connection to a Studio repositoryA Studio administrator can enable to automatically connect to the Studio repository for each Petrel workstation. If thisoption is enabled, when the Petrel project is opened, it will automatically reconnect to the last Studio repository that wasaccessed. This way, the Studio notifications, alerts, and synchronization workflows are immediately enabled, withouthaving the Petrel user open a Studio dialog.

This option can be enabled at the application level (and deployed to all the Petrel workstations if this is the companypolicy).

A Petrel user can enable this option by clicking File > Project setup > Project settings > Studio settings > Repositorysettings.

If the option is defined from Petrel, it will take precedence over the application level.

STUDIO DATABASE CONFIGURATION

Third-party software configuration 37

The automatic connection is only available when connecting to a repository using Windows authentication with SQLServer or SSO with Oracle.

To enable the automatic connection at the application level:

1. On the Petrel workstation, open the Slb.P4E.Dbx.Config file (in the Petrel installation directory, located at ...\Schlumberger\Petrel 20xx\Extensions\Schlumberger\Studio).

2. Look for ConnectionOptionsSection in the config file and set EnableAutoConnect to True.3. Save the file.

Enable the Remember password featureA Studio administrator can enable the Remember password feature for each Petrel workstation. When enabled, aRemember password option appears in the Studio Login window. Selecting this option saves the user's password so thathe or she does not need to log in when opening Studio.

1. On the Petrel workstation, open the Slb.P4E.Dbx.Config file (in the Petrel installation directory, at ...\Schlumberger\Petrel 20xx\Extensions\Schlumberger\Studio).

2. Set ProvideSavePasswordOption to True.

The line is:

<ConnectionOptionsSection ProvideSavePasswordOption= “false” />3. Save the file.

Change the configuration for custom coordinate systemsPetrel provides coordinate reference systems from these standard authorities:

• European Petroleum Survey Group (EPSG)• Esri©

• Software Integrated Solutions (SIS)

If your company’s geodesy group uses custom coordinate systems with internally developed codes, you can prevent yourusers from making changes to the standard authority coordinate reference systems, transforms, and conflation policies.

NOTE: If you did not deploy Studio and you want to make these configuration changes, change the configuration ofthe Coordinate System Manager. If you did deploy Studio, change the configuration of Studio Manager.

A flag in a configuration file controls this behavior. By default:

• The flag for the Coordinate System Manager’s configuration file is set to True• The flag for the Studio Manager’s configuration file is set to False

Comparison of the True and False flags

AllowAdminOutOfBoxCatalog=True AllowAdminOutOfBoxCatalog=False

Default flag for Coordinate System Manager Default flag for Studio Manager

Can delete any coordinate reference system, transform, or conflationpolicy

Cannot delete any coordinate reference system, transform, or conflationpolicy

Can create any coordinate reference system, transform, or conflationpolicy, using any authority or code if there is no conflict with existingones in the catalog

Only can create coordinate reference systems, transforms, or conflationpolicies with Petrel as the authority (that is, Source=Petrel) and with acode that is within the designated ranges


38

AllowAdminOutOfBoxCatalog=True AllowAdminOutOfBoxCatalog=False

Can add a coordinate reference system or simple transform from the Esricatalog, using the code (for example, if a person deletes one and laterwants to add it back)

Cannot add a coordinate reference system or simple transform from theEsri catalog, using the code (because it cannot be deleted)

To change the configuration:

1. Open the configuration file in a text editor:

• If you did not deploy Studio, open the Coordinate System Manager configuration fileCoordinateSystemAdmin.exe.config

• If you did deploy Studio, open the Studio Manager configuration file StudioManager.exe.config.

Refer to the Studio Installation and Configuration Guide for the location of the file.2. In the ApplicationConfigurations section, change the flag for AllowAdminOutOfBoxCatalog to True or

False.3. Save and close the configuration file.

STUDIO DATABASE CONFIGURATION

Change the configuration for custom coordinate systems 39

Support information

User assistance

The full set of Petrel 2020 documentation, and documentation for any prior Petrel release, can be downloaded from the Software Integrated Solutions (SIS) Support Portal.

Contact Schlumberger

Schlumberger has sales and support offices around the world. For Technical Support information for Software IntegratedSolutions (SIS) software:

• Schlumberger Support Portal: https://www.software.slb.com/support/• Customer Care Center email: [email protected]• Support Contact Details: https://www.software.slb.com/support/contact-details. Select your country to view support

phone numbers. If your country is not listed, select the nearest location


40
