ADMINISTRATOR TRAINING

ADMINISTRATOR TRAINING

Administration Training Schedule
Time Duration Topic 8:30 30 Introduction 9:00 Behind the Scenes - What is running where? 9:30 Deployment Configurations 10:00 OpenSpirit Installation Considerations 10:30 45 OpenSpirit Master and Satellite Installation Demonstration 11:15 UNIX and Windows Data Store Configuration 12:00 60 Lunch 1:00 UNIX Master Installation Exercise 1:45 PC Installation Exercise 2:15 License Manager 2:45 15 User Manager 3:00 Log files and Troubleshooting 3:30 Wrap-up Adjourn Welcome to OpenSpirit Administrator Training. This training will take a complete day and focus on OpenSpirit Administrator applications. © TIBCO Software Inc.

Behind the Scenes © TIBCO Software Inc.

V4.0- Service Oriented Middleware
Available in Java, .NET, and C++ Windows, and Linux REST* Web Services: Query, Plot, Report, xml Exposes OpenSpirit model, native model , or other… Event Service Unit Service Coordinate Service Data Access Service Reference Value Service Metamodel Service Exposes data models’ entities, attributes, relationships and constraints Publish/ subscribe model based on CORBA Notification Service Based on POSC/ISO unit definitions Based on ESRI Projection engine and EPSG data Data Connector Data Connector Allowable attribute values and mappings Metadata Repository May be built using model mapping tools in Framework Extenders kit Used by all services. Stored in embedded database. *Representational State Transfer © TIBCO Software Inc.

Client Application(s) OpenSpirit Data Viewers & Utilities
OpenSpirit - A Process View Client Application(s) OpenSpirit Data Viewers & Utilities Shared Servers Per User flexLM daemon Notification (Event) OpenSpirit Desktop Locator Reference Value Event Gateway OpenSpirit Shared Services Units Coordinate Metadata Data Connector* * GeoFrame & OpenWorks data servers are per user– others may not be Metadata Repository Vendor Datastore(s) Data server are per datastore type NOT necessarily object type….. © TIBCO Software Inc.

Sequence of Events PC NFS Files UNIX Host 4 UNIX Host 3 UNIX Host 1
1. User starts OpenSpirit Desktop 2. Locator starts on PC 3. User starts DataSelector and selects a datastore that references an OW project 6. DataSelector displays requested data 7. User starts 3DViewer 8. User sends a data selection event from DataSelector to 3DViewer 9. 3DViewer receives event and requests data to display 10. User exits Launcher and chooses to shutdown data servers NFS Files Oracle db tables (OW) OW_HOME (binaries for Host 3 OS type) SeisWorks project data OSP_HOME (binaries for Host 3 OS type) UNIX Host 4 0. OpenSpirit flexLM daemon (e.g. network 4. Locator starts (ssh, rexec, etc.) 5. Locator starts OW data server - OW data server connects to OW project and reads requested data 11. Locator and OW data server shutdown 0. Oracle listener for OW instance running 0. Shared Services & Notification daemons running (default port 15<version>) UNIX Host 3 UNIX Host 1 UNIX Host 2 Hosts 1-4 and NFS files may be all on one host or distributed across multiple hosts (as shown) © TIBCO Software Inc.

Deployment Configurations
© TIBCO Software Inc.

Master Satellite Master and Satellite Configurations
Can only have ONE OpenSpirit Master per enterprise site Runs OpenSpirit Shared Services, Location Services, and Metadata Repository used by all Has all OpenSpirit code, to include satellite Satellite Used when cannot share Master code Different Operating System Different disk system Different network © TIBCO Software Inc.

Windows Apps and Unix Data Sourcesxx
Master Linux running OSP Shared Services, Notification Services and Metadata Repository Also runs GeoFrame Satellite(s) Linux – OpenWorks - no disk visibility to Master PC – Petrel - different OS and no disk visibility to Master Master Windows Desktop Applications & Unix Data Sources Deployment The 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 Solaris server which is used to run OpenSpirit data connector processes to access data sources available only on Solaris (e.g. Finder). Another 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 (e.g. 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 (e.g. Petrel, Gocad, etc.) 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 Petra.

Master Satellite(s) Windows Apps and Unix Data Sources
Linux running OSP Shared Services, Notification Services and Metadata Repository Also runs GeoFrame Satellite(s) Linux: OpenWorks no disk visibility to Master PC: Petrel different OS and no disk visibility to Master Master © TIBCO Software Inc.

Master on one machine Standalone Deployment
Runs Shared and Notification Services and has Metadata Repository All application run on this single computer Typically disconnected laptop Windows or Linux © TIBCO Software Inc.

Windows Master on server class machine
Windows Only Deployment Windows Master on server class machine Maintains Shared and Notification Services and Metadata Repository Satellites installed on Windows desktops across network Must include apps to run data connectors (i.e. Kingdom, Petra) Windows Only Deployment This OpenSpirit deployment configuration is used at companies that do not use Linux or Solaris to run OpenSpirit enabled applications and do not have data stores that require Linux or Solaris. 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. © TIBCO Software Inc.

Multi-Site Enterprise Deployment
Sat A Sat A Sat A Sat B Sat B Sat B VPN Master A Master B Sat B Sat A Sat B Sat A Sat B Sat A Sat B Sat A 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. © TIBCO Software Inc.

OpenSpirit Installation

Installation & Configuration Guide
Installation Resources Installation & Configuration Guide Goes into specific detail Release Notes All documentation available at Download site: © TIBCO Software Inc.

Identify OpenSpirit environment
OpenSpirit Installation Process Identify OpenSpirit environment Master installation Satellite installation(s) License server Obtain install kits Lay down files with installer Configure Master and Satellite(s) Start License demon and shared services © TIBCO Software Inc.

Environment - Supported Platforms
Operating Systems Platform Versions Windows Windows XP (32 & 64 bit) Windows Vista (32 & 64 bit) Windows 7 (64 bit) Windows 10 (64 bit) Windows Server 2003 (32 bit) Windows Server 2008 (64 bit) Linux Red Hat Enterprise Linux release 3 (32 bit) Red Hat Enterprise Linux release 4 (32 & 64 bit) Red Hat Enterprise Linux release 5 (64 bit) OpenSpirit Runtime Installation Operating system Platform versions. © TIBCO Software Inc.

Temp Space During Installation (MB)
Environment - System Requirements OpenSpirit - highly parallel, distributed, N-tier client server architecture Platform Disk Space (GB) Temp Space During Installation (MB) Linux 1.85 703 Solaris 1.51 668 Windows 1.74 468 © TIBCO Software Inc.

Estimated Metadata repository storage requirements per user
Environment - Storage Requirements Estimated Metadata repository storage requirements per user Metadata Category Typical Disk Space Requirements User definition and credentials 1 KB to 4 KB per user Data source configuration 1 KB per data source Session definitions 1 KB per session Model view 1 KB to 500 KB per model view; typical average size is 100 KB Copy rules 3 KB to 40 KB per rule; average size of the default rules is 14 KB Copy job definition 15 KB to 6 MB per job; typical average size is 50 KB Copy job run history 5 KB to 30 MB per job run; typical average size is 700 KB Scan job definition 5 KB to 4 MB per job; typical average size is 100 KB Scan job run history 5 KB to 10 MB per job run; typical average size is 400 KB © TIBCO Software Inc.

OpenSpirit Master installation OpenSpirit data connector
Environment - Memory Requirements OpenSpirit Master installation Requires 2 – 3 GB of virtual memory, 1 – 2 GB of resident memory during OpenSpirit use. OpenSpirit data connector Requires 1 – 4 GB of virtual memory, 0.3 – 1.5 GB of resident memory during OpenSpirit use. OpenSpirit desktop Requires 1 – 3 GB of virtual memory, 0.3 – 2.0 GB of resident memory during OpenSpirit use. NOTE: Memory requirements are highly dependent on the number of applications and data connectors that are being run concurrently on the same machine. © TIBCO Software Inc.

Separated out handling of the license daemon
Environment - License Separated out handling of the license daemon The Flex License daemon in a separate installation kit Starting the SharedServices will not try to start a license daemon Can only configure the master installation with a flex value. © TIBCO Software Inc.

Obtain Installation Kits
OpenSpirit install kits Available on the TIBCO software download web site Download the installers for the operating system platforms to run OpenSpirit applications or data connectors. Linux and Solaris installers are self extracting shell scripts that have a .bin file name extension. Windows installer executable has a .exe file name extension. A connection to the internet is required during installation to download MICO, JacORB, and JTS zip files that contain third party software products required by OpenSpirit. NOTE: Links are provided to download the required zip files to the same directory as the OpenSpirit installer prior to installation. © TIBCO Software Inc.

Lay Down Files with Installer
Windows Master and Satellite installation Administrative permissions are required to have the installer create Start menu entries for all users. Master installation on Windows requires an account with authority to install and run Windows services. Linux and Solaris installations Configure Linux and Solaris masters with UNIX account created specifically to manage and run the master installation services. Will own the master installation's metadata repository storage files. Will run the Shared Service and Notification Service processes. This account will be the OpenSpirit administrator account. Perform all administrative tasks for the master installation. NOTE: Does not require root privileges. © TIBCO Software Inc.

Lays down scripts, programs, libraries.
OpenSpirit Installer Simple application Lays down scripts, programs, libraries. Includes other files needed to run OpenSpirit enabled applications, tools, and data connectors Run with required account © TIBCO Software Inc.

Configure Master and Satellite Installations
Run OpenSpirit Installation Config Manager AFTER installation Creates or modifies Master or Satellite installation Master installation Sets up or modifies the OSP home, host, port, data directory (optional), and SharedServer log file location (optional) information in the configuration file ‘config.properties’ in the OSP_CONFIG directory. Starts/stops Shared Services (moved from the existing Master Installation Admin Tool) © TIBCO Software Inc.

Configure OpenSpirit Master
OpenSpirit Master and Satellite Configurations Configuration files Controls how OpenSpirit enabled applications, tools, and data connectors will behave. Uses the Install Config Manager tool

Configure OpenSpirit Satellite
Use Install Config Manager to configure or modify a satellite installation Sets up or modifies the OSP home, host, and port information in the configuration file ‘config.properties’ in the OSP_CONFIG directory. Registers/deregisters Unix satellites with the corresponding master to make available for remote activation © TIBCO Software Inc.

config.properties Master Satellite Configuration File Management
Run out of same code base with multiple configuration files Satellite Can deploy with code so users do not have to run Installation Configuration Manager © TIBCO Software Inc.

Coordinate with FlexLM Admin to make sure license demon is running
Start OpenSpirit Master Services Coordinate with FlexLM Admin to make sure license demon is running Start Shared Services When master config saved click on red button in Installation Configuration Manager © TIBCO Software Inc.

Configuring UNIX Data Sources

Data Store Configuration
Purpose: To ‘tell’ OpenSpirit about the various data stores that will be accessed Information needed: Configuration Name: a free-form unique name given to each data store to be configured Data store install directory: used to access vendor libraries and functions Data store Oracle database information: used to access project data in the vendor data stores Data store FlexLM license information: needed in order to checkout vendor licenses General UNIX data store configuration details © TIBCO Software Inc.

GeoFrame Data Store Configuration
URL BUILDER Creates a URL to connect to the project data store’s DB SID Oracle instance name for data store (OW, GF…) Located in the tnsname.ora file HOST Machine Oracle runs on Either name or IP address PORT Oracle Listener Port number GeoFrame URL builder configuration details © TIBCO Software Inc.

QUERY ACCOUNT BUILDER Creates an Oracle account in the project data store, used by OSP to access list of available projects DBA Account Oracle DBA account DBA privileged account used to create OSP user account DBA Password Oracle DBA account password New Account Query Account user name Account requires connect privilege to project data stores, to access project public read tables New Password Query Account password OWSYSP Password (OW only) Password for OWSYSP account Created during OpenWorks installation GeoFrame query account builder details. © TIBCO Software Inc.

NAME DESCRIPTION HINTS OpenSpirit Name Freeform unique name for data store UNIX file naming conventions GF_PATH GF installation directory LM_LICENSE_FILE Location of GF license file In GeoFrame_Runtime.csh file ORACLE_HOME Oracle installation directory TNS_ADMIN Location of tnsname.ora file $ORACLE_HOME/network/admin TWO_TASK GF Oracle instance name In tnsnames.ora file DB URL Project data store’s Oracle DB connection From URL builder tool Query Account OSP Oracle access account From Query Account builder tool BASELINE_ACC GF baseline account name (e.g. catalog account) IESX or Charisma? Default is IESX. GeoFrame data store configuration details © TIBCO Software Inc.

OpenWorks Data Store Configuration
NAME (OpenWorks) DESCRIPTION HINTS OpenSpirit Name Freeform unique name for data store UNIX file naming conventions OWHOME OW installation directory LM_LICENSE_FILE Location of OW license file In $OWHOME/lam/ ORACLE_HOME Oracle installation directory TNS_ADMIN Location of tnsname.ora file $ORACLE_HOME/network/admin SYSADM_USER_NAME Name of OW sysadmin OWSYSSID OW Oracle instance name SID value in tnsname.ora file; in $OWHOME/conf/lgcenv.cf DB URL Project data store’s Oracle DB connection From URL builder tool Query Account OSP Oracle access account From Query Account builder tool NAME (SeisWorks) DESCRIPTION HINTS OpenSpirit Name Freeform unique name for data store UNIX file naming conventions plist.dat Location of plist.dat file In $OWHOME/conf dir.dat Location of dir.dat file SW Lib Path Location of SeisWorks library directory $OWHOME/Seisworks/lib Configure a new OW data store for each plist.dat (Tip: copy data store and then change SW Info) OpenWorks data store configuration details © TIBCO Software Inc.

EPOS 4 Data Store Configuration
NAME DESCRIPTION HINTS Data Source Name Freeform unique name for data store UNIX file naming conventions EPOS Base Directory Root directory of installation $EPOS_HOME/EPOS4 PNS Host Machine where PNS Server is PNS Server must be started Default project coordinate system Check to define a default coordinate system if not present in project Click ‘Select Coordinate System’ EPOS 4 data store configuration details. For EPOS projects do not click “Use Well DB projects”. © TIBCO Software Inc.

EPOS 4 Data Store Configuration
NAME DESCRIPTION HINTS Data Source Name Freeform unique name for data store UNIX file naming conventions EPOS Base Directory Root directory of installation $EPOS_HOME/EPOS4 PNS Host Machine where PNS Server is PNS Server must be started Default project coordinate system Check option to define a default coordinate system if not present in project Click ‘Select Coordinate System’ Use Well DB Projects Check option if using Geolog database EPOS 4 data store configuration details. For Geolog database click option “Use Well DB projects”. © TIBCO Software Inc.

R5000 Data Store Configuration
Wallet Accounts R x data store configuration details. © TIBCO Software Inc.

Configuring Windows Data Sources

Data Store Configuration
Purpose: To ‘tell’ OpenSpirit about the various data stores that will be accessed Information needed: General Information: a free-form unique name given to each data store to be configured Data store information: used to access vendor libraries and functions Installation information: used to define application installation Project information: used to identify and verify project information General Windows data store configuration details © TIBCO Software Inc.

Kingdom Data Store Configuration
NAME DESCRIPTION HINTS Data Store Name Freeform unique name for data store Windows file naming conventions KINGDOM_VERSION Kingdom version and bitness (32-bit 64bit) Run DBAdmin.exe to include SINGLE_AUTHOR_MODE Click option to see only one particular author’s interpretation and well pick data. Use when interpreting seismic or Well Picks. INSTALLATION SUMMARY Status of installation INSTALL_HOME Verification of installation home GLOBAL_SEISMIC_FILE Seismic file location Usually network drive Add All Projects Under Available Projects Drilldown to .tks file Kingdom Data Store configuration details © TIBCO Software Inc.

Petra Data Store Configuration
NAME DESCRIPTION HINTS Data Store Name Freeform unique name for data store Windows file naming conventions INSTALLATION SUMMARY Status of installation PETRA_HOME Verification of installation home PETRA_VERSION Verification of Petra version Allow log Multiversion Identify multiple version of the same well log E.g. GR, GR_1, etc. All can be transferred using Copy Manager Add All Projects Under Available Projects Drilldown to PROJECT Petra Data Store configuration details © TIBCO Software Inc.

License Monitor Tool © TIBCO Software Inc.

OpenSpirit Licensing Example
Petrel Modules SIS ArcView ESRI OpenSpirit Adaptor for Petrel SIS/OSP OpenSpirit Extension OSP OpenSpirit Runtime OSP OpenWorks Data Module GeoFrame Data Module OSP OSP OpenWorks GeoFrame LGC SIS © TIBCO Software Inc.

Accessing the License Monitor License Monitor Layout
License Monitor Tool Accessing the License Monitor License Monitor Layout License Path Views Details License administration mode We will be covering the following (view slide). © TIBCO Software Inc.

Accessing the License Monitor Tool
Accessing: You can only access the license monitor through the OpenSpirit desktop. So, after launching the OpenSpirit desktop go to Tools  Adminstrator  License Monitor. © TIBCO Software Inc.

License Monitor Layout
License Monitor Tool License Monitor Layout License Path Views Feature User Details section License Path section: Shows you the machine and port # the license daemon runs on. You cannot change this information here, to change this information you need to go to Tools  Administrator  Installation Admin. If you had multiple licenses, you would click on the up/down arrow at the right to select another license path. You should always use the syntax for your license path. Multiple licenses: You can have multiple licenses, if you do, however, there are toggle buttons at the right which will allow you to toggle between licenses. You can not change the license path here, you would change the license path in the configuration tool. © TIBCO Software Inc.

License Monitor Layout
License Monitor Tool License Monitor Layout License Path section Views section Feature View User View Details section Views : There are two views (Feature View, and User View): Feature View: Allows you to view all the license features. If you want to see who has a particular license feature checked out, all you need to do is select the feature and information about that feature will show up in the Detail section right below. Other information available is the: Total number of licenses Licenses in use Expiration date Maintenance date Who and when was the license checked out. © TIBCO Software Inc.

Sections in License Monitor
License Monitor Tool Sections in License Monitor License Path section Views section Feature View User View Details section User View: If you click on the “User View” tab, you will see all users who has an OpenSpirit license feature checked out. If you select a user, all the features that user has checked out will be displayed in the Feature section at the bottom. © TIBCO Software Inc.

Freeing up Licenses: License Monitor Tool User and Feature Feature
Sometimes it becomes necessary to free up licenses. This can be done in three different ways: Go back to the previous slides. You can free up a license based on the feature and user You can free up all the licenses checked out for a particular feature You can free up all the licenses a particular user has checked out Licenses that are freed up using the License Monitor tool will be checked back out if the application that originally checked it out is still running. There is typically a delay of 10 to 15 minutes before the license is checked back out by the running application. Consider using the Process Manager tool or the User Manager tool's user deactivation option if your goal is to free up all OpenSpirit licenses that are being consumed by a specific user. © TIBCO Software Inc.

User Manager © TIBCO Software Inc.

Admin mode must be enabled to make changes to user information
User Manager Admin mode must be enabled to make changes to user information User Manager tool can only be used to view if not run in admin mode Must set password to run in admin mode Window tab will reflect Admin Mode when logged in as admin The User Manager tool can be used to view and modify information about registered OpenSpirit users. It can also be used to grant and revoke user rights. The User Manager Tool is accessed by selecting it from the icon displayed within the Desktop or from the pull down menu Tools > Administrator > User Manager. Address BULLETS ON SLIDE>>The User Manager window tab will display Admin Mode when connected as the administrator. Admin mode must be enabled to make changes to the user information. The User Manager tool can only be used to view user information if not run in admin mode. The User Manager tool has two tab displays, a Users tab and a Users Rights tab. © TIBCO Software Inc.

User Manager - Users © TIBCO Software Inc. Users tab overview
The Users tab displays a table of all the registered OpenSpirit users. Columns can be sorted by clicking on the headers. The Is Active? column indicates, with a check mark, if the user is currently connected to the OpenSpirit services. Users are automatically registered with the OpenSpirit framework the first time they run any OpenSpirit enabled application. Automatically registered users will appear with a primary account, name, and description that all match the name of the Windows or UNIX account that they were running on when automatically registered. A user's primary account cannot be changed. Users must be deleted and re-registered to change their primary account. The secondary account is optional and can be edited. User names and descriptions may also be edited. The User Manager's tool bar contains buttons that can be used to create, delete, and disconnect OpenSpirit users. Interactively demo the icons Summary of icon functionality: Adding New Users The User Manager tool can be used to register new OpenSpirit users rather than waiting for automatic registration to occur (i.e. the first time you use OSP). New users can be added individually by clicking on the create user icon. The create user icon will open a dialog that is used to enter the new user's primary account, secondary account, name, and description. Users can also be added in batch by clicking on the import icon to select a file containing information for many users. Deleting Users The User Manager tool can be used to delete OpenSpirit users. Deleting an OpenSpirit user will remove all information associated with a user from the OpenSpirit repository. This includes the user's sessions, server activation preferences, data source credentials, and private data source configurations. Deleting a user does not remove any Windows or UNIX account associated with the user. Only OpenSpirit information is removed. Editing User Information The user name, description, and secondary account information can be edited by simply clicking in the table cell and typing. Click on the save icon in the tool bar to save changes. Disconnecting Users The User Manager tool can be used to disconnect active users from the OpenSpirit runtime. This feature is provided to enable the OpenSpirit administrator to free resources being held by OpenSpirit users if it is not possible for the user to release the resources themselves. Disconnecting a user will force the user's data connector processes to shut down and will disconnect any OpenSpirit enabled applications they may be running. No warning is given to the disconnected user, so make sure they are not at risk of losing valuable work before disconnecting them. Select one or more active users and click on the stop sign icon in the User Manager tool bar to deactivate the selected active users. Refreshing User List Click on the refresh icon to refresh the list of users shown in the User Manager tool. Refresh will include any new users that have been registered since the list was last displayed. Refresh can also be used to discard any unsaved edits to user information. © TIBCO Software Inc.

User Manager – Users Rights
Users Rights tab overview Companies may wish to restrict access to some of the capabilities provided by OpenSpirit tools. For example, some companies may want to restrict the ability to run OpenSpirit scan jobs to their data management personnel. Other companies may want to prohibit Petrel users from exporting data out of Petrel using the OpenSpirit Ocean Petrel Application Adapter. The granting and revoking of these rights is done using the Users Rights tab in the User Manager tool. The rights that can be managed using the Users Rights tab are: Administer Copy Jobs >The right to create, modify, and delete copy job definitions and copy rules. Administer Data Views >The right to create, modify, and delete public model views. Administer OpenSpirit Runtime >The right to act as the OpenSpirit administrator without having to know the OpenSpirit password. Administer Scan Jobs >The right to create, modify, and delete scan job definitions. Petrel Data Export >The right to use the export and save to external features of the OpenSpirit Ocean-Petrel Application Adapter. Run Copy Jobs >The right to schedule and run copy jobs. Run Scan Jobs >The right to schedule and run scan jobs. © TIBCO Software Inc.

Selection box pops up to :
User Manager – Grant or Revoke rights Selection box pops up to : Assign Global Rights Add User Rights Remove User Rights Interactively demo the icons explaining that this selection box pops up for each icon Summary of icon functionality: Assigning Global Rights Global rights are rights that are granted to every OpenSpirit user. Any OpenSpirit right can be made global. You must have administrator privilege to grant or revoke global rights. Global rights are granted or revoked by clicking on the Global rights icon (the globe) in the User Manager tool bar. This displays the Assign Global Rights window. All OpenSpirit rights are listed. Check the rights you would like all users to have and un-check the rights that you want to control on a per-user basis. Adding User Rights Rights that are not already granted as a global right may be granted to specific users by selecting one or more user rows and clicking on the Add rights icon (plus sign) in the User Manager tool bar. This displays the Add User Rights window. Removing User Rights Rights that are not already granted as a global right may be removed from specific users by selecting one or more user rows and clicking on the Remove rights icon (minus sign) in the User Manager tool bar. This displays an Are you sure warning. Click the No button to cancel the user rights removal operation. Click the Yes button to proceed to the Remove User Rights window. © TIBCO Software Inc.

Log Files © TIBCO Software Inc.

Helpful troubleshooting log files:
Need for Log Files It is very difficult, if not impossible to troubleshoot a problem without the log files Helpful troubleshooting log files: Master Shared services log file Satellite or User Data server log files Executor log files Desktop.log App log files © TIBCO Software Inc.

Shared Services log in $OSP_CONFIG/logs
Unix Log Files Locations Shared Services log in $OSP_CONFIG/logs Default: $OSP_HOME/config/logs Can be changed in the config.properties file User logs in $HOME/OpenSpirit/v4.0/logs/ Data server logs further be grouped into different folders based on datastore type and version: $HOME/OpenSpirit/v4.0/logs/DataProvider/OpenWorks_2003/ $HOME/OpenSpirit/v4.0/logs/DataProvider/GeoFrame_4 © TIBCO Software Inc.

Using Windows system parameters
Windows Log File Locations Using Windows system parameters Shared Services: CSIDL_COMMON_APPDATA User logs: CSIDL_LOCAL_APPDATA Divorces Windows writable files from the read-only files Avoids UAC issues on Windows7 and Windows10 Conforms to Microsoft recommended practice Enables companies to put the installation files on a read-only disk © TIBCO Software Inc.

Using CSIDL_COMMON_APPDATA (all users):
Windows Shared Server Log File Using CSIDL_COMMON_APPDATA (all users): XP: C:\Documents and Settings\All Users\Application Data\OpenSpirit\v4.0\logs Vista: C:\ProgramData\OpenSpirit\v4.0\logs Windows 7: note: same as C:\Users\All Users\OpenSpirit\v4.0\logs Default value unless overridden in the config.properties file Log files are not written into the installation directory. Must use the application data area to write files. © TIBCO Software Inc.

Using CSIDL_LOCAL_APPDATA (local user):
Windows User Log Files Using CSIDL_LOCAL_APPDATA (local user): XP: C:\Documents and Settings\<userid>\Local Settings\Application Data\OpenSpirit\v4.0\logs\... Vista and Windows 7: C:\Users\<userid>\AppData\Local\OpenSpirit\v4.0\logs\... © TIBCO Software Inc.

Informational (default):
OpenSpirit Logging Levels Diagnostic (Debug): Detailed log file on processes and data errors Informational (default): Status of the workflow or job completion along with warnings and errors Warning: Just warnings and errors encountered Error: Just errors encountered © TIBCO Software Inc.

Interactive Logging Many OpenSpirit apps have interactive logging where level and log output can be set Desktop Copy Job Manager Scan Job Manager ArcMap Extension Petrel Plug-In © TIBCO Software Inc.

Enable a User’s debug Using osp.debug File to Enable Debug
Place an empty ‘osp.debug’ file in the user OpenSpirit/v4.0 directory: Unix: $HOME/OpenSpirit/v4.0 Windows: CSIDL_LOCAL_APPDATA\OpenSpirit\v4.0 Remember ability to turn on/off for a given data server via the new Process Manager! Unix PC © TIBCO Software Inc.

Enable Master’s debug Running a Master in Debug
Place an empty ‘osp.debug’ file into the installation home directory <OSP_HOME>/osp.debug Turning on debug for the admin user turns on debug for all the SharedServices run under that userid NOT recommended and should be used only when using private or local installation, or instructed by OpenSpirit Support © TIBCO Software Inc.

osp.debug remains empty during process
Using osp.debug File to Turn on Debug osp.debug remains empty during process DELETE osp.debug when finished to turn off debug Remember the ability to turn on/off debug for a given data server via the new Process Manager! © TIBCO Software Inc.

OpenWorks R5000 Log File GeoFrame log file details

Set your PC and Unix installation to run in debug
Exercise Set your PC and Unix installation to run in debug Start a Data Selector and display some well data Exit out of debug Compare the size of the data server debug file to one you used earlier © TIBCO Software Inc.

OpenSpirit Troubleshooting

New Tools to help the troubleshooting process
TIBCO OpenSpirit Troubleshooting New Tools to help the troubleshooting process Change log level on the fly Easy access to log files Machine Connectivity issues User manager tool & License Admin Tool Monitor & Managing the progress of a process Reporting issues to Support Because of its complexity and an attempt to give the user instant feedback, OpenSpirit v4.0 has introduced a number of troubleshooting tools that will help the user and administrator isolate, and in some cases, resolve problems that they were not able to resolve in the past. We will review some of these tools individually; other tools will be left up to you to review in the User’s Guide. Most of the tools can be accessed from the ospdesktop; others you will access from the $OSP_HOME/bin/etc directory. © TIBCO Software Inc.

Change log level on the fly
TIBCO OpenSpirit Troubleshooting Change log level on the fly The log Level controls the amount of information that will be available for viewing in the error log window, or in the output log file. The meaning of each log level is described in the User’s Guide. It is virtually impossible to start troubleshooting without the use of log files, by default the log level is set to “WARN”, however when you are going to troubleshoot you must set the log level to DEBUG. Do not change the log level to “DEBUG” or “ALL” unless instructed by OSP Support. Prior to OpenSpirit v4.0 to change the log level, users had to exit OpenSpirit, create an osp.debug file, then, restart their workflow. During this process valuable time is wasted. Users can now change log level,“turn on debug mode” at any time. It is also not all or nothing; users have the ability to turn on debug on certain modules (data servers) while leaving the log level set to WARN on others. To turn on debug all the user needs to do is: talk about the jpg above (describe jpg) © TIBCO Software Inc.

Easy access to log files
TIBCO OpenSpirit Troubleshooting Easy access to log files One of the challenges the user has always had, is knowing where the log files are located. In OpenSpirit v4.0 You can find out where the log files are by selecting the “Process Manager”, then highlighting the process whose log file you want to review, then click on the Information button at the top right, or the scroll icon right next to it to view the actual file. If you are logged in as the administrator you will be able to see all the process running off of that master installation, including the Shared Services process. This allows the administrator to view all the users’ log files and where they are being written to. Be sure to mention that the log file shown is on Windows but we are running the ospdesktop on Linux (to demonstrate the flexibility). Let them know that the default location for the log files is: For UNIX: $HOME/OpenSpirit/v4.0/logs/DataServer/data-source directory. For Windows: C:\Users\<user_id>\OpenSpirit\v4.0\logs folder © TIBCO Software Inc.

Machine connectivity Issues
TIBCO OpenSpirit Troubleshooting Machine connectivity Issues On the PC Execute $OSP_HOME/bin/etc/OSPExeptions.bat Add additional executables to firewall exceptions list. If problem persist launch the Network Tester Tool to check connectivity One of the main issues we have with clients is that when they try to send data from one application to another, nothing happens. Most of the time, this is due to a firewall. Many times this firewall is not set on the PC, it is set somewhere else. If the firewall must be set on the PC, there is a script $OSP_HOME/bin/etc/ OSPExemptions.bat that the administrator can execute to add the OpenSpirit exceptions to the firewall. You will still have to add other executables to the exceptions list. We have a tool that you can execute on the machines you want to talk to each other and it will tell you if there is connectivity between the machines or not. To launch NetWorkTester $OSP_HOME/bin/etc/networktest.sh. You must launch on both machines you want to test connectivity. You will enter the information of one machine in the open field of the opposing machine, and vice versa, then click on the “Run Test” button. You should get a “Test was successful” © TIBCO Software Inc.

The User Manager Tool & License Admin Tool
TIBCO OpenSpirit Troubleshooting The User Manager Tool & License Admin Tool The User Manager Tool and the License Admin Tool are accessed through the OpenSpirit desktop (ospdesktop) We have talked about these two tools previously. These tools are accessed through the OpenSpirit desktop. The License Admin Tool allows the administrator to check in (free up) licenses, even if it requires killing data servers. The User Manager Tool allows the administrator to delete or register users with OpenSpirit. © TIBCO Software Inc.

Monitor & Managing the progress of a process
TIBCO OpenSpirit Troubleshooting Monitor & Managing the progress of a process As an administrator you also have the ability to monitor ALL the processes running off of a master installation. In addition as seen above a whelt of information is displayed in the process manager. machine the process is running on process id time process started if the process is active or not Data server type, etc. If necessary, you can kill any process you need to by selecting the process then clicking on the red “Stop” button on top right. © TIBCO Software Inc.

Reporting issues to Support
TIBCO OpenSpirit Troubleshooting Reporting issues to Support Issues should be reported through the TIBCO portal. For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: If you already have a valid maintenance or support contract, visit this site: . Entry to this site requires a user name and password. If you do not have a user name, you can request one. Important information to be included: Data Server Log files in debug mode (Log level DEBUG) Shared Services Log file in debug mode (Log level DEBUG if possible) OpenSpirit License file Version of third party applications Synopsys of the issue you are having The best way to report an issue to support is through the TIBCO support portal. And when submitting an issue to TIBCO Support it is very important that you submit all the log files in debug mode (log level DEBUG); we have explained how to do that. Do remember, after collecting the log files, you must reset the log level to “WARN”. © TIBCO Software Inc.

Represents a custom view of the OpenSpirit or native data models
What is a Model View? Represents a custom view of the OpenSpirit or native data models Think of it as an SQL view in a data base Totally customizable Drives applications like the Data Selector Copy Manager Scan Utility A Model View represents a custom view of the OpenSpirit data model, or of a native data model. Think of a model view as a SQL view in a data base. They are used to present a database in a more user friendly form. A model view can present a subset of the data model’s data types and a subset of the related attributes. A model view can also change the names of data types and attributes and can join related data types to create a new data type. Model views enable companies to present data in the OpenSpirit tools using terminology common to the company. Model views also enable companies to subset the data types to only expose the data types and attributes that are populated in their data stores. © TIBCO Software Inc.

Data models apply to any OpenSpirit “Data Store”
Types of Data Models Data models apply to any OpenSpirit “Data Store” Two types of data models OpenSpirit Uses the OpenSpirit common data model Only data types and attributes in OpenSpirit common data model Used by any process sending events, Copy, and Scan Native Provides access to any table or attribute Currently, only used in Data Selector Cannot send as an event Data models are available, and effect, any OpenSpirit “Data Store” such as GeoFrame, OpenWorks, Finder, PPDM, Petra, Kingdom, etc.. Two types of data models exist; the OpenSpirit Common data model and the Native data model. The first is the OpenSpirit common data model. In this case all data types and attributes have been mapped to an OpenSpirit “standard” data model. Data mapped to the OpenSpirit common data model can be freely shared between applications using OpenSpirit. It is possible, however, to have data types and attributes that are not available in the OpenSpirit common data model. Applications that reply on sending and receiving events, and most OpenSpirit applications use the common data model. The second type of data model is the native data model. A native data model is a complete representation of all available tables and their columns for any OpenSpirit supported “data store”. The advantage to the native data model is all data types in a “data store” are exposed and available. The weakness, however, is there is no “mapping” between a native data model from one data store (i.e. OpenWorks) to another data model (i.e. GeoFrame) so data cannot be sent as events, or scanned with the Scan Utility. © TIBCO Software Inc.

OW R5000 Native drives Data Selector
Example: Data Model Drives Data Selector OW R5000 Native drives Data Selector OpenSpirit Common drives Data Selector A good example of how a Model View effects an OpenSpirit application is the Data Selector. In the Data Selector, a data model is used to customize the data presented to the end user. In the first case, the OW R5000 native model view called r5k_COTS is presented in the model view manager on the left. Take a look at the details of the model view. Note the item Well Costs has many sub items such as Cost, MultipleCasings, and Lost Circulation. These are tables directly out of OpenWorks R Now take a look at the associated data selector on the right. There is now a data group call Well Costs, and when selected, it displays the associated tabs Cost, MultipleCasings, Lost Circulation, etc.. Each data tab is controlled by the data model where column names, and displayed columns are set-up. In the second case, the OpenSpirit Default data model called OpenSpirit Default is displayed in the model view manager on the right. Again, note the data groups, and data tabs are driven by the associated data model. © TIBCO Software Inc.

Model View Manager started from the OpenSpirit Desktop
Starting the Model View Manager Model View Manager started from the OpenSpirit Desktop Tools -> Data Manager -> Model View Manager Model View Manager icon The Model View Manager Tool is accessed from the OpenSpirit Desktop by clicking on the Model View Manager tool bar icon or by choosing the Tools > Data Manager > Model View Manager menu item. The Model View Manager tool is used to inspect, create, and modify model views used by the OpenSpirit Data Selector and the OpenSpirit Scan Job Manager. © TIBCO Software Inc.

Select Model View TIBCO OpenSpirit Model View Manager
View/Edit header information View/Edit details The upper left section of the model view manager displays the current model views available to the user. Click on a model view to select it for viewing and editing. The Default column indicates if a model view is the default model view for its type. Only one model view of a given type can be a default. Marking a model view as the default for its type will cause the tools that use the model view to have it selected by default. For example, making a Data Selector model view the default will cause the Data Selector tool to show it as the selected model view in its Data Source Selection window. Making a Scan Job model view the default will cause the Scan Job Manager to show it as the default scan model view. The Model View Name column shows the name of the model views. The Version column shows the model view's version. Newly created model views are assigned version 1.0. The version number is incremented each time the model view is edited. Only the highest version of a model view is available in the Model View Manager. The Type column indicates if the model view was created for use in the Data Selector or in the Scan Job Manager. The Data Model column indicates the data model that the view is for. The Visibility column indicates if the model view is available for use by all OpenSpirit users or only by the user running the Model View Manager. Private model views can only be seen and used by the user that creates them. The upper right section of the model view window displays the model view header information. This includes the name of the data model that the model view is based on. It also shows the name of the model view, the type (Data Selector or Scan Job), the visibility scope (Public or Private), the version of the model view, and any description that was given to the model view. When editing and creating model views, it can also be used to change the description and properties of a model view. The bottom half of the Model View Manager window is used to browse and edit the details of the model view selected in the upper left portion of the Model View Manager. The lower left section of the model view window displays the data types and data type groups that make up the data model that the model view is based on. The lower right section of the model view window shows the model view data types and groups. Clicking on the description icon next to a model view data type opens a window that displays the description given to the model view data type by the person constructing the model view. The window also displays the description of the data type from the data model. The upper right hand corner houses the Model View Manager Tool Bar that contains buttons used to view, create, edit, delete, import, and export model views. Model views can be saved as a file, and then shared with other OpenSpirit users. © TIBCO Software Inc.

Add groups and data types
Creating a New Model View Select create new Select the data model Enter name Select the type Select the visibility Enter a description Add groups and data types Wells only. New model views are created by clicking on the Create model view icon in the Model View Manager tool bar. This will clear out the Model View Name field and Description field in the upper right section of the Model View Manager window and will set the Selected Data Model, Model View Type, and Visibility selections to their default values. The bottom left section of the window will show the data type groups that exist in the selected data model and the lower right section of the window will be empty. © TIBCO Software Inc.

Work in Model View area Right click to rename Modify with Configure
Modifying Model View Groups and Data Types Work in Model View area Right click to rename Modify with Configure Select and manage attributes Set filters, scope, and geographic query attribute © TIBCO Software Inc.

Extra Well Bore tab called “Exportable Wells”
Exercise: Create a Customized Model View Create a common OpenSpirit Model View to drive a wells only data selector Only show well related data Extra Log tab called “Triple Combo” containing only the following Log Types CALI, GR, SP, HRLA, RT, ILD, RHOB, DRHO, NPHT Extra Well Bore tab called “Exportable Wells” Elevation not null and < 5000 m TD not null and < m Top hole location not null Bottom hole location not null Create an OpenSpirit Model View for wells and well related data only. In this model view, need an extra log view called “Triple Combo” for logs used in correlation, and an additional well bore tab that contains exportable wells. © TIBCO Software Inc.

ADMINISTRATOR TRAINING

Similar presentations

Presentation on theme: "ADMINISTRATOR TRAINING"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

ADMINISTRATOR TRAINING

Similar presentations

Presentation on theme: "ADMINISTRATOR TRAINING"— Presentation transcript:

Similar presentations

About project

Feedback