RTR Reliable Transaction Router Roadmap & Quality

1. Dipu Deshmukh Development Manager, Enterprise Application SW Engineering RTRReliable Transaction RouterRoadmap & Quality

2. Topics • Directions for RTR Development • RTR Roadmap 1999-2000 • Migration from V2 • Quality • Summary

3. Directions for RTR development • Make it simpler to develop RTR applications • Support ISVs, VARs and other system integrators by making it simpler for them to extend RTR features, and embed RTR into their products • Be an invisible component inside other Compaq offerings (e.g. Business Bus, Application Server Plus, etc…) • Enhance ability to exploit RTR also for Web applications

4. CY98 CY99 CY00 Q4 Q1 Q2 Q2 Q3 Q3 Q4 Q1 Aug Sep Apr May Jul Mar Apr May Jun Sep Dec Feb Jun Aug Jan Oct Nov Mar Jan Feb Oct Jul Nov Dec Compaq RTR Road Map Compaq RTR V3.2 • V3.2 Theme: 24 X 365 operation & Industry std interfaces • Partition & Journal Management • Industry std. rm interface[XA/DTC] • Nested transaction support • Management application & snmp interface (3rd party BMC Patrol support) • Improved availability features

5. RTR V3.2: Themes Second generation shadowing • Enhanced 24 * 365 operations • Tighter integration with external RMs & TMs • Industry standard management tool • Better & more user friendly documentation

6. RTR V3.2: Enhance 24*365 operations • Partitions became managed objects • Definable & predictable failover policies • Change attributes (standby/shadow/etc…) online • Influence recovery policies • Operators have more control over their journals • Selectively dump and/or forget contents • Binary message dump support • Exception transactions for offline handling • Improved availability • Reduced journal scan time • Independent transaction support • Easy online shadow site synchronization

7. RTR V3.2: Other New Features • Transactional coordination of external Resource Managers (RTR as a TM) • XA with Oracle (Unix) • DTC with SQL Server (NT) • Transactional subordination to any Transaction Manager (RTR as an RM) • Support for nested transactions • Enterprise Management with BMC Patrol KM Version 25-Sep-98

8. RTR V3.2: Documentation Updates • Revised Documents • RTR System Manager’s Manual • RTR Application Programmer’s Reference Manual • RTR Installation Guide ( single manual for all o/s) • New Documents • RTR Migration Guide • RTR Application Design Guide • New Online Deliverables • All documents now in HTML format • Selected documents available on RTR website:http://www.software.digital.com/rtr/ • Support/Partner website:http://www.compaq.com/products/software/ntenterprise

9. CY98 CY99 CY00 Q4 Q1 Q2 Q2 Q3 Q3 Q4 Q1 Aug Sep Apr May Jul Mar Apr May Jun Sep Dec Feb Jun Aug Jan Oct Nov Mar Jan Feb Oct Jul Nov Dec Compaq RTR Road Map Compaq RTR V3.3 Compaq RTR V3.2 • V3.2 Theme: 24 X 365 operation & Industry std interfaces • Partition & Journal Management • Industry std. rm interface[XA/DTC] • Nested transaction support • Management application & snmp interface (3rd party BMC Patrol support) • Improved availability features • V3.3 Theme: Object interface & Legacy Integration • object API • Component technologies support • Gateway to MVS • Store & Forward • Extensibility features

10. RTR V3.3: Themes Embedding & Interoperability • Objects & Components • Legacy Interoperability • Reliable Asynchronous Messaging • Extensibility • Tools

11. Planned RTR V3.3 Features: Objects • Object oriented API for RTR • Class library for RTR: Easier to use with C++/Java • COM access to RTR: Easier to use with VB • Compatible with existing applications • Support for component technology • Use your favorite tools to write COM+ applications • Better support for ODBC/ADO to allow component level plug-in

12. The oRTR Classes RTRServerEnvironment RTRClientEnvironment RTRData RTRServerTransactionController RTRClientTransactionController RTRServerTransactionProperties RTRClientTransactionProperties RTRServerMessageHandler RTRClientMessageHandler RTRServerEventHandler RTRClientEventHandler RTRPartition Client Classes Common Classes RTRPartitionProperties Server Classes

13. Planned RTR V3.3: Interoperability • Asynchronous transactional interface to MVS environments • Gateway to MQ-Series (RTR clients posting messages) • Reliable store and forward support • Building block technology to interconnect multiple RTR domains • Usage of SQL database as message store. • Support for both synchronous & asynchronous connections. • Reliable broadcasts

14. TR TR Planned RTR 3.3: Interoperability ? RTR ? Tandem

15. Planned RTR V3.3: Extensibility • Expose internal interfaces in RTR so that customers and partners can customize or extend RTR features • Routing algorithms (e.g. XML) • Security • Integration with other external RMs & TMs (e.g. Transaction Internet Protocol) • Embedding into other management tools (e.g. MMC)

16. Planned RTR 3.3: Extensibility Basic RTR routing Custom RTR routing RTR shared library Basic security (access strings) Custom security

17. Planned RTR V3.3: Tools • Tools to allow customers to exercise RTR • Functionality oriented tools • Performance oriented tools • Diagnostics oriented tools

18. Beyond RTR V3.3 • Support Linux • Support Tandem HW • Browser access to RTR over Internet • Enhanced load balancing of requests across backends • Policy based management • Application Management • Server restarts • Group failovers • Application Integration (Business Bus)

19. The migration story: Status • Impact of migration to V3 was underestimated • Several customers were impacted • V3.2 schedules were disrupted • Problems mainly in the following areas • System tuning requirements changed • RTR’s error returns not always identical to V2 • Bugs in the compatibility layer • Our lab conditions did not adequately reflect our customer environments

20. The migration story: Support plan • V2.2D has been certified for Y2K compliance • Most customers have successfully deployed V3 • Migration help is available to customers • Benefits of V3: Immediate advantage of • TCP/IP, DECnet-OSI • Anonymous clients • Connections through Internet firewalls • Many feature enhancements in V3

21. Keys to RTR Quality • Code Management & Formal Engineering Processes • Multi-faceted Testing • Problem Tracking • Release Predictability

22. RTR Code Management &Formal Engineering Processes • Source library using shadowed CMS libraries • Common automated build procedure • Use of OO methods & Tools for design • Designs are published and reviewed • Code changes require Test plan & verification • Unit Tests added to Regression Suite • Final verification against released kit only

23. Multi-faceted Testing • Scripted regression tests • Performance/Load tests • Fault-injection tests • Multi-platform tests • V2/V3 interoperability tests • Rolling Upgrade tests • Need help in field testing different environmental issues

24. Problem Tracking • Problems have associated severity & state • Tracks current owner and state of each problem according to the RTR Engineering Process • Management summary reports created weekly • Engineering priorities driven through this tool

25. Release Predictability • Usage of Object oriented technology & tools (Rational Rose) • Design reviews to catch problems early • Closer management scrutiny

26. Summary • Development priorities • Continue to support Classic RTR customers with better price/performance and state-of-the-art features • Support ISVs and System Integrators with ease of integration into applications & products • Make it easier to extend and support RTR by partners and application providers • Improved quality and predictability of releases