As promised in the previous article, let’s apply the multi-tier conceptual approach in a couple of architecture implementations.
Before we begin, a quick note: This article relies heavily on the previous one, so if you haven’t read it, please do so before continuing.
A Simple Multi-Tier Architecture Implementation
The three tiers should be independent from each other so that each block can be reused in a different program. How is this possible? Well, ILE’s modularity allows us to create service programs that aggregate the blocks belonging to each of the three tiers.
Let’s assume that a simple program uses only one block of each tier. Consider the inventory management program I’ve been using as an example in this series. The program allows users to create, update, and delete items from a company’s inventory, via screen interaction. Its implementation in ILE would look like Figure 1.
Figure 1: A simple multi-tier architecture implementation for an interactive inventory management program
In this implementation, the INVMNT module controls the main flow and the screen interaction, calling procedures and functions from the INVBL service program to check if the action requested by a user is valid and possible. It might also call procedures and functions from the INVDA service program, for example to retrieve item descriptions or stock quantities.
The INVBL service program might check whether the user is allowed to delete items from inventory or whether new orders can be accepted from a certain client. The business logic procedures and functions that INVBL contains will, in turn, call INVDA’s procedures and functions to perform the lower-level database operations—such as reading the necessary records from a client’s current account and writing a new record to the order master file—and apply the business logic to the data that was retrieved. Thus, appropriate business decisions (validations, enforcement of business rules, and so on) are made.
If there is a need to print something, a separate program should be built, following the same multi-tier architecture implementation. Some of the functions called by the original program will probably be reused in the new program, such as retrieving item descriptions and client names. Sometimes it even makes sense to transform a “printing program” into a service program, if it gets called by several programs, to avoid mass-recompilation problems.
This is a simplified model, with only one module for each tier. It doesn’t account for the utility, generic, or pure calculation modules that exist in almost every ILE application. I didn’t include them in Figure 1, but they exist in the form of additional modules, bound by copy to the respective service programs, which in turn are bound by reference to the INVMNT program.
A More Realistic Multi-Tier Architecture Implementation
Now, let’s analyze a slightly more realistic example: an order management program. The ORDMNT program, depicted in Figure 2, allows the user to enter new orders, check an order’s status, and perform all sorts of other order-related operations. In an OPM implementation, this would be a huge piece of code, with routines duplicated from other programs, such as inventory and client management programs.
Figure 2: A realistic multi-tier architecture implementation
In an ILE multi-tier architecture implementation, there’s no code duplication, just reuse. I chose to depict program ORDMNT the same way I pictured the ILE program concept in Figure 1 of the previous TechTip to show how the different service programs used by ORDMNT “fit” in the concept.
You’ll notice that service programs INVDA, ORDDA, and CLIDA are connected to the data access tier of the program. These service programs would provide data access functions, in the form of RPG or SQL I/O servers, designed to read and write records to the database.
Service programs INVBL, ORDBL, and CLIBL would supply higher-level procedures and functions like Rtv_Item_Description, Rtv_Order_Delivery_Date, Wrt_Order_Record, Upd_Order_Record, Rtv_Client_Name, Upd_Item_Qty, Clc_Delivery_Fee, Clc_Earliest_Delivery_Date, and Chk_Client_Debt, just to name a few. There are many more procedures and functions involved. Just like in the previous example, I neglected the utility (to send the order confirmation by email, fax, or web service invocation, for instance) and general calculation service programs (such as date operations needed to calculate the actual delivery date assuming it cannot be on a weekend, for example). I also omitted the modules linked to each of the service programs depicted to try to keep things simple. Only the ORDMNT module was depicted to remind you that the ILE program doesn’t contain code, only the respective entry module (ORDMNT, in this case) does.
Program ORDMNT’s binding directory would contain an entry for each of the service programs used. Otherwise, the compiler wouldn’t be able to resolve all of the imports of module ORDMNT. You would be able to compile the module, but you’d fail to create the program.
It’s an interesting approach, right? But you’re probably thinking about its limitations. I’ll discuss those and introduce the MVC concept in the next TechTip!
Rafael Victória-Pereira has more than 20 years of IBM i experience as a programmer, analyst, and manager. Over that period, he has been an active voice in the IBM i community, encouraging and helping programmers transition to ILE and free-format RPG. Rafael has written more than 100 technical articles about topics ranging from interfaces (the topic for his first book, Flexible Input, Dazzling Output with IBM i) to modern RPG and SQL in his popular RPG Academy and SQL 101 series on mcpressonline.com and in his books Evolve Your RPG Coding and SQL for IBM i: A Database Modernization Guide. Rafael writes in an easy-to-read, practical style that is highly popular with his audience of IBM technology professionals.
Rafael is the Deputy IT Director - Infrastructures and Services at the Luis Simões Group in Portugal. His areas of expertise include programming in the IBM i native languages (RPG, CL, and DB2 SQL) and in "modern" programming languages, such as Java, C#, and Python, as well as project management and consultancy.
MC Press books written by Rafael Victória-Pereira available now on the MC Press Bookstore.
 |
||
 |
|
Evolve Your RPG Coding: Move from OPM to ILE...and Beyond Transition to modern RPG programming with this step-by-step guide through ILE and free-format RPG, SQL, and modernization techniques. List Price $79.95 Now On Sale
|
|
||
 |
|
Flexible Input, Dazzling Output with IBM i Uncover easier, more flexible ways to get data into your system, plus some methods for exporting and presenting the vital business data it contains. List Price $79.95
Now On Sale
|
|
||
 |
|
SQL for IBM i: A Database Modernization Guide Learn how to use SQL’s capabilities to modernize and enhance your IBM i database. List Price $79.95
Now On Sale
|
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online