Omega 2017.

1 Quick Start Guide - Omega Windows

Installation

Document Version Control

Classification Schlumberger Private - Customer Use
Release 2017.1
Date 07 Aug 2017
Source QsgOmegaWindowsShell
Copyright © 2017 Schlumberger. All rights reserved.
This document is copyright protected. No part of this document may be reproduced, stored in a retrieval system,
or transcribed in any form or by any means, electronic or mechanical, including photocopying and recording,
without the permission of Schlumberger. Further, the document contains information proprietary to Schlumberger
and should not be disclosed or distributed to third parties without the permission of Schlumberger. To the extent
that documents are provided in electronic format, Schlumberger grants permission for the document to be stored
electronically. All other restrictions set forth above regarding the document's use or distribution shall apply.

Schlumberger Trademarks & Service Marks

Schlumberger, the Schlumberger logotype, and other words or symbols used to identify the products and services
described herein are either trademarks, trade names, or service marks of Schlumberger and its licensors, or are the
property of their respective owners. These marks may not be copied, imitated or used, in whole or in part, without
the express prior written permission of Schlumberger. In addition, covers, page headers, custom graphics, icons,
and other design elements may be service marks, trademarks, and/or trade dress of Schlumberger, and may not be
copied, imitated, or used, in whole or in part, without the express prior written permission of Schlumberger.

Other company, product, and service names are the properties of their respective owners.

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

 Table of Contents
Note............................................................................................................................................................................1

1 Network and user accounts..................................................................................................................................2

2 Linux Side Preparation.........................................................................................................................................3

2.1 Configuration entries...............................................................................................................................3
2.2 Check Samba setting on all file servers..................................................................................................4
2.3 Install Global Repository RPMs.............................................................................................................5
2.4 Start Windows Update service................................................................................................................7

3 Omega Desktop Installation on Windows...........................................................................................................8

3.1 Software needed for each PC..................................................................................................................8
3.2 Install Open Text Exceed 14 x64 and Open Text Secure Shell 14 x64 on each PC...............................8
3.3 Register Linux user id and password in Open Text Exceed on each PC................................................9
3.4 Install prerequisite software from DVD OmegaWindowsDesktop on each PC.....................................9
3.5 Install Omega Desktop Update from DVD OmegaWindowsDesktop on each PC................................9
3.6 Install Omega desktop from DVD OmegaWindowsDesktop on each PC..............................................9
3.7 Select Omega site and force Omega update on each PC......................................................................10
3.8 Open Omega desktop and test on each PC...........................................................................................12

i
Note
• For a transition installation, please refer to the 2017.1 Transition Guide (also available on the 2017.1ext
DVD and the external client support portal) .
• Please follow Quick Start Guide for System Preparation to prepare hosts and system side first.
• This Quick Start will prepare Windows installation on Linux side and install Omega Desktop 2017.1 on
Windows side. To install Omega on Linux side, please follow Quick Start Guide for Omega Linux
Installation. To install OCM, MMS and WHSM, please refer to separate quick-starts or the Omega
Admin Guide.

Schlumberger Private - Customer Use 1

1 Network and user accounts
Omega Windows Desktops (WDT) need to be able to talk to at least the following hosts: Omega Global
Repository server, Windows Update Server, Omega license servers, Oracle servers, OPM/CORBA/WSN/RDM
server, File Servers (samba hosts), Job submit hosts, Linux backend login nodes, Linux NIS server

These servers need to have public IP addresses that can be resolved on Windows side.

It s best the Linux and Windows side share the same DNS server. If two sides do not share the same DNS and if
we only have a few WDTs, we can add the hostname and IP in c:\Windows\System32\drivers\etc\hosts file on
each PC.

Currently Omega Desktop on Windows require same user id on both Windows side and Linux side. The Linux
user id should be lower case. The same omega user id needs to be a member of the Omega project group to work
in the Omega project. Usually we add the same user id in both Windows AD and Linux side NIS.

The account to install all Omega software on the PC need to have local administrator privilege. The Omega user
account can have non-admin privilege.

Account omadmin is needed on the Omega Global Repository server and this account needs to be owned by
omadmin group.

Schlumberger Private - Customer Use 2

2 Linux Side Preparation
2.1 Configuration entries
Omega Desktop on Windows needs to communicate with Windows Update Server (WUS) and Omega Global
Repository server (GR) on Linux side to get configuration and updates from Linux side.

Most centers just need one Omega Global Repository server and one Windows Update Server. These two roles
can be set up on one Linux server. Usually we use the OCM server as Omega Global Repository and Windows
Update Server.

Configure the following entries in Configuration.omcdb file.

Table: Entries in Configuration.omcdb file

Configuration Entry Explanation Recommended Setting

Omega.WindowsUpdate.GlobalRepositories Omega Global Repository Server host xxoc001.dnsdomain.com
Omega.WindowsUpdate.LocalServers Omega Windows Update Server host xxoc001.dnsdomain.com
NIS server for all Omega system
Omega.WindowsUpdate.NISServers NIS master server name
accounts
Omega.WindowsUpdate.PortNumber Port number for Windows update service 56000 (default)

# on xxoc001
su - omadmin
omega2 config&
# open /wg/omega/2017.1####/share/config/Configuration.omcdb
# browse through the entries and update the value
# then save and close the file

# push out the updates if we have login nodes with local /wg
cd /wg/omega/support/rsync
scripts/rsync_push&
watch ls status

Schlumberger Private - Customer Use 3

2.2 Check Samba setting on all file servers

2.2 Check Samba setting on all file servers

Windows desktops need to see project setup file systems, bulk seismic file systems and interactive application or
Petrel file systems.

In our example, the servers that host the following file systems need to set up Samba:

• /ud/
• /wgdisk/xx0100
• /wgdisk/xx0200
• /inter01

Sample Samba configuration (using Active Directory on Windows side):

[root@xxfs001 samba]$ cat smb.conf | grep -vE '#|^$|;'

[global]
realm = dnsdomain.com
workgroup = dnsdomain
netbios name = DOMAINXXFS001
name resolve order = host bcast wins
server string = xxSite file server xxfs001
password server = *
wins server = x.x.x.x
security = ADS
encrypt passwords = yes
template shell = /bin/false
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
hosts allow = 127.0.0.1 x.x.x.0/16
hosts deny = 0.0.0.0/0
deadtime = 2
keepalive = 0
log file = /var/log/samba/%m.log
max log size = 1000
log level = 1
local master = no
preferred master = no
winbind use default domain = Yes
preserve case = Yes

Schlumberger Private - Customer Use 4

2.3 Install Global Repository RPMs

case sensitive = Yes

load printers = no
printcap name = /etc/printcap
printing =
max protocol = SMB2
fake oplocks = yes
use sendfile = true
[xx0100]
comment = /wgdisk/xx0100
path = /xx0100
read only = No
create mask = 0664
directory mask = 2775
[inter01]
comment = /inter01
path = /inter01
read only = No
create mask = 0664
directory mask = 2775

Start Samba services on each file system host:

# as root on each file server

cat /etc/samba/smb.conf | grep -vE #|^$
service smb status
# start it if smb service off
service smb start
# if Linux file server not added to Windows side Active Directory
# windows machine won't see the linux shares even smb service is up
net ads join -U ADadminAccount

On one WDT, check if these file systems are exported correctly. In address bar of Windows Explorer, type
\\xxfs001\xx0100.

2.3 Install Global Repository RPMs

We need to install the following 5 RPMs on the Omega Global Repository server:

• apache-cxf-2.2.7-2.x86_64.rpm

Schlumberger Private - Customer Use 5

2.3 Install Global Repository RPMs

• apache-log4j-1.2.16-2.x86_64.rpm
• globalrepository-2.0-2.x86_64.rpm
• globalrepository_services-2.0-2.x86_64.rpm
• java-mail-1.4.4-2.x86_64.rpm

We have a convenient script to install the above RPMs on the Omega Global Repository server.

The script installGlobalRepositoryRPMs.sh is under /01-OmegaLinux/03-Miscellaneous/RPMs of DVD

OmegaAndOCM.

Please copy /01-OmegaLinux/03-Miscellaneous/RPMs to

/wg/omega/installations/Omega2_Miscellaneous_Files/RPMs directory.

# to find out which servers are defined as Global Repository servers

# the entry is under Omega.WindowsUpdate.GlobalRepositories
omega2017.1### dump-config | grep -A 10 GlobalRepo

# to install these RPMs as root on the designated Omega Global Repository server
# in this example xxoc001
su - root
cd /wg/omega/installations/Omega2_Miscellaneous_Files/RPMs
sh installGlobalRepositoryRPMs.sh
# answer 'n' to install the RPMs

# config Global Repository service, as omadmin on xxoc001

su - omadmin
cd /wg/omega/GlobalRepository/common/config
ls
vi Application.properties
# in the file replace repository1 server name
REPOSITORY1=xxoc001.dnsdomain.com
# Comment out REPOSITORY2
# Leave REPOSITORY_PORT=55000 unchanged

# turn on service in chkconfig

su - root
chkconfig omegaupdaterepository on

# start service

Schlumberger Private - Customer Use 6

2.4 Start Windows Update service

service omegaupdaterepository restart

sleep 5
service omegaupdaterepository status
# to trouble-shoot and check logs
less /var/log/updaterepository/Repository.log

2.4 Start Windows Update service

Start omegawindowsupdate service on the Windows Update server.

# on xxoc001
su - root
service omegawindowsupdate start
service omegawindowsupdate status

# to trouble-shoot issues, check log at /wglogs/omega/windowsupdateserver/

_Note: Omega.WindowsUpdate.PortNumber cannot be the same as REPOSITORY_PORT in

/wg/omega/GlobalRepository/common/config/Application.properties. The recommended port for the
WindowsUpdate.PortNumber is 56000 and REPOSITORY_PORT is 55000.

Schlumberger Private - Customer Use 7

3 Omega Desktop Installation on Windows
3.1 Software needed for each PC
Omega Desktop requires Open Text Exceed 14 x64 and Open Text Secure Shell 14 x64. These two software
packages are not included on the DVD. The Client needs to purchase these for themselves.

Other pre-requisite software includes: Perl, Python, Ruby, .NET Framework 4.x and Microsoft Visual C++ 2015
Redistributable.

Perl, Python, and Ruby are included in the DVD OmegaWindowsDesktop

The .NET Framework 4.6.2 and MS VC++ 2015 redistributable can be downloaded with the links below:

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

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

3.2 Install Open Text Exceed 14 x64 and Open Text Secure
Shell 14 x64 on each PC
Just accept the defaults.

After system reboot, double check the system environment variable path and Exceed installation folder.

A few utility relies on Exceed. If Exceed path is not added to system environment variable 'Path', we will see
errors like below:

Error: could not find Hummingbird Exceed executable. Please define Exceed xstart.exe path in Windows' path.

To fix the issue, append 'C:\Program Files\Hummingbird\connectivity\14.00\Exceed' to system environment path

(restart Omega desktop if you encountered the error from Omega).

Schlumberger Private - Customer Use 8

3.3 Register Linux user id and password in Open Text Exceed on each PC

3.3 Register Linux user id and password in Open Text Exceed

on each PC
Register Linux user name and password with Exceed Connection Manager .

Find the program from Start -> All Programs -> Open Text Exceed 14 x64.

From the Exceed Connection Manager window, click on Tools -> Xstart Global Options -> enter Linux user
id and password at the top, then click OK.

Note: each time a user resets Linux side password, the user will need to reregister the Linux password here.

3.4 Install prerequisite software from DVD

OmegaWindowsDesktop on each PC
unzip 03-Miscellaneous\Prerequisites\ThirdPartiesTools\Omega_2017.1_Prerequisites.zip.

Double click InstallOmegaPrerequisites.bat to install Strawberry Perl 5.24.0.1 , Python 2.7.12 and Ruby 1.9.2.

3.5 Install Omega Desktop Update from DVD

OmegaWindowsDesktop on each PC
Run 03-Miscellaneous\Prerequisites\OmegaDesktopUpdate\OmegaDesktopUpdate.17.1.17171.1.msi.

When prompted for global repository server name, enter the GR server name.

3.6 Install Omega desktop from DVD OmegaWindowsDesktop

on each PC
Run 02-Installation\Omega-2017.1xxx.msi and accept the default.

Schlumberger Private - Customer Use 9

3.7 Select Omega site and force Omega update on each PC

3.7 Select Omega site and force Omega update on each PC

From Start -> All Programs -> Schlumberger -> Omega Desktop Update -> Omega Site Selector -> select site
xxSite and click Ok .

From Start -> type in event viewer in search program and files field and hit Enter .

Then click on Windows Logs -> Application, and look for Omega Desktop Update logs. Press F5 to refresh until
the update is complete. Check if there are any errors here.

Schlumberger Private - Customer Use 10

3.7 Select Omega site and force Omega update on each PC

It may take a few minutes for the updates to finish.

Now check in C: and see if you see /ud and /wgdisk shortcuts (assume you use /wgdisk and /ud for seismic data
and project data directory) .

Click on /ud and /wgdisk/xxxxx and see if you can click through. If not, verify the samba setting and Linux user
id registration in Open Text Exceed.

Schlumberger Private - Customer Use 11

3.8 Open Omega desktop and test on each PC

3.8 Open Omega desktop and test on each PC

Bring up Omega2017.1###p on the Windows machine and submit one job.

Please make sure the Windows user name exists on the Linux side and is a member of the project group.

Open Xterm from Programs -> T-Z -> Xterm. If you could not open Xterm, check if you have login nodes
defined in RDM. And check if your Linux password is correct.

Open QCviewer and Attribute Display. If you can open Attribute Display but not QCviewer, then check firewall
setting and the group policy. Turn firewall off and see if you have the issue or not. Or unplug the network cable,
reboot the machine and see if you can open QCviewer.

Schlumberger Private - Customer Use 12