NASA Engineering Database NASA Engineering Database (NED) (NED) Prototype Prototype Stephen C. Waterbury NASA/Goddard Space Flight Center December, 2000
Model Interaction and Transformation Security, Services: Auth., Thin Expresso and Client Request Web Browser API: Database: Routing Java Server Repository Services: PostgreSQL Pages Manager Database of Users File Vault/Storage Search Manager (STEP, proprietary, docs, etc.)
MetaServices (Dictionaries, MetaRepository MOF, etc.) (read/write) Control Services Directories (Roles/Perms) (people, orgs, licenses, products, etc.) (read/write) System External API Systems Library (peer/peer, (PDM, etc.) Services federation, Libraries global search) (read/write) (part models, IP, etc.) Security, Auth., Model and Interaction and CAD/CAE Request Transformation Tools Routing Thick Services Services Client (translate and API transform models, Utility Tools generate views) (Viewers, Special Editors, Transaction Databases and Caches etc.) Manager [R/O/O-R] DBMSs (reads/writes) (Master Model Repository) Thin Client Web Browser Search API File Vault Manager (p21, proprietary files, docs, etc.) (reads only)
Expresso Repository Manager PostgreSQL Check-in Process 1. File upload via Web browser 2. RM calls Expresso to run Express-X to extract PDM data. File Vault/Storage 3. Expresso outputs XML-encoded PDM data. (Unix Filesystem) 4. RM executes transaction to write PDM data into PostgreSQL and AP210 file to “vault” (PDM data contains reference to file).
Recommend
More recommend