OpenWorks R5000 Data Sources Configuration

OpenWorks R5000 can be configured for Linux or Windows platforms.

Selecting the option to create a OpenWorks R5000 data source displays the following panel on the right-hand side of the Data Source Configuration tool.

Figure 10: OpenWorks R5000 data source

 

Before filling out this panel, ensure that you refer the following table:

Name

Description

Hints & Finding Values

Data Source Name

Free form name for data source

Names might NOT contain blanks, the period character (“.”), or other special characters that are not allowed in UNIX file names. Also, the data source name must be unique within the same OpenSpirit installation.

OWHOME

Directory location of OpenWorks installation

Your system administrator must have this information.

LM_LICENSE_FILE

Location of the OpenWorks license file

Normally found at $OWHOME/lam/license.dat. This value can also be in the form of port@host

PLATFORM/VER

Operating System of the OpenWorks installation

This value defaults to the Operating System of the host where the desktop is running for configure.

OW_CONF_DIR

Location of the OpenWorks configuration directory.

Your system administrator should have this information. It must be the directory that contains your OpenWorks district.dat file.

OW_DISTRICT

OpenWorks District to be used are set up by the OpenWorks administrator. Configure multiple OpenSpirit data sources to access more than one OpenWorks district. The districts that are available for selection are read from the district.dat file.

OpenWorks District to be used are set up by the OpenWorks administrator. Configure multiple OpenSpirit data sources to access more than one OpenWorks district. The districts that are available for selection are read from the district.dat file.

OWSYSSID

Display only field that shows the OpenWorks Oracle instance name.

The Oracle SID is obtained from the district.dat file. It is based on the selected OW_DISTRICT.

TNS_ADMIN

Directory location where the tnsnames.ora file is located for this Oracle installation

Normally, the administration files are in $ORACLE_HOME/network/admin.

SYSADM_USER_NAME

Oracle account for OW project information

Your system administrator should have this information. It should be the Oracle account that owns the Oracle schema containing the OW_SYS_PRJ_USER table.

DB URL

OpenWorks Oracle database instance connection information (host, port, and SID).

See previous explanation.

Query Account

Oracle database account and password used to obtain a list of the OpenWorks projects.

Can be any Oracle database account that has selected privilege on the ${SYSADM_USER_NAME}.OW_SYS_ PRJ_USER table, where ${SYSADM_USER_NAME} is the value.

Use EPSG Codes

Give precedence to a coordinate system or transform the EPSG code (if available) when detecting the coordinate system.

Companies that tag their coordinate systems and transforms in their coordinate catalogs with EPSG codes may consider using this option. If checked, OpenSpirit uses the EPSG code to create the coordinate system. All transform and other coordinate-related parameters, including the project horizontal unit, is ignored. When the specified EPSG code is not found in the OpenSpirit's EPSG database, then the existing mechanism of using coordinate parameters is used.

Increment Pick Occurrence

Check this option to turn on incrementing the pick_obs_no value when inserting well picks.

The pick_obs_no value used to insert is one greater than the highest existing number for picks having the same well id, name, and interpreter.

Skip well status mapping

Selecting this option causes well status values to be passed through as it is on both read and write rather than converting them to the OpenSpirit canonical status values.

Enabling this option prevents successful copying of well status information when using the OpenSpirit Copy Manager to copy data from one data store type to a different data store type. Copying between dissimilar data store types usually requires well status information to be mapped from the source data store's well status values to the OpenSpirit well status values and then to the target data store's allowable values. Disabling this mapping may cause copied wells to have an UNKNOWN status.  The skip option is typically used when importing well status information from a data store to an application such as Petrel. Select this option if you want to preserve the original well status value, rather than using the OpenSpirit canonical well status values.

OW_HOME_DIR

Linux: Directory that should be used as the OW_HOME_DIR directory. Windows: Full path to directory containing the wallet folder

Companies that locate their UNIX OpenWorks users' Oracle wallet directories in a directory other than the user's home directory should set this field. It is required for Windows configuration.