Japanese Virtual Observatory Project Abstract : The National Astronomical Observatory of Japan (NAOJ) started the Japanese Virtual Observatory (JVO) project since April JVO utilizes the Grid technology to combine several remote computational resources. We have defined the query language for the JVO to federate multiple astronomical databases and constructed a prototype of the JVO to confirm whether federated databases can be accessed through Grid technology. More information is available at: Masatoshi OHISHI, Yoshihiko MIZUMOTO, Naoki YASUDA, Yuji SHIRASAKI, Masahiro TANAKA, Satoshi HONDA (NAOJ) and Yoshifumi MASUNAGA (Ochanomizu Univ. and NAOJ) in Collaboration with Fujitsu Ltd. Contact Address: Road Map Design for Prototype II JVO Prototype Ver 1. Main Control Window Write JVO QL here or use an editor. Open a JVO QL Editor User’s own service User’s own service Security mngmt Resource mngmt MVC MVCMVC JVO Portal JVO Portal Astronomical Catalog Query Service Astronomical Catalog Query Service Globus Toolkit Catalog DB Service Registry Service Registry Researcher Browser for JVO Browser for JVO Viewer for JVO Viewer for JVO Data Archive Service Data Archive Service Data manage DB Data Virtual Observation execution service Virtual Observation execution service Data Analysis service Data Analysis service Service Registry Service Registry Other VO services Other Catalog services Other Catalog services Globus Toolkit JVO GRID Environment Other GRID Environment UDDI server Web Browser Web ブラウザ Services callable through Grid Globus Toolkit V2 Data management Security mngmt Resource mngmt Data management At the beginning, researchers provide the JVO with simple instructions how they plan to use their own ''Virtual Observation''. The JVO portal interprets them and generates a work flow through consulting the UDDI servers, where available JVO services are registered. Based on the work flow, built-in or user- defined services are called. The GRID framework is used for dynamical assignment of distributed resources according to their availabilities. Execution results of the work flow are transferred through GridFTP and presented to the researchers. Three-Tiered Design of the JVO Prototype I The first version of JVO prototype has been completed. The design of the JVO prototype is shown as a schematic diagram. We adopted to use the Globus Toolkit 2 for our prototype. However, we also take into account the Web Service concept which is included in the Globus Toolkit 3. A main control window provides you to specify a query in JVO Query Language. You can save/load the QL in a file with the Export/Import button. A QL editor is opened by pushing the editor button and provides an easy way to specify search conditions. The JVO system splits the user input query into pieces of queries for each database, then issues search commands to appropriate servers through a “globus-job-submit” command of Globus Toolkit. This example shows a demo doing a cross-matching search between the two databases SDF-i’ and SDF-z’. At first a search command is issued to the SDF-i’ database server, mizu-g, then the result is transferred to the SDF-z’ database server, minazuki-g, where cross-matching search is executed. Image requests are issued at the last two steps.The query results are transferred through GridFTP in a VOTable format for table data and in FITS for image data. The query result is shown up in a result page, which is a kind of VOTable viewer and provides an easy access to both the table and image data. For graphical viewing of the table data, plotting tool is available. You can specify any column or expression for X/Y axis. Column attributes are displayed by pushing the “column_info” button, where you can also control the column layout. We are designing the JVO prototype II, which is an extension of the prototype I and incorporates functions required in the practical system. Followings will be newly implemented or improved on the prototype II: JVO project start Development of Prototype I Development of Prototype II Development of Practical Systems Experimental service start 1. Adoption of Globus Toolkit 3 (OGSA), 2. User management, 3. Simple user interface for making a query, showing the result, and so on.., 4. Federation of the distributed DBs, 5. Integrated data analysis services. The current JVO prototype can communicates with four distributed database, “Subaru Deep Field i’-band” (SDF-i’), SDF-z’, “Subaru XMM Deep Survey” (SXDS), and 2MASS. Linux X match データ検索処理 データ数 count PostgreSQL 画像管理 DB WSDL データベースサーバ２ SUBARU SupCam i-band Globus Toolkit V3 OGSA-DAI Analysis services Query request Gb Ether Solaris8 Web Browser User operation Window Windows, Solaris8, Linux Globus Toolkit V3 Make schedule I JVO-QL parse server Portal Server Solaris8 X match Distributed Resource manager OGSA -DAI DAISGR Results Window Search criteria Window ・ Search DAISGR ・ Parse GWDSL ・ Preparation, Execute ・ Confirmation of results Web Server Make schedule II Data query services Globus Toolkit V3 Data number count PostgreSQL Image management DB Linux Data query services Data number count ORACLE Image management DB Security Manager Resource Manager Globus Tk Portal servlet GWSDL WSDL Data base server N Data Base server 1 SUBARU SupCam z-band 2MASS Query request Registry search Query Results Status monitor Window Status monitor Registry User management Status display Data storage Globus Toolkit V3 OGSA-DAI Globus Toolkit V3 OGSA-DAI Analysis services Query request GT3 user data User DB server Linux Analysis services Analysis server Gb Ether Analysis request Federation of distributed DBs Distributed processing control