Merak Installation Guide

Merak planning, risk & reserves
Version 2013.1
Merak Installation Guide
Copyright
Copyright 1994-2012 Schlumberger. All rights reserved. This work contains the confidential and proprietary trade secrets of Schlumberger and may not be copied or stored in an information retrieval system, transferred, used, distributed, translated, or retransmitted in any form or by any means, electronic or mechanical, in whole or in part, without the express written permission of the copyright owner.
Trademarks & Service Marks

"Schlumberger," the Schlumberger logo type, and other words or symbols used to identify the products and services described herein are trademarks, trade names, or service marks of Schlumberger and its licensors, or the property of their respective owners. These marks may not be copied, imitated or used, in whole or in part, without the express prior written permission of Schlumberger. In addition, covers, page headers, custom graphics, icons, and other design elements may be service marks, trademarks, and/or trade dress of Schlumberger, and may not be copied, imitated, or used, in whole or in part, without the express prior written permission of Schlumberger. December 2012
*Mark of Schlumberger Copyright 2012 Schlumberger. All rights reserved.
Merak planning, risk & reserves 2013.1
Section 1: Introduction........................................................................................................ 1 Installation workflows ......................................................................................................... 2
Installing a new database on a database server .................................................................2 Installing the sample databases on a local machine ............................................................ 2 Upgrading an existing database on a database server ......................................................... 2 Merak installation workflow diagram ................................................................................. 3
DVD contents ..................................................................................................................... 4
Installation folder............................................................................................................ 4 Resource folder .............................................................................................................. 5

Section 2: Pre-installation ................................................................................................... 7 Prerequisites ...................................................................................................................... 7 System requirements .......................................................................................................... 7
Merak 2013.1 hardware and operating system requirements ............................................... 8 Merak 2013.1 database server requirements ...................................................................... 8 Merak 2013.1 client-side database requirements ................................................................ 9
Database setup ................................................................................................................ 10
Database privileges and permissions ............................................................................... 10 SQL Server Database Engines and tools .......................................................................... 11 Identifying SQL Server versions ...................................................................................... 11 SQL Server settings required by Merak 2013.1 ................................................................. 12
License setup ................................................................................................................... 13
Configuring your Windows Firewall to work with a network license ..................................... 14 Configuring Data Execution Prevention (DEP) to work with a network license ...................... 15
Multiple Versions .............................................................................................................. 16
Multiple Version Peep Selector Utility............................................................................... 17

OFM Versions ................................................................................................................... 17 Section 3: Merak suite installation .................................................................................... 18 Administrative installations ................................................................................................ 19 Stand-alone installations.................................................................................................... 20 Installing the Merak suite for Citrix environments ................................................................. 21 Silent installations ............................................................................................................. 23
Silent installations for stand-alone systems ...................................................................... 23 Running silent installations on stand-alone systems .......................................................... 23
Schlumberger Private - Customer Use
iii
Silent remote installation for multiple systems .................................................................. 24 Running silent remote installations on multiple systems ..................................................... 24
Network installations ......................................................................................................... 26
Installing Merak 2013.1 on a server ................................................................................ 26

Section 4: Post-installation................................................................................................ 29 ODBC data source setup .................................................................................................... 29
Oracle 32-bit drivers on a 64-bit operating system ............................................................ 29 SQL Server 32-bit drivers on a 64-bit operating system ..................................................... 29 Setting up ODBC Data Sources on a 64-bit operating system ............................................. 29 Setting up Oracle data sources ....................................................................................... 30 Setting up SQL Server data sources ................................................................................ 30
Installing and upgrading databases ..................................................................................... 32
Creating a new Merak database ...................................................................................... 33 Installing new databases................................................................................................ 33 Upgrading existing databases ......................................................................................... 35
Merak database users and roles.......................................................................................... 37
Resetting Merak database passwords for secure databases ................................................ 37 Adding new database user accounts for secure databases ................................................. 39
Section 5: Appendices ........................................................................................................ 40 Appendix A: Creating an Oracle user script .......................................................................... 41
Working with the script.................................................................................................. 41

Appendix B: Application user mapping setup for Oracle Merak schemas that have been copied or moved ......................................................................................................................... 42
Working with the Ora_SetupUserMap.sql script................................................................. 42

Appendix C: Security script for secure Merak SQL Server databases ........................................ 43
Working with the SS_SetupSecurity.cmd script ................................................................. 43 Using SQL Server Management Studio to adjust security ................................................... 45
Appendix D: Troubleshooting tips for problems logging into Merak applications ....................... 47 Appendix E: Parameters for silent installations on stand-alone systems ................................... 49 How to reach us ................................................................................................................. 50
iv

Section 1: Introduction
This guide contains comprehensive information on installing all components in the Merak 2013.1 planning, risk & reserves suite. You can access this and other Merak release documentation through the Schlumberger Information Solutions (SIS) Support Portal (https://support.slb.com). For more information, about the SIS Support Portal, see How to reach us on page 50. The Merak Installation Guide is divided into five main sections: Introduction Pre-installation Merak suite installation Post-installation Appendices
Section 1: Introduction
This section summarizes the installation process and provides you with an installation workflow diagram. It also lists the files that you will find in the Installation and Resources folders on the Merak installation DVD.
Section 2: Pre-installation
This section shows the software versions supported by Merak 2013.1, system requirements to run the Merak suite, and how to obtain and set up your Merak licenses. It also contains information about setting up your database server, privileges and permissions required for Oracle or Microsoft SQL Server databases, and specific SQL Server settings required for Merak.
Section 3: Merak suite installation

This section describes the procedures for stand-alone and network installations. It also shows how to run a silent installation script and how to install the Merak suite for Citrix environments.
Section 4: Post-installation
This section describes how to set up your Oracle and SQL Server data sources. It also covers how to install or upgrade databases and reset passwords using Merak Database Toolkit.
Section 5: Appendices
This section contains supplemental information about silent installation parameters, creating Oracle users, using scripts to set up user mapping and security, and troubleshooting tips if errors occur during login.

Installation workflows
Because most Merak applications require a SQL Server or Oracle database to be installed, the way in which you install Merak 2013.1 depends on whether you are installing or upgrading a database. If you are installing a new database, you also have the option to install the Merak sample databases. There are three scenarios in which you can install Merak 2013.1: Installing a new database on a database server Installing the sample databases on a local SQL Server database server Upgrading an existing database on a database server
For a visual description of the installation process, see the Merak installation workflow diagram on page 3.
Installing a new database on a database server

If you are installing a new database, first you will need to set up your database on the database server, and then install Merak 2013.1 on a client-side machine. After the Merak suite is installed, you will set up your data sources, and then use Merak Database Toolkit to install the new database.
Installing the sample databases on a local machine

Merak 2013.1 comes with sample databases (secure and unsecure), which you can install to test how the different Merak features work without compromising your data. Although the sample databases can be manually attached to any SQL Server instance, the Merak 2013.1 installation routine is only able to attach the sample databases to a local instance. To have the Merak installation attach and create connections to these sample databases, you must have a SQL Server instance installed on your machine.
Upgrading an existing database on a database server

After the Merak suite has been installed on the client-side machine, you will set up your data sources, and then use Merak Database Toolkit (DBTools) to upgrade the database.

Merak installation workflow diagram

DVD contents
The installation DVD includes Merak 2013.1 setup files, the Merak Installation Guide, and a Resource folder containing release notes and supplemental software required to install Merak 2013.1. Schlumberger files are signed with an Authenticode digital signature. Digitally signing our files ensures their authenticity. Third-party components are not signed by Schlumberger. The certificate thumbprint is available from the SIS Support Portal (http://support.slb.com) by searching the Knowledge Base for either Merak Authenticode digital signature, or article 6070825.
Installation folder
The Install folder contains the installation files for Merak 2013.1. This folder
\Install\Merak
Contains
The MerakSetup.exe executable file installs these Merak 2013.1 applications: Capital Planning Data Link Administrator Database Toolkit Decision Tool Kit Global Edit Merak Administration Console Peep Petroleum Financials Results Broker VOLTS

Resource folder
The Resource folder contains additional software and utilities that you might require. This folder \Resource\Database Scripts Contains The following scripts: Ora_SetupDBTools_10g11g.sql: Creates Oracle users with the proper permissions required for Merak 2013.1. It needs to be run when you install or import an Oracle database.
Creating an Oracle user script on page 41.
For more information about this script, see Appendix A:
Ora_SetupUserMap.sql: Creates the security framework required for a Merak Suite 2013.1 Oracle database that was copied or moved. For more information about this script, see Appendix B:
Application user mapping setup for Oracle Merak schemas that have been copied or moved on page 42.
SS_SetupSecurity.cmd: This script adjusts logins for SQL Server databases, and is required after copying or moving a secure database to a new instance. For more information about this script, see Appendix C: Security script for secure Merak SQL Server databases on page 43. \Resource\File Manifests Excel spreadsheets containing complete lists of files for each application. The most common problems encountered when installing or upgrading the Merak suite are caused by Dynamic Link Library (DLL) file version control and incompatibility. To ensure that every third-party installation program (from vendors such as Microsoft) checks each version number and date before overwriting any system DLL files, you must run the latest commercial release of the required sub-system DLL files. Installation of some third-party software such as Microsoft Office can cause system failure by overwriting newer versions of system DLL files with older versions. If problems or errors occur with a Merak application after installation, check the program file list in the Resource folder to ensure that you are running the correct DLL, and re-install the Merak suite if the required version has been overwritten. \Resource\FlexNet Licensing\Schlumberger Licensing \Resource\FlexNet Licensing\Aladdin Dongle Driver \Resource\Merak Fiscal Model Library The SchlumbergerLicensing2012.exe file and installation guide required to run FlexNet as a service on a network. For information about FlexNet licenses, see License setup on page 13. The FLEXidCleanUtility.exe, FLEXid_Dongle_Driver_Installer.exe, and driver installation guide for use with the Aladdin dongle. Merak Fiscal Model Library (FML) 2012.3. Alternatively, download the latest release of FML from http://support.slb.com by clicking the link to the Software Download Centre (SDC).

This folder \Resource\Open Source Software\Antlr \Resource\Open Source Software\SharpZipLib \Resource\Peep Multiple Version Selector\
Contains The readme.txt file that acknowledges our use of the Open Source software component Antrl 2.0. Source code and license notice for the Open Source software component SharpZipLib. Merak.Peep.Selector.exe, which enables you to select the version of Peep your custom tools (Merak Results Broker, Merak VOLTS, etc.) to access in a multiple version install. This folder can be copied anywhere, but all of the files (Merak.Peep.Register.dll, Register.Peep.exe, Register.Peep.exe, mxCom42.dll, and mxCore42.dll) must be in the same folder in order for Selector to work.

Section 2: Pre-installation
This section covers the software versions supported by Merak 2013.1, system specifications needed to run the Merak suite, and how to obtain and set up your Merak licenses. It also describes setting up your database server, privileges and permissions required for Oracle or SQL Server databases, and specific SQL Server settings required for Merak. Before installing Merak 2013.1, read the following sections:
Prerequisites on page 7 to understand which database-management systems are compatible with

Merak 2013.1, and hardware and database requirements for installing Merak 2013.1.
Database setup on page 10 to understand which Oracle and SQL Server permissions must be
established on your system, which SQL Server settings you need to configure, and installation information for SQL Server and Oracle.
License setup on page 13 to understand how to obtain your license files, the difference between
setting up a stand-alone license and setting up a license server, and how to configure Windows Firewall and Data Execution Prevention (DEP).
Multiple Versions on page 16 to understand how to install the latest version of Merak on the same machine as a prior version.
Prerequisites
The following must be installed on your system in order to run the Merak Suite 2013.1: Microsoft .NET Framework 3.5 SP1 (included by default in Windows 7) Microsoft Windows Installer 4.5
If these pre-requisites are not present on your system, the Installation Wizard will install them before installing Merak 2013.1. This may require you to reboot your system each time, depending on which prerequisites are missing. In addition, Adobe Acrobat Reader must be installed on your system in order to read some of the documentation embedded in the help files. Download and install the free version of Adobe Reader from http://get.adobe.com/reader/ Contact your local SIS support center if you are uncertain what versions are currently installed on your system, or if you are looking for the latest updates. For more information about contact information, see How to reach us on page 50.
System requirements
This section describes how to set up your system before installing Merak 2013.1, including: hardware and operating system requirements database server requirements client-side requirements

Merak 2013.1 hardware and operating system requirements

See the table below for hardware specifications for the machine where you are installing Merak 2013.1. Merak 2013.1 Hardware and System Specifications Operating System You can install Merak 2013.1 on these operating systems: Processor Memory Workstation hard disk space Screen resolution Windows XP Professional SP3 (32-bit) with Microsoft hotfix KB943232 installed1. Windows Vista Business Edition SP2 (64-bit) Windows 7 Professional SP1 (32 or 64-bit) Windows Server 2008 R2 SP1 (64-bit) with Citrix XEN App 6.5
Minimum: 1 GHz Recommended: 2 GHz Minimum: 1 GB (32-bit) or 2 GB (64-bit) Recommended: 2 GB (32-bit) or 4 GB (64-bit) Stand-alone: 2 GB Network: 1 GB Minimum: 1280 x 1024
Merak 2013.1 database server requirements

The Merak 2013.1 suite (with the exception of Merak Decision Tool Kit) requires the installation of an underlying database-management system (DBMS). Merak products support the following database servers: Oracle 10g (release 2) Oracle 11g (release 2) Microsoft SQL Server 2008 (SP3) Microsoft SQL Server 2008 R2 (SP2)
Note: Ensure that you use only those database versions and ODBC drivers identified in this document. Versions that are not identified here can cause application failure and are not supported.
SQL Server Express Edition

SQL Server Express Edition is a free version of SQL Server. Because of its limitations, SQL Server Express Edition is not a recommended installation for a centralized server solution that has multiple users connecting to it. However, SQL Server Express Edition is a great solution for stand-alone simple data-driven applications, such as stand-alone Merak Peep on a single PC.
As KB943232 is not classified as a security update by Microsoft, it may need to be manually selected and installed on Windows XP operating systems. See http://support.microsoft.com/kb/943232 for details and to download the Microsoft patch. Failing to install the patch can result in sudden closure of Merak applications.
8 Merak planning, risk & reserves
For more information about SQL Server 2008 Express Edition features, go to
http://www.microsoft.com/sqlserver/2008/en/us/editions-compare.aspx.
For more information about how to install and configure SQL Server 2008 Express to work with Merak, and how to install SQL Server Management Studio 2008 Express, search the SIS Support Portal for either Merak SQL Server 2008 configuration or Knowledge Base article 5102085. You can access the SIS Support Portal at https://support.slb.com.
Merak 2013.1 client-side database requirements

Before you install Merak 2013.1 on individual workstations, ensure that you have installed the Oracle Client or the SQL Server client components ODBC and OLE DB. To connect to an OFM workspace that uses a Microsoft Access database, you must install either Microsoft Access or the Microsoft Access Database Engine (available from the Microsoft Download Center). See Problems linking Peep to OFM workspaces, p. 48.
Microsoft SQL Server 2008

Merak products can be added to existing SQL Servers or placed on dedicated servers, as long as the instance meets the settings required by Merak. You are responsible for obtaining, installing and maintaining the appropriate SQL Server 2008 software. This table provides the SQL Server database requirements for Merak 2013.1. Merak 2013.1 Database Version ODBC Driver Database (initial size) Log size (initial size) TempDB size (initial size) SQL Server 2008 SP3 SQL Server 2008 R2 SP2 2008: SQL Server Native Client 10.0 - 2007.100.5500.0 (32-bit) 2008 R2: SQL Server Native Client 10.0 - 2009.100.4000.0 (32-bit) Minimum: 250 MB Minimum: 50 MB Minimum: 75 MB
Note: If your ODBC drivers are different than those shown above (for example, your driver is 2007.100.1600.22), then you are likely using an unsupported Windows or SQL Server service pack.
Oracle 10.2.0.X and 11.2.0.X

Merak products can be added to existing servers or placed on dedicated servers depending on relative loading and demand. You are responsible for obtaining, installing and maintaining the appropriate Oracle software.

Oracle 10g and 11g

This table provides the Oracle database requirements for Merak 2013.1. Merak 2013.1 Database Version Oracle Client ODBC Driver Data tablespace size (initial size) Index tablespace size (initial size) Open cursors (initial size) 10gR2: 10.2.0.X 11gR2: 11.2.0.X 10g: 10.2.0.5 (32-bit) 11g: 11.2.0.3 (32-bit) Minimum: 250 MB Minimum: 50 MB 500
W orkaround for Oracle 11.2.0.3 OLE DB provider com ponent
As per Oracle issue ID 1380742.1, the Oracle OLE DB provider component may not register correctly. It appears as installed when using the Oracle Universal Installer; however, it is not listed as an available provider when testing the connection using a UDL file. After installing the 11.2.0.3 ODBC and OLE DB components, register the OLE DB component manually using the command prompt. 1. Choose Start > Programs > Accessories > Command Prompt to open the Command Prompt window. Note: If UAC is enabled, the Command Prompt window must be run as administrator (right-click Command Prompt and choose Run as administrator). 2. Register the Oracle Provider for OLE DB with the following command: regsvr32 <OracleHome> \bin\OraOLEDB11.dll where <OracleHome> is the physical path to the Oracle home where the driver is installed. For example, regsvr32 c:\ app\oracle\product\11.2.0\client_1\bin\OraOLEDB11.dll
Database setup
All Merak applications with the exception of Merak Decision Toolkit (DTK) require a SQL Server or Oracle database.
Database privileges and permissions

Merak Database Toolkit (DBTools) is used to create database roles and users, database objects (such as tables, views, procedures, etc.) for new Merak databases, upgrade existing database table structures, and reset passwords required to run applications in Merak 2013.1. Windows Administrator privilege is required to run DBTools. Before installing or upgrading a Merak database, DBTools ensures that the database login name has the appropriate database privileges. When DBTools performs this security check, it writes the results to a file called Check.log, located in the Merak installation directory. You can review this log file if access to DBTools is denied, and it will identify the missing and necessary database privileges.
10

SQL Server permissions

To install or upgrade a SQL Server database, the SQL Server login used to run Merak DBTools must have these roles: db_owner database role (for the database you are installing or upgrading) Security Administrators server role (to enable the creation of database logins and roles)
Oracle permissions
It is recommended that you use the schema owner account when running Merak DBTools to install or upgrade Oracle databases. When installing or importing an Oracle database, you must first run the Ora_SetupDBTools_10g11g.sql script to set the proper permissions required for Merak 2013.1, including: CREATE USER ALTER USER CREATE SESSION WITH ADMIN OPTION CREATE ROLE CREATE ANY SYNONYM2 CREATE PUBLIC SYNONYM DROP PUBLIC SYNONYM DROP ANY SYNONYM2 DROP USER CREATE SEQUENCE CREATE PROCEDURE2 CREATE TABLE2 CREATE VIEW CREATE TRIGGER
For more information about the Ora_SetupDBTools_10g11g.sql script, see Appendix A: Creating an Oracle user script on page 41.
SQL Server Database Engines and tools

SQL Server is a Database Engine that allows you to store database tables and structures. SQL Server Management Studio is not necessary to run the Merak suite, but can be used to attach, detach, or back up databases, check tables and database objects in general, and perform queries.
Identifying SQL Server versions

Although older versions of SQL Server databases can be attached to a newer Database Engine, the reverse is not true. For example, SQL Server 2008 R2 databases cannot be attached to a SQL Server 2008 Database Engine. After a SQL Server 2008 database is attached to 2008 R2 Database Engine, it is automatically upgraded to the 2008 R2 format and from that point forward, it can no longer be attached to a SQL Server 2008 Database Engine. Any attempt to attach a SQL Server 2008 R2 database instance to a SQL Server 2008 Database Engine will result in errors. To avoid attaching your database to the incorrect version of database engine, you must identify which version of SQL Server your database instance is. To do this, launch SQL Server Management Studio and log in. The database number listed in the Object Explorer window will identify the Database Engine version.
Permissions marked must be granted directly to the Schema Owner and not through a ROLE.
11
Some of the version numbers for SQL Server releases are listed in the table below. Only the marked rows are supported database versions for Merak 2013.1. Database SQL Server 2005 SQL Server 2008 Release All Releases RTM SQL Server 2008 SP1 SQL Server 2008 SP2 SQL Server 2008 SP3 SQL Server 2008 R2 SP2 10.0.1600 10.00.2531 10.00.4000 10.00.5500 10.50.4000 Sqlservr.exe Merak 2013.1 Not supported Not supported Not supported Not supported Supported Supported
SQL Server settings required by Merak 2013.1

You must configure the SQL Server instance to work with Merak products. The sections below describe which settings must be changed during and after the SQL Server instance installation. Ensure that you use the default SQL Server installation settings except as defined below. Changing options (e.g., the server collation) can cause problems with Merak applications. The following settings must be changed during the SQL Server installation: Choose an account for the SQL Server Database Engine service to run under: It is recommended to use the local system account and select the option that enables the Database Engine service to run automatically at the computer startup. If you are using a named SQL Server instance, set up the SQL Server Browser service to run as system account and to automatically start when your server starts up. Select the authentication method: Select the Mixed Mode (SQL Server and Windows authentication) option and type the password for the sa user. Merak does not currently support Windows Authentication. Define the SQL Server administrators: Because network or PC administrators are not automatically SQL Server administrators, you can optionally specify the domain or PC users who will be SQL Server administrators for the instance. SQL Server administrators have unrestricted access to the Database Engine. Open SQL Server Configuration Manager and protocols for your instance name: By default the Named Pipes and TCP/IP protocols are disabled for the database-server side. If you want your SQL Server database engine to accept connections, you must enable these protocols. Add Windows Firewall exceptions as necessary: Depending on your network policies, you might need to create some Windows Firewall exceptions for the SQL Server side to take incoming connections from clients.
The following settings must be changed after the SQL Server installation.
http://msdn.microsoft.com/en-us/library/ms175043.aspx.
For more information about configuring your Windows Firewall for Database Engine access, see
12

License setup
Your Merak license can be a stand-alone license file linked to a single machine, accessed through a network license server, or linked to a USB or Dongle key. Because Schlumberger Information Solutions (SIS) must authorize all Merak applications, Merak licenses must be obtained through the SIS Help Desk. To simplify the licensing and software upgrade process, Merak has recently moved to Date Based Version (DBV) licensing. With DBV licensing, in the normal case of events, there is no need to request a new license when a new version is commercialized; the license that you already have will run the latest version if it was commercialized on or prior to the DBV date. In a DBV license, the version number in the license file is replaced by a year and month value. This value is derived from the maintenance end date for perpetual licenses, or license end date for variable duration licenses. The license will then run any version of software published up until that year and month. There is also a separate license expiry date. For example, the license feature below is a DBV license that expires on July 19th, 2013, and supports any version of World Peep commercialized prior to December 31st, 2013:
INCREMENT World_Peep slbfd 2013.12 19-jul-2013 10 NOTICE=OCEANSTORE \ SIGN="0018 D48D 0FC4 74D6 1AF3 2A78 5338 FD00 F862 0078 CEFA \ 76AC E874 1B96 19C8"
Note: Merak 2009 and prior releases will not work with DBV licenses, and will require separate versionbased licenses.
Stand-alone license file tied to a physical machine

Stand-alone license files are tied to the physical address of a single machine. The stand-alone license allows a user to access Merak products when they do not have access to a licensing sever; for example when the machine is offline. The license file can be saved on the local machine and pointed to directly; it is not necessary to set up a licensing server. However, if you are working with multiple SIS software products, you can also choose add the stand-alone license to a local FlexNet server using the Schlumberger licensing tool.
Network license
You can set up a licensing server on a network so that multiple users can share licenses. Use the Schlumberger licensing tool to implement, manage, and monitor your FlexNet licenses.
License tied to a USB or Dongle key

You can also tie a stand-alone or server license to the physical address of a USB or Dongle key, which allows offline access, and the ability to share the license across multiple machines. The license file must be saved on the local machine of each computer, and a small utility must be installed so that Merak recognizes the USB key. As long as the USB or Dongle key is in a USB port on the machine, a license will be available to the user. Please refer to the driver installation guide in the Resource/FlexNet Licensing/Aladdin Dongle Driver folder of the DVD for further information.

13
For more information about installing the Schlumberger licensing tool, refer to the InstallingSchlumbergerLicensing.pdf guide located in the Resource/FlexNet Licensing/Schlumberger Licensing folder of the DVD. For more information about this tool and its features, read the Schlumberger Licensing Tool User Guide that is also accessible through the tools Help menu after installation.
Configuring your Windows Firewall to work with a network license

By default, most Windows machines have a Windows Firewall enabled that blocks communication between the licensing server and the system. To unblock FlexNet from the Windows Firewall and allow license requests on networked machines, you might need to create program exceptions and open the FlexNet access port on the license server. The instructions below are for unblocking FlexNet from the Windows Firewall on a Windows Server operating system; the way in which you perform this task may vary slightly depending on your operating system.
To add program exceptions for FlexNet (W indow s Server):

1. Open the Windows Control Panel and click Windows Firewall. 2. Choose the Allow a program through Windows Firewall option, and then click Continue. 3. On the Exceptions tab in the Windows Firewall settings dialog box, click Add program to open the Add a Program dialog box. 4. Click the Browse button, and then navigate to the FlexNet installation folder; the default location is C:\Program Files (x86)\Schlumberger\Schlumberger Licensing\flex118. 5. Select slbsls.exe and click Open to add it to the Programs list. 6. Click OK to add slbsls.exe to the list on the Exceptions tab. 7. Repeat steps 3 to 6, but now add an exception for lmgrd.exe.
To add exceptions for the FlexNet access port:

1. Open the Add a Program dialog box as you did in the procedure above. 2. On the Exceptions tab, click the Add Port button.
14

3. In the Add a Port dialog box, type a name for the exception (for example, FlexNet License Port), and identify the port number (the default port is 27000). You do not need to change the type or scope of the exception.
4. Click OK when finished.
Configuring Data Execution Prevention (DEP) to work with a network license

Data Execution Prevention (DEP) is a set of hardware and software technologies that perform additional checks on memory to help prevent malicious code from running on a system. To ensure that the Data Execution Prevention Windows feature does not block lmgrd.exe and slbsls.exe, you must instruct your system to allow these executable files to run. The instructions below are for configuring your DEP preferences on a Windows Server operating system; the way that you perform this task will vary slightly depending on your operating system.
To configure DEP settings to allow lm grd.exe and slbsls.exe to run (Window s Server):
1. In the Windows Control Panel, click System to open the System window. 2. Click the Advanced System Settings option, and then click Continue to open the System Properties dialog box. 3. On the Advanced tab, click the Settings button in the Performance group to open the Performance Options dialog box. 4. On the Data Execution Prevention tab, select the Turn on DEP for all programs and services except those I select option, and then click the Add button. 5. Navigate to the FlexNet installation folder; the default location is C:\Program Files (x86)\Schlumberger\Schlumberger Licensing\flex116. 6. Select lmgrd.exe and click Open, and then click OK at the warning prompt to add it to the list on the Data Execution Prevention tab.

15
7. Repeat steps 5 and 6, this time adding slbsls.exe to the list, which should look something like this:
Multiple Versions
In previous Merak releases, only one version of Merak could be installed on a machine at a time, and the previous version of Merak had to be uninstalled before upgrading to the latest version. This is no longer the case. The 2013.1 release can be installed on the same machine alongside Merak 2010.1 or 2011.1, and/or 2011.2. Ensure installations are performed in order from oldest to newest release. For example, do not attempt to install first Merak 2013.1, and then an older version of Merak; install the older version of Merak first, and then Merak 2013.1. With 2013.1 it will therefore be possible to have up to three simultaneous Merak versions, installed in the order: 1. Install one of 2010.1 or 2011.1 2. Then install 2011.2 3. Then install 2013.1 During the Merak 2013.1 installation routine, if you already have a single Merak version installed, choose whether to uninstall the previous Merak installation and replace it with the latest 2013.1 release, or to add the 2013.1 release to the list of available programs. Versions of Merak older than 2010.1 cannot run alongside 2013.1 and will be automatically uninstalled. Note: The Merak installation routine may not automatically remove non-commercial updates and hot fixes. You may have to manually uninstall the suite if it included non-commercial updates and hot fixes before continuing the 2013.1 installation. Only one version of Merak Fiscal Model Library (FML) can be installed on a single machine, and all installed versions of Merak Peep must use the same FML library version. Additionally, if running multiple versions of Peep on a single machine, only FML 2011.4 or later is supported. As licensing is backwards compatible back to 2010.1, as long as you have a license available for the latest release, you do not need unique licenses for each version of Merak installed on the same machine. However, each Merak version installed requires its own version-specific database. It is also important to ensure that each version of Merak installed is supported on that platform (operating system, database version, ODBC driver version, etc.). In multiple version installations, applications that communicate with Peep will try to communicate with the last registered version of Peep, causing errors (e.g. Merak VOLTS, Merak Results Broker, Merak
Global Edit, Merak Decision ToolKit, Capital Planning Portfolio Export Wizard, Merak Administration Console, and any tools making use of OLE Automation in order to communicate with Peep). Use the Merak Peep Selector utility located on the installation DVD to register the current version of Peep.
Selector Utility on page 17.
For more information about this tool and its features, read the following section Multiple Version Peep
Multiple Version Peep Selector Utility

As of Merak V2011.2, it is possible to install more than one version of Merak Peep on the same machine. However, in environments with more than one version of Merak installed, applications that communicate with Peep always try to connect with the last registered version. In order for these tools to function properly, ensure they are connecting to the correct version of Peep. This is done using the Merak Peep Version Selector utility. Copy the folder\Resource\Peep Multiple Version Selector\ and its files to the machine on which multiple versions of Merak are installed: 1. Close all Merak applications, close any custom applications that use Peep automation, and launch the Merak Peep Version Selector by double-clicking Merak.Peep.Selector.exe. The Merak Peep Version Selector displays all versions of Merak Peep that are currently installed. 2. Select the desired working version, and click either Set as Default or Select for Current User. If you choose Set as Default, the selected Peep version is registered at a system level, and no further action is required. The Select for Current User option is intended for users who do not have administrative privilege on their machine; if you choose Select for Current User, the selected Peep version is registered locally at a user-level, and a reboot of the machine is necessary.
3. Click Exit to close the Merak Peep Version Selector. 4. If you chose Select for Current User to register the Peep version locally, reboot the machine. This process must be repeated each time you want to run a different version of Merak. It is only necessary if you use custom tools that make use of Peep automation, or use Merak applications that launch a Peep process in the background (such as Merak VOLTS, Results Broker, Global Edit, Decision ToolKit, Capital Planning Portfolio Export Wizard, and Merak Administration Console). If you are not running any tools that communicate with Peep via automation, the Merak Peep Selector Tool is not necessary.
OFM Versions
Peep 2013.1 supports Schlumberger Oilfield Manager (OFM) 2009.1 and later.

17
Section 3: Merak suite installation

You can install Merak 2013.1 locally on individual computers or in a Citrix environment (stand-alone installation) or on a server (network installation). Standalone Merak 2013.1 can be installed in one of three ways: Using the Merak installation DVD, with silent installation scripts, or using an administrative installation. For network installations, you must first run an administrative installation of Merak 2013.1 on the server (i.e. host machine), and then on each client-side machine. The advantages of a network installation are: There is a smaller space requirement on the client-side machine where the applications are launched from. It could therefore take less bandwidth to push out a large number of installations. However, it will require more network traffic to run the applications. When there is a patch or an update to a common dll, you only need to apply the changes to the server, and then all client machines will have the changes applied.
Both the stand-alone and network installations are supported with multiple versions of Merak. See Multiple Versions on page 16 for more information. Merak 2013.1 comes with sample databases, which you can optionally install to test how the different Merak features work without compromising your data. To have the Merak installation routine install the Merak sample databases and create ODBC connections, you must have SQL Server installed on the local machine prior to running the M erak installation . You can at any time manually attach the sample databases to any supported SQL Server engine and create the ODBC connections. Sample databases are located on the installation DVD in the Install\program files\Schlumberger\Merak 2013.1\Database folder.
To install M erak 2013.1, read the follow ing sections for specific installation instructions:
Administrative installations on page 19 to find out how to configure the ODBC database connection and licensing information for a number of identical standalone or network installations.
Stand-alone installations on page 20 to find out how to install Merak 2013.1 on a stand-alone
machine.
Installing the Merak suite for Citrix environments on page 21 to understand how to install
standalone Merak 2013.1 in a Citrix environment.
Silent installations on page 23 to understand how to install standalone Merak 2013.1 on a

single machine or on multiple machines using command-line scripts.
Network installations on page 26 to understand how to install Merak 2013.1 onto server and
client-side machines.
18

Administrative installations
If you have a number of Merak installations to perform (standalone or network), you can configure the ODBC database connection information and licensing information in advance by using the administrative installation option. The installation files are copied to a network location, allowing you to configure the ODBC and licensing information that will be installed on all of the client machines at one time. Note: The administrative installation option cannot be used to install the sample databases; however, you can manually attach the sample database(s) and use the administrative installation to configure the ODBC connections. 1. Create a shared folder (for example, Merak 2013.1 Administrative Install) on the server where you will copy the Merak 2013.1 administrative installation files. The client machines will eventually need read access to this location. 2. Open a Windows Command Prompt window and type the location of the DVD drive or the shared file path of the server that contains the Merak 2013.1 setup.exe, followed by a space and the command switch /a to run the installation. For example, to run MerakSetup.exe from the source DVD drive, type this in the Command Prompt:
<drive>:Install\Merak\MerakSetup.exe /a
3. On the Database Connection dialog box, specify the database connection information. This information is not validated, but is simply used to create an ODBC data source on the client machine. Type the ODBC Connection Name, and optionally, a Description. Type the Driver Name exactly as it appears in the Drivers tab of the ODBC Administrator. Type the Database name exactly as it is attached in SQL Server Management Studio. If the client machines are 64-bit operating systems, the Driver .dll must point to the 32-bit dll located in C:\Windows\SysWOW64\sqlncli10.dll. If the client machines are 32-bit operating systems, the Driver dll must point to C:\Windows\System32\sqlncli10.dll. The Server field should contain the SQL server name and instance name in the format servername\instancename. The Driver dll should point to sqora32.dll, located in the Oracle client bin directory (e.g. C:\oracle\product\10.2.0\client_1\bin\sqora32.dll). The Server field should contain the TNS service name where the Merak database resides.
To connect to a SQL Server database:
To connect to an Oracle database:
4. On the FlexLM dialog box, specify the location of your Merak 2013.1 licenses. This licensing information is not validated; settings are simply populated on the client machines. For more information about Merak licenses, see License setup on page 13. If you have a license server, select the Server option, and then type the port number and the name of the FlexNet license server. If you have a standalone license file or dongle license, select the File option, and then browse to and select the local file. The license file must be located in the same directory on each client machine. If your licensing was set up on each individual workstation prior to running the Merak 2013.1 Installation Wizard, or if the license location is unknown, select the Use Current option.
19
5. Click Next to continue. 6. On the Network Location dialog box, click the Change button. 7. On the Change Current Destination Folder dialog box, browse to the folder you created in step 1. 8. Click OK to return to the Network Location dialog box, and then click Next to begin copying the installation files to the server location. 9. Click Finish when the installation is complete. 10. Install the client-side by clicking MerakSetup.exe from the server location created in step 1. Refer to Stand-alone installations on page 20, or Network installations on page 26, depending on the type of installation desired.
Stand-alone installations
1. Using Windows Explorer, open the Install/Merak folder on the Merak 2013.1 DVD, or if running an Administration installation (see Administrative installations on page 19), browse to the server location where the setup files were installed. 2. Click MerakSetup.exe and follow the prompts in the wizard. If a single version of Merak 2010.1 or later is detected on the machine, a screen appears allowing you to choose to replace the previous version of Merak with 2013.1, or to install 2013.1 alongside the previous version (versions of Merak older than 2010.1 are automatically uninstalled). For general details, see Multiple Versions on page 16 3. On the Custom Setup dialog box, select the applications that you want to install. By default, all programs and sample databases are installed: If you do not want to install a feature, click the icon next to the desired node, and then select the This feature will not be available option. Applications or features with the icon beside their name will not be installed.
Note: The Merak sample databases can only be installed on a local SQL Server instance when using the Merak Installation Wizard. The sample databases will not be available to select if running an Administrative installation (see Administrative installations on page 19 for further information) or if the operating system is Windows Server. If you install the sample databases, you must complete steps 4 and 5 (which describe the Database Server and Merak SQL Logins dialog boxes in the Installation Wizard). Otherwise proceed to: Step 6 (Peep Economic Regimes dialog box of the Installation Wizard) if you are not installing the sample databases and are installing Merak Peep, or Step 7 (FlexLM dialog box of the Installation Wizard) if you are not installing the sample databases or Merak Peep.
4. On the Database Server dialog box, select your local SQL Server instance from the drop-down list and type the password for the sa user. Note: If your local database instance does not appear in the drop-down list, you can type it into the Database Server field in the following format: Server\Instance. 5. On the Merak SQL Logins dialog box, type the passwords for the MERAK_AUTH_USER, MERAK_APP_USER and MERAK_BOOT_USER accounts.
If you have not installed a Merak database on this server instance before, the logins will be created with the passwords you specified above (by default, they will be set to M#rak2010). The passwords you specify must meet the security policies for your computer. If you have installed a Merak database on this server instance before, the SQL logins already exist, and you need to provide the current passwords for these accounts. 6. If you are installing Merak Peep, you will also have to choose which economic regimes you want to use. To do this, on the Peep Economic Regimes dialog box, select the economic regimes that you want (and are licensed) to use. If you are unsure what you are licensed for, leave all three selected. 7. On the FlexLM dialog box, specify the location of your Merak 2013.1 licenses. Your Merak license can be a stand-alone license file or a network license server.
component on page 10.

For more information about Merak licenses, see Workaround for Oracle 11.2.0.3 OLE DB provider
If you have a license server, select the Server option, and then type the port number and the name of the FlexNet license server (for example, 1700@release2-cal). If you have a license file, select the File option and browse to the location of the local file. If your licensing was set up prior to running the Merak 2013.1 Installation Wizard, or if you are unsure of the license location, select the Use Current option. Note: No validation of the licensing is done during the Merak installation. If you are running an Administrative installation, the licensing option will be pre-populated and greyed out (see Administrative installations on page 19 for further information).
8. Click Next, and then Install to finish installing the Merak Suite. 9. If you added Merak 2013.1 to a previous installation of Merak Peep, ensure you follow the post installation instructions Section 4: Post-installation on page 29. 10. Merak Fiscal Model Library (FML) is a separate installation from the rest of the suite, and is recommended if you installed the sample databases. You can either install FML from the Resource\Merak Fiscal Model Library folder on the DVD, or download and install the latest FML release from the Software Download Centre (SDC), accessible from the Support Portal (http://support.slb.com).
Installing the Merak suite for Citrix environments

This document assumes that you have Citrix Access Management Console installed on your server machine. For more information about system requirements, see Merak 2013.1 hardware and operating system requirements on page 8. For more information about installing Citrix Access Gateway and configuring Citrix Access Management Console, go to http://support.citrix.com/proddocs/index.jsp?topic=/access-gateway-45/agae-accessmanagement-console_1.html. The Citrix administrator uses Citrix Access Management Console to host applications and assign access rights to applications/users. Citrix clients use the Citrix Online plug-in-Web to access the server that hosts the Merak suite.

21
To download the plug-in go to http://www.citrix.com/English/ss/downloads/details.asp?downloadId=1858087&productId=186&c1=sot 2755#top. Installing Merak 2013.1 in a Citrix environment requires you to first install the Merak suite onto Windows Server. Then use the Citrix Access Management Console to publish the application and give the required users access to the applications that they need. Citrix clients will access these applications online (for example, http://<server_name>/Citrix/AccessPlatform/auth/login.aspx?), where <server_name> is the name of the server where the Merak suite is installed.
To install M erak 2013.1 in a Citrix environm ent:

1. Follow Stand-alone installations on page 20 to install Merak 2013.1 onto a Windows Server machine. 2. Log in to the Citrix Access Management Console and publish the Merak applications. 3. Assign users the appropriate access rights for the applications they require.
For more information on how to do this, refer to the Citrix Access Management Console help file.
To m odify environm ent variables for M erak VOLTS installations:

Merak VOLTS will not run if the Crystal Reports Print Engine component (CRPE32.dll) is not found, which is common in Citrix environments. Modify the system Path environment variable to include C:\Program Files (x86)\Common Files\Crystal Decisions\2.0\bin. To do this: 1. Right-click the Computer icon on your Windows Desktop and choose Properties to open the System Properties dialog box. 2. Click Advanced system settings to display the System Properties dialog box, and then click the Environment Variables button. 3. In the System variables group, select the Path variable, and then click Edit.
4. Add the C:\Program Files (x86)\Common Files\Crystal Decisions\2.0\bin path to the Variable value field, separated from the previous entries by a semi-colon, and then click OK.
22

Silent installations
You can deploy silent installations on stand-alone or multiple systems. Installing the Merak suite on multiple systems using the silent installation method requires a remote connection from the workstations needing Merak 2013.1 to a single machine that contains the installation files. Because scripts are customized according to specific client requirements, a script file is not provided with the Merak 2013.1 installation DVD. Refer to Appendix E: Parameters for silent installations on stand-alone systems on page 49 for the information required to customize an installation script.
Silent installations for stand-alone systems

The silent installation method for stand-alone systems requires little interaction because it uses MerakSetup.exe to install Merak 2013.1 without an Installation Wizard interface. Before running a silent installation script for a stand-alone system, ensure that: The machine where you are installing Merak 2013.1 meets the appropriate software, hardware, and database requirements. For more information about these requirements, see Prerequisites on page 7. You have access to the remote server path without going through the Windows Authentication login window. To do this, add the required exception or path to the Windows Firewall. You have administrator rights to the machine where you are installing Merak 2013.1.
Running silent installations on stand-alone systems

1. As you have the capability to install multiple versions, if you do not want to have multiple versions of Merak on a single machine, you must first uninstall the prior version by creating a customized script in Notepad. Here is an example of how your uninstall script might look:
"path to MerakSetup.exe" /s /v"/qn REMOVE=ALL /lvx* C:\logfile.txt"
2. After uninstalling the prior version of Merak, create another customized script in Notepad for the Merak 2013.1 installation. For example, to script a Merak installation that includes the sample database, you could use the following:
"path to MerakSetup.exe" /s /v"/qn ADDLOCAL=ALL /lvx* C:\logfile.txt IS_SQLSERVER_SERVER=Machine name\SQL Server instance IS_SQLSERVER_PASSWORD=M#rak2010 MERAK_AUTH_USER=M#rak2010 MERAK_APP_USER=M#rak2010 MERAK_BOOT_USER=M#rak2010"
For more information about script parameters, see Appendix E: Parameters for silent installations on stand-alone systems on page 49. 3. Open a Windows Command Prompt window and paste your customized script into the command prompt.
4. Press <ENTER> to run the script and begin the installation process. The log file is created in the location you specified in the script, and is used to determine if the installation was successful.

23
5. Open the log file (for example, in the script above C:\logfile.txt) and verify that the installation was successful. 6. Browse to the folder where Merak 2013.1 was installed (the default path is C:\Program Files(x86)\Schlumberger\Merak 2013.1) and verify that all the applications are installed. If you installed the Merak sample databases, ensure that they were also installed properly on a local SQL Server instance. If you added Merak Peep 2013.1 to a previous installation of Merak Peep, follow the post installation instructions Section 4: Post-installation on page 29.
7. Merak Fiscal Model Library (FML) is a separate installation from the rest of the suite, and is recommended if you installed the sample databases. You can either install FML from the Resource\Merak Fiscal Model Library folder on the DVD, or download and install the latest FML release from Software Download Centre (SDC), accessible from the Support Portal (http://support.slb.com).
path to Resource\Merak Fiscal Model Library\setup.exe /s /v/qn
Silent remote installation for multiple systems

Installing the Merak suite on multiple systems using the silent installation method requires a remote connection from the workstations needing Merak 2013.1 to a single machine that contains the installation files. This type of installation uses both the PsExec and msiexec utilities. PsExec enables you to run a batch file to install Merak 2013.1 from one machine to another, and msiexec installs Merak 2013.1 without using an Installation Wizard interface. Before running a silent remote installation for multiple systems, ensure that: The machines where you are installing Merak 2013.1 meet the minimum software, hardware, and database requirements. For more information about these requirements, see Prerequisites on page 7. You have access to the remote server path without going through the Windows Authentication login window. To do this, add the required exception or path to the Windows Firewall. You have administrator rights to the machines where you are installing Merak 2013.1. PsTools is installed on the local machine where you are running the batch file. PsTools is a set of command-line utilities (for example, PsExec) that enable you to manage remote systems.
For more information about PsTools, read the PsTools article at http://technet.microsoft.com/enus/sysinternals/bb896649.aspx.
Note: If you are running the PsExec utility on a 64-bit machine, you should use the SysWOW64 command line (that is, C:\Windows\Syswow64\wscript.exe) to run the silent installation.
Running silent remote installations on multiple systems

When you run a silent remote installation for multiple systems, first you must create a batch file and then use the Windows Command Prompt to run the batch file along with the path to the MerakSetup.exe file. 1. The syntax for the script is based on this:
psexec [\\computer[,computer2[,...] | @file]][-u user [-p psswd][-n s][-l][s|-e][-x][-i [session]][-c [-f|-v]][-w directory][-d][-<priority>][-a n,n,...] cmd [arguments]
For more information about the PsExec utility and its syntax, read the PsExec v1.97 article at
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
2. With 2013.1, the capability to install multiple versions of Merak on the same machine has been added. Thus, if you do not want to have multiple versions of Merak on a single machine, you must first uninstall the prior version. In the example below, the existing version will be uninstalled:
set set set set REM REM REM REM Remote_Machine_Name=\\<machine_name> User_Name=DIR\<user_name> DB_Server_Name=<server\instance> Path_Installer=\\server\Install\Merak\MerakSetup.exe echo echo echo echo %Remote_Machine_Name% %User_Name% %DB_Server_Name% %Path_Installer%
psexec %Remote_Machine_Name% -u %User_Name% %Path_Installer% /s /v"/qn REMOVE=ALL /lvx* C:\logfile.txt IS_SQLSERVER_SERVER=%DB_Server_Name% IS_SQLSERVER_PASSWORD=M#rak2010 MERAK_AUTH_USER=M#rak2010 MERAK_APP_USER=M#rak2010 MERAK_BOOT_USER=M#rak2010"
3. Open a Microsoft Notepad document and prepare your PsExec script. In the example below, the Merak sample databases will be installed:
set set set set REM REM REM REM Remote_Machine_Name=\\<machine_name> User_Name=DIR\<user_name> DB_Server_Name=<server\instance> Path_Installer\\server\Install\Merak\MerakSetup.exe echo echo echo echo %Remote_Machine_Name% %User_Name% %DB_Server_Name% %Path_Installer%
psexec %Remote_Machine_Name% -u %User_Name% %Path_Installer% /s /v"/qn ADDLOCAL=ALL /lvx* C:\logfile.txt IS_SQLSERVER_SERVER=%DB_Server_Name% IS_SQLSERVER_PASSWORD=M#rak2010 MERAK_AUTH_USER=M#rak2010 MERAK_APP_USER=M#rak2010 MERAK_BOOT_USER=M#rak2010"
For more information about the scripts parameters, see Appendix E: Parameters for silent installations on stand-alone systems on page 49. 4. Save the document as a batch file (for example, MerakInstall.bat). 5. Open a Windows Command Prompt window and run the batch file you created. 6. Press <ENTER> to run the script and begin the installation process. The log file is created in the location you specified in the script and you can review it to determine if the installation was successful. 7. Browse to the folder where Merak 2013.1 was installed (the default path is C:\Program Files (x86)\Schlumberger\Merak 2013.1) and verify that all the applications were installed. If you installed the Merak sample databases, ensure that they were also installed to the local SQL Server instance. 8. If you added Merak Peep 2013.1 to a previous installation of Merak Peep, follow the post installation instructions Section 4: Post-installation on page 29.

25
9. Merak Fiscal Model Library (FML) is a separate installation from the rest of the suite, and is recommended if you installed the sample databases. You can either install FML from the Resource\Merak Fiscal Model Library folder on the DVD, or download and install the latest FML release from Software Download Centre (SDC), accessible from the Support Portal (http://support.slb.com). A sample script to install FML would look like:
REM set Remote_Machine_Name=\\<machine_name> set Remote_Machine_Name=\\192.168.97.122 set User_Name=DIR\<user_name> REM set DB_Server_Name=<server\instance> set Path_Installer=\\<server>\Resource\Merak Fiscal Model Library\setup.exe REM REM REM REM echo echo echo echo %Remote_Machine_Name% %User_Name% %DB_Server_Name% %Path_Installer%
psexec %Remote_Machine_Name% -u %User_Name% %Path_Installer% /s /v"/qn ADDLOCAL=ALL /lvx* C:\logfile.txt"
A sample script to uninstall FML would look like:

REM set Remote_Machine_Name=\\<machine_name> set Remote_Machine_Name=\\192.168.97.122 set User_Name=DIR\<user_name> REM set DB_Server_Name=<server\instance> set Path_Installer=\\<server>\Resource\Merak Fiscal Model Library\setup.exe REM REM REM REM echo echo echo echo %Remote_Machine_Name% %User_Name% %DB_Server_Name% %Path_Installer%
psexec %Remote_Machine_Name% -u %User_Name% %Path_Installer% /s /v"/qn REMOVE=ALL /lvx* C:\Removelogfile.txt"
Network installations
Network installations consist of two separate installations: server-side and client-side. Server-side: Merak 2013.1 files are transferred from the installation DVD to a server. During this process, the entire Merak suite is copied onto the server that you assign. Client-side: Individually licensed workstations access the network and install only those applications that are required by specific users.
Installing Merak 2013.1 on a server

1. Follow the instructions in Administrative installations on page 19 to copy and configure the Merak installation files on a server location accessible by the client machines (for example, \\MyServer\Merak2013.1 Administrative Install\). 2. Using Windows Explorer, navigate to the location specified in Step 1. 3. Double-click MerakSetup.exe and follow the prompts in the wizard.
If a single existing version of Merak 2010.1 or later is detected on the machine, a screen appears, allowing you to choose to replace the previous version of Merak with 2013.1, or install 2013.1 alongside the previous version (versions of Merak older than 2010.1 are automatically uninstalled). For general details, see Multiple Versions on page 16. 4. On the Custom Setup dialog box, click the icon next to Applications, and then choose This feature, and all sub features, will be installed to run from the network. After setting all applications to install and run from the network, set the individual features that you do not want to install by choosing This feature will not be available. Applications or features with an icon beside their names will not be installed. Note: The sample databases will not appear in the feature selection screen for a network installation. If desired, the sample databases can be manually attached to a SQL Server instance. 5. If you are installing Merak Peep, you also choose which economic regimes to use. To do this, on the Peep Economic Regimes dialog box, select the economic regimes that you want (and are licensed) to use. 6. On the FlexLM dialog box, click Next. Note: The license options are disabled as they were configured during the server-side of the installation. For more information about Merak licenses, see License setup on page 13. 7. Click Install to begin the installation. 8. If you added Merak Peep 2013.1 to a previous installation of Merak Peep, follow the post installation instructions Section 4: Post-installation on page 29. 9. Merak Fiscal Model Library (FML) is a separate installation from the rest of the suite, and is recommended if you installed the sample databases. You can either install FML from the Resource\Merak Fiscal Model Library folder on the DVD, or download and install the latest FML release from the Software Download Centre (SDC), accessible from the Support Portal (http://support.slb.com). Merak Fiscal Model Library always installs in the same directory as the last registered Peep.exe. Therefore, when running the Merak FML installation from the client machine, ensure that the Windows user has write privileges to the network location from step 1 where Peep is installed.
Adjusting .NET Framework security settings with the CasPol utility

Some items within the Merak 2013.1 suite are Microsoft .NET Framework components. In order for these components to work correctly in network installations, you must use the CasPol utility that comes with the .NET Framework. You can use the CasPol utility to set only the files in the Merak folder to Full Trust for proper operation of Merak 2013.1. Caution: Changes to .NET Framework security settings may affect the overall security of your system and should only be changed in accordance with your company security policy. We recommend that you coordinate any changes in the .NET security settings with your network administrator. The CasPol utility is installed as part of the .NET Framework installation and is available in the following location: .Net 2.0. (%WINDIR%\Microsoft.NET\Framework\v2.0.50727).
27
1. Choose Start > Programs > Accessories > Command Prompt to open the Command Prompt window. Note: If UAC is enabled, then the Command Prompt window must be run as administrator (right-click Command Prompt and choose Run as administrator). 2. Set the directory to the .NET 2.0 Framework (for example, C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727). 3. Type the following command to set the Merak folders to Full Trust: CasPol.exe -m -ag 1.2 -url file:\\servername\serverpath\program files\schlumberger\merak 2013.1\* FullTrust -n Merak2013.1 The table below describes the syntax of the Caspol commands used above. Command
m
Description
Indicates that all options following this one apply to the machine-level policy. Users who are not administrators do not have sufficient rights to modify the machine policy, even though they can view it. For administrators, -machine is the default. Adds a code group under group 1.2. In the default policy, group 1.2 is the Local Intranet group, so the new code group that you are creating is checked only if the file comes from the intranet. The membership condition for the new code group should be a UrlMembershipCondition, and it should match anything with a URL that starts with file:// <servername>/Tools, meaning that any file on \\<servername>\Tools share will match this code group. The permission set to grant assemblies that match the code group (in this case, FullTrust). Name of the code group. Adds a code group under group 1.3. In the default policy, group 1.3 is the Internet group, so the new code group that you are creating is checked only if the file comes from the Internet. Note: If the machine under test is not under a specific or user domain, the syntax of the CasPol utility is:
ag 1.2
url file: //ServerName/ Schlumberger/ Merak/* FullTrust n ag 1.3
CasPol.exe -m -ag 1.3 -url file: \\servername\serverpath\program files\schlumberger\merak 2013.1\* FullTrust -n Merak2013.1
Note: The contents of this table are based on material from the MSDN .NET Security Blog. For more information, read Code Access Security Policy Tool (Caspol.exe) at http://msdn.microsoft.com/en-us/library/cb6t8dtz(VS.71).aspx or Using CasPol to Fully Trust a Share at http://blogs.msdn.com/b/shawnfa/archive/2004/12/30/344554.aspx.
28

Section 4: Post-installation
This section covers how to set up your Oracle and SQL Server data sources, and also how to install or upgrade databases and reset passwords using Merak Database Toolkit. After installing Merak 2013.1, review: Section 4: Post-installation on page 29 if you have added Merak Peep 2013.1 to run alongside a previous Merak Peep installation. ODBC data source setup on page 29 to understand how to set up your Oracle and SQL Server data sources.
Installing and upgrading databases on page 32 for instructions on installing new databases or
upgrading existing databases.
Merak database users and roles on page 36 to read about how to reset Merak database
passwords and Merak database role passwords for secure databases.
ODBC data source setup

The ODBC Administrator allows you to add, modify or delete ODBC data source names (DSN). Because Merak applications are 32-bit applications, you must use 32-bit ODBC drivers and OLE DB providers when configuring your database. Merak applications will not work with 64-bit ODBC or OLE DB drivers. For a list of supported Oracle drivers, see Oracle 10.2.0.X and 11.2.0.X on page 9. For a list of supported SQL Server drivers, see Microsoft SQL Server 2008 on page 9.
Oracle 32-bit drivers on a 64-bit operating system

Oracle provides separate Oracle Client installations for 32 and 64-bit operating systems. For Merak, you must install the Oracle Client 32-bit drivers when using a 64-bit operating system. Installing the Oracle client 64-bit will not install the 32-bit versions of the Oracle ODBC and OLE DB drivers.
Windows Platform.
For more information read the Oracle Metalink article ID 870253.1 32-bit Client Install on 64-bit
SQL Server 32-bit drivers on a 64-bit operating system

Microsoft provides separate SQL Server Client installations for 32 and 64-bit operating systems. Installing SQL Server Client tools 64-bit also installs the 32-bit versions of the SQL Server Native Client ODBC and OLE DB drivers.
Setting up ODBC Data Sources on a 64-bit operating system

After installing the 32-bit versions of the ODBC and OLE DB drivers, you must use the 32-bit ODBC Data Source Administrator tool to create the DSN. On a 64-bit operating system, this tool can generally be found in: On a 32-bit operating system, this tool can generally be found in:
C:\Windows\SysWOW64\odbcad32.exe. C:\Windows\system32\odbcad32.exe.

29
Setting up Oracle data sources

This section assumes that you have the required ODBC and OLE DB components installed on your system. For a list of supported Oracle drivers, see Oracle 10.2.0.X and 11.2.0.X on page 9. 1. If you are using Windows (32-bit) to set up a DSN, use the ODBC Data Source Administrator tool found in C:\Windows\system32\odbcad32.exe. If you are using Windows (64-bit), you must use the 32-bit ODBC Data Source Administrator tool found in: C:\Windows\SysWOW64\odbcad32.exe. 2. In the ODBC Data Sources Administrator dialog box, click Add to create a new data source. 3. In the Create New Data Source dialog box, select a supported Oracle ODBC driver, and then click Finish. 4. Complete the following fields in the Oracle ODBC Driver Configuration dialog box: Data Source Name and Description: Type the name and a description of the database to which you will point the data source. TNS Service Name: Select the location of the Oracle database that contains the data retrieved by the ODBC driver. User ID: Type the user name of the account (located on the server) that will access the data (e.g. the schema owner).
5. Ensure that the Enable Query Timeout check box is cleared (as shown above). 6. Click the Test Connection button to verify that you are connected to the database server. 7. When the test is successful, click OK.
Setting up SQL Server data sources

This section assumes that the required ODBC and OLE DB components are installed on your system. For a list of supported SQL Server drivers, see Microsoft SQL Server 2008 on page 9. 1. If you are using Windows (32-bit) to set up a DSN, use the ODBC Data Source Administrator tool found in C:\Windows\system32\odbcad32.exe. If you are using Windows (64-bit), you must use the 32-bit ODBC Data Source Administrator tool found in: C:\Windows\SysWOW64\odbcad32.exe. 2. In the ODBC Data Sources Administrator dialog box, click the System DSN tab and then click Add to create a new data source. 3. In the Create New Data Source dialog box, select SQL Server Native Client 10.0 and then click Finish.
30

4. On the first page of the Create a New Data Source to SQL Server wizard: Type a name and description of your database. From the Server drop-down list, either type the name of the SQL Server instance or select the SQL Server you want to connect to and then click Next.
5. On the second page of the wizard, select the With SQL Server authentication option and type the login ID and password for your SQL Server. Windows Authentication is not currently supported by Merak.

31
6. On the fourth page of the wizard, select the Change the default database to check box, and select the database you will be using from the drop-down list. No other changes are required on this or the following pages.
7. Click Finish to complete the setup of your SQL Server database. A confirmation dialog box opens, displaying the details of the data source you have created. Click the Test Data Source button to verify the connection. 8. Click OK if your connection is successful.
Installing and upgrading databases

Merak Database Toolkit (DBTools) is used to create the database objects (such as tables, views, procedures, etc.) for new Merak databases, upgrade existing database table structures, and reset passwords required to run applications in the Merak 2013.1 suite. Note: You must have Windows Administrator privileges to run Merak DBTools. Before creating or updating your table structure for the Merak database, you must ensure that the database and ODBC versions comply with the supported versions listed in this installation guide. Using Oracle, SQL Server, and ODBC versions not supported by Merak 2013.1 can cause applications in the suite to fail. For more information about the supported database versions, see Merak 2013.1 database server requirements on page 8.
32

Creating a new Merak database

For this type of database SQL Server Oracle Do this Create a new empty database with the sa user. Create data and index tablespaces. Run the Ora_SetupDBTools_10g11g.sql script as either system or DBA user to create an Oracle user. This script is located in the Resource\Database Scripts folder of the Merak installation DVD. For more information about this script, see Appendix A: Creating an Oracle user script on page 41.
Installing new databases

Before installing the database, ensure that you have performed these tasks: Created a new empty SQL Server or Oracle database. Installed Merak Database Toolkit from the Merak 2013.1 installation DVD. For more information about the installing Merak Database Toolkit, Section 3: Merak suite installation p. 18. Created an ODBC data source using a supported driver, and using the 32-bit ODBC Data Source Administrator. For more information about creating ODBC data sources, see ODBC data source setup on page 29. For more information about supported ODBC drivers, see Merak 2013.1 clientside database requirements on page 8.
1. Open Merak Database Toolkit, select Install a new database, and click Next.
2. On the Select Data Source dialog box, select the Merak data source from the ODBC Data Sources drop-down list.

33
3. Type your user ID and password in the ODBC Security fields to access your Oracle or SQL Server database. For Oracle databases, this should be the schema owner (the owner of the Oracle objects). For SQL Server databases, this should be the sa user and password. For more information about the necessary privileges, see Database privileges and permissions on page 10.
4. On the Application Select dialog box, select the applications to install in the database.
5. DBTools creates a transaction log that records the progress of the database creation, and can be used to troubleshoot problems with the installation. By default, a log file called Install.log is saved to the system Temp directory. Update the path and file name if desired, and click Next. 6. If you are installing an Oracle database, select the data and index tablespaces that you want to populate. DBTools will verify that there is enough free space available in the tablespaces selected before allowing you to continue. 7. Click Finish to install the database. Notes: If an error occurs during the process, stop the installation, retain the log file and contact SIS Support. By default, the log file install.log is located in the same directory that the system environment variable TEMP points to. The most common reason for database installation to fail is an unsupported ODBC driver. If this occurs, delete the database, create a new blank database, and install the tables again using a supported driver. For more information about supported ODBC drivers, see Merak 2013.1 client-side database requirements on page 8.
34

Upgrading existing databases

In order to trim down the Merak Installation Guide and make the upgrade process more seamless, some of the less-frequently required documentation relating to upgrades from older versions has been made available on the SIS Support Portal. 1. If upgrading from an Oracle database version prior to 4.2, you must perform several manual steps to determine if the RS_SUMMARY_RESULT_SET table has been customized, and to prevent the loss of any data. The steps must be run BEFORE upgrading your database with Merak Database Toolkit. 2. If upgrading from a Peep database version prior to v4.4, you must trigger the document dependency update through the Peep application, which must be run after you have upgraded both the software and databases. 3. If upgrading from any Merak database version prior to v2007.1, you must upgrade your databases with DBTools in two steps. 4. If you meet any of the conditions above, search the Knowledge Base for either Merak upgrade older database or Knowledge Base article 5029471 before proceeding with the DBTools upgrade. You can access the Knowledge Base by logging into the SIS Support Portal at https://support.slb.com/. Before upgrading a database, ensure that you have performed these tasks: Backed up the database. Installed Merak Database Toolkit from the Merak 2013.1 installation DVD. For more information about the installing Merak Database Toolkit, see Section 3: Merak suite
installation p. 18.
Created an ODBC data source using a supported driver, and using the 32-bit ODBC Data Source Administrator. For more information about creating ODBC data sources, see ODBC data source setup on page 29. For more information about supported ODBC drivers, see Merak 2013.1 client-side database requirements on page 8. Note: Ensure all data is backed up before upgrading your database, because if errors occur during the upgrade, you will need to restore the database to its previous state.
5. Open Merak Database Toolkit and select Upgrade an existing database, and then click Next to open the Select Data Source dialog box.
6. Select the Merak data source from the ODBC Data Sources drop-down list.

35
7. Type your user ID and password in the ODBC Security fields to access your Oracle or SQL Server database. For Oracle databases, this should be the schema owner (the owner of the Oracle objects). For SQL Server databases, it should be the sa user. For more information about the necessary privileges, see Database privileges and permissions on page 10.
The Application Upgrade Selection dialog box automatically upgrades all Merak products and objects to use
8. Note: Only the currently installed products are enabled. 9. DBTools creates a transaction log that records the progress of the database creation, and can be used to troubleshoot problems with the installation. By default, a log file called Install.log is saved to the system Temp folder. Update the path and file name if desired, and click Next. 10. If you are installing an Oracle database, select the data and index tablespaces that you want to populate. DBTools verifies there is enough free space available in the tablespaces selected before allowing you to continue. 11. Click Finish to upgrade the database. Notes: If an error occurs during the upgrade process, stop the upgrade, restore the schema from the backup, retain the log file, and contact SIS Support. By default, the log file install.log is located in the same folder that the system environment variable TEMP points to. The most common reason for database upgrade to fail is an unsupported ODBC driver. If this occurs, restore the database from the backup, and upgrade the database again using a supported driver. For more information about supported ODBC drivers, see Merak 2013.1 client-side database requirements on page 8.
36

Merak database users and roles

Resetting Merak database passwords for secure databases
Updating Merak database user and role passwords could be a regularly scheduled task to meet internal software security policies, or it may be necessary after moving a database to a new SQL Server instance or Oracle server. Since the passwords are stored in the Merak database in an encrypted state, it is necessary to update the APP_USER and ADMIN_ROLE passwords using DBTools. Depending on the mappings in the database, it may also be necessary to update the Oracle schema owner and SQL Server sa user using DBTools. Note: You must have Windows Administrator privileges to run Merak DBTools. 1. Open Merak Database Toolkit and select Add and reset database security accounts.
2. Select the data source in which you want to reset user passwords from the ODBC Data Sources drop-down list.
3. Type your user ID and password in the ODBC Security fields to access your Oracle or SQL Server database. For Oracle databases, this should be the schema owner (the owner of the Oracle objects). For SQL Server databases, it should be the sa user. For more information about the necessary privileges, see Database privileges and permissions on page 10.

37
4. On the Security Manager dialog box, select Reset Merak database user password from the Operation drop-down list, and then select the user name from the Username drop-down list. This is a list of all of the database logins mapped to application users.
5. Type a new password for the database user. 6. Click Save to reset the database password; you should receive a Processing Complete message. The encrypted version of the new password will then be adjusted and applied to all of the application users who are mapped to this database user. 7. Repeat steps 4 to 6 for each user in the Username drop-down list. 8. On the Security Manager dialog box, select Reset Merak database role password from the Operation drop-down list, and then select a role from the Role drop-down list. This list shows all database roles that are mapped to application users.
9. Type a new password for the role. 10. Click Save to reset the password in the database for the role selected; you should receive a Processing Complete message. The encrypted version of the new password will then be adjusted and applied to all of the application users mapped to this role profile. 11. Repeat steps 8 to 10 for each role in the Role drop-down list. 12. Click Finish when the password for each user and role has been reset. Note: The BOOT_USER password is not stored in the Merak database. The password should be reset directly using Oracle or SQL Server tools.
38

Adding new database user accounts for secure databases

You can use DBTools to add new database user accounts. Generally you would add database users only if you wanted an application user to connect as a different database user than the APP_USER. This could allow you to assign different resource profiles to certain application users, or allow database-level auditing of certain application users. DBTools will create the new user in the database, and grant the same synonyms and grants as the APP_USER. After adding new user accounts using Merak DBTools, you can use the Merak Administration Console (MAC) to map the application users to different database user accounts. You must have Windows Administrator privileges to run Merak DBTools. 1. Open Merak Database Toolkit and select Add and reset database security accounts. 2. Select the data source in which you want to reset user passwords from the ODBC Data Sources drop-down list. 3. Type your user ID and password in the ODBC Security fields to access your Oracle or SQL Server database. For Oracle databases, this should be the schema owner (the owner of the Oracle objects). For SQL Server databases, it should be the sa user. For more information about the necessary privileges, see Database privileges and permissions on page 10. 4. On the Security Manager dialog box, select Add a new Merak database user account from the Operation drop-down list, and then type a new database user name into the Username field.
5. Type a new password for the database user. 6. Click Save to create the new database user; you should receive a Processing Complete message. The new user will be created, and can now be mapped to application users in the Merak Administration Console (MAC).

39
Section 5: Appendices
This section contains supplemental information about silent installation parameters, creating Oracle users, using scripts to set up user mapping and security, and troubleshooting tips if errors occur during login.
Appendix A: Creating an Oracle user script on page 41 includes a script that must be run every time you install or import an Oracle database. Appendix B: Application user mapping setup for Oracle Merak schemas that have been copied or moved on page 42 shows how to use the Ora_SetupUserMap.sql script to re-build the security
framework after copying or moving a secure or unsecure Oracle Merak schema.
Appendix C: Security script for secure Merak SQL Server databases on page 43 explains how to
use the SS_SetupSecurity.cmd script after copying or moving the MDF file from one SQL Server database instance to another SQL Server database instance. explains some of the common error messages encountered when logging in.
Appendix D: Troubleshooting tips for problems logging into Merak applications on page 47 Appendix E: Parameters for silent installations on stand-alone systems on page 49 describes the
different parameters used in a silent installation script for stand-alone machines.
40

Appendix A: Creating an Oracle user script

You must run the Ora_SetupDBTools_10g11g.sql script whenever you install or import an Oracle database. The script is located in the Resource/Database Scripts folder of the Merak installation DVD.
Working with the script

This script sets the appropriate permissions required for Merak 2013.1. It must be run every time you install or import an Oracle database, and must be run with the system or DBA user. The statements shown in the script below define the permissions.
create role dbtools; grant grant grant grant grant grant grant grant grant grant grant grant grant grant ALTER USER to dbtools ; CREATE ANY SYNONYM to dbtools ; CREATE PROCEDURE to dbtools ; CREATE PUBLIC SYNONYM to dbtools ; CREATE ROLE to dbtools ; CREATE SEQUENCE to dbtools ; CREATE SESSION to dbtools with admin option; CREATE TABLE to dbtools ; CREATE TRIGGER to dbtools ; CREATE USER to dbtools ; CREATE VIEW to dbtools ; DROP ANY SYNONYM to dbtools ; DROP PUBLIC SYNONYM to dbtools ; DROP USER to dbtools ;
The statements shown in the script below create the schema owner who will own the tables. The highlighted parameters must be customized before running the script.
create user <username> identified by <password> default tablespace <data_tablespace> temporary tablespace temp quota unlimited on <data_tablespace> quota unlimited on <index_tablespace>; grant dbtools to <username>; grant grant grant grant create table to <username>; create any synonym to <username>; drop any synonym to <username>; CREATE PROCEDURE to <username>;
To custom ize the script, m odify:

<username> parameter with the actual schema owner name. <password> parameter with the actual password for the schema owner. <data_tablespace> and <index_tablespace> parameters with the actual table space names used to hold the data and indexes.
For information about how to copy or move an Oracle schema, search the SIS Support Portal for either Merak move Oracle schema or Knowledge Base article 4889083. You can access the SIS Support Portal at https://support.slb.com.

41
Appendix B: Application user mapping setup for Oracle Merak schemas that have been copied or moved
Since the contents of this document are intended to be read by a database administrator (DBA), is it highly recommended that the script be deployed by a DBA. The Ora_SetupUserMap.sql script, which is used to build the required security framework for the Merak version 2013.1 database, is located in the Resource/Database Scripts folder of the Merak installation DVD. This script must be run each time you copy or move a secure or unsecure Oracle Merak schema (version 2013.1) from its original location.
Working with the Ora_SetupUserMap.sql script

The Ora_SetupUserM ap.sql script must be run as the schema owner of the Merak object. This script cannot be run as SYS or SYSTEM users. Before running the script, if any of the APP_USER, BOOT_USER, or AUTH_USER exist, drop them. The old username and new username parameters are used when the script is run: old username- identify the previous schema name that is saved in the database with the following script:
select control_string from merak_sys_ctrl_value where control_name='SchemaOwner' and Application_name='DBTools';

new username- The name of the schema at the destination database instance. Update the MERAK_USER_MAP table and Update to ADMIN_ROLE: All rows in the MERAK_USER_MAP table containing APP_USER and ADMIN_ROLE entries are updated from the old username to the new username. Create Oracle users and Oracle role: The Oracle users (APP_USER, BOOT_USER, and AUTH_USER) are created with password M#rak2010, and the password-protected Oracle role (ADMIN_ROLE) is created with password A#min2010. Set grants for Oracle users and Oracle role: Grants are set up for Oracle users (APP_USER, BOOT_USER, and AUTH_USER) and the Oracle role (ADMIN_ROLE). Update the SchemaOwner entry in the MERAK_SYS_CTRL_VALUE table: The SchemaOwner entry in the MERAK_SYS_CTRL_VALUE table is updated to the new username parameter. Update the encrypted passwords in the MERAK_USER_MAP table: The encrypted passwords for any rows containing the APP_USER or schema owner in the MERAK_USER_MAP table are reset to "M#rak2010", and any rows containing the ADMIN_ROLE are reset to "A#min2010". Create synonyms for database objects: Synonyms are created for Oracle users (APP_USER, BOOT_USER, and AUTH_USER). Set temporary and default tablespaces for Oracle users above: The temporary and default tablespaces for Oracle users (APP_USER, BOOT_USER, and AUTH_USER) are set to the same temporary and default tablespaces as the schema owner. Update the password for Administrator and Guest application users: Password for the application users Administrator and Guest is reset to M#rak2010.
The Ora_SetupUserMap.sql script performs several different tasks, including:
42
After the Ora_SetupUserMap.sql script has run successfully: 1. Use Merak Database Toolkit (DBTools) to reset the passwords for the schema owner, APP_USER, AUTH_USER, and ADMIN_ROLE. 2. Use Oracle tools to reset the password for the BOOT_USER. 3. Use the Merak Administrative Console (MAC) to reset the application user passwords for Administrator and Guest. For more information about updating passwords with DBTools, see Merak database users and roles on page 37. For more information about how to copy or move an Oracle schema, search the SIS Support Portal for either Merak move Oracle schema or Knowledge Base article 4889083.
You can access the SIS Support Portal at https://support.slb.com.
Appendix C: Security script for secure Merak SQL Server databases

When you copy or move a secure SQL Server Merak database to a new database instance, the MERAK_APP_USER, MERAK_BOOT_USER and MERAK_AUTH_USER users are not properly linked to their respective logins. For this reason, a script must be run each time after you copy or move a secure Merak SQL Server database from one database instance to a new database instance. There are two options for re-associating the SQL database users and logins: 1. Using the SS_SetupSecurity.cmd, an interactive command prompt script, or; 2. Running a script directly in SQL Server Management Studio. Note: A reset of the database security account passwords may also be necessary in order to synchronize the SQL Server login passwords with the passwords stored in an encrypted state in the database. See Resetting Merak database passwords for secure databases on page 37 for further information.
Working with the SS_SetupSecurity.cmd script

The SS_SetupSecurity.cmd script should be run on Merak secure SQL Server databases after the MDF file has been copied or moved from one SQL Server database instance to another SQL Server database instance. The SS_SetupSecurity.cmd command prompt script (CMD file) uses the Microsoft OSQL utility, an interactive tool that executes transact-SQL statements and scripts. The SS_SetupSecurity.cmd script requires the SQL Server system administrator (sa) credentials.
Running the SS_SetupSecurity.cmd script

1. Open the Resource/Database Scripts folder located on the Merak installation DVD. 2. Double-click SS_SetupSecurity.cmd and type the following information when prompted: SA Password The password for the sa user account. DB Server The full name of your SQL Server instance in the format servername\instancename. DB Name The database name as it is attached in SQL Server. This is not the mdf file name, but the name displayed inside SQL Server Management Studio, OSQL, or SQLCMD.
43
Note: If the database name contains any spaces, you must enclose the entire database name with double quotation marks. 3. After the SA Password, DB Server, and DB Name have been entered, the script displays a summary of this information and the location of the log file (see the image in step 4). Press any key to continue. 4. When the script asks if you want to continue, type either Y or N. If you type Y (to confirm that the information is correct), the script adjusts the logins and database users so they are synchronized again. If you type N (to reject the information entered), the script stops running and doesnt make any changes.
5. Click any key to close the Command Prompt window; the log file will open automatically so that you can verify that the script ran successfully.
Using the LOGIN_ADJUST.LOG file to verify that the SS_SetupSecurity.cmd script ran successfully
The log file from a new SQL Server installation should look like this:
Msg 3701, Level 11, State 5, Server GVEGA-CAL\SS2008, Line 1 Cannot drop the procedure 'check_auth_user', because it does not exist or you do not have permission. Script has been executed on 06/18/2010 at 14:29:08.29
The log file from an existing SQL Server installation that already contains the Merak logins should look like this:
Msg 15025, Level 16, State 1, Server GVEGA-CAL\SS2008, Line 1 The server principal 'MERAK_BOOT_USER' already exists. Msg 15025, Level 16, State 1, Server GVEGA-CAL\SS2008, Line 1 The server principal 'MERAK_APP_USER' already exists. Msg 15025, Level 16, State 1, Server GVEGA-CAL\SS2008, Line 1 The server principal 'MERAK_AUTH_USER' already exists. Msg 3701, Level 11, State 5, Server GVEGA-CAL\SS2008, Line 1 Cannot drop the procedure 'check_auth_user', because it does not exist or you do not have permission. Script has been executed on 06/18/2010 at 14:35:24.72
Contact your local SIS support center if you are uncertain about the log results. For more information, see How to reach us on page 50.
44

Using SQL Server Management Studio to adjust security

Instead of using the SS_SetupSecurity command script, you can run a script directly in SQL Server Management Studio. The lines below only need to be run if the logins don't already exist on the SQL Server instance; simply replace M#rak2010 with the desired passwords (ensuring that they meet the server complexity requirements). If the logins already exist, SQL Server returns an error message and the existing logins and passwords remain unaffected.
sp_addlogin @loginame='MERAK_BOOT_USER',@passwd='M#rak2010' go sp_addlogin @loginame='MERAK_APP_USER',@passwd='M#rak2010' go sp_addlogin @loginame='MERAK_AUTH_USER',@passwd='M#rak2010' go
The lines below need to be run against the Merak database, and will delete and recreate the MERAK_BOOT_USER, MERAK_AUTH_USER, and MERAK_APP_USER database users so that they are linked to the respective SQL logins:
sp_dropuser 'MERAK_BOOT_USER' go sp_dropuser 'MERAK_APP_USER' go sp_dropuser 'MERAK_AUTH_USER' go sp_adduser @loginame='MERAK_BOOT_USER',@name_in_db='MERAK_BOOT_USER' go grant select on merak_users to merak_boot_user grant select on merak_user_map to merak_boot_user grant select on merak_login_vw to merak_boot_user grant select on merak_security_settings_vw to merak_boot_user grant execute on merak_login_update to merak_boot_user go sp_adduser @loginame='MERAK_APP_USER',@name_in_db='MERAK_APP_USER' go sp_adduser @loginame='MERAK_AUTH_USER',@name_in_db='MERAK_AUTH_USER' go

45
Using SQL Server Management Studio to verify that the SS_SetupSecurity.cmd script ran successfully
1. Log in to SQL Server Management Studio open the folder for the desired Merak database, and then open the Security > Users folders.
2. Right-click MERAK_BOOT_USER and choose Properties. The Database User dialog box opens.
If MERAK_BOOT_USER is displayed in the first two fields of the Database user dialog box, then the logins and users are synchronized and the script ran successfully. Otherwise, check if the parameters used in the script are correct, and check the log file for errors. 3. Repeat step 2 for the MERAK_APP_USER and MERAK_AUTH_USER.
46

Appendix D: Troubleshooting tips for problems logging into Merak applications

Default Login Credentials
When logging into a Merak database without Security enabled, you will need only one user name and password: Database user: SA (SQL Server), or schema owner (Oracle) Default password: M#rak2010
When logging into a Merak database with Security enabled, you will be prompted for an Application user name and password, AND a database user name and password: Application user name: Administrator Default application password: M#rak2010 Database user name: MERAK_BOOT_USER (SQL Server), or schemaowner_BOOT_USER (Oracle, where schemaowner is the actual schema name) Default password: M#rak2010 Capital Planning application login user name: SA (SQL Server), or schema owner (Oracle) Default Capital Planning application login password: M#rak2010 Results Broker application login user name: Administrator Default Results Broker application login password: M#rak2010 Secure database login user name: MERAK_BOOT_USER (SQL Server), or schemaowner_BOOT_USER (Oracle, where schemaowner is the actual schema name) Default secure database login password: M#rak2010
When logging into a Capital Planning database with Security enabled, a third login will be required:
Problems logging into Merak applications

Here are some common reasons why a user may not be able to gain access to the Merak database: If you have copied or moved an existing secure Merak SQL Server database to a new instance, the SQL logins and users may not be associated. See Appendix C: Security script for secure Merak SQL Server databases on page 43 for details. If a secure database (Oracle or SQL Server) was moved or copied, or if database passwords including SA or the schema owner were updated, then it could be an issue with the encrypted passwords stored in the Merak database not being synchronized with the actual database passwords. See Resetting Merak database passwords for secure databases on page 37 for further information. If an Oracle database has been moved or copied, a script needs to be run to set up the security framework. This process needs to be done regardless of whether or not the database is secure or unsecure. Refer to "Appendix B: Application user mapping setup for Oracle Merak schemas that have been copied or moved" on page 42 for details.

47
If there is a problem with the mappings of the application user Administrator, they can be corrected with the script below. Replace schemaowner with MERAK for a SQL Server database, and replace schemaowner with the actual schema name (in upper case) for an Oracle database:
UPDATE merak_user_map SET db_user_name = 'schemaowner_APP_USER', db_role = 'schemaowner_ADMIN_ROLE' WHERE (user_guid = (SELECT user_guid FROM merak_users WHERE (user_name = 'Administrator')))
If the Administrator has been marked inactive (for example, if there were several failed login attempts), then you can reactivate the Administrator through the back end with the script:
UPDATE merak_master_objects SET status=0 WHERE object_name LIKE 'Administrator'
If you receive an error message saying that the data source is incorrect or no version, this usually indicates that the database version does not match the application version, and needs to be upgraded with DBTools. See "Upgrading existing databases" on page 35 for details. If the Administrator password is unknown, you can use the script below to reset it to 'M #rak2010' . When complete, log into the MAC with the Administrator and password M#rak2010, then update the password within the application so that it is again stored in an encrypted state in the database.
UPDATE merak_user_map SET user_password = '!JEhedrCb0f2TNfsH3AQHgWTnCJc' WHERE (user_guid = (SELECT user_guid FROM merak_users WHERE (user_name = 'Administrator')))
For more information on common login error messages and their solutions, search the Knowledge Base for either Merak login troubleshooting or Knowledge Base article 4749619. You can access the Knowledge Base by logging into the SIS Support portal at https://support.slb.com.
Problems linking Peep to OFM workspaces

When attempting to link Peep to an OFM workspace, an error may appear stating that the connection failed because Microsoft.ACE.OLEDB.12.0 is not registered on the local machine. Peep uses the ACE driver found in Microsoft Access to link to OFM workspaces. The above error message indicates that this driver is not installed. To resolve this issue, install the 32 bit version of the Microsoft Access Database Engine 2010 redistributable located at http://www.microsoft.com/en-us/download/details.aspx?id=13255.
48

Appendix E: Parameters for silent installations on stand-alone systems

You can deploy silent installations on stand-alone or multiple systems. The silent installation method for stand-alone systems requires little interaction because it uses the msiexec utility to install Merak 2013.1 without an Installation Wizard interface. Note that the default for the installation process is to keep any prior versions of Merak that are already installed to enable a Multiple Version scenario. If you do not want different versions of Merak installed on the same machine, you must first uninstall the previous version using a script you create. Refer to Multiple Versions on page 16 for further details. For more information about deploying Merak 2013.1 using the msiexec utility, see Silent installations on page 23. The table below describes each property of the msiexec utility. This property ADDLOCAL=ALL Means this Which features will be installed. When ADDLOCAL=All, all of the Merak applications and features will be installed, whereas ADDLOCAL=Peep_App,VOLTS_App will only install Peep and VOLTS. Available Features include: Capital Planning: Capital_Planning_App Portfolio Export Wizard: Portfolio_Export_Wizard_App Database Toolkit: Schlumberger_Database_Toolkit_App Decision Tool Kit: Decision_Tool_Kit_App Global Edit: Global_Edit_App Merak Administrative Console: MAC_App Peep: Peep_App o Canadian Economics Regime: PE_Canada3 o US Economics Regime: PE_US 3 o World Economics Regime: PE_World 3 Petroleum Financials: Petroleum_Financials_App Results Broker Administration: RBA_App Results Broker Templates: RBA_Templates Volumetric Tracking System: VOLTS_App VOLTS Report Files: VOLTS_Reports Sample Databases: Merak_Sample_Data4 o Secure Sample Database: Merak_Secured_Sample_Data o Unsecure Sample Database: Merak_Unsecured_Sample_Data Log all information except for Verbose output (v) and Extra debugging information (x) options. The log file property lvx* should be followed by a fully qualified path to a log file (e.g., C:\tmp\MyLogFile.txt).
/lvx* C:\logfile.txt
Peep_App must be selected to install Merak Peep. PE_Canada, PE_US, and PE_World are default installation user preference settings that specify which Peep licenses to request at startup. 4 Merak_Sample_Data must be selected in order to install the sample database(s), in addition to one or both of Merak_Secured_Sample_Data and Merak_Unsecured_Sample_Data.
49
This property IS_SQLSERVER_SERVER=
Means this Type your local SQL server and instance name separated by a backslash (e.g., My_Server\merak), and the password for the sa user where the sample databases should be installed.
Server name\SQL Server instance

IS_SQLSERVER_PASSWORD=
password password
MERAK_AUTH_USER= MERAK_APP_USER=
password
MERAK_BOOT_USER=
password
If installing the sample databases, you will need to provide passwords for the MERAK_AUTH_USER, MERAK_APP_USER, and MERAK_BOOT_USER if they already exist in the SQL Server instance. If the logins dont exist in the SQL Server instance, define a new password and the login will be created. The passwords must meet the local machines security policy.
How to reach us
The Schlumberger Information Solutions (SIS) Support Portal (https://support.slb.com) provides a single location for all your support needs. Within the Support Portal you can quickly search a vast knowledge base for the answers you need, participate with your peers in discussion forums, and receive the latest news about SIS products and services.
To find docum entation in the Support P ortal for the M erak Suite:
1. Log in to the Support Portal and choose Technical Information > Documentation.
2. On the Documentation page, click the Merak Suite link to access release notes, installation guides and user guides for current and previous Merak releases. 3. Alternatively, use the Search field to search the Knowledge Base for solutions. All support requests are entered into the SIS Customer Care Center incident tracking system, where they are resolved by local support staff. For those times when you need to speak with a support specialist, contact numbers are provided for your local support center. You can also submit support requests via e-mail, at customercarecenter@slb.com.
50

For Merak software products, you can obtain assistance from local experts by calling one of the numbers listed below.
United States Houston Tel.: 1-866-829-0234 Canada Calgary Tel.: 1-888-986-4357 (toll-free) United Kingdom Tel.: 0800 328 9055 (toll-free) Russia and Caspian Moscow Tel.: 7 495 935 8200 Ext. 1218 Latin America Mexico Tel.: 001 866 326 0174 Argentina Tel.: 0 800 444 0919 International Offices Brazil Tel.: 000811 005 9068 Colombia Tel.: 980912 3029 Venezuela Tel.: 0800 1 00 3588 Middle East Egypt Tel.: +20 2 768 4881 United Arab Emirates Tel.: +971 2 632 2065 Kuwait Tel.: +965 9 720 3573 Asia Pacific Malaysia Tel.: +1-800-88-2299 Indonesia Tel.: +62-21-5229343 Australia Tel.: +61-1800001112 Thailand Tel.: +66-2-9371300 China Tel.: +86-10-64746699 Ext. 2816
Merak is a product line of Schlumberger Information Solutions (SIS). For more information about SIS, please go to our Web site at http://www.slb.com/services/software.aspx.

51

Merak Installation Guide

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Merak Installation Guide

Enviado por

Direitos autorais:

Formatos disponíveis

Merak planning, risk & reserves