Welcome!

Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Modernizing Legacy Systems, part 1

Why modernize?

When I started working as a WebLogic consultant a couple of years ago, I systematically avoided projects with legacy systems integration. At the time, I was interested only in "pure" J2EE projects. The technology was very new and there was more than enough to do in order to help organizations adopt the J2EE/WebLogic platform as a viable solution for their e-business initiatives.

Today, J2EE has matured and the BEA WebLogic Platform has become an essential part of mission-critical applications in large organizations. But a new trend is also emerging: the need to integrate WebLogic with legacy systems in order to provide a unified, business process-centric IT environment. Moreover, organizations realize that in order to streamline their processes and provide value-added services to their customers, some critical business processes have to be "ported" or "re-hosted" from the legacy system to the WebLogic platform. This is what I call "modernizing" legacy systems. This series will discuss why the process of modernizing legacy systems is becoming an increasingly important business-driven requirement for organizations. I will present a step-by-step, incremental approach in order to minimize risks during the modernization effort. This article is an overview of the entire process and looks at why the modernization effort should be initiated. In part 2, I'll concentrate on integration and "re-hosting" patterns as well as building a common business domain model between the legacy system and the WebLogic platform. In part 3, I'll concentrate on the runtime and workflow aspects of the "modernized" platform.

Defining Modernization
Let's start by defining "modernizing" legacy systems and why such an effort should be initiated. First, what is a legacy system? I'm certain that the definition I'm going to give will make most Cobol programmers very unhappy! My perception of a legacy system is a software platform developed in a procedural language such as Cobol or RPG, hosted on a mainframe or an IBM iSeries. In most cases the maintenance costs of the system tend to increase over time while the available technical expertise around it decreases. Another way of defining a legacy system is the moment where the system cannot service new business requirements because of limitations such as technology and would therefore require modifications far beyond maintenance. However, most organizations have invested enormous amounts of intellectual property and money in these systems and expect to capitalize their return on investment, not counting that most of their mission-critical business processes run on them. So what is modernization? Modernization is the process of modifying a legacy system beyond maintenance in order to provide new added-value services such as enhanced reliability, flexibility, and security.

It is also worth mentioning here what modernization is not. It's not "revamping" or "screen-scraping," which consists mainly of replacing "green-screen" terminals with new presentation interfaces such as Web-enabled thin clients. Therefore, revamping affects presentation only. Modernization is also very different from "replacement," which is an effort to rebuild the system from scratch by a total code-rewrite process. Replacement may be an extremely risky process with a high chance of failure. In our case, the process of modernizing a legacy system involves the process of gradually "re-hosting" specific business processes initially written in Cobol to the BEA WebLogic Platform as J2EE components. The process is incremental and continuous, thus minimizing risks. Reasons why such an initiative could be desirable are:

  • Cobol is a procedural language ill-suited for today's enterprise-scale application developments. Therefore, the maintenance costs of legacy systems surpass the modernization costs.
  • Modernizing an existing legacy system is less costly and risky than completely replacing it because the process is less disruptive. Besides, organizations can continue to leverage their existing infrastructure during the effort.
  • The WebLogic Platform provides the essential building blocks for delivering component-based and service-oriented architectures, essential to today's e-business initiatives.
  • Tools such as BEA WebLogic Workshop enhance productivity far beyond the Cobol development environments.
  • The Java programming language and the J2EE platform, because of their component-based approach, promote software reuse and facilitate system maintenance in the medium to long term.
  • BEA WebLogic Server provides additional services such as scalability, security, and availability that would be hard to implement if created from scratch.
Modernization can take two approaches: in a black-box approach, we are not interested in understanding the inner workings of the legacy system. We simply use interfaces to the system and provide component wrappers to it. In a white-box approach, the inner workings of the legacy code are studied. For example, Cobol modules are examined in order to grasp the underlying business processes and rewrite them as EJB components. Often, the white-box approach might be required to provide true added value and move beyond enterprise application integration.

The Step-by-Step Approach
A modernization effort can span several years. During that time many factors, such as technology, can dramatically change. It is therefore essential to take a step-by-step, incremental approach towards modernizing legacy systems in order to minimize the risks of failure. In my experience, mostly in modernizing banking systems, I have found the following steps useful:

  • Build the business case
  • Understand the legacy system
  • Understand the value-added services provided by the WebLogic platform and define the target architecture
  • Prioritize use cases for porting business processes
  • Integrate the legacy system with the WebLogic platform
  • Port the business processes
Building the business case basically states the rationale and the reason why a modernization effort should be initiated over a less drastic change such as a maintenance effort. For example, for a back-office banking package, the business case could state that B2B business processes require the implementation of a WebLogic Server "front end" to the legacy system and some of the business processes such as portfolio management and straight-through processing should be re-hosted by the WebLogic platform. Basically it emphasizes that the return on investment for modernization will be higher than simply maintaining the legacy system.

Once the business case has been approved, the next step is to understand the legacy system's architecture. In our banking example, the legacy system consists of a two-tier architecture using "dumb" terminals for the presentation layer and modules written in Cobol hosted on an AS/400 encapsulating the business logic. At this point, after studying the system using a white-box approach, we might discover that some modifications are required in order to provide an integration path to the WebLogic Platform. For example, we might discover that some Cobol modules contain a mix of presentation logic and business logic. We could therefore "refactor" those modules as service programs (a service program is a special kind of Cobol module that can be easily encapsulated and called from Java code) in order to separate business logic from presentation logic. An important point to emphasize is that understanding the legacy system requires the knowledge and help of Cobol programmers and they should be included as stakeholders early in the process. Finally, this step results in a good understanding of the legacy system's architecture as well as possible ways of integrating the legacy system with the BEA WebLogic platform.

Leveraging value-added services provided by the WebLogic platform is usually easier because now we are in the realm of J2EE programming. The objective here is to define a component-based, service-oriented architecture for providing functional and nonfunctional services such as security and availability. However, the major task at this stage of the modernization process is to devise an architectural mapping between the two-tier legacy system and the WebLogic platform. For example, as illustrated in Figure 1, we might decide to build a five-tier architecture with the following tiers:

  • Client
  • Presentation
  • Business logic
  • Integration
  • Resource

 

The mapping process will then have to specify which modules of the legacy system will be mapped or "migrated" to specific tiers of the BEA WebLogic Platform as presentation-tier or business-tier components. This architectural transformation is actually a very critical step in the entire process. It has to achieve a certain number of goals, or qualities, in order to provide true added value to the modernization effort. The target architecture based on the WebLogic Platform should therefore have the following characteristics:

  • Service-oriented architecture
  • Component-based design
  • Layered architecture
A service-oriented architecture publishes discrete business functions and processes through discoverable interfaces. The processes can then be leveraged by other WebLogic applications or services as fundamental building blocks for higher-level services. Componentization and component-based design bring structure to the unstructured legacy Cobol code. Basically, it maps coarse-grained business processes as WebLogic hosted session or entity beans. The achieved added value is a higher level of code reuse as well as an interface-based "plug and play" architecture. Finally, the modernized architecture should be designed in layers where services are implemented on top of components that are in turn implemented using a common business domain class hierarchy.

The next step is to prioritize business processes - gathering a certain number of use cases identified in the legacy system by the project stakeholders as those with the most added value. They should become our initial candidates for the modernization process. In our banking example, the project stakeholders might decide that straight through processing provides enormous added value. They could therefore decide that the order-processing and account-management Cobol modules should be the first ones to be ported to the WebLogic platform as EJB components. At this point we have a development plan and we feel confident that we have identified the most valuable business processes of the legacy system to consider.

The next step is integration, which provides a way of having the legacy system and the modernized WebLogic platform "coexist" in a single, unified business platform. Once again, our objective is to take an incremental approach in order to minimize risks. We cannot afford to do a single "big-bang" replacement of the entire legacy system. Therefore, integration provides a pragmatic, intermediary step. During integration, we usually build adapters in order to "hide" the legacy system. For example we could use coarse-grained component wrappers implemented as EJBs in order to encapsulate the legacy system. Basically, the integration step provides the bridge between the legacy world and the WebLogic Platform. Integration should be transparent so that at any point in the effort, from an external perspective, the modernized WebLogic and legacy systems should provide a unified set of services, independent of their location. From a technical perspective, integration can be done by using different technologies such as JMS, SOAP/Web services, or JCA.

Finally, the last and longest step of the entire process, porting the business processes identified by project stakeholders and implementing them as EJB components, can be initiated. This componentization is a continuing effort and can be separated into two main aspects: code and data migration. The process of code migration consists of "re-creating" some equivalent functionality available in a legacy Cobol module and replacing it with its modernized EJB counterpart. If a whiteboard approach is used, the actual legacy code could be analyzed and the algorithm implemented inside it rewritten in Java as an EJB. In a blackboard approach, only the module's inputs and outputs are analyzed, in other words its functional interface, and a corresponding EJB with an equivalent interface is developed in Java. Both approaches are viable. For example, in a legacy banking system the whiteboard approach might be the only way to modernize an undocumented taxation module. Ever heard of the sentence "the code is the document"? In both cases the overall behavior of the legacy and modernized platforms should remain the same.

Data migration can be a bit trickier. Basically, data migration consists of modernizing the legacy database schema, perhaps because it has become unmanageable over time. For example, the original schema might be implemented using a DB2 database hosted on an AS400. It might be interesting for the modernized system to redesign the schema using entity beans and leveraging WebLogic's container-managed persistence services in a database-independent manner. Data migration can be done in two ways: data migration during code migration and data migration after code migration. Personally, for the sake of keeping a consistent behavior between the modernized WebLogic Platform and the legacy system, I recommend using a data-migration-after-code-migration approach. This will help keep the modernized and legacy systems consistent and in sync without requiring techniques such as data replication. If this approach is taken, then as mentioned under "integration," component wrappers should be used to encapsulate the legacy data.

Conclusion
This article introduced a step-by-step approach to modernizing legacy systems with the BEA WebLogic Platform. Modernization is the process of incrementally and continuously replacing specific modules of a legacy system developed in a procedural language such as Cobol or RPG by EJB components. The objectives of such an effort are to either provide additional business services going beyond maintenance of the legacy system or to leverage the services of the WebLogic Platform such as security, availability, and transaction processing. Modernization is a pragmatic approach in order to minimize risks and often has higher returns on investment than a complete replacement of the legacy system, which is also extremely risky. I have also mentioned some of the qualities, such as a service-oriented architecture and component - based platform, that the modernized architecture should exhibit in order to maximize reuse as well as return on investment.

This article provided a high-level overview of the entire process. In upcoming articles, I will delve into the details and show how to use specific tools such as BEA WebLogic Workshop to implement the different phases of the process.

More Stories By Anwar Ludin

Anwar Ludin specializes in service-oriented architectures for the financial sector. He currently works as an independent consultant for
financial institutions in Switzerland, where he helps design J2EE architectures based on the WebLogic platform.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@ThingsExpo Stories
Leading companies, from the Global Fortune 500 to the smallest companies, are adopting hybrid cloud as the path to business advantage. Hybrid cloud depends on cloud services and on-premises infrastructure working in unison. Successful implementations require new levels of data mobility, enabled by an automated and seamless flow across on-premises and cloud resources. In his general session at 21st Cloud Expo, Greg Tevis, an IBM Storage Software Technical Strategist and Customer Solution Architec...
Nordstrom is transforming the way that they do business and the cloud is the key to enabling speed and hyper personalized customer experiences. In his session at 21st Cloud Expo, Ken Schow, VP of Engineering at Nordstrom, discussed some of the key learnings and common pitfalls of large enterprises moving to the cloud. This includes strategies around choosing a cloud provider(s), architecture, and lessons learned. In addition, he covered some of the best practices for structured team migration an...
Product connectivity goes hand and hand these days with increased use of personal data. New IoT devices are becoming more personalized than ever before. In his session at 22nd Cloud Expo | DXWorld Expo, Nicolas Fierro, CEO of MIMIR Blockchain Solutions, will discuss how in order to protect your data and privacy, IoT applications need to embrace Blockchain technology for a new level of product security never before seen - or needed.
Imagine if you will, a retail floor so densely packed with sensors that they can pick up the movements of insects scurrying across a store aisle. Or a component of a piece of factory equipment so well-instrumented that its digital twin provides resolution down to the micrometer.
In his keynote at 18th Cloud Expo, Andrew Keys, Co-Founder of ConsenSys Enterprise, provided an overview of the evolution of the Internet and the Database and the future of their combination – the Blockchain. Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settle...
BnkToTheFuture.com is the largest online investment platform for investing in FinTech, Bitcoin and Blockchain companies. We believe the future of finance looks very different from the past and we aim to invest and provide trading opportunities for qualifying investors that want to build a portfolio in the sector in compliance with international financial regulations.
No hype cycles or predictions of a gazillion things here. IoT is here. You get it. You know your business and have great ideas for a business transformation strategy. What comes next? Time to make it happen. In his session at @ThingsExpo, Jay Mason, an Associate Partner of Analytics, IoT & Cybersecurity at M&S Consulting, presented a step-by-step plan to develop your technology implementation strategy. He also discussed the evaluation of communication standards and IoT messaging protocols, data...
Coca-Cola’s Google powered digital signage system lays the groundwork for a more valuable connection between Coke and its customers. Digital signs pair software with high-resolution displays so that a message can be changed instantly based on what the operator wants to communicate or sell. In their Day 3 Keynote at 21st Cloud Expo, Greg Chambers, Global Group Director, Digital Innovation, Coca-Cola, and Vidya Nagarajan, a Senior Product Manager at Google, discussed how from store operations and ...
In his session at 21st Cloud Expo, Raju Shreewastava, founder of Big Data Trunk, provided a fun and simple way to introduce Machine Leaning to anyone and everyone. He solved a machine learning problem and demonstrated an easy way to be able to do machine learning without even coding. Raju Shreewastava is the founder of Big Data Trunk (www.BigDataTrunk.com), a Big Data Training and consulting firm with offices in the United States. He previously led the data warehouse/business intelligence and B...
"IBM is really all in on blockchain. We take a look at sort of the history of blockchain ledger technologies. It started out with bitcoin, Ethereum, and IBM evaluated these particular blockchain technologies and found they were anonymous and permissionless and that many companies were looking for permissioned blockchain," stated René Bostic, Technical VP of the IBM Cloud Unit in North America, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Conventi...
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, whic...
When shopping for a new data processing platform for IoT solutions, many development teams want to be able to test-drive options before making a choice. Yet when evaluating an IoT solution, it’s simply not feasible to do so at scale with physical devices. Building a sensor simulator is the next best choice; however, generating a realistic simulation at very high TPS with ease of configurability is a formidable challenge. When dealing with multiple application or transport protocols, you would be...
Smart cities have the potential to change our lives at so many levels for citizens: less pollution, reduced parking obstacles, better health, education and more energy savings. Real-time data streaming and the Internet of Things (IoT) possess the power to turn this vision into a reality. However, most organizations today are building their data infrastructure to focus solely on addressing immediate business needs vs. a platform capable of quickly adapting emerging technologies to address future ...
We are given a desktop platform with Java 8 or Java 9 installed and seek to find a way to deploy high-performance Java applications that use Java 3D and/or Jogl without having to run an installer. We are subject to the constraint that the applications be signed and deployed so that they can be run in a trusted environment (i.e., outside of the sandbox). Further, we seek to do this in a way that does not depend on bundling a JRE with our applications, as this makes downloads and installations rat...
Widespread fragmentation is stalling the growth of the IIoT and making it difficult for partners to work together. The number of software platforms, apps, hardware and connectivity standards is creating paralysis among businesses that are afraid of being locked into a solution. EdgeX Foundry is unifying the community around a common IoT edge framework and an ecosystem of interoperable components.
DX World EXPO, LLC, a Lighthouse Point, Florida-based startup trade show producer and the creator of "DXWorldEXPO® - Digital Transformation Conference & Expo" has announced its executive management team. The team is headed by Levent Selamoglu, who has been named CEO. "Now is the time for a truly global DX event, to bring together the leading minds from the technology world in a conversation about Digital Transformation," he said in making the announcement.
In this strange new world where more and more power is drawn from business technology, companies are effectively straddling two paths on the road to innovation and transformation into digital enterprises. The first path is the heritage trail – with “legacy” technology forming the background. Here, extant technologies are transformed by core IT teams to provide more API-driven approaches. Legacy systems can restrict companies that are transitioning into digital enterprises. To truly become a lead...
Digital Transformation (DX) is not a "one-size-fits all" strategy. Each organization needs to develop its own unique, long-term DX plan. It must do so by realizing that we now live in a data-driven age, and that technologies such as Cloud Computing, Big Data, the IoT, Cognitive Computing, and Blockchain are only tools. In her general session at 21st Cloud Expo, Rebecca Wanta explained how the strategy must focus on DX and include a commitment from top management to create great IT jobs, monitor ...
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
The IoT Will Grow: In what might be the most obvious prediction of the decade, the IoT will continue to expand next year, with more and more devices coming online every single day. What isn’t so obvious about this prediction: where that growth will occur. The retail, healthcare, and industrial/supply chain industries will likely see the greatest growth. Forrester Research has predicted the IoT will become “the backbone” of customer value as it continues to grow. It is no surprise that retail is ...