Example OpenSpirit Deployment Configurations

TIBCO OpenSpirit® Runtime configuration contains a master installation and zero or more satellite installations. An enterprise may need a single OpenSpirit® Runtime configuration, or it may need many configurations. User community, geography, and network topology considerations all play a role in designing your company's OpenSpirit Runtime environment.

Following are examples of the most common OpenSpirit deployment configurations. Each deployment configuration is illustrated with a network diagram and a description of the usage pattern that the deployment was designed to address. Consult OpenSpirit Support if you are unsure of the best network deployment configuration for your computing environment. The examples below are not exhaustive. They are the subset of most common deployment configurations currently in use.

Windows Desktop Applications & Linux Data Sources Deployment

The following network diagram illustrates the most common OpenSpirit deployment configuration. The diagram shows an OpenSpirit master installation running on a large Linux server.

A satellite installation has been configured on a different Linux server to run Linux data connectors. The additional satellite is needed in this deployment example because the Linux server running the master installation does not have visibility to files needed by a Linux data connector (for example, cannot see the SeisWorks project directories needed by an OpenWorks data connector from the master installation server).

Finally, each Windows PC that needs to run OpenSpirit enabled applications (for example, Petrel, Spotfire, and so on) has an OpenSpirit satellite installed on their local C drive. The PC satellites can also be used to run Windows only data connectors, such as Kingdom and Studio.

Tip: Note, this deployment configuration also enables Linux applications to be run in addition to running Linux data connectors. Users wanting to run Windows and Linux applications may need to set a secondary account if their Windows account name is different from their Linux account name. This is done using the User Manager tool.

Standalone Computer Deployment

This is the simplest OpenSpirit deployment configuration. This configuration can be used when all users, OpenSpirit enabled applications, and data connectors can run on a single host computer. The computer could be running Windows or Linux. This deployment configuration is typically used for laptops that require OpenSpirit access when not connected to the company network.

Windows Only Deployment

This OpenSpirit deployment configuration is used at companies that do not use Linux to run OpenSpirit enabled applications and do not have data stores that require Linux. An OpenSpirit master installation is installed on a Windows server and each Windows desktop has a satellite used to run the applications and the data connectors.

Multi-Site Enterprise Deployment

An enterprise deployment is sometimes used by companies that want business units to be able to access each other's data sources. Each business unit has a master installation that contains users working for that business unit. Satellites are configured on servers in other business units to provide visibility to the other business unit's data stores across the company's wide area network.

An enterprise deployment may require a site-to-site VPN connection to be established to enable OpenSpirit processes to communicate through firewalls that may exist between the company's wide area network and local area networks. Also, login accounts must be provided to enable users from one business unit to create data connector processes on servers managed by other business units.

Tip: Before version 4 of the OpenSpirit Runtime this enterprise deployment configuration would require multiple installations of the OpenSpirit software on each server. OpenSpirit version 4 introduced the ability to configure multiple masters and satellites using one software installation.