Oracle Modernization Solutions

Table of Contents

Oracle Modernization Solutions

Credit

About the Authors

About the Co-Authors

Preface

What This Book Covers

What You Need for This Book

Who is This Book For

Conventions

Reader Feedback

Customer Support

Downloading the Example Code for the Book

Errata

Piracy

Questions

1. Introduction to Legacy Modernization

What We Won't Cover

Methodology and Estimation

The Modernization Marketplace and Why Modernize

Deep Dive on Approaches

Overview of the Modernization Options

Legacy Understanding

Application Portfolio Analysis (APA)

APA Macroanalysis

APA Microanalysis

Application Portfolio Management (APM)

Re-Architecturing

SOA Integration

Platform Migration

Automated Migration

Re-Hosting

Re-Hosting Based Modernization

Data Modernization

Legacy Adapters

Replacement

Business Value — What Really Matters?

Summary

2. Overview of SOA Integration

Integrating SOA into a Legacy Framework

Drivers for SOA Integration

Considerations for SOA Enablement

Where to Begin — a Word on Application Discovery

Assessment Process: Bringing it together

Summary

3. SOA Integration — Functional View, Implementation, and Architecture

SOA Integration: Functional View

SOA Integration: Technical View

User Interface

Legacy Service Bus (LSB) and Application Server

Legacy Services Engine (LSE)

LSE Components

Connectivity and Processing Engine

SQL Engine

Optional LSE Components

Orchestration

Security

Caching

LSE Development

LSE Implementation/Deployment

LSE Server Location

Legacy Artifacts

Metadata Repositories

Other Technical and Business Aspects

Scalability

Performance

Failover

Transaction Processing

Governance

Human Factors

Agility and Adaptability of Architecture

Host Support

SOA Integration

Implementation Options

Roll My Own

Buy a Bunch of Products and become an Integrator

One Pre-Integrated Stack

Implementation Approach

Phases in the Implementation Cycle

Understanding the Business Drivers

Products and Technologies Used in this Phase

Determine Business Processes to Expose

Products and Technologies Used in this Phase

Install/Configure the Software

Products and Technologies Used in this Phase

Expose Legacy Artifacts

Integrate Services into the application server

Products and Technologies Used in this Phase

Security and Governance

Products and Technologies Used in this Phase

Performance and Scalability

Products and Technologies Used in this Phase

Production Rollout

Products and Technologies Used in this Phase

Monitor Usage and Refine

Products and Technologies Used in this Phase

SOA Integration — Top Four Scenarios and Oracle Solutions

Oracle Products Included in the Solution

Oracle Products Not Included in the Solution

Scenario One — Enterprise Information Integration

Problem

Context

Forces

Solution

Scenario One Summary

Scenario Two — Web Enablement

Problem

Context

Forces

Solution

Scenario: Two Summary

Scenario Three — Report Off-Load Using Data Migration

Problem

Context

Forces

Solution

Scenario Three: Summary

Oracle BAM

Oracle BPEL

Oracle Data Integrator (ODI)

Oracle BI

Scenario Four: End-to-End SOA

Problem

Context

Forces

Solution

Scenario Four: Summary

Oracle WebCenter

Oracle BAM

Oracle ESB

Oracle OID and SSO

SOA Integration — Final Product Summary

IBM and Legacy SOA Integration

Summary

4. SOA Integraton — Scenario in Detail

Oracle Software Required

UML and Database Diagrams

Deployment Diagram

Use Case Diagram

Activity Diagram

Sequence Diagram

Data Model Diagram

Which Legacy Artifacts Should I Expose? — Using the Relativity Product Set

Application Layers — Understanding Relativity Terminology

Understanding an Artifact's Place in the Architecture

Vertical Slices

Horizontal Slices

Understanding Anomalies

Client Programs with Data Access

Calling Client Programs

Calling Transitional Programs

Impure Service Programs

Other Anomalies that Need Remedial Action

Data Validation Problem

The Problem of Transient or Temporary Data Queues

Finding the Service Functionality — Relativity SOA Analyzer Product

Starting from Screens

Looking for Special Program Constructs

The Case of Mixed Programs — Program 'Slicing'

Determining the Data Interface

Summary Legacy Artifact Discovery Using Relativity

Exposing the Legacy VSAM File Data Access

Connecting to Oracle Connect on Mainframe and Setting Connection Properties

Oracle Connect Data Source

Oracle Connect Adapter

Development Using Oracle JDeveloper

Prework

Application Modules

Presentation-Tier/User Interface — HTML Page

Legacy Web Service — VSAM Adapter Service

Two-Phase Commit

Oracle Database Persistence

Deploying to the Oracle Application Server

Configuring Oracle Application Server for the Legacy Adapter

Configuring Oracle Application Server Oracle Database Connection

Deploying to Oracle Application Server Using JDeveloper

Running the Example

Running the application

Summary

5. Overview of Re-architecturing

What is Re-Architecture?

Drivers and Considerations for Re-Architecture

Platform Agility

Human Factors to Consider in a Re-Architecture Project

How IBM Views Re-Architecture

IT/Technical Drivers and Considerations

Getting Off the Mainframe

Creating a Flexible, Adaptable, and Agile Architecture

Advanced Development Tools

Technical Considerations for a Re-Architecture Effort

Subject Matter Experts (SME)

Risk of Modernization

System Performance

Usability/Training

Re-Architecture versus Re-Host

Re-Architect Deep Dive

No Ripping and Replacing

Pros and Cons

Pros

Cons

Summary

6. Re-Architecture — Functional View, Implementation, and Architecture

Technical Advantages of Re-Architecture

Application Maintenance

Enterprise Information Integration (EII) and Enterprise Application Integration (EAI)

Architected for the Internet

Scalability

Availability

Greater Software Options

On Demand Reporting

Security

Overcoming Barriers to Change

Custom Integration Applications and Utilities

Custom Workflow

Custom ETL

Undisciplined Development

Decoupling the Application-Tiers

Presentation-Tier

Business Rules

Data Access

Workflow/Business Process Flow

Re-Architecture is Happening

Re-architecture — Functional View

A Technical Perspective of the Functional View

Other Components of the Functional Infrastructure

Re-architecture — Optional Software Components

Implementation Process: Common Attributes, Approach for Batch, and Online Processes

Top Three Re-Architecture Approaches

Three Iterative-Phased Approaches (IPA)

Data Migration

Business Processes and Application Logic

Move Standalone Application

Re-archtecture Modernization Life Cycle

Life-Cycle Caveats

Application Portfolio Analysis Completed

Life Cycle compared to Legacy SOA Integration Life Cycle

Big Bang and Parallel Production

The Human Element

Training

Re-Architecture Phases

Discovery/Recovery

Design Target Architecture

Install and Configure Oracle Software and Hardware

Model Target Application

Development Iterations

User Acceptance Testing (UAT)

Performance Scalability

Production Roll out

Running in Parallel

Unplug the Legacy Application

Using a Modernization Factory for Re-Architecture Implementation

Final Architecture — Common Oracle Products for Batch and Online

Hardware, Operating System, and IBM

Summary

7. Batch Systems Re-architecture Technical Deep Dive

Historical Reasons for Batch

Requirements of a Batch System

Top Five Batch Patterns

Multi Record Type Files — Pure Batch File Processing

Transaction Processing — Pure Autonomous Transactions

Administrative Batch — Backup, Archiving

Reporting — 'Green Bar', Exception Handling, Error Handling

Third-Party Interfaces — Internal and External Information Integration

Technical View

Optional Products

Job Scheduler and BPEL Compared

Implementation Process

Recovery/Discovery Approaches

Methodology

Best practices

Tooling

Re-Design/Re-Factoring Approaches

The Top-Down Approach

The Bottom-up Approach

The Hybrid Approach

Repositories

Relativity Repository

Scheduler Repository

OWB Repository

ADF/OFM Repositories

ADF

OFM SOA Suite for BPEL

OFM SOA Suite Business Rules

Re-Design/Re-Factoring for each Legacy Artifact Group

Green Bar Reports

Recovery/Discovery

Re-Design/ Re-Factor

Job Scheduler — UML Process Flow

Recovery/Discovery

Re-Design/ Re-Factor

Business Flows

Recovery/Discovery

Re-Design/ Re-Factor

COBOL Business Rules

Recovery/Discovery

Re-Design/ Re-Factor

COBOL Data Access Logic

Recovery/Discovery

Re-Design/Re-Factor

Database and database schema

Recovery/Discovery

Re-Design/Re-Factor

Target Generation

Oracle Implementation Tools and Source to Target Mapping

Summary of Tools and Frameworks

Source to Target Artifact Mapping

Final Oracle Batch Architecture

Scenario Description

New Batch Design Pattern(s) in Oracle

Summary

8. Online Systems Re-architecture Technical Deep Dive

History and Evolution of Online Systems

History of SOA and SaaS

Top Five Online Patterns

COBOL/CICS Applications Accessing VSAM and DB2 Databases

COBOL and CICS

DB2

VSAM

COBOL, IMS/DC, or IMS/TM Applications Accessing IMS/DB Database

IMS/DC and IMS/TM

IMS/DB (IMS Database)

COBOL, CICS, Assembler Applications Talking to Datacom or IDMS Database

Datacom

IDMS (Integrated Data Management System)

Assembler

PL/I and CICS Applications Making Use of VSAM and DB2 as Data Store

NATURAL and COBOL Applications Accessing an ADABAS Database

ADABAS (Adaptable DAta BAse System)

Natural

Technical View

Infrastructure Unique to Re-architecture

Single Management Tool

Single Security Model

Development Tools

Metadata Repositories

Enterprise Information Integration (EII)

Enterprise Application Integration (EAI)

Transactions

Infrastructure Not Required for Legacy SOA Integration

UI Navigation

Java EE Applications (EJB, Java, POJO, JSP, Servlets, JSF)

Relational Database

Grid Infrastructure (Grid Computing)

Backup and Recovery

Technologies Not Necessary for Legacy SOA Integration

Business Rules

Data and Business Services

Technical View Infrastructure Components

Capacity Planning Tools

Chargeback and Accounting Solutions such as CA (JARS)

Application Development Tools

Testing Tools

Reporting

High Speed Printing and Viewing

Data Archiving

Disaster Recovery

Tape Management

Human Error Recovery

Internationalization

Network Architecture/Protocol

Reliability, Availability, and Scalability

Implementation Process — Online Systems

Presentation/User Interface

Recovery/Discovery

Re-Design/ Re-Factor

UI Navigation

Recovery/Discovery

Re-Design/ Re-Factor

Oracle Implementation Tools and Source to Target Mapping

Summary of Tools and Frameworks

Development Life Cycle Support Tools

Source to Target Artifact Mapping

Final Oracle On-line Architecture

Scenario Details

New Online Design Pattern in Oracle

Presentation

UI Navigation

Application Server

Information and Business Services

Relational Database

Summary

9. Re-Architecture — Scenario in Detail

Oracle Software Required

UML and Screen Flow Diagrams

Source Application

Oracle Target Architecture

Application Mining Using Relativity

Mining the User Interface and Navigation-Tiers

Capturing the Legacy User Interface

Legacy User Interface Discovery

Screen Navigation Discovery

Forward Engineering

Mining Business Rules

Prerequisites

Identifying the Business Rules

Using Pattern Search

Searching Validation Rules

Using Backward Auto-Detection

Putting it Together

Forward Engineering into Oracle and Java EE

Producing the Target User Interface and Navigation

Running the Presentation-Tier Mock-up in Oracle Application Server

Deploying to the Oracle Application Server

Running the Application

Producing the Target Business Rules

Creating the Rules Repository and Dictionary

Creating Ruleset

Java Fact — Adding the Java Fact Class to the Rules Author

Adding the Rule

Calling the Business Rules from Java EE and BPEL

Automatic Business Rules Generation Using Java Code

Data Migration — A Quick, Easy, and a Cost-Effective Approach

Summary

10. Introduction to Re-Host based Modernization Using Tuxedo

Re-Hosting Based Modernization

Critical Success Factors in Mainframe Re-hosting

Preserving Application Logic and Data

Online Transaction Processing Environment

User Interface Migration

Workload Monitoring and Management

Batch Jobs

Files and Databases

Mainframe DB2

IMS

VSAM

Meeting Performance and Other QoS Requirements

Phased Migration and Mainframe Integration

SOA Enabling Re-hosted Applications

Further Re-architecture of Re-hosted Applications

Summary

11. Legacy Modernization — The Future

Green Computing

Standards Organizations

Object Modeling Group (OMG)

Record Type (COBOL)

WC3

Model Driven Architecture (MDA)

Challenges with the Traditional Approach

The MDA/MDM Approach

Cloud Computing

Amazon Elastic Compute Cloud

Grid Computing

Virtualization

Application Fabrics

Extreme Processing

Summary

A. Technology Glossary

Common Legacy Acronyms

Acronyms and Initials

PCI Security Standards

Index

Oracle Modernization Solutions

Tom Laszewski

Jason Williamson

Oracle Modernization Solutions

Copyright © 2008 Packt Publishing

All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.

Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, Packt Publishing, nor its dealers or distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book.

Packt Publishing has endeavored to provide trademark information about all the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.

First published: September 2008

Production Reference: 1090908

Published by Packt Publishing Ltd.

32 Lincoln Road

Olton

Birmingham, B27 6PA, UK.

ISBN 978-1-847194-64-0

www.packtpub.com

Cover Image by Vinayak Chittar (<vinayak.chittar@gmail.com>)

Credit

Authors

Tom Laszewski

Jason Williamson

Co-Authors

Mark Rakhmilevich

Michael Oara

Prakash Nauduri

Reviewers

Bob Mackowiak

Marc Connolly

Mike Ballyntine

Senior Acquisition Editor

Louay Fatoohi

Development Editor

Nikhil Bangera

Technical Editor

Bhupali Khule

Copy Editor

Sumathi Sridhar

Editorial Team Leader

Akshara Aware

Project Manager

Abhijeet Deobhakta

Project Coordinator

Lata Basantani

Indexer

Monica Ajmera

Proofreaders

Claire Lane

Camille Guy

Production Coordinator

Shantanu Zagade

Cover Work

Shantanu Zagade

About the Authors

Tom Laszewski has over 20 years experience in databases, middleware, software development, management, and building strong technical partnerships. He is currently the Director of the Oracle Modernization Solutions team. He established the initial business and technical relationships with Oracle's modernization Systems Integrators and tools partners (the Oracle Modernization Ecosystem). His main responsibility is successful completion of all modernization projects initiated through the partner ecosystem. Tom works on a daily basis with EDS and HP alliances, technical architectures and account managers to ensure the success of joint modernization projects. He is also responsible for Oracle Modernization customer assessments and workshops, modernization reference architectures and modernization best practices.

Before Oracle, Tom held technical and project management positions at Sybase and EDS. He has provided strategic and technical advice to several starts up companies in the Database, Blade, XML, and storage areas. Tom holds a Master of Science in Computer Information Systems from Boston University.

I would like to thank my wife for being my voice of reason and helping me to be a better person. For my two boys (Slade and Logan), who make life worth living. Thanks to Marc Connolly and Bob Mackowiak of Oracle, and Mike Ballantyne of EDS for their technical advice and ideas to make the book better. To my current and best manager I have ever worked for, Lance Knowlton, for always being supportive of my career aspirations. To my previous manager, John Gawkowski, for giving me the initial opportunity to work in the exciting world of legacy modernization. Lastly, to Jay Peretz and Prakash Balebail for giving my first big break at Oracle.

As Product Manager of Modernization Solutions at Oracle, Mr. Williamson is part of the team responsible for developing and implementing Oracle's Modernization strategy, cultivating a partner ecosystem for implementing solutions that modernize to Oracle products. Mr. Williamson works with product management within Oracle and its partners to drive integration, innovation and adoption for modernization to open-systems.

Mr. Williamson has over 14 years experience in the software industry and has extensive knowledge in legacy modernization techniques and commercial software development. Prior to joining Oracle, Mr. Williamson was Global Product Management for BluePhoenix Solutions, where he was responsible for providing technical leadership and new product development within the legacy modernization space. Mr. Williamson also worked for Relativity Technologies assisting the modernization efforts of companies around the world. He has also successfully founded and launched a commercial software company, leveraging emerging technologies as well as creating and managing strategic partnerships key to the company's success. In addition his work within the technology sector Mr. Williamson also served in the United State Marine Corps. He lives with his wife Susan and four small children.

Mr. Williamson has a BSc MIS from the Virginia Commonwealth University.

I would like to thank my wife for her love and support in all of my efforts. God could not have given me a better partner! Thanks very much to all of the Oracle folks who helped me out and our partners. Thanks to the best boss I've ever had, Lance Knowlton, for encouraging me to do great things.

About the Co-Authors

Mark Rakhmilevich is a Director of Product Management for Mainframe Re-hosting and Modernization at Oracle. In this role he focuses on bringing together Oracle and partner solutions that help customers cut costs and modernize legacy applications by migrating mainframe applications to Oracle Database and Oracle's Tuxedo and WebLogic middleware platforms and extending them to SOA and XTP with ESB, BPM, and Business Rules solutions. Mark works with Oracle engineering to address the needs of extreme transaction processing for mainframe-class applications, and to provide mainframe extension and integration capabilities as part of Oracle Fusion Middleware. He supports marketing and sales, delivers customer seminars on Mainframe Modernization, and works closely with customers in US, Europe, and Asia. Mark has worked with platform vendors, global and regional SIs, banking and insurance ISVs, and key technology vendors to provide a complete solution that helps mainframe customers cut loose from the mainframes and/or extend their mainframe applications to SOA.

Prior to Oracle, Mark held senior engineering, management, product management and marketing roles at IBM, Compuware, Tandem, Valicert, Tumbleweed, Chordiant, and BEA. He has extensive experience in system design, software and systems architecture, program and product management, marketing and business development. Mark worked extensively with banks, insurers, payment networks, healthcare, and government organizations focusing on enterprise middleware and SOA platforms, mainframe application modernization, Web services security, financial messaging, PKI, B2B integration, and BPM-driven CRM solutions for customer servicing and selling across multiple channels. His early work at IBM on mainframe operating systems architecture for VM and MVS led to a patent award for Logical Resource Partitioning of a Data Processing System — the basis of the IBM LPAR technology for partitioning mainframes and UNIX servers into multiple virtual machines. He also led development and product management for several versions of IBM mainframe UNIX OSes and their clustering capabilities.

Mark has an MS in Computer Science from State University of New York at Albany, and BS in Computer Science from Lehigh University where he was elected to Phi Beta Kappa.

Michael Oara is a Co-founder and Chief Technology Officer at Relativity Technology Inc.

Michael Oara has 28 years of experience in enterprise software and is an acknowledged expert in automation methodologies for modernization and transformation of legacy applications.

Michael has written multiple articles on the subject of legacy modernization and is the author of a number of patents. He is an active member of the Architecture Driven Modernization Task force of the Object Management Group.

Prior to Relativity Technologies, Michael was Director of Development for Seer Technologies, a pioneer in technology for building large-scale client/server systems and legacy modernization software. He has also worked for a number of banks in New York, where he has established an IT consulting company.

Michael has a MS in Mathematics from the University of Bucharest in 1979 and pursued graduate studies at the Courant Institute of New York University. As a teenager, he received the 1st prize in the Mathematical Olympiad in Romania.

Prakash Nauduri has over 16 years experience in databases, middleware, software development, and maintaining partnerships with SI's and ISVs. Prakash possess the unique ability to work on technologies from Java EE to Oracle Warehouse Builder, and from mainframe CICS adapters to Oracle BPEL Manager. His strong technical aptitude along with customer relationship skills has helped him become very successful in his roles throughout his career.

Prakash Nauduri is currently the Technical Director of the Oracle Modernization Solutions team. He played a major role in creating initial technical relationships with Oracle's modernization SIs and tools partners (the Oracle Modernization Ecosystem). He was instrumental in defining Modernization Framework as well as promoting Oracle technology stack as the foundation for target platforms. Prakash works with strategic SIs like EDS, HP and Unisys on a regular basis to bring fruition to customer projects/POCs. Prakash is also responsible for technical architectures and project leadership to ensure the success of joint partner and customer modernization projects. He is also responsible for Oracle Modernization Workshops, modernization reference architectures and modernization best practices.

At Oracle, Prakash formerly was a Principal Technologist in Oracle's Partner Technology Group (PTS). Since joining Oracle in 1998, Prakash has engaged with hundred's of ISVs in various industry verticals like healthcare, financial services, retail, public sector, education etc enabling partner solutions on latest Oracle technology providing wide range of services including Architecture Reviews, Performance Benchmarks, Training etc.

Prakash previously worked as a Sr. Systems Analyst at auto major Hero Group in India handling system design, development, implementation roles.

Prakash holds a Bachelor of Science from India.

Preface

Much has been written about legacy modernization in the past few years. Most of the books, analyst reports and white papers focus on why you should modernize and theorize at a high level regarding the different approaches and possible outcomes. This book intends to get to the heart of the matter very quickly and into the details of two very well known modernization approaches — SOA Integration and Re-architecturing.

The book is agnostic in terms of hardware and operating systems as most of these have proven to be able to handle the reliability, scalability, and performance of a mainframe system.

What This Book Covers

Chapter 1 gives an overview of the legacy modernization space. Here, we look at the different options for modernization and some of the drivers of modernization.

Chapter 2 Here, we will present an overview of modernization through SOA Integration. We will explore three strategies for SOA Enablement and when these options make sense.

Chapter 3 The focus of this chapter is to place SOA in the context of Modernization. SOA Legacy Modernizaton will bring you legacy IT infrastructure into the world of World Wide Web, Web 2.0, and all the other latest Internet-based IT architectures.

Within days, a legacy system can be accessed via a web browser. Your time-to-market using the Legacy SOA Integration approach is weeks, instead of months or years for some other modernization options.

Chapter 4 is an SOA Integration hands-on example using web enablement of mainframe COBOL/VSAM. We will use Java Server Pages (JSP), Java Database Connectivity (JDBC), the Oracle Legacy Adapter, Oracle Application Server, Java EE Connector API, and XA transaction processing to show a two-phase commit across an Oracle database and VSAM on the mainframe.

Chapter 5 takes a deep dive into what re-architecture is, how to approach re-architecture and strategies for execution. This will enable you to gain an understanding of this modernization option and prepare you for hands-on examples in the next chapters.

Chapter 6 Re-architecture is a multidimensional set of technologies and business drivers, similar to a Rubik's cube. In this chapter, we will simplify the target architecture variable, by making a move to Oracle. Even as we do this, we will find a wide selection of Oracle products and technologies, which we will narrow down for you. We end the chapter with a mapping of re-architecture business drivers to Oracle products, and finally a bit about modernization re-architecture and IBM.

Chapter 7 There are probably some legacy systems out there without batch, but it is most likely that batch processing is a key component of your mainframe legacy system. Business information processing in today's world is workload automation centered, event focused, and business-centric. However, we learn in this chapter that there are many reasons — both technical and business — why nightly batch jobs will be with us for some time. New technologies such as BPEL could potentially replace classic mainframe job scheduling software in the distant future.

Chapter 8 The online technical architecture has the potential to be much more complex than the batch open system architecture because the possible combination of products and technologies are endless. The combinations of target products and technologies include everything from cell phone access, to ERP application integration, to business intelligence, and transactions across multiple databases from different vendors. The same can be said of the source legacy system: multitudes of end user devices, languages, transactions processors, and databases. What we will immediately do is simplify the target architecture to three layers: presentation, transaction, business logic processing and database.

Chapter 9 The purpose of the scenario is to reinforce that re-architecture is not rip and replace, but leveraging existing mainframe artifacts and forward engineering these artifacts into an Oracle/Java EE architecture using Relativity, and Oracle tools and products. The focus in this example will be on Relativity tools because the most complex and important aspects of re-architecture are discovery, recovery, capture of legacy artifacts, and creating a source model. The source application is a classic mainframe COBOL/CICS/VSAM/DB2 order entry system.

Chapter 10 Re-host based modernization approach is focused on migrating the application off the mainframe to a compatible software stack on an open-systems platform, preserving the language and middleware services on which the application has been built. It preserves legacy investment by relying on a mainframe-compatible software stack to minimize changes in the core application, and preserve the application's business logic intact, while running it on an open-system OS using more flexible and less expensive system infrastructure. It keeps open the customer's options for SOA enablement and re-architecture, by using an SOA-ready middleware stack to support Web services and ESB interfaces for re-hosted components.

Chapter 11 will let us examine trends in computing, where the modern data center is going and how this affects modernization choices today. We will see where the industry is trending with respect to tools, software and infrastructure. We'll examine concepts such as cloud computing, model driven modernization and green computing.

Appendix A gives an overview of the technological terms and legacy acronyms used throughout the book.

What You Need for This Book

Application Server 10g Release 3—Version 10.1.3.3

http://www.oracle.com/technology/software/products/ ias/index.html

Application Server Adapters for Legacy Applications with Oracle Connect Mainframe component, Oracle Studio for Legacy Adapters, Legacy adapters for CICS, IMS/TM, IMS/DB, and VSAM

http://www.oracle.com/technology/software/products/ias/htdocs/101310.html

Oracle Business Process Analysis Suite — Version 10.1.3.4

http://www.oracle.com/technology/software/products/ bpa/index.html

Oracle JDeveloper — Version 10.1.3.3

http://www.oracle.com/technology/software/products/ jdev/index.html

Oracle SQL Developer — Version 1.5.1

http://www.oracle.com/technology/software/products/ sql/index.html

Who is This Book For

Legacy system architects, project managers, program managers, developers, database architects and Cx0 technology decision makers tasked with modernization will all find this book useful.

The book assumes some knowledge of mainframes, J2EE, SOA, and Oracle technologies. The reader should have some background in programming and database design.

Conventions

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text are shown as follows: This is not sufficient, as ERROR-CODE value 15 does not tell me anything about the real expectation about the shipping date.

A block of code will be set as follows:

MOVE INPUT-DATE TO DATE1

MOVE CURRENT-DATE TO DATE2

PERFORM DATE-INTERVAL-COMPUTATION

IF DATE-INTERVAL < 3 THEN

MOVE 15 TO ERROR-CODE

When we wish to draw your attention to a particular part of a code block, the relevant lines or items will be made bold:

button onclick="window.location=

'ORDSET1.ORDMAP1.html' value=Update style=background-

color:while;color:blue;border:1px solid black">

button onclick="window.location=

'MENSET1.MENMAP1.html' value=Return style=background-

color:while;color:blue;border:1px solid black">

New terms and important words are introduced in a bold-type font. Words that you see on the screen, in menus or dialog boxes for example, appear in our text like this: So we will name it the inventory_by_state ruleset .

Note

Important notes appear in a box like this.

Tip

Tips and tricks appear like this.

Reader Feedback

Feedback from our readers is always welcome. Let us know what you think about this book, what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.

To send us general feedback, simply drop an email to <feedback@packtpub.com>, making sure to mention the book title in the subject of your message.

If there is a book that you need and would like to see us publish, please send us a note in the SUGGEST A TITLE form on www.packtpub.com or email .

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.

Customer Support

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.

Downloading the Example Code for the Book

Visit http://www.packtpub.com/files/code/4640_Code.zip to directly download the example code.

The downloadable files contain instructions on how to use them.

Errata

Although we have taken every care to ensure the accuracy of our contents, mistakes do happen. If you find a mistake in one of our books — maybe a mistake in text or code — we would be grateful if you would report this to us. By doing this you can save other readers from frustration, and help to improve subsequent versions of this book. If you find any errata, report them by visiting http://www.packtpub.com/support, selecting your book, clicking on the let us know link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata added to the list of existing errata. The existing errata can be viewed by selecting your title from http://www.packtpub.com/support.

Piracy

Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide the location address or website name immediately so we can pursue a remedy.

Please contact us at <copyright@packtpub.com> with a link to the suspected pirated material.

We appreciate your help in protecting our authors, and our ability to bring you valuable content.

Questions

You can contact us at <questions@packtpub.com> if you are having a problem with some aspect of the book, and we will do our best to address it.

Chapter 1. Introduction to Legacy Modernization

A lot has been written on legacy modernization in the past few years. Most of the books, analyst reports, and white papers discuss at a high level why one should modernize and theorize, and the different approaches to, and possible outcomes of modernization. Instead of going into modernization theory, we will quickly dive into the details of two very well known modernization approaches: SOA Enablement and Re-architect. There will be a specific focus on modernization to Open Systems taking advantage of the Oracle technology stack, which can provide mainframe quality of service while delivering the agility of a modern architecture simultaneously. We will uncover a specific set of tools and show the process from end-to-end.

We will take an agnostic perspective of hardware and operating systems as most of these have proven to be capable of handling the reliability, scalability, and performance of a mainframe system. In fact, at the time of this writing, the current records for transactions per second have been delivered with Oracle on Intel-based servers.

For most organizations, the ideal solution would be to re-architect everything since re-architecting yields the most modernized environment — the environment that makes the best use of modern technology, is the most agile when it comes to change, and relies no longer on legacy skill sets.

Although such a big bang scenario is technically feasible, in reality, it is difficult and risky for any organization to accomplish this in a single re-architecting step — no matter how desirable the outcome. Most organizations would view such a big bang approach as putting their entire organization at risk. As a result, they take several intermediate steps. The following chapters show several options that could be considered in order to break down the modernization problem into byte-sized chunks — all the while delivering the final goal of achieving a process-driven SOA architecture based on J2EE. Additionally, these intermediate steps of SOA enablement will yield measurable ROI and benefit.

What We Won't Cover

Before we begin our path to modernization, let's take some time to talk about the things that we will not cover in this book. The main focus of this book is a practical application of how to modernize a legacy application using two specific techniques. We won't cover topics such as marketplace, methodologies, and estimation techniques.

Methodology and Estimation

Countless books have been written on application development methodology. Every system integrator/programming shop within a large company or technology group has a general development methodology, be it waterfall, agile, or eXtreme programming. The techniques in this book can fit any given protocol.

Estimation is a bit different and varies from system to system and with the choice of the modernization option. It can depend upon factors such as target language, tools, and the level of automation you are employing. If someone tries to sell you a solution based on the line of code or function point counts and complexity, you can pretty much throw that out of the window. Function point analysis is a great tool for understanding the complexity of the source code and can drive estimation, but there is certainly no general formula for how long a modernization will take, or how much it will cost. Another book can be written on this subject.

The Modernization Marketplace and Why Modernize

If you are reading this book, then we will assume that application modernization is a necessity for you. You are looking at how to modernize rather than why modernize. Further, much market research has been done on this subject. Countless presentations, white papers, and events are actively being conducted on this subject.

The largest and best of breed systems integrators of the world have practices built solely around the modernization market. There are several reasons that drive a legacy modernization project. High costs, lack of agility, an aging technology workforce are just some of the reasons for modernization. Sometimes the motivation to modernize is driven from the business, at other times it is pure technology play. The reasons are many, and the final decision to embark on this effort depends on each organization. Again, much material is being developed on this subject and is not the topic of this book.

The Oracle Modernization Alliance (OMA) is an effort by Oracle to bring together the best of breed partners and products to enable modernization to open systems. This is truly an emerging field both for companies considering modernization, and for the