1 / 45

14 th Annual Natural Conference

14 th Annual Natural Conference. Application Reengineering Effort Pays Big Dividends in eServices California State Board of Equalization. BOE Background Reengineering EntireX ACI: Web clients w/ Mainframe Servers EntireX ACI: Mainframe clients w/ non-Mainframe servers.

kedma
Télécharger la présentation

14 th Annual Natural Conference

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. 14th Annual Natural Conference Application Reengineering Effort Pays Big Dividends in eServices California State Board of Equalization

  2. BOE Background Reengineering EntireX ACI:Web clients w/Mainframe Servers EntireX ACI:Mainframe clients w/non-Mainframe servers JavaService: design/code example RPC Servers in Mainframe Batch Natural The Future of RPC at BOE Q & A Overview

  3. Background

  4. CaliforniaBoard of Equalization • Taxing Agency • Over $40 billion annually • Over a third of California tax revenue • A financial institution • An information source

  5. Reengineering

  6. Before Reengineering Entered the 1990s with: • Stove pipe type systems • Redundant de-normalized data structures • Running on in-house mainframe

  7. Reengineering Summary • Entire Business process was inspected • Business Entities and workflows identified • Normalized relational data model created • Object oriented principles introduced: Reusable components, Encapsulation • Presentation, rules, I/O layer separation principles • Natural and Adabas selected • Natural, coded with OO & layer separation principles • Adabas, files defined with relational principles • Moved to State data center • Integrated Revenue Information System (IRIS)

  8. EntireX Advanced Communication Interface(ACI) examples:Web clients withMainframe Servers

  9. First EntireX Application Seller’s Permit

  10. Seller’s Permit - 1998 • Web query of Seller’s tax status • Read only, no updates • EntireX ACI, code both client and server • ASP/Delphi Web client presentation • Mainframe batch Natural/Adabas ACI server • Co-developed with Interactive Voice Recognition (IVR) and CICS client presentations • Reuse of rules and I/O layer objects

  11. Business-to-Government (B2G)Example

  12. Electronic Return – late 2000 • 3rd party Electronic Return Originator (ERO) Web presentation • Messaging format is XML • A Web service (w/o the SOAP envelope) • Real-time updates to Adabas and Tamino • Selected fields saved first to Adabas • Complete Tax filing saved as XML in Tamino • Delphi ACI on mid-tier • Mainframe batch Natural/Adabas ACI server • Reuse of existing Mainframe Natural backend

  13. EntireX ACI examples: Mainframe clients withnon-Mainframe servers

  14. Mainframe Clients with: • Visual Basic Desktop Servers • JAVA Mid-tier Servers

  15. JavaService: design/code example • Late 2002 • From Mainframe Natural to Mid-tier Java • Encapsulate Java

  16. JavaService – Mainframe Components • Application object: uses standard Callnat • Validation object: Natural subprogram, checks parameters, adds Java Classpath • ACI client: Natural subprogram, selects Broker node and class, sends and receives Broker message

  17. Send Email Example

  18. Parameter Data Area

  19. Application object

  20. VALIDATE object - excerpts

  21. ACI Client - excerpts

  22. XML Template - excerpt

  23. Extending JavaService

  24. Mainframe Batch NaturalRPC Servers

  25. Journey into RPC Servers Issues: • Higher administration with ACI servers, always a need for a new service and servers • Leveraging existing ACI servers not viable option Resistance: • Know and trust ACI servers

  26. ACI Server Proliferation ACI Server Count Year Prod Test/Devl • Sellers Permit 1998 1 2 • ERO Filing 2000 2 4 • B2G Fuels Filing 2002 4 6 • Total Server Count = 19 • Total Service Definition Count = 19

  27. Seller Permit ACI Server • Had multi-use data area with ACTION field to direct secondary subprogram CALLNATs via a controlling subprogram • There was always “developer anxiety” associated with changes to the controlling subprogram • Developers did not want other subsystems using the controlling subprogram

  28. Resistance to RPC • New technology • ACI servers already proven • No time for Research and Development • The next project already had a hard delivery date

  29. We took the gamble RPC has paid back big time!

  30. Benefits of RPC Tangible (original goal): • Reduced administration • Reduced service definition and server count • No more coding of Natural servers Intangible: • Natural Interface Definition Language (IDL) object generation • Wrapper generation for: Java, WSDL, etc. • Error handling • Trace facilities

  31. IDL/Wrapper Generator • Java programmers now worked with generated Java wrapper objects versus parsing data strings • The generated Java wrapper object performed the complex task of language-dependent data alignment • Leveraged many existing IRIS subprograms (e.g. Tax Calculator subprogram) • Wrapped existing mainframe rules and exposed via EntireX versus duplicating rules on another platform

  32. IDL/Wrapper Generator – cont. • Allowed Java developers to utilize existing mainframe Natural data areas without the overhead of having to code for each variable • Changed the focus to the data being passed between Java and Natural versus the technical issues of dealing with the data at either end • Java programmers feel enabled with the Natural IDL and Java wrapper generator

  33. IDL/Wrapper Generator – cont. • Faster development, a few clicks of the mouse and the Natural IDL and Java wrapper objects are generated • Regenerate Natural IDL and Java wrapper objects if Natural PDA changes – no more bit-by-bit parsing changes within Java

  34. RPC Server Error handling • The RPC server acts similar to a CICS region in that individual transactions do not bring down the server

  35. RPC Trace Facilities Adjustable setting: • 0 - Nothing is traced. • 1 - Only messages (inclusive Natural errors) are traced. • (1,E) - Messages are traced in the event of an error only. • 2 - All messages and data from/to client are traced. • (2,E) - Messages and data from/to client are traced in the event of an error only.

  36. The Future of RPC at BOE

  37. The Future of RPC at BOE • Old ACI servers and services will be retired as time permits. The Seller’s Permit has already been converted. • Logging RPC errors from user exit NATRPC01 to generalized Error log reporting mechanism • Additional production RPC server instances (i.e. batch jobs) will be added to support increasing load • XML/SOAP Wrappers and Web Services

  38. Thank you!

More Related