Master Installation
A master installation is a configuration of the OpenSpirit Runtime that runs two service processes and manages a database of information needed by the OpenSpirit framework. A master installation is identified by the host computer used to run the service processes and the network port address that is assigned to the master installation when it is configured.
At least one master installation is required in order to run any OpenSpirit enabled application. A master installation can be used to run OpenSpirit applications and data connector processes in addition to running the service processes described below.
Metadata Repository
A database is created and provisioned as part of the process of creating and configuring a master installation. The database is also known as the OpenSpirit metadata repository. The metadata repository is an embedded relational database composed of a hierarchy of directories and files. The root directory of the database file hierarchy is chosen during the master installation configuration process.
All reading and writing of the metadata repository files is done by the Shared Service process, which is described below. The metadata repository is used to store the information described in the following table.
Metadata Category |
Description |
---|---|
Master installation settings |
Various settings that are established during the master installation configuration process. |
Catalog of satellite installations |
Host computer name, operating system version, software installation directory, and configuration directory of all Linux satellite installations that are associated with the master installation. Satellite installation information is saved in the metadata repository when configuring a Linux satellite. This information is used to create data connector processes to service requests from OpenSpirit enabled applications running on a different host computer. |
User definitions and rights |
Information about all users that have used the OpenSpirit installation, including any rights assigned to them by the OpenSpirit administrator. User definitions are created automatically the first time that a new account is used to run an OpenSpirit enabled application. User definitions can also be created by an OpenSpirit administrator using the User Manager tool. |
User data source credentials |
Data source credentials entered using the User Setup wizard. |
Data source configuration settings |
Information about data stores that can be accessed using OpenSpirit data connectors. This information is entered using the Data Source Configuration tool. This information enables OpenSpirit to access and publish data residing in data stores that are supported by an OpenSpirit data connector. |
Data model definitions |
Detailed information describing the OpenSpirit common data model and the native data model supported by each OpenSpirit data connector. This information is pre-loaded in the metadata repository. It is used by many OpenSpirit tools, such as the Data Selector and Copy Manager, and it is used by OpenSpirit data connectors. |
Data source capabilities |
Detailed information describing the read, write, update, and delete capabilities of each data source type supported by an OpenSpirit data connector. This information is pre-loaded in the metadata repository. |
Copy Manager rules |
Rules describing how data is copied between two data sources using the OpenSpirit Copy Job Manager tool. Default copy rules are added to the metadata repository that the first time Copy Job Manager is used. Additional custom rules can be created using the Copy Rule Manager tool. |
Copy and scan job definitions |
Job definitions are created using the Copy Job Manager tool or the Scan Job Manager tool. Job definitions describe how data is to be copied or scanned. |
Copy and scan job run histories |
Job run histories are created each time a copy job or a scan job is run. Job run histories can be quite large and should be cleaned out periodically using the Job run history tool. |
Model view definitions |
Model view definitions describe how a data model is to be presented. A default model view of the OpenSpirit data model for use by the Data Selector tool is pre-loaded in the metadata repository. Model views are also added to the metadata repository the first time the Copy Job Manager tool or the Scan Job Manager tool is run. New model views can also be created using the Model View Manager tool. |
Session definitions |
A Session is a set of data source selections, a coordinates system preference, and a set unit of measure preferences that has been given a name. Sessions are created using the Session Manager tool. |
EPSG coordinate system definitions |
A catalog of pre-defined coordinate reference systems and transformations obtained from the International Association of Oil & Gas Producers. This information is pre-loaded in the metadata repository. |
Unit catalog definitions |
A collection of catalogs of units of measure. This includes a POSC catalog and catalogs for data stores that have their own unit of measure definitions. This information is pre-loaded in the metadata repository. |
Reference value catalogs and maps |
A collection of reference data catalogs that define allowable values for selected data model attributes. For example, the set of country names, well status codes. This includes the OpenSpirit reference catalog values and catalogs for data stores supported by OpenSpirit data connectors. Reference values are used when transferring data from one data source type to a different data source type and when application write data using OpenSpirit. This information is pre-loaded in the metadata repository. |
Shared Service
A Shared Service process is run by each OpenSpirit master installation. The Shared Service process runs on a specified host computer using a port that is assigned during the master installation configuration procedure. The primary function of the Shared Service process is to provide access to the information managed in the master installation's metadata repository.
Notification Service
The other service process that runs from an OpenSpirit master installation is the Notification Service. This process is started automatically when the Shared Service process is started. The Notification Service manages OpenSpirit event sending and receiving.