1 / 26

VLAM-G Architecture & VIMCO Integration

VLAM-G Architecture & VIMCO Integration. CO-IM Group & AM Group VLAM-G Meeting July 3, 2001. Outline. Architecture A simple scenario for a MACS study Information management in VLAM-G Implementation. 4-tier Architecture. Science portals. client tier.

mauve
Download Presentation

VLAM-G Architecture & VIMCO Integration

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. VLAM-G Architecture &VIMCO Integration CO-IM Group & AM Group VLAM-G Meeting July 3, 2001

  2. Outline • Architecture • A simple scenario for a MACS study • Information management in VLAM-G • Implementation

  3. 4-tier Architecture Science portals client tier Web server and supporting functionality Web tier VLAM-G generic functionality, application specific functionality application server tier Data / information resources, hardware resources,… resource tier

  4. Architecture - Components Front-End client tier Web application servers Web server Authentication server Web tier RTS VIMCO Server Session manager Processing modules application server tier VLAM-G archive Linux cluster CAVE µ-Beam resource tier Expressive Kernel DB MACS hardware resources data / information resources

  5. Architecture - Technology Front-End Java Web Start, XML client tier Web application servers Java Servlets Authentication server Globus Security Infrastructure Web server Apache Web tier Session Manager Java RTS C, C++, Globus VIMCO Server Java, C, C++, XML, JDBC/ODBC, Matisse JAPI Processing Modules C, C++ application server tier VLAM-G Archive replication over raw disks Expressive Matisse Kernel DB Matisse MACS Matisse Linux cluster CAVE µ-Beam resource tier hardware resources data / information resources

  6. Interactions between components Front-End client tier XML internet Servlets Web tier authentication Web server XML session manager XML application server tier VIMCO Server RTS resource tier Hardware resources Kernel database application databases & archives

  7. A simple scenario A physicist VLAM-G user: • Log-on to VLAM-G • Perform a new surface analysis study • Fill in the MACS PFT • Perform surface analysis of a sample using the FTIR • Save the output of FTIR to the archive • Save (commit) the study • Log-out

  8. Log-on to VLAM-G Front-End client tier Physics Portal 1 internet Web tier authentication 5 Web server 2 3 session manager application server tier 4 VIMCO Server resource tier

  9. Surface analysis study – 1Obtain the MACS PFT Front-End client tier Physics Portal MACS PFT 1a 4c internet 4b Servlets Web tier Web server 1b 1c 4a application server tier VIMCO Server 2 3 resource tier MACS Kernel database application databases & archives

  10. Front-End – PFT Instantiator • PFT instantiator • Provides a guideline to the user • Allows the class to display its interface to get the information • Sends the information to the server as XML • Allows the user to establish the links between the steps

  11. Surface analysis study – 2Instantiate the MACS PFT Front-End client tier MACS PFT 1a internet XML Servlets Web tier Web server 1b 1c application server tier XML VIMCO Server 2 resource tier MACS application databases & archives

  12. Front-End – Experiment Editor • Experiment editor • Allows the user to compose his experiment using the available modules • Allows the user to save the experiment and submit it to the RTS to be executed

  13. Surface analysis study – 3Define a surface analysis experiment Front-End client tier Experiment Editor 1a 5d internet XML XML 5c Servlets Web tier Web server 1b 5b 1c application server tier XML XML VIMCO Server 2 4 3 resource tier MACS Kernel database application databases & archives

  14. Surface analysis study – 4Save and execute the experiment Front-End client tier Experiment Editor 1a 3 internet XML 3 Servlets Web tier Web server 1b 3 1c 1c application server tier XML XML VIMCO Server RTS 3 3 3 2 1d 3 resource tier Archive Hardware resources MACS Kernel database application databases & archives

  15. Information Management in VLAM-G VIMCO support to VLAM-G requirements: • Generic VLAM-G requirements: • VIMCO Server: data/information management functionalities • RTS information management modules • Session information management • VLAM-G AM requirements: • Kernel DB: Available modules, experiment topologies, PFTs for applications • Applications’ requirements: • Modeling application databases • PFTs for applications • Application user interfaces (interfaces for PFT instances)

  16. VIMCO Databases • Application databases (Expressive, MACS): • Study steps information (annotations) • (Structured) study/experiment results • Archive • (Unstructured) study/experiment results • Large data sets • Kernel DB • Information about available VLAM-G modules (developer, computing requirements, documentation, input and output data types, etc.) • Experiment topologies • PFTs for the VLAM-G applications (in the future) • User profiles and preferences (in the future)

  17. VIMCO Server • Single access point (broker) to the databases providing uniform and consistent support to all information management related aspects of VLAM-G components, namely the: • Front-end • RTS • Session manager • Session information management in a distributed environment • Open and flexible for integration of advanced information management functionalities in the future (e.g. Archipel and VO support)

  18. VIMCO Server functionality • Generic data/information management functionalities • Several Java, C, and Web based DB manipulation libraries • Support for VIMCO RTS processing modules • XML data management/exchange functionalities • Session information management • Supporting information management in a distributed and heterogeneous environment • Web application servers (Servlets)

  19. VIMCO RTS Modules • Connect/disconnect database • Start/commit/abort transaction • Archive operations: • Read from an existing file, write it to archive • Read from archive, write to a given file • Read from an input port, write it to archive • Read from archive, write it to an output port • Query processing: • Execute a query, write the result to a given file • Execute a query, write the result to an output port • Remote query processing: • Execute a query on a remote Grid node

  20. Experiment Editor Process Flow Template Front-End Start Portal End Portal Distributed RTS Connect Node B Node A Read / Write Disconnect Write Read Write Read VIMCO Server VL ARCHIVE EXPRESSIVE MACS EFC

  21. Implementation • Recall the simple scenario: • Log-on to VLAM-G • Perform a new surface analysis study • Fill in the MACS PFT • Perform surface analysis of a sample using the FTIR • Save the output of FTIR to the archive • Save (commit) the study • Log-out

  22. Implementation requirements(to support the scenario) • User session information management • Storage and retrieval of PFTs • Modifying the application user interfaces to fit into this architecture • Application classes capable of drawing itself and generating XML • XML data/information management for: • All Front-end – database communication • Front-end – RTS communication • Base VIMCO RTS processing modules • Web application servers to support client-server interaction (Servlets) • VIMCO Server – RTS interface

  23. Implementation plansshort term (with the current staff) • Start from the most required functionality: • XML support (central to VLAM-G information management): • Defining XML schemas for the required XML documents to be exchanged • Developing generic tools that can understand the XML schemas and create and parse the XML document accordingly • XML generator/parser tools – database interface • Application user interface modifications • Base VIMCO RTS processing modules • One group member is additionally working on the Front-End implementation

  24. Implementation planslong term • Archipel - federated information management system integrated within VIMCO Server: • Information sharing and integration • visibility and access rights • VO support integrated within VIMCO Server • Flexible PFTs and supporting data manipulation toolkits • Support for advanced user profile management, user preferences, etc.

  25. Considerations • Priorities have to be set • Component design and implementation must be open for future modifications/extensions • Minimal effort for modifications/extensions • External developments have to followed • Matisse developments

More Related