1 / 36

Reach Your Technical Peak 2004

Reach Your Technical Peak 2004 Fathom: Internals to Deployment Agenda Introduction Internals Deployment Summary Questions Introduction Last Tech Peak – we introduced Fathom and why it was important to use Fathom Today – we will discuss the technology and deployment of Fathom.

jacob
Télécharger la présentation

Reach Your Technical Peak 2004

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. Reach Your Technical Peak 2004

  2. Fathom:Internals to Deployment

  3. Agenda • Introduction • Internals • Deployment • Summary • Questions

  4. Introduction • Last Tech Peak – we introduced Fathom and why it was important to use Fathom • Today – we will discuss the technology and deployment of Fathom.

  5. Under Development D I S C L A I M E R • This talk includes information about potential future products and/or product enhancements. • What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here.

  6. Internals – Core Technologies • JAVA • JSP • XML • New in 3.0A – extensible rules in the catalog.xml • XSLT

  7. Internals – Core Technologies JAVA • Main component of Fathom • Fathom loads into the Progress AdminServer JVM

  8. Internals – Core Technologies JSP • Most of the Fathom Console uses JSP • Allows for dynamic page generation • Allows for events (like Alerts) to be posted to Console

  9. Internals – Core Technologies XML • Format for importing and exporting templates • Format used when dumping the Project database to text • Format for Extensible rules manipulation in 3.0A

  10. Internals – Core Technologies XSLT • Reports use XSLT in this way • 4GL reports run and output both text and XML • The XML is used to create an HTML report with graphs • The XSLT is used convert the XML to HTML format including graphs for the report representation in the Fathom Console

  11. Internals – Core Technologies

  12. Internals – Commercial and Open Source Technologies • Jetty Web Server (for Fathom console) • Perl (jobs support) • Kava Chart (graphing) • Jakarta-Oro (regular expression support – log file monitoring) • New in 3.0A – Quartz scheduler (jobs and reports), allows for “cron” like syntax • See the Help  Credit page for more technologies

  13. Internals – Commercial and Open Source Technologies Jetty Web Server • http://jetty.mortbay.com • Small efficient java based web server • Designed to be embedded into Applications • Supports servlets and JSP

  14. Internals – Commercial and Open Source Technologies Perl • Perl version 5.6.1 • Allows for multi-platform writing of jobs • Well accepted and widely used • Fathom jobs use Perl extensively • http://www.cpan.org • http://www.perl.com • http://www.perldoc.com

  15. Internals – Commercial and Open Source Technologies Kava Charts • Java based graph creation software • Data retrieved in Fathom displayed in graphical form • New in 3.0A, more control of graph viewlets, more graph options, more graph types,… • http://www.ve.com/servlet.html

  16. Internals - Graph

  17. Internals – Commercial and Open Source Technologies Jakarta-Oro • http://jakarta.apache.org/oro/ • Allows for regular expression searching of log file for the Log File Monitor

  18. Internals – Commercial and Open Source Technologies Quartz Scheduler • New in 3.0A • http://www.quartzscheduler.org/ • Allows for more flexible scheduling of jobs and reports • Allows for “cron” type scheduling of jobs and reports

  19. Internals – Commercial and Open Source Technologies More technologies

  20. Internals – Object Store Technologies • JAVA based, single user, Object Store database designed to be embedded • PSE Pro database for project storage • New in 3.0A - graphing storage and customization

  21. Internals – Graph with threshold

  22. Internals – Progress Technologies in Fathom • Fathom Trend Database – Progress DB • Schema explained in documentation • Reports – Progress 4GL (including XML) • Report source code supplied in a Progress Library • New in 3.0A – alerts on reports • Progress 4GL now alerts Fathom of any problems running the report

  23. Internals – Fathom Technologies in Progress • Osmetrics.dll • Installed with every Progress product that supports the AdminServer since 9.1D06 • Loads in the AdminServer • Gathers system information • _dbagent • Installed with every Progress database product since 9.1C30 • Gathers database information directly from the VSTs

  24. Internals – SonicMQ Technologies • Communication for Remote Monitoring • In Progress • In Fathom • New in 3.0A - _dbagent incorporated into Sonic infrastructure

  25. Internals – Using technologies for Deployment • Jetty Web Server - allows for remote management and browser based interface • Fathom Technologies in Progress - foundation for remote monitoring • Progress Technologies in Fathom – allows for remote trend databases and remote reporting • SonicMQ Technologies – infrastructure for remote monitoring

  26. Deployment Topology

  27. Stand Alone Deployment Admin Trend Database Production Machine OpenEdge Databases OpenEdge AppServers Fathom Admin Admin Admin WebSpeed Management Server Server Server Brokers System Resources

  28. Stand Alone DeploymentCharacteristics and Challenges • Characteristics • Fathom Management Installed on production machine • Customer uses Fathom Management to support production machine only • No additional hardware commitment • Challenges • Maintenance

  29. Multiple Deployments Admin OpenEdge OpenEdge Machine A Machine B Databases Databases OpenEdge OpenEdge AppServers AppServers Fathom Fathom Fathom Admin Admin Admin Admin Admin Admin WebSpeed WebSpeed Management Management Management Server Server Server Server Server Server Trend Brokers Brokers Database System System Resources Resources Monitoring Machine

  30. Multiple DeploymentsCharacteristics and Challenges • Characteristics • FM Installed on all production machines and management machine • Customer uses Fathom Management to support all machines • Additional hardware needed (1 machine) • Challenges • Stand alone challenges • Installation • Security

  31. Multiple DeploymentsWhere Fathom Management Helps • Installation / Confguration • Standard Progress Installation • Auto-discovery of resources • Defaults set up to be conservative • Security • HTTPS • JAAS Authentication • Admin/Operator Roles • Deployment Automation • Perl API • Import/Export functionality

  32. Remote Deployment OpenEdge Machine A Databases OpenEdge AppServers Admin Admin Admin WebSpeed Server Server Server Brokers Admin System Resources OpenEdge Machine B Databases OpenEdge AppServers Fathom Admin Admin Admin WebSpeed Management Server Server Server Trend Brokers Database System Resources Monitoring Machine

  33. Remote DeploymentCharacteristics and Challenges • Characteristics • Fathom Management Installed Once • Use Fathom to Monitor Remote Applications and machine • Persistent Network Connection required • Additional Hardware Needed (1 machine) • Challenges • Same as multiple machines

  34. Remote MonitoringWhere Fathom Management Helps • Enabling Remote Monitoring • All required components in Progress 9.1D08 • No customer install required • Enable customer site with fmconfig utility • Security • Sonic MQ for all Messaging (3.0A) • Sonic MQ Authentication & Encryption • Deployment Automation • Same as Multiple Machines

  35. Summary • Many different technologies make Fathom • Allows for many deployment options

More Related