ThePetrinex Registry Reader is an interactive tool that is utilized forgenerating reports with data obtained from Petrinex.ca which is awebsite for “Canada Petroleum Information Network.” The websiteis significant since it provides an interface that permits accessingand querying a large and well-maintained database. As a result,there was a need to integrate the Petrinex Registry Reader into aheavily-used and well-maintained web application. In the developmentof Standalone Reader architecture, there was no definitearchitectural pattern followed. Comprehensive understanding of theweb application design was drawn from observing the structure of thecode. Similarly, various components were monitored on how theyinteract since the system was to be upgraded to be self-documentingcode.
Dueto the nature and size of the Standalone Reader, the team gotinvolved in a more in-depth analysis of its structures, and that wasachieved by evaluating dependencies required versus a typical“software ticket.” Diagrams and documentation are verysignificant since they help to isolate components that need to beremoved as integration progress. The architecture of StandaloneReader is in the form of layers which assist in the understanding ofthe application and that is also a sign of how the application wasunderstood. In the uppermost layer of the Standalone Reader, theuser interface (UI) and the Java UI are replaced with a view withinthe business web application.
Duringthe Standalone Reader development, the second component of the UIlayer was challenging. On the other hand, Selenium forms the thirdparty library and is the core of Standalone Reader functionality.Selenium is a tool that is utilized for automating browsers. Duringthe integration process, Petrinex Credential Management waseliminated since it was considered a low priority. The component hadthe ability to manage two sets of usernames and passwords. TheStandalone Reader is composed of a third layer which is responsiblefor the core function of the application. The data that was collectedfrom the Petrinex.ca were temporarily stored in the A HyperSQLdatabase.
Theapproach that was used to integrate the Standalone Reader is known asthe divide-and-conquer technique. Every component was handled andsolved independently and merged and the central point of the systemwas Registry Service class. This particular web app makes use ofspring that provides a platform for configuration model andall-inclusive programming. Developing the registry reader is veryinvolving since it comprises of five steps which are very criticalfor its operation. First, there is a development of the view, wheresingle JSP was used that replicates all the GUI features that arelocated in the Standalone Reader.
Thesecond step involves creating of the controllers that helped inprocessing the user requests for data from the Petrinex database. Thethird step entails making the registry reader as a service because ithas access to the entire application context including therepositories, database, and other services. The fourth step includescreating the model where the HSQLDB layer was replaced in theStandalone Reader. The final step was testing the registry readerespecially during the integration and development period, and moretesting was conducted on the report generation and registry browser.
Inessence, the integration of the Petrinex registry Reader to become abusiness web application was successful. The architecture of theStandalone Reader has the model portion which is the weakest part ofthe registry reader after the removal of the HSQLDB.
No related posts.