You are previewing Oracle Modernization Solutions.
O'Reilly logo
Oracle Modernization Solutions

Book Description

A practical guide to planning and implementing SOA Integration and Re-architecting to an Oracle platform

  • Complete, practical guide to legacy modernization using SOA Integration and Re-architecture

  • Understand when and why to choose the non-invasive SOA Integration approach to reuse and integrate legacy components quickly and safely

  • Understand when and why to choose Re-architecture to reverse engineer legacy components and preserve business knowledge in a modern open and extensible architecture

  • Modernize to a process-driven SOA architecture based on Java EE, Oracle Database, and Fusion Middleware

  • Covers real-life scenarios with detailed hands-on examples

In Detail

Much has been written about legacy modernization in the past few years. Most of the books, analysts' 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 provides a detailed guide to how to implement two well known mainframe modernization approaches—SOA Enablement and Re-architecture.

SOA Integration is a non-invasive approach and allows legacy components to be used as part of an SOA infrastructure quickly and without risk and is often the first step in the larger modernization process. Re-architecture focuses on reverse engineering legacy applications to preserve business knowledge then forward them to modern architectures that take advantage of open and extensible standards.

In this book you will learn how to quickly and easily expose a mainframe VSAM data store in an Oracle-based Java EE application. You will also learn how to leverage your mainframe application code to create a new Oracle/Java EE SOA-based application. The book is agnostic in terms of hardware and operating system as most of these have proven to be able to handle the reliability, scalability, and performance of a mainframe system.

After reading this book, you will feel much more comfortable that mainframe modernization is possible and can made less risky by following the recommendations and approaches used in the book.

Table of Contents

  1. Oracle Modernization Solutions
    1. Table of Contents
    2. Oracle Modernization Solutions
    3. Credit
    4. About the Authors
    5. About the Co-Authors
    6. Preface
      1. What This Book Covers
      2. What You Need for This Book
      3. Who is This Book For
      4. Conventions
      5. Reader Feedback
      6. Customer Support
        1. Downloading the Example Code for the Book
        2. Errata
        3. Piracy
        4. Questions
    7. 1. Introduction to Legacy Modernization
      1. What We Won't Cover
        1. Methodology and Estimation
        2. The Modernization Marketplace and Why Modernize
        3. Deep Dive on Approaches
      2. Overview of the Modernization Options
        1. Legacy Understanding
          1. Application Portfolio Analysis (APA)
            1. APA Macroanalysis
            2. APA Microanalysis
            3. Application Portfolio Management (APM)
        2. Re-Architecturing
        3. SOA Integration
        4. Platform Migration
          1. Automated Migration
          2. Re-Hosting
            1. Re-Hosting Based Modernization
        5. Data Modernization
          1. Legacy Adapters
        6. Replacement
      3. Business Value — What Really Matters?
      4. Summary
    8. 2. Overview of SOA Integration
      1. Integrating SOA into a Legacy Framework
      2. Drivers for SOA Integration
        1. Considerations for SOA Enablement
      3. Where to Begin — a Word on Application Discovery
        1. Assessment Process: Bringing it together
        2. Summary
    9. 3. SOA Integration — Functional View, Implementation, and Architecture
      1. SOA Integration: Functional View
      2. SOA Integration: Technical View
        1. User Interface
        2. Legacy Service Bus (LSB) and Application Server
        3. Legacy Services Engine (LSE)
          1. LSE Components
            1. Connectivity and Processing Engine
              1. SQL Engine
          2. Optional LSE Components
            1. Orchestration
            2. Security
            3. Caching
          3. LSE Development
          4. LSE Implementation/Deployment
            1. LSE Server Location
            2. Legacy Artifacts
            3. Metadata Repositories
        4. Other Technical and Business Aspects
          1. Scalability
          2. Performance
          3. Failover
          4. Transaction Processing
          5. Governance
          6. Human Factors
          7. Agility and Adaptability of Architecture
          8. Host Support
      3. SOA Integration
        1. Implementation Options
          1. Roll My Own
          2. Buy a Bunch of Products and become an Integrator
          3. One Pre-Integrated Stack
          4. Implementation Approach
        2. Phases in the Implementation Cycle
          1. Understanding the Business Drivers
            1. Products and Technologies Used in this Phase
          2. Determine Business Processes to Expose
            1. Products and Technologies Used in this Phase
          3. Install/Configure the Software
            1. Products and Technologies Used in this Phase
          4. Expose Legacy Artifacts
          5. Integrate Services into the application server
            1. Products and Technologies Used in this Phase
          6. Security and Governance
            1. Products and Technologies Used in this Phase
          7. Performance and Scalability
            1. Products and Technologies Used in this Phase
          8. Production Rollout
            1. Products and Technologies Used in this Phase
          9. Monitor Usage and Refine
            1. Products and Technologies Used in this Phase
        3. SOA Integration — Top Four Scenarios and Oracle Solutions
          1. Oracle Products Included in the Solution
          2. Oracle Products Not Included in the Solution
        4. Scenario One — Enterprise Information Integration
            1. Problem
            2. Context
            3. Forces
            4. Solution
          1. Scenario One Summary
          2. Scenario Two — Web Enablement
            1. Problem
            2. Context
            3. Forces
            4. Solution
          3. Scenario: Two Summary
        5. Scenario Three — Report Off-Load Using Data Migration
            1. Problem
            2. Context
            3. Forces
            4. Solution
            5. Scenario Three: Summary
            6. Oracle BAM
            7. Oracle BPEL
            8. Oracle Data Integrator (ODI)
            9. Oracle BI
        6. Scenario Four: End-to-End SOA
            1. Problem
            2. Context
            3. Forces
            4. Solution
          1. Scenario Four: Summary
            1. Oracle WebCenter
            2. Oracle BAM
            3. Oracle ESB
            4. Oracle OID and SSO
      4. SOA Integration — Final Product Summary
      5. IBM and Legacy SOA Integration
      6. Summary
    10. 4. SOA Integraton — Scenario in Detail
      1. Oracle Software Required
      2. UML and Database Diagrams
        1. Deployment Diagram
        2. Use Case Diagram
        3. Activity Diagram
        4. Sequence Diagram
        5. Data Model Diagram
      3. Which Legacy Artifacts Should I Expose? — Using the Relativity Product Set
        1. Application Layers — Understanding Relativity Terminology
        2. Understanding an Artifact's Place in the Architecture
          1. Vertical Slices
          2. Horizontal Slices
        3. Understanding Anomalies
          1. Client Programs with Data Access
          2. Calling Client Programs
          3. Calling Transitional Programs
          4. Impure Service Programs
        4. Other Anomalies that Need Remedial Action
          1. Data Validation Problem
          2. The Problem of Transient or Temporary Data Queues
        5. Finding the Service Functionality — Relativity SOA Analyzer Product
          1. Starting from Screens
          2. Looking for Special Program Constructs
        6. The Case of Mixed Programs — Program 'Slicing'
        7. Determining the Data Interface
        8. Summary Legacy Artifact Discovery Using Relativity
      4. Exposing the Legacy VSAM File Data Access
        1. Connecting to Oracle Connect on Mainframe and Setting Connection Properties
        2. Oracle Connect Data Source
        3. Oracle Connect Adapter
      5. Development Using Oracle JDeveloper
        1. Prework
        2. Application Modules
          1. Presentation-Tier/User Interface — HTML Page
        3. Legacy Web Service — VSAM Adapter Service
        4. Two-Phase Commit
        5. Oracle Database Persistence
      6. Deploying to the Oracle Application Server
        1. Configuring Oracle Application Server for the Legacy Adapter
        2. Configuring Oracle Application Server Oracle Database Connection
        3. Deploying to Oracle Application Server Using JDeveloper
      7. Running the Example
        1. Running the application
      8. Summary
    11. 5. Overview of Re-architecturing
          1. What is Re-Architecture?
        1. Drivers and Considerations for Re-Architecture
              1. Platform Agility
              2. Human Factors to Consider in a Re-Architecture Project
        2. How IBM Views Re-Architecture
              1. IT/Technical Drivers and Considerations
              2. Getting Off the Mainframe
              3. Creating a Flexible, Adaptable, and Agile Architecture
        3. Advanced Development Tools
              1. Technical Considerations for a Re-Architecture Effort
            1. Subject Matter Experts (SME)
            2. Risk of Modernization
            3. System Performance
            4. Usability/Training
        4. Re-Architecture versus Re-Host
        5. Re-Architect Deep Dive
          1. No Ripping and Replacing
        6. Pros and Cons
          1. Pros
          2. Cons
      1. Summary
    12. 6. Re-Architecture — Functional View, Implementation, and Architecture
      1. Technical Advantages of Re-Architecture
        1. Application Maintenance
        2. Enterprise Information Integration (EII) and Enterprise Application Integration (EAI)
        3. Architected for the Internet
        4. Scalability
        5. Availability
        6. Greater Software Options
        7. On Demand Reporting
        8. Security
      2. Overcoming Barriers to Change
        1. Custom Integration Applications and Utilities
        2. Custom Workflow
        3. Custom ETL
        4. Undisciplined Development
      3. Decoupling the Application-Tiers
        1. Presentation-Tier
            1. Business Rules
        2. Data Access
            1. Workflow/Business Process Flow
      4. Re-Architecture is Happening
      5. Re-architecture — Functional View
        1. A Technical Perspective of the Functional View
        2. Other Components of the Functional Infrastructure
        3. Re-architecture — Optional Software Components
      6. Implementation Process: Common Attributes, Approach for Batch, and Online Processes
        1. Top Three Re-Architecture Approaches
          1. Three "Iterative-Phased" Approaches (IPA)
            1. Data Migration
            2. Business Processes and Application Logic
            3. Move Standalone Application
        2. Re-archtecture Modernization Life Cycle
          1. Life-Cycle Caveats
            1. Application Portfolio Analysis Completed
            2. Life Cycle compared to Legacy SOA Integration Life Cycle
            3. "Big Bang" and Parallel Production
            4. The Human Element
            5. Training
        3. Re-Architecture Phases
          1. Discovery/Recovery
          2. Design Target Architecture
          3. Install and Configure Oracle Software and Hardware
          4. Model Target Application
          5. Development Iterations
          6. User Acceptance Testing (UAT)
          7. Performance Scalability
          8. Production Roll out
          9. Running in Parallel
          10. Unplug the Legacy Application
        4. Using a Modernization Factory for Re-Architecture Implementation
      7. Final Architecture — Common Oracle Products for Batch and Online
      8. Hardware, Operating System, and IBM
      9. Summary
    13. 7. Batch Systems Re-architecture Technical Deep Dive
      1. Historical Reasons for Batch
      2. Requirements of a Batch System
        1. Top Five Batch Patterns
          1. Multi Record Type Files — Pure Batch File Processing
          2. Transaction Processing — Pure Autonomous Transactions
          3. Administrative Batch — Backup, Archiving
          4. Reporting — 'Green Bar', Exception Handling, Error Handling
          5. Third-Party Interfaces — Internal and External Information Integration
      3. Technical View
        1. Optional Products
        2. Job Scheduler and BPEL Compared
      4. Implementation Process
      5. Recovery/Discovery Approaches
        1. Methodology
          1. Best practices
          2. Tooling
        2. Re-Design/Re-Factoring Approaches
          1. The Top-Down Approach
          2. The Bottom-up Approach
          3. The Hybrid Approach
        3. Repositories
          1. Relativity Repository
          2. Scheduler Repository
          3. OWB Repository
          4. ADF/OFM Repositories
            1. ADF
            2. OFM SOA Suite for BPEL
            3. OFM SOA Suite Business Rules
        4. Re-Design/Re-Factoring for each Legacy Artifact Group
          1. Green Bar Reports
            1. Recovery/Discovery
            2. Re-Design/ Re-Factor
          2. Job Scheduler — UML Process Flow
            1. Recovery/Discovery
            2. Re-Design/ Re-Factor
          3. Business Flows
            1. Recovery/Discovery
            2. Re-Design/ Re-Factor
          4. COBOL Business Rules
            1. Recovery/Discovery
            2. Re-Design/ Re-Factor
          5. COBOL Data Access Logic
            1. Recovery/Discovery
            2. Re-Design/Re-Factor
          6. Database and database schema
            1. Recovery/Discovery
            2. Re-Design/Re-Factor
          7. Target Generation
        5. Oracle Implementation Tools and Source to Target Mapping
          1. Summary of Tools and Frameworks
          2. Source to Target Artifact Mapping
      6. Final Oracle Batch Architecture
        1. Scenario Description
          1. New Batch Design Pattern(s) in Oracle
      7. Summary
    14. 8. Online Systems Re-architecture Technical Deep Dive
      1. History and Evolution of Online Systems
      2. History of SOA and SaaS
      3. Top Five Online Patterns
        1. COBOL/CICS Applications Accessing VSAM and DB2 Databases
          1. COBOL and CICS
          2. DB2
          3. VSAM
            1. COBOL, IMS/DC, or IMS/TM Applications Accessing IMS/DB Database
          4. IMS/DC and IMS/TM
            1. IMS/DB (IMS Database)
        2. COBOL, CICS, Assembler Applications Talking to Datacom or IDMS Database
            1. Datacom
            2. IDMS (Integrated Data Management System)
            3. Assembler
        3. PL/I and CICS Applications Making Use of VSAM and DB2 as Data Store
        4. NATURAL and COBOL Applications Accessing an ADABAS Database
            1. ADABAS (Adaptable DAta BAse System)
            2. Natural
      4. Technical View
        1. Infrastructure Unique to Re-architecture
          1. Single Management Tool
          2. Single Security Model
        2. Development Tools
        3. Metadata Repositories
          1. Enterprise Information Integration (EII)
          2. Enterprise Application Integration (EAI)
        4. Transactions
        5. Infrastructure Not Required for Legacy SOA Integration
          1. UI Navigation
          2. Java EE Applications (EJB, Java, POJO, JSP, Servlets, JSF)
          3. Relational Database
          4. Grid Infrastructure (Grid Computing)
          5. Backup and Recovery
        6. Technologies Not Necessary for Legacy SOA Integration
          1. Business Rules
          2. Data and Business Services
        7. Technical View Infrastructure Components
          1. Capacity Planning Tools
            1. Chargeback and Accounting Solutions such as CA (JARS)
          2. Application Development Tools
          3. Testing Tools
            1. Reporting
            2. High Speed Printing and Viewing
            3. Data Archiving
            4. Disaster Recovery
          4. Tape Management
          5. Human Error Recovery
            1. Internationalization
          6. Network Architecture/Protocol
            1. Reliability, Availability, and Scalability
      5. Implementation Process — Online Systems
        1. Presentation/User Interface
          1. Recovery/Discovery
            1. Re-Design/ Re-Factor
        2. UI Navigation
          1. Recovery/Discovery
          2. Re-Design/ Re-Factor
      6. Oracle Implementation Tools and Source to Target Mapping
        1. Summary of Tools and Frameworks
        2. Development Life Cycle Support Tools
        3. Source to Target Artifact Mapping
      7. Final Oracle On-line Architecture
        1. Scenario Details
        2. New Online Design Pattern in Oracle
          1. Presentation
          2. UI Navigation
          3. Application Server
          4. Information and Business Services
          5. Relational Database
      8. Summary
    15. 9. Re-Architecture — Scenario in Detail
      1. Oracle Software Required
      2. UML and Screen Flow Diagrams
      3. Source Application
      4. Oracle Target Architecture
      5. Application Mining Using Relativity
        1. Mining the User Interface and Navigation-Tiers
          1. Capturing the Legacy User Interface
          2. Legacy User Interface Discovery
          3. Screen Navigation Discovery
          4. Forward Engineering
        2. Mining Business Rules
          1. Prerequisites
          2. Identifying the Business Rules
          3. Using Pattern Search
          4. Searching Validation Rules
          5. Using Backward Auto-Detection
          6. Putting it Together
      6. Forward Engineering into Oracle and Java EE
      7. Producing the Target User Interface and Navigation
      8. Running the Presentation-Tier Mock-up in Oracle Application Server
          1. Deploying to the Oracle Application Server
          2. Running the Application
      9. Producing the Target Business Rules
        1. Creating the Rules Repository and Dictionary
        2. Creating Ruleset
        3. Java Fact — Adding the Java Fact Class to the Rules Author
        4. Adding the Rule
          1. Calling the Business Rules from Java EE and BPEL
          2. Automatic Business Rules Generation Using Java Code
      10. Data Migration — A Quick, Easy, and a Cost-Effective Approach
      11. Summary
    16. 10. Introduction to Re-Host based Modernization Using Tuxedo
      1. Re-Hosting Based Modernization
      2. Critical Success Factors in Mainframe Re-hosting
        1. Preserving Application Logic and Data
        2. Online Transaction Processing Environment
        3. User Interface Migration
        4. Workload Monitoring and Management
        5. Batch Jobs
      3. Files and Databases
        1. Mainframe DB2
        2. IMS
        3. VSAM
      4. Meeting Performance and Other QoS Requirements
      5. Phased Migration and Mainframe Integration
      6. SOA Enabling Re-hosted Applications
      7. Further Re-architecture of Re-hosted Applications
      8. Summary
    17. 11. Legacy Modernization — The Future
        1. Green Computing
        2. Standards Organizations
          1. Object Modeling Group (OMG)
              1. Record Type (COBOL)
          2. WC3
        3. Model Driven Architecture (MDA)
          1. Challenges with the Traditional Approach
          2. The MDA/MDM Approach
        4. Cloud Computing
            1. Amazon Elastic Compute Cloud
        5. Grid Computing
          1. Virtualization
          2. Application Fabrics
      1. Extreme Processing
      2. Summary
    18. A. Technology Glossary
      1. Common Legacy Acronyms
        1. Acronyms and Initials
      2. PCI Security Standards
    19. Index