２D－ｄ２

Development of Federated Database System in Astronomy(Virtual Observatory)～Demonstration of Science Use Cases ～Satoshi HONDA, Yuji SHIRASAKI, Masahiro TANAKA, Satoshi KAWANOMOTO, Masatoshi OHISHI, Yoshihiko MIZUMOTO, Masafumi
OE (National Astronomical Observatory), Naoki YASUDA (University of Tokyo), Yoshifumi MASUNAGA (Ochanomizu University), Yasuhide
ISHIHARA, Jumpei TSUTSUMI (Fujitsu Ltd.), Hiroyuki NAKAMOTO, Yusuke KOBAYASHI, and Michito SAKAMOTO (SystemEngineering Consultants Co. Ltd.)
http://jvo.nao.ac.jp
http://jvo.nao.ac.jp//
The virtual observatory (VO) is designed to provide astronomers with seamless access to astronomical DBs distributed all over the world. It is considered to be anindispensable system for the modern astronomy that produces huge amount of data day by day, therefore development of and collaboration on VOs have been advancedin leading countries of the world. We are developing Japanese VO (JVO), and we have already succeeded to interconnect with some other VOs since 2004. In the lastyear, we improved its performance of the JVO system, and upgraded the system toward future open use. Especially, we have implemented a workflow system to invoke
data retrieval and analysis services. The workflow description language is described based on the BPEL4WS. In this conference, we will demonstrate the JVO portal
system, and will perform some astronomical science use cases by executing the workflows and accessing to the astronomical DBs in the world. The basic concept andthe structure of the VO system may be applied to other fields of science.

Architecture of JVO portal server

Present Situation of Astronomical Data
Need Cat’s help!

Too hard to collect andanalyze whole data.

Astronomical data are
distributed all over theworld

Modern astronomy
produces huge amountof data day by day
Nobeyama ~ 1TB/year

VO makes the digital universe incomputers by using the databasetechnologies and through which
we observe the universe.

Input Queries
and Analysis
Parameters

We have succeeded tointeroperate the JVO
prototype system with VOs
in the USA and Europe
since Dec. 2004,
and more than 127
astronomical resources areavailable as of Feb. 2006.

• VOTable Viewer• DB Search• Plotter•Workflow• etc

SIAP/SSAP/SkyNode• Parser• Scheduler• ExecuterSIAP/SSAP/
SkyNodeUser DB

Even for educational use.

XML etc.

JVO Portal Server

VirtualObservatory

Accelerate
astronomical research,and sufficient time forresearch itself !

Accessible from anywhereat any time.

Table
Interface tothe VO world• column1• column2• ...

c.f., 4A-o5 Kawanomoto et al.

Design of Workflow• Can not treat complex analysis flow
– No loop operation, no conditional expression The following items were taken into account Described in XML.
 Users can construct a workflow byediting Templates, or Human hands should be needed.
writing workflow from scratch.
– Can not run task automatically.
 Available services are found from VOResource.
 Usage of a service is also found fromWorkflow description
VOResource.
 Service Provider can register their services easily.
language is required urgently.

mainTableColumn• name• dataType• unit• UCD• ...

• dataID• ...

mainHTM• dataID• htmIndex

regionTable

regionHTM• queryID• regionID
• ra
• dec
• size1• size2• regionExpr• queryID• regionID• htmLow• htmUpp

A collection of tables actuallyqueried.

Catalog FITS
DBUS/CanEurope

Server 3
Web ServiceAnalysis
Services
HyperZ
SExtractor

SIAP& SSAP

SOAP/HTTP

Parameter
QueryADQLSQL forbackend DB

VOTableConverter

ResultSetFormatter
SkyNode Controller

We developed a SkyNode toolkit for building a VO compliant dataservice. The toolkit mainly provides a part of “SkyNode controller”
where ADQL is converted to the DB native SQL, and the result isreturned in the VOTable format.

Science Use CaseTo achieve our requirement, we aredesigning a workflow language in XML.
Its schema is based on other workflow
systems such as BPEL4WS.

This language is capable of :• Variable definition (variable)• Controls (Loop, Condition)• Parallel execution• Invoke external services• Invoke built-in Java Classes
1. Workflow engine converts XML-based
workflow into groovy script.
2. The portal server of JVO runs generated
groovy script

XML Schema diagram of JVO Workflow Language

Meta
DBSkyNodeSkyNode

SIAP & SSAP
HTTP

Defect of VO of previous versions

Server 2Web Service

Integration of standard protocols
Metadata QueryThe Implementation of WorkflowMetaDB
Catalog FITS
DBVOTableFITSController• JVOQL Editor

Web Service

JVOQL(VOTable)

XPathUser
InterfaceServer 1

JVO
ServerResource MetadataRegistry(XMLDB)XMLSubaru ~ 20TB/year ALMA ~ 1PB/year

Schematic diagram of JVO

Web Service

The originality of research is required ofresearcher by construction of workflow.

Available resources
Workflow display image

Please see our demonstrations
Search results