International workshop on Météo-Franceand UK Met Office vGISC implementation
OpenWIS installation and requirementsfor NC / DCPC
5th June to 7th June 2013
NC (minimum)
Existing GTS
flow
Web
Access to VGISC
portal
DCpc
Telecom
harness
Dissemination
harness
dcPC
Data source
harness
Dissemination
harness
System Requirements
•RedHat x86_64 (official) or CentOS
•Versions 5.5 to 5.8
•English language (required by OpenAMinstaller)
Architecture
•Modules:
–Portals: User & Admin with embedded MDservice
–Database
–LDAP & SSO Server
–User Management
–Data Service
–Harnesses: DataSource + Dissemination + MSS
–Staging Post
–Indexing Service (SolR)
Software
•The OpenWIS software architecture iscomposed of the following elements:
• Sun JDK 1.6u21
• Tomcat 6.0.28
• JBoss EAP 5.1
• OpenDS 2.2.0
• OpenAM release9
• Apache Solr 1.4.1
Proposed Configuration
•Compact configuration:
–2 servers: front-end and back-end
•Front-end server:
–WISPortal module (can be Virtualized)
•One ‘WIS Portal’ module grouping an Apacheserver (HTTP Front-end) and the OpenWIS® UserPortal (Web portal running on Tomcat).
–WISSecurity (can be Virtualized)
•One ‘WIS Security’ module hosting theauthentication server (OpenAM running on JBoss).
Proposed Configuration
•Back-end server:
–WISAdmin module (can be Virtualized)
•One ‘WIS Administration’ module hosting theOpenWIS® Administration portal (Web portalrunning on Tomcat).
–WISData module (can be Virtualized)
•One ‘WIS Data’ module hosting the database(Postgres), the Data service (running on JBoss)and the harnesses: dissemination harness (datadissemination through FTP or Email) and theharness to the local data sources.
Technical Requirements
•Front-end server
Requirement
Minimum
Recommended
CPU
1 (2.4 GHz Quadcore)
2 (2.4 GHz Quadcore)
RAM
8GB
Hard Disk
200 GB / HDD7200 rpm
Technical Requirements
•Back-end server
•Monitoring station
–HP 7400 or equivalent
Requirement
Minimum
Recommended
CPU
1 (2.4 GHz Quadcore)
2 (2.4 GHz Quadcore)
RAM
8GB
16GB
Hard Disk
500 GB / HDD7200 rpm
1TB
Network
•Both servers must have an access to theinternet.
•OpenWIS requires a public domain andsub-domains.
•For instance, if the main site URL ishttp://dcpc.myorg.com, the user portal will beaddressed as follows:
–http://dcpc.myorg.com/openwis-user-portal
Network
•The OpenSSO security module must havea public URL as well:
–http://sso.myorg.com
•The Administration Portal must be able toestablish HTTP connections with a remoteGISC centre for meta-data harvesting.
Network
•Front-end apache server manages thefollowing HTTP redirections:
–Administration Portal URLs redirectedtowards the tomcat server installed on back-end server
–User Portal URLs redirected towards thetomcat server installed on front-end server
–OpenSSO URLs redirected towards theJBOSS server installed on front-end server
System Requirements
Interfaces with the local systems
• Interfaces needed to communicate with the local systems
•Acquisition systems (MSS)
•Dissemination systems
•Local data sources (Data Bases)
Local requests are for locally Cached or locally produced data, on an ad-hoc basis or as arecurrent subscription. Local products can be retrieved via the interfaces to local datasources: archive or product creation system.
Local data source harness
Local data source harness
•Implementation of harness Web servicesto Interface with existing data source(dcPC)
•Sub-selection parameters for Local DataSource
•Allows selection of product instance from metadatafor request/subscribe
•Local Data Source product access
•Give access to local data source products(extraction)
•Check availability of new products (for subscribers)
Telecom harness
Telecom harness
•Mainly for DCpc and GISC
•No special development needed for
•Data collection (GTS→ OpenWIS)
•Data feeding (OpenWIS → GTS)
•Implementation of harness Web services
•MSS/FSS subscriptions management
•Get list of available channels for a user
•Create/Update routing of product
•Monitor data flow (routings)
Requested data are delivered via the software interface
to the local dissemination system.
Dissemination harness
Dissemination harness
•Implementation of harness Web servicesto Interface with existing disseminationtool (DCpc and dcPC)
•Allow dissemination of product instancesto the user
•By FTP or Email
•Asynchronously
•Two interfaces can be configured
•Public or RMDCN dissemination tool
Manage failover
•High availability through Heartbeat andeither
•a shared DRBD partition
•SAN/NAS solution
Staffing
•Administrator of the WIS System
–Advanced skills of Unix operating systemadministration
–Good knowledge of OpenWIS distributedarchitecture + WIS concepts
•Operators of the WIS System
–WIS Concepts (harvesting/OAIPMH)
–Basic skills on Unix
•Metadata editors
–Basic knowledge of ISO 19139 (WMO CoreProfile)
How to get OpenWIS
•From vGISC members:
–Météo France
–UK Met Office
•From MFI (co-founder of OpenWIS®)
