1 / 33

E2E Data Provider

Training on the management of the End to End data Management (E2EDM) prototype system at IODE NODCs. E2E Data Provider. Requirements, installation, features, setup, usage and maintenance. E2E Data Provider. Features.

acacia
Télécharger la présentation

E2E Data Provider

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Training on the management of the End to End data Management (E2EDM) prototype system at IODE NODCs E2E Data Provider Requirements, installation, features, setup, usage and maintenance

  2. E2E Data Provider. Features • Providing connection between local data sets of Data Centers and distributed system • Access to the local data source (databases, files) • Data source/resources registry and metadata update • Schedule mechanisms • Generation and updating of resource descriptions in compliance with the current status of the local data set • Codes and dictionaries mapping • Request handling and data delivery • Security services • Administration tools (CMS) Ostende, 2007

  3. Requirements to local data system • Rational database management systems: Oracle, MS SQL Server, MySQL, PostgreSQL, Interbase, ODBC, … • Structured data files in “flat” (non-hierarchical) data formats: ASCII files with separator or fixed values positions • Object files: electronic documents, images, data files in formats, which are not handled by the E2EDM technology software • Web-applications performing an access to local data sets Ostende, 2007

  4. Software and hardware requirements Software requirements • Windows OS (XP, 2000, 2003) or Unix-like OS (RedHat, Debian, Sun Solaris) • Apache web server 1.3.27 or higher • PHP 4.0 or higher • Java2 SDK 1.5.0 or higher • JBoss application server 4.0.0 Recommended technical requirements • Intel Pentium Core 2 Duo 2Ghz, 2Gb RAM, 10Gb HDD • Network connection 100Mbit/s speed Ostende, 2007

  5. Apache web server installation • Start distribution installation, defining server name. • Server name is a DNS or computer name 2. Select custom setup type to specify installation path and components Ostende, 2007

  6. Apache web server installation • Specify installation path to c:\usr\local • It’s better to use path that doesn’t contain any space characters 4. Final step After successful installation apache system service is managed from the “Services” section of Windows Control Panel Ostende, 2007

  7. PHP installation (continue) • PHP is an language interpreter that running under Apache web server. • Run the executable installer and follow the instructions: • Specify installation path to directory c:\usr\local\php-4.4.4 (It’s a default path in installer) • To make sure that the php libraries can be found by Apache web server copy php4ts.dll and sapi\php4apache.dll from installation directory to Windows system directory (e.g. c:\windows\system32) • Additionally, in order to work with DBMS except MySQL you need to uncomment proper extension in php.ini configuration file and put dll library to c:\windows\system32 path. To work with MS SQL Server put extensions\php_mssql.dll to this path. • Copy the file, php.ini from additional files in Data Provider distribution to c:\windows.Make sure to rename php-4.1.1.ini file from distribution to php.ini. All necessary settings in this file are done for successful work of Data Provider with MS SQL Server.Note, that MS SQL Client must be installed on the server also. Ostende, 2007

  8. PHP installation (continue) • Overwrite c:\usr\local\apache\conf\httpd.conf Apache configuration file from Data Provider distribution. Before copying httpd-1.3.28.conf to Apache conf directory rename it to httpd.conf. This file loads php module into Apache web server. • Note: By overwriting your configuration file with file from distribution you overwrite all previous settings. In case of Data Provider you have to edit httpd.conf file after overwriting and set your server name again. • It can be done by searching the string starts with “ServerName” in this file and typing correct value Ostende, 2007

  9. Database Access Service (DiGIR) installation • Run digir2.exe installer from Data Provider distribution and follow instructions. Installation path is c:\www\digir2 by default. • Make sure that DiGIRis installed correctly by typing in your web browser address: http://localhost/digir2/admin Ostende, 2007

  10. Java SDK installation • Run jdk-1_5_0_04-windows-i586-p.exe installer from Data Provider distribution and follow instructions. Specify installation path to c:\jdk1.5.0_04. • After installation create system variable JAVA_HOME and set it to c:\jdk1.5.0_04 pathTo set system variable click right mouse button on My Computer and choose Properties. On Advance tab press Environment variables button below. Then in system variables section create JAVA_HOME variable • Installation complete and all java application will use this JAVA_HOME variable pointing to installed Java SDK Ostende, 2007

  11. JBoss application server installation • Copy JBoss from Data Provider distribution to c:\jboss-4.0.0 path • Go to c:\jboss-4.0.0\bin directory and run !installJbossAsService.bat file to install JBoss as system service. • After installation JBoss system service is managed from the “Services” section of Windows Control Panel • Server log is placed to c:\jboss-4.0.0\server\default\log\server.log file. All errors that occurs can be read from this log file. • Make sure that JBoss server application works properly by typing address in web browser: http://localhost:8080/ Ostende, 2007

  12. Data provider management system installation • Run dpms.exe installer from Data Provider distribution to c:\jboss-4.0.0\server\default\deploy path • Restart JBoss application server for application deployment • Make sure that application works properly by typing address in web browser: http://localhost:8080/dpms/ Ostende, 2007

  13. Data provider setup Administration section: Configure settings Setup parameters and define paths of locating system files: Data Provider identifier, server name and port, path to application files, path to DiGIR Ostende, 2007

  14. Data provider setup Administration section: Configure schedulers Data Provider performs automated updating of each resource description which data set is in DBMS or structured files. Ostende, 2007

  15. Data provider setup Administration section: Localization of system elements Localization of system elements consists in specifying those system elements, which are relevant for the data sets of a specific Data Center and will be used for resource descriptions. Ostende, 2007

  16. Data provider usage Operator section: Manage information resources Entry point for resource descriptions management. Ostende, 2007

  17. Data provider usage • Operator section: Create new resource description • 2 ways of registrations: create new description or import existing • Registration steps: • Identification and connection to data (if data source is DPMS or structured files) • Data presentation and dissemination • Time and geographic characteristics • Contacts • Data hierarchy setup setting structural units of data set (subsets) and data records structure Ostende, 2007

  18. Data provider usage Operator section: Create new resource description Identification and connection to data Ostende, 2007

  19. Data provider usage Operator section: Create new resource description Edit resource mapping Metadata section contains identification and contact information Ostende, 2007

  20. Data provider usage Operator section: Create new resource description Edit resource mapping Datasource section: data base and login account settings Ostende, 2007

  21. Data provider usage Operator section: Create new resource description Edit resource mapping Tables section: specify table or set of tables linked by foreign keys First step: select root table and key field (primary key is preferable) Second step: select foreign key in root table, select foreign key from another table and press “add” button Ostende, 2007

  22. Data provider usage Operator section: Create new resource description Edit resource mapping: filter Specify criteria of data sampling out of the database. It is used when resource is a part of the database, determined by the period of observation, geographic location and other characteristics. Ostende, 2007

  23. Data provider usage Operator section: Create new resource description Edit resource mapping: Mapping Define a one-to-one mapping between system data elements (codes/names) and local data elements *tables and table fields). To save time it is recommended to prepare and use a working table of mapping. Ostende, 2007

  24. Data provider usage Operator section: Create new resource description Data presentation and dissemination Define a space-time structure of local data provided by resource as well as form and conditions of presenting information to users. Ostende, 2007

  25. Data provider usage Operator section: Create new resource description Time and geographic characteristics Set time and geographical characteristics of data provided by resource Ostende, 2007

  26. Data provider usage • Operator section: Create new resource description • Contacts • Enter contact information of three categories: • Role “generator” – organization that has a rights of data owner (or entitled to a right of ownership) of the data set provided by resource; • Role “resource provider” – Data Center that provides resource • Role “point of contact” –resource description author Ostende, 2007

  27. Data provider usage Operator section: Create new resource description Data hierarchy 1. Defines resource structure – data segmentation (granulation) into resource instances, 2. Defines data structure – data segmentation (granulation) into transport data file records 3. Resource structure setup is based on logical and physical basis. Logical is made by instance key. Physical is one data file – one resource instance Ostende, 2007

  28. Data provider usage Operator section: Resource maintenance Registered resources Managing instances, codes mapping settings, tasks Resources under registration Eliminating errors and warnings in resource descriptions Ostende, 2007

  29. Data provider usage Operator section: Resource maintenance Task creation Information resources should by ready to meet requests from Integration Server. To assure actuality of resources it is necessary to set frequency of automatic resource description updating and instance generation Ostende, 2007

  30. Data provider usage Operator section: Codes This section is intended to provide an access to system codes used for resource descriptions Ostende, 2007

  31. Data provider usage Operator section: Dictionaries This section is intended to provide an access to system dictionaries (guides) used for code unification of local data Ostende, 2007

  32. Data provider usage Operator section: Data elements List of elements, which used in resource descriptions Operations: sort the list of system elements by the chosen field, obtain the full list of codes without paging, copy list to one of the formats: excel, word, pdf, csv Ostende, 2007

  33. Data provider usage Operator section: Help All documentation and contacts Ostende, 2007

More Related