180 likes | 315 Views
PWB520: Customer Case Study: Migrating Complex PowerBuilder Applications to the Web w. DataWindows and All. Gil Pina gil.pina@cynergysystems.com August 15-19, 2004. Current Information Technology Demands. Global Internet usage sends a wakeup call to organizations everywhere
E N D
PWB520: Customer Case Study: Migrating Complex PowerBuilder Applications to the Web w. DataWindows and All Gil Pina gil.pina@cynergysystems.com August 15-19, 2004
Current Information Technology Demands • Global Internet usage sends a wakeup call to organizations everywhere • The Internet is just a network… • No different than the network in the office… • Applications don’t have to stop at company walls… • Management realizes the potential and decides it’s time to get their presence out on the internet…
Current Information Technology Demands • Management looks to IT to make this happen • For the first time, IT is seen as a way to improve the bottom line and gain competitive advantage • IT gets never before seen funding and is told to make it happen • How?
Current Information Technology Demands • Tidal wave of capital creates flood of new and competing technologies • IT management given the daunting task of choosing which technology is the best for them • Rich client technologies quickly dissipate in favor of very thin, browser technologies • Thin client technologies are script based and effectively code modules performing one grandiose string concatenation • Seem to need a different and new language at every tier • HTML, JavaScript, Java, VBScript, etc. • Each language has steep learning curve • Data binding to a web page is unmanageable
Current Information Technology Demands • Technology impediments take their toll • New applications are delayed months and years • Cost overruns are through the roof • Functionality is greatly reduced to bare bones • Management is displeased • IT Managers need solutions to their problems… • Reduce the learning curve • Provide better maintainability by separating business logic from the spaghetti code HTML concatenation • Facilitate data binding to web pages • These requirements are starting to sound strangely familiar…
Setting the Stage • We all work with PowerBuilder so, how about using PowerBuilder for web development? • Interesting but PowerBuilder is just a client/server technology….right? • Wrong • PowerBuilder displays DataWindows in Windows applications…not HTML…right? • Wrong • PowerBuilder doesn’t have a web server so how can we create web applications with it?
Setting the Stage • PowerBuilder DataWindows can now create rich HTML output from standard DataWindows with full data binding… • But PowerBuilder by itself is not a complete solution… • However, PowerBuilder combined with Sybase Enterprise Application Server IS a complete solution • Sybase Enterprise Application Server • End-to-End Solution – Web Server, Application Server, etc. • PowerBuilder components ( NVO’s ) run natively on EAServer as CORBA components • Allows PowerBuilder developers to quickly build distributed and Web applications using a powerful and familiar language • PowerBuilder components and JavaServer Pages provide a high performance and scalable architecture for Web applications
Setting the Stage • With EAServer, we have the core pieces to build web applications using PowerBuilder • It is technically possible to develop web applications with these technologies….but is it plausible? • The answer is that with unlimited time and resources, most anything that’s possible becomes plausible…but who has unlimited time and resources?
PowerBuilder, EAServer and EAF • Where PowerBuilder and EAServer end, Cynergy Enterprise Application Framework (EAF) takes over • EAF provides a proven and reliable framework of objects and services to turn the possible into the plausible • Set of building blocks to simplify the development of Web and Distributed apps using PowerBuilder & EAServer • Mature product developed by PB/EAServer experts • 5 years of development • Customers worldwide • Not a Tool • Developers build on top of EAF objects to create applications • PowerBuilder and Java objects
EAF Features • DataWindow-Centric Design • DataWindows deployed to EAServer within PowerBuilder components • DataWindow Uses – User Interface, Database Access, Business Logic • JavaServer Pages invoke EAF components • EAF components merely NVO’s written in PowerBuilder • EAF components return content generated from DataWindows (HTML, PDF, XML, Excel, etc.) • Users are presented with the content in standard browsers • No need for plugins • JSP API simplified • Very basic understanding of Java only • No costly learning curves
EAF Features • Robust event model in PowerBuilder • Developers provided placeholders for business logic, custom user interface creation and data access logic • Developers can take as much or as little control of the process as they choose • Event model is based around DataStores and coding styles familiar to PowerBuilder developers
EAF Customers • Over 1,000 companies and organizations using EAF Worldwide • Customers within nearly every vertical • Financial • Agriculture • Healthcare • Telecommunications • Education • Local, State and Federal Government
EAF Customers (US) • US Library of Congress ( USA ) • US Department of Energy ( USA ) • State of Michigan Department of Natural Resources ( USA ) • State of Montana Department of Labor and Industry ( USA ) • Gary Job Corps ( USA ) • National Cooperative Bank ( USA ) • New York State Workers Compensation Board ( USA ) • PacificSource Health Plans ( USA ) • University of Houston ( USA ) • Steel Dynamics ( USA ) • Unisys ( USA ) • Global Marine Insurance ( USA )
EAF Customers (International) • University of Sydney ( Australia ) • Danish Cancer Society ( Denmark ) • Alberta Gaming and Liquor Commission ( Canada ) • DataFusion ( Hungary ) • Blue Whale Group ( France ) • Belgacom Mobile ( Belgium ) • Which Limited and Consumers Corporation ( UK ) • Saudi Aramco ( Saudi Arabia ) • KI Teroplan ( Norway )
EAF Case Study • The Unites States Department of Energy (DOE) had an existing application known as the Facilities Information Management System (FIMS) written in PowerBuilder 5 that maintains specific information about all DOE owned or controlled properties in the United States. • FIMS runs in various DOE facilities nationwide as a stand alone 2-tier client server application which connects to a single repository database maintained by DOE. • Cynergy was asked by DOE IT Service Provider RSIS to find the best solution for migrating the FIMS application to the web.
EAF Case Study • FIMS Migration Metrics • 2 Cynergy Developers • Over 75 PowerBuilder DataWindows with several tiers of corresponding business logic • 55 Oracle database tables • Implementation of highly secure application to meet strict federal Department of Energy security requirements (SSL w/ Entrust certificates) • 6 months total development time • Technologies Used • PowerBuilder 8 for EAF object development and FIMS data access • Sybase EAServer 4.2.2 for EAF/FIMS object and web hosting • JavaScript for client-side validations and processing • J2EE-based objects for integrated security • Oracle 9i secured data repository
More Cynergy Successes • Sybase has developed many case studies on EAF customers • http://www.sybase.com/content/1030931/KeyLink_ss.pdf • http://www.sybase.com/detail?id=1025264 • http://www.sybase.com/detail?id=1029272 • http://www.sybase.com/content/1018839/L02091_MedicWare_ss.pdf • Check out more at Cynergy’s web site… • https://www.cynergysystems.com/public/casestudies/
Get Started with EAF Today • Download EAF on the Cynergy web site • Source Code • Tutorials • Whitepapers • Examples • http://www.cynergysystems.com/public/products/eaf • Cynergy Contacts • Gil Pina – gil.pina@cynergysystems.com • Keith O’Donnell – keith.odonnell@cynergysystems.com • Carson Hager – carson.hager@cynergysystems.com