IBM Rational Software

Transcription

1 IBM Rational Software Development Conference 2008 Mission-Critical Financial Services Application Modernization Using IBM Rational Business Developer/Enterprise Generation Language - An IBM and Wipro Success Story Omkar Nimbalkar Manager, Enterprise Ecosystems, IBM omkarn@us.ibm.com Jaydip Sanyal Group Head, Legacy Modernization Practice, Wipro Technologies Jaydip.sanyal@wipro.com Select View/Master/Slide Master to add Session Number Here 2007 IBM Corporation

2 Application Modernization Options OPTION SOLUTION DELIVERY Reface H A T S E G L Browser Rich Client Portal Mobile Existing Core Business Applications Build Transform SW Factory E G L E G L COBOL Java COBOL Java Text UI Browser Portal Rich Client Mobile Text UI Browser Portal Rich Client Mobile Analyze Refactor E G L COBOL Java S O A Text UI Browser Portal Rich Client Mobile EM02 2

3 Proposition: Application Transformation Functionality Performance and Stability 100% The Legacy Bar (Running your Business Today) 75% 50% Transform 25% Equivalent Replace Re-Write Equivalent Equivalent 0% Year 1+ Year 3+ Year 5+ Year n EM02 3

4 Modernize Development Investments Transform your legacy applications Non IBM Technologies HPS/AppBuilder COBOL Maestro RPG * IBM Technologies VA Gen Ideal Basi c PowerBuilder * Enterprise IDMS ADS/Online * CSP 4GL * Future Capability * Migrate from out-of-date and expensive legacy development platforms onto IBM SDP via Rational Business Developer featuring Enterprise Generation Language (EGL) Process & portfolio management Conversion Tooling Consolidate & Advance with EGL Change & release management Quality management Architecture & construction Integrated Requirements Management Deploy to: Linux AIX Solaris HP-UX System i System z Windows WAS EM02 4

5 Transform Existing Applications into EGL Large Complex Programs 3270UI 4GLs/COBOL EGL EGL Business Logic Database Access SW Factory EGL EGL EGL Eliminate Skills silos allowing IT to freely shift resources across projects according to business priorities Exploit new System Z/I configurations Transform your assets and create new options for your business EM02 5

6 Building and modernizing applications today is not easy SQLJ AJAX Servlet VSAM EJB RPG HTML JavaScript COBOL JSP IMS SOAP SWT XML JCA CSS Struts MQ JSF JMS O/R CL CICS JDBC but leveraging the IBM Rational Software Delivery Platform and standardizing on Rational Business Developer (EGL) can make the difference between success and failure EM02 6

7 Why is Rational Business Developer featuring Enterprise Generation Language (EGL) strategic? Skills: Learning and Adoption Java great language and technology; too difficult for many customers to learn and adopt.net RPG/ COBOL/ 4GLs (Natural) C# is an OO language same issues as Java plus many API s Comfortable languages, great capabilities, but graying staff, no new developers Re-training COBOL developers to Java/J2EE costs over $50K each, and only 12% may actually succeed Gartner Group The task force had an initial meeting and identified challenges to teaching Java based on the literature and our experiences. ACM Education Board Java Task Force An insurance company spent approximately $250,000 to train 12 RPG developers. One out of 12 succeeded. This person had an MS in Computer Science and 8 years of C programming experience. Bob Cancilla, IBM EM02 7

8 What s New in Application Transformation New Products Coming in 2H 2008 IBM Rational Migration Extension for Natural IBM Rational Migration Extension for IBM i New White Papers Natural to EGL Adobe Acrobat Document RPG to EGL Adobe Acrobat Document EM02 8

9 Customer Pain Points Faced with language obsolescence due to legacy 4GL implementation of current system Requirement to leverage existing talent pool with strong procedural language skills System i platform specific implementation Necessity to leverage other platforms including Solaris and Windows Necessity to leverage existing assets in a modern web enabled environment Need to standardize on SOA as a design principle EM02 9

10 The Road to Choosing RBD/EGL - Customer Application Identification and Proof of Concept POC with screens to be converted to a web based application was identified Ecosystem team worked closely with the customer to identify requirements, and necessary functionality An Ecosystem team resource was on the ground to help with Education and training for POC resources Application architecture and best practices Mentoring on the actual POC Trouble shooting and optimization of code created for the POC Efficient resolution of any potential issues or tooling problems EM02 10

11 The Road to Choosing RBD/EGL - Proof Of Concept Conclusions and Results Entire POC was implemented and all POC design points were successfully met within 1 month POC resources learnt RBD/EGL and were able to create a reasonably sophisticated web application during the course of the POC including, Calls to backend System i COBOL programs through the use of a simple CALL statement Access to data areas and data queues, and execution of CL statements Deployment of an MVC compliant web application on WebSphere Application Server Access to data on a DB2 database running on System i from the POC web application Modularization and componentization of the new application artifacts, through the use of libraries and services Net Result: Customer chose RBD/RGL as the strategic language of choice moving forward for all development Wipro validated EGL as the language of choice, let s see how EM02 11

12 Case Study EM02 12

13 Introduction IBM Rational Software Development Conference 2008 Customer Large Financial Services Sector (FSS) client in North America Customer has a mission critical application managing and trading in mutual fund products Application built in a 4GL language running on ISeries Drivers End of support for the 4GL language on iseries No separation between the presentation logic and the businesses logic in the application Enhancing User experience by migrating towards browser based GUIs Current functionality not designed as reusable service Migration of screens Scope Migration of 1 M lines of code Understand the business logic from the legacy code base Enhance the functionality Re - use the existing database Objective Rewrite the application to a 3 tier modern architecture that can leverage the principles of SOA Leverage the existing legacy developers so as to meet the strict dead lines EM02 13

14 Key Business Drivers DD Interim Impl Business Drivers Support in EGL Quicker time to market Reduced TCO RBDe/EGL provides productivity improvement over normal J2EE development RBDe/EGL helps legacy developers to quickly pick up the development work in EGL Productivity improvement will reduce the cost of Key Architectural development Drivers considered Re utilize the legacy developers to maintain the system post development EM02 14

15 Key Technology Drivers DD Interim Impl Technology Drivers Scalability Support in EGL Support for execution in clustered environment Layered Architecture Ability to have multiple layers in application with distinct responsibilities Supports MVC model of execution Modularity Key Architectural Drivers considered Heterogeneous Integration Components in EGL application have the ability to exist in modular format and hence promotes reusability Support to consume Doc and RPC style web services Support to produce RPC style web services Extensibility through support for external data types Multi thread support in EGL EGL cannot create multiple threads through the language Exception Handling Can propagate exceptions across layers and user can create and throw custom messages Transaction Management Performance Supports transaction management using EGL s inbuilt mechanism for flat transactions Generated Java code is tuned for performance EM02 15

16 Key Technology Drivers DD Interim Impl Architectural Drivers Asynchronous support Support in EGL EGL supports the integration with MQ Support for 3rd Party packages like Log4j, Reporting tools Security Maintenance XML Support Supported through using external types using Java wrapper classes EGL does not have native support on encryption/decryption but can utilize external types Key Architectural Drivers considered Development is independent of runtime environment and hence users need not worry of handling runtime issues. Easy to maintain the code. Support for incremental build EGL does not have an inbuilt XML parser. However, Third Party API s can be utilized as External Type, i.e. using Java wrapper classes A work around is possible in most cases through the use of external types EM02 16

17 Our Recommendation EGL Benefits Easy for developers trained in procedural language to pick up as the technical complexities are hidden Allows developers to be portable across technologies The ability to create a Graphical User Interface (GUI) with the base UI components ready Ability to auto generate the Data Access code in terms of Record Sets, Data Items, DAL Libraries Productivity benefit of % over traditional J2EE approach Rapid development leading to a quicker time to market Separation of presentation layer, application layer and data layer in order to facilitate SOA strategy Creating of granular services is made easy RBDe/EGL Approach was chosen for application transformation EM02 17

18 Implementation Phase EM02 18

19 Implementation approach Re-engineer business Logic from code base Identify business services EGL development and testing 1. Identify services from top down and bottom approach 1. Gather the business logic from the legacy code base 2. Validate the business logic 3 Develop wireframes 1. Implementation plan 2. Design the screens 3. Develop and test the screens 1. Develop wireframes for the GUI screens EM02 Slide 19 19

20 Implementation methodology DD Interim Impl Code Re-eng Phase orules catalog ocreation of the Functional specification documents oreview of FS documents with customer ocreation of wire frame oreview of wire frames with the customer oclient approved FS and wireframes UAT Plan EM02 20

21 Implementation Statistics Peak Team Size 8+ Business Analyst 6+ EGL Architects 60+ EGL Developers 10+ EGL Testers 4 Project Managers 80 experienced people Project Period 15 Months Two Phase approach ( Phase 1 10% of screens) EGL Productivity Gain 15 % Ramp up time for developers 2 weeks of class room training 2 weeks of POC Number of reusable business functions 20 EM02 21

22 EGL Training Process Architecture/Integratio n Layer ( 1 week) Enable Architects/Solution Designers Enablement for Designing Best practices/coding guidelines/naming convention (0.5 week) Assimilate practical experiences in the project Enablement for Implementation Hands on experience (1.5 week) POCs for sample scenarios Practical training EGL Basics/ Development Methodology (2 weeks) EGL class room training Awareness & Appreciation EM02 22

23 EGL Project Best Practices Presentation Layer Page Handlers should have only screen logic or controller logic and no business logic Business Layer Create a EGL external language data type mapping in advance to save time EGL generated SQL Records should not be directly used to populate the UI Components of Page Handlers Database Layer Customer queries to be stored in separate library from EGL generated queries as Import operations drop and re-create the default <tablenames>.egl library files While generating the SQL query, choose only columns that are required for the query General For optimal performance single eclipse project should not have all the application programs If projects have more than 200 programs, split into smaller projects Avoid the occurrence of - while naming the variables EM02 23

24 Benefits to Customer Increased productivity leads to faster time to market Reusable business services identified for future use reducing future cost of development Laid out a good technical platform to be leveraged in future for new user access channels like mobile Modernize the green screens into web based GUI increasing user productivity Usage of Wipro s domain SMEs reduced load on Customer SMEs thereby allowing them to focus on other strategic initiatives Technical issues were made transparent to the customer EM02 24

25 Possible situations for usage of EGL Business Need Business Scenario How EGL helps Unavailability of skills on mainframe Customer has applications written in Natural,PL/1, COBOL and other obsolete languages Difficult to hire people skilled in some of these languages Various resource pools need to be maintained Usage of resources not uniform as the stability of applications differ Understand the applications and rewrite them in EGL EGL generated COBOL can run on the existing hardware Only EGL trained people need be maintained Legacy programmers can be easily trained in EGL Shorten time to market Customer wants to re-engineer applications on the legacy to new platform Business demands that the applications are reengineered in a short span of time Productivity improvement features inbuilt into EGL and leveraging of legacy developers makes this possible Build products for multiple technologies Customer builds product for both mainframe and J2EE end customers Customer wants to keep the product in sync across both the platforms Customer wants to shorten the cycle time for development EGL has inbuilt capability to generate code in COBOL and Java Customer can build the product in EGL and generate the run time based on its end customer EM02 25

26 QUESTIONS EM02 26

27 THANK YOU Learn more at: IBM Rational software IBM Rational Software Delivery Platform Process and portfolio management Change and release management Quality management Architecture management Rational trial downloads Leading Innovation Web site developerworks Rational IBM Rational TV IBM Rational Business Partners Copyright IBM Corporation All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, the ondemand business logo, Rational, the Rational logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. EM02 27