A Petrosys installation can be tailored to the needs of a specific site by putting custom configuration information into a generally accessible folder referred to as ‘ps_local’. Amongst the site specific information managed in ps_local are site specific entries for the CRS database, the list of active projects, multi-connect data links, custom title blocks, site specific plotter configurations, custom well symbols and general company information.

‘ps_local’ is actually just a folder (directory) that is identified by the system variable ‘$ps_local’ in Linux and PS_LOCAL in Windows. It typically has the name ‘local’ and by default resides in the Petrosys tree above or beside the version specific branches.

It’s increasingly common for larger sites to use Petrosys in both Windows and Linux environments, requiring separate software installation locations. Fortunately this does not mean that two separate ‘ps_local’ configuration directories are required, with the associated problems of managing multiple versions of custom CRS, title blocks, logos and other materials.

Only a small subset of configuration material is operating systems dependent; here’s how you can maximize the sharing of configuration data across platforms.

  1. You need to have Petrosys installed on a Linux and a Windows system to start and you need to know where the ‘ps_local’ directories for each of those installations is located.
  2. On a network shared drive that is accessible by both Linux and Windows systems, create a directory for your new ps_local with any name that makes it easily identifiable, eg. local_global.
  3. Copy all the files from the ‘best’ ps_local in your current installation to that new directory.
  4. In your new ‘local_global’, create sub-directories for each operating system to be supported. These must currently have the specific names linux_rhel4 for Linux and win32 for Windows.
  5. Now move the platform specific files from the local_global down to the appropriate platform specific sub-directory, for example if you had copied a Linux ps_local, move them to linux_rhel4. The platform specific files are listed below.
  6. For the ‘other’ operating system, copy the same files from a ps_local in a Petrosys installation on that operating system.
  7. Finally, point your existing Linux installation to the new local_global by changing the environment variable in the file ‘petrosys.cfg’ at the root of the Linux Petrosys installation and update your existing Windows installations by changing the registry key (for Windows 32-bit)

\HKEY_LOCAL_MACHINE\Software\
Petrosys\Mapping\CurrentVersion\LocalDir

or (for Windows 64-bit)

\HKEY_LOCAL_MACHINE\Software\Wow6432Node\
Petrosys\Mapping\CurrentVersion\LocalDir

Do NOT include the operating specific suffix, such as win32 or linux_rhel4, in the directory names specified here.

The operating systems dependent files that need to be moved into the operating systems sub-directories are:

 

pscfgfil Contains platform specific setup commands and plotter configurations.
connections.xml The multi connect configuration file, it usually contains operating systems specific references.
titleblk.pnx This file may or may not exist, it contains a dialogue to get information for map title blocks in a site specific manner.

Files that can be shared at the top level ps_local directory include the CRS database ps_crs_site_sdb, the default query database psyslite.sdb, text based configuration files such as datummap.dat and wellinfo.dat, the source to title block dialogues such as titleblk.pnl, custom title block CGM files, and commonly used images such as company logos.

The project list file ‘projects.plf’ can be shared at the moment but you will need to add the project once for Windows and again for Linux. Petrosys only displays directories in the Project list that can be resolved by the operating system. It does not convert forward and backward slashes from one operating system to the other. Also, in Linux, Petrosys displays the owner of the directory, which isn’t available in the Windows project list.

When Petrosys looks for a configuration item, it will look in the operating systems specific subdirectory first, then go to the higher level if the entry is not found.

For more information see the online help topics on ‘Configuration and Installation / Site Configuration’ or contact Petrosys Support.