Given by Wojtek Furmanski at SANDIA Presentation on 11 March 98. Foils prepared 15 March 98
Outside Index
Summary of Material
This is a summary of Status and Design of JWORB which is a Java Server that combines CORBA Web and COM capabilities and so implements concept of the pragmatic object Web |
We give performance results compared to RMI and CORBA brokers |
We describe a "ping demo" which nicely shows interplay between CORBA and Web capabilities |
We describe the RTI application to distributed modeling and simulation with the Globus integration described separately by Tom Haupt |
Outside Index Summary of Material
Wojtek Furmanski NPAC Syracuse University 111 College Place Syracuse NY 13244 |
This is a summary of Status and Design of JWORB which is a Java Server that combines CORBA Web and COM capabilities and so implements concept of the pragmatic object Web |
We give performance results compared to RMI and CORBA brokers |
We describe a "ping demo" which nicely shows interplay between CORBA and Web capabilities |
We describe the RTI application to distributed modeling and simulation with the Globus integration described separately by Tom Haupt |
Integrates protocols for inter-tier communication |
Client-Middleware protocol integration via protocol detection and dedicated protocol handlers |
Currently supported: HTTP (Web) and IIOP (CORBA) |
Detection via anchor strings in message headers: GIOP for CORBA, GET, POST etc. for the Web |
At the planning stage: RTP (A/V streams), T120 (collab/multimedia), DCE RPC (DCOM base) |
CORBA - JWORB is an OMG compliant ORB written in Java and acting as middleware in the 3-(or more)-tier CORBA applications |
DCOM - we are planning to implement COM/CORBA bridge as specified by OMG to enable interoperability between CORBA and DCOM objects |
RMI - JWORB is written in Java so the interface to the 100% Pure Java world is naturally available via RMI |
W3C - we intent to implement new Web Object Model (XML+RDF+DOM) using CORBA services in JWORB |
HTTP - support for base Web services operational (serving pages, servlets, cgi) |
IIOP - work in progress
|
Other Protocols (RTP etc.) - planning stage |
Fig. 1 compares JWORB performance for integer array transfer with other Java ORBs. RMI is the fastest and it probably uses custom native library. |
Fig. 2 presents a similar comparison for array of structures - here performance differences are due to various strategies used for object serialization |
Fig. 3 illustrates that C ORB such as omniORB is oreder of magnitude faster than even the fastest (here RMI) Java ORB. |
Screendumps illustrate Performance Monitoring Applet which measures and displays real-time performance of the ping sequence between Netscape4 ORBlet client and JWORB server using IIOP protocol. |
Screen 1 illustrates the Performance Monitoring applet in a typical steady state of operation |
Screen 2 illustrates the same applet while the client downloads a Web page (with JWORB paper text and gifs) from JWORB/HTTP server - HTTP spikes indicate transient performance losses in the IIOP channel. |
Implement core ORB services: POA (Portable Object Adapter), IR (Interface Repository), COM/CORBA bridge |
Implement base CORBA services: Naming, Events, Relationship, Concurrency. |
Address/plan advanced CORBA services: Trader, Security, Transactions, Messaging |
Start using JWORB services to prototype WOM |
Portable Metacomputing and Parallel Processing Environment (WebFlow over JWORB over Globus) |
WebHLA - Object Web based DoD Modeling and Simulation (WebFlow over JWORB-RTI over FOM/SOM simulation objects) |
NPAC leads FMS (Forces Modeling and Simulation) CTA PET programs at ARL and CEWES within the DoD High Performance Modernization Program. |
Our strategy for High Performance FMS is called WebHLA and based on the convergence of three ongoing technology evolution/standardization thrusts:
|
DMSO HLA (High Level Architecture) is based on RTI (Run-Time Infrastructure) - a distributed object bus similar to CORBA |
Current RTI is a smaller model than CORBA and aimed at integrating existing simulation frameworks and codes |
New advanced simulations will benefit from CORBA strength and DMSO already leads M&S SIG in OMG to prepare ground for CORBA based HLA/RTI to come. |
JWORB based Object Web RTI under development at NPAC can be viewed as one such early prototype. |
RTI is a software bus used by HLA Federates (simulation objects) to plug in and interact with other Federates within a Federation (distributed simulation) |
This interaction is based on publish/subscribe model and is mediated by two RTI communication objects: RTI Ambassador and Federate Ambassador |
Ambassadors provide access to RTI Services such as Time Management, Data Distribution Management etc. |
JWORB implements both Ambassadors as CORBA objects; all services in Object Web RTI are distributed and they use CORBA services to implement RTI services (economy, QoS etc.) |
|
|
|
Object Web RTI will provide us with a middleware glue to experiment with connecting several simulation packages (CMS, ModSAF, SPEEDES) an ddistributed centers. |
WebFlow, acting as visual authoring for JWORB managed components, will be adapted here to support visual design of HLA object models (FOM, SOM) and visual programming of HLA simulations (e.g. Virtual Prototyping for T&E) |
|
|