You are currently on IBM Systems Media’s archival website. Click here to view our new website.


Benefit From Non-Disruptive Modernization With IBM API Connect

IBM API Connect

This is the third article in a series about modernization of enterprise applications. The first article, Modernize Legacy Systems to Enable Full Potential, gives an overview of legacy systems, modernization tactics, benefits, strategies, risk and cost as well as challenges and areas of focus like updating the user interface and data modernization. The second article, Easily Modernize Applications to Stay Competitive, explores specific suggestions regarding the user interface, data, function, process and middleware modernization.

Modernization is about making change for a purpose. It could be catching up to changes in technology—like embracing database systems when you currently have indexed files—or using a mobile device for display when you have a desktop PC running a 3270 emulator. These can be big changes. However, change can also be smaller in the form of additional functionality that’s delivered within a new release of COBOL or CICS. These changes are perhaps less consequential on a large scale but nevertheless have to be discovered, planned and implemented.

Another important idea with modernization relates to timing (i.e., ongoing versus occasional, one-time changes). Ongoing change is achieved when organizations integrate modernization along with routine application fixes and enhancements. Occasional, one-time changes occur when after years of neglect, applications change to catch up to IT innovations that have “changed the game.”

How Is Non-Disruptive Different?

When you have a stable application that delivers business value, it can be modernized without disruption. All modernization needs can’t be met in a non-disruptive way, but a surprising variety of changes are nevertheless possible. When you achieve non-disruptive change, you experience advantages that include parallelism, coexistence and low risk. Parallelism happens when the team implementing modernization works parallel to or independent of the application development and maintenance team.

Coexistence occurs when the legacy function runs at the same time as the modernized version of the application functionality. The functionality, in its old and new form, operates using the same base. Business and technical risk is low with non-disruptive modernization because few, if any, changes are required to the running application. By comparison, replacing or upgrading the application, provides a much greater threat of disturbance to day-to-day operations. This low-risk approach is a selling feature for a number of non-disruptive integration software products. How is this achieved? IBM API Connect is a useful product model to examine as it is a API Management leader according to both Forrester and Gartner research.

Non-Disruptive Modernization

IBM API Connect is a software product and a medium for application modernization. It’s also is a kind of integration middleware used to create data applications that are sometimes called microservices. Like other applications, these micro APIs need to be developed and tested, but there’s more to it than that. After installation, they also have to be sized for their environment and managed throughout their lifecycle.

An important feature of IBM API Connect is the automated creation of APIs working with enterprise back ends like WebSphere, IBM Integration Bus, IBM z and other systems and assets. IT departments, as well as lines of business, can make available enterprise applications and data in their systems of record; unbridling the creativity of developers without surrendering security and governance. So how is this done? What components are used?

Modernization Components

IBM API Connect has components that support the creation of API programs. In order to use API Connect, you need to deploy the Cloud Management Console, Management Server and at least one API Gateway. Use of the Developer Portal is a great asset for new APIs as is the API Designer.

Joseph Gulla is the general manager and IT leader of Alazar Press, a publisher of award-winning children’s books. Joe is a frequent contributor to IBM Destination z (the community where all things mainframe converge) and writes weekly for the IT Trendz blog where he explores a wide range of topics that interconnect with IBM Z.

Like what you just read? To receive technical tips and articles directly in your inbox twice per month, sign up for the EXTRA e-newsletter here.



2019 Solutions Edition

A Comprehensive Online Buyer's Guide to Solutions, Services and Education.


3 Points to Consider When Modernizing IBM Z


Making Sense of APIs and the API Economy

IBM Systems Magazine Subscribe Box Read Now Link Subscribe Now Link iPad App Google Play Store
Mainframe News Sign Up Today! Past News Letters