Enterprise Modernization Made Easy with IBM Development Tools
Enterprise Modernization Agenda
Positioning Improve Transform Innovate Summary Meeting the On Demand Challenge
Significant business intelligence exists "200 Billion lines of COBOL code in existence"eWeek "5 Billion lines of COBOL code added yearly Bill Ulrich, TSG Inc. "Between 850K and 1.3 Million COBOL developers" IDC "Majority of customer data still on mainframes Computerworld Rewriting is an option but..... How long will it take? Who will do it? How much will it cost? As corporations assess their current IT operations as part of their move to an On Demand strategy, they are faced with a significant challenge how do they get there?Should they start over? Probably not. Consider why? The applications that run their business today are a culmination of years of work. The business rules are still valid The high cost and risk of rewriting all existing applications is not a viable option time, manpower, or money will be a barrier. As we said before We use the term "Enterprise Modernization" to refer to the process of preserving, evolving and integrating existing applications that predate e-business We cite some statistics here re: COBOL - but as we called out on the previous chart the applications we are talking about include a broad set - e.g., VisualBasic, PowerBuilder, PL/1, etc.. Enterprise Modernization is critical part of a business' application development strategy as the high cost and risk of rewriting all existing applications is not a viable option Regardles of potential unknowns in integrating these applications, the performance, reliability and scalability requirements associated with these applications often make their current environment the best choice. What this means is that the "legacy developers", as they are now called even in television advertisements, must be considered an important part of theoverall e-business development team. And as availability of these skills begins to tighten in todays job markets- it becomes more critical to have a development environment where these assets can be maintained and extended leveraging current development approaches and available skills Enterprise Modernization Strategy
Leverage existing applications and skills reduce costs "New code costs 5X reusing existing code" Software Productivity Research achieving faster time to market What corporations need is a strategic approach to deliver e-business applications by harvesting or reusing existing IT assets systems, skills, and applications. We use the term "Enterprise Modernization, which refers to the process of preserving, integrating, and evolving existing applications that predate e-business with new e-business application models. If we recall one of the industry research firms, Software Productivity Group indicating that creating new code can be up to 5 times more costly than reusing existing code, we need to keep in mind that much of this cost relates to not simply the programming effort, but rather the more wide cost relative to all the other activities such as verifying the compliance to specification (analysis) ,testing, deploying, verifying the scalability and functionality, performance tuning, and so on. If you could reuse existing code that has been running satisfactorily for years, tuned and deployed, clearly the saving can be this significant. We cite some statistics here re: COBOL - but as we called out on the previous chart the applications we are talking about include a broad set - e.g., VisualBasic, PowerBuilder, PL/1, etc.. Enterprise Modernization is critical part of a business' application development strategy as the high cost and risk of rewriting all existing applications is not a viable option Regardless of the high cost and risk of migrating these applications, the performance, reliability and scalability requirements associated with these applications often make their current environment the best choice. What this means is that the "legacy developers", as they are now called even in television advertisements, must be considered an important part of theoverall e-business development team. And as availability of these skills continues to tighten in the marketplace- it becomes more critical to have a development environment where these assets can be maintained and extended with current development approaches and available skills e-business transaction server e-business component developers e-business components Three Styles of Modernization
Strategic Innovate Business Value Create Entirely New Differentiated Solutions Transform Develop Customer, Partner & Supplier Relationships Improve Quick ROI: Better User Experience Opportunistic So, if we are going to reuse existing applications that are running the business where do we start? How does one leverage and integrate these traditional core assets, which are the existing systems, applications and data that run businesses today? IBMs Enterprise modernization strategy defines three solutions, referred to as styles of moderization, to help customers move theirIT assets from siloed applications to shared resources to inter-dependent software components. *The goal is to innovate new inter-dependent software components that have strategic business value and operate in an On Demand environment.However, that will take time, effort, and money.So more immediate solutions are required as well. *For example, being able to transform siloed applications to shared resources can create better ways of interacting with customers, partners, and suppliers. *Some changes to applications will be require immediate solutions that can drive reasonable business value, but will not be as flexible in adapting to changes in the business process. Called the improve style, it typically precedes the transform and innovate stylesof modernization. While customers have 3 choices for modernizing their enterprise, they are not limited to selecting only one style.Businesses may, and often will choose different styles of modernization for different departmental solutions.For example, a bank may choose to improve an applications usability by "re-engineering" the user interface for tellers checking account balances and transform another set of applications by integrating them together for a loan officer that needs to verify past credit history, personal data and run a series of calculations to determine maximum credit available. Nor having selected one style of modernization should not be viewed as locking the customer in to that solution forever. To help understand how and when to apply these styles of modernization, lets look at the problems they solve. Static On Demand Business Process Flexibility Modernization Styles: A Continuum of Solutions
A roadmap for solving problems. Segment Problem What value do customers want? Solution Improve Application interfaces are difficult to use, user workflows are outdated Quick ROI: Better User Experience Improve the user interface and workflows of multiple mission-critical applications to reduce training costs, increase end-user productivity and extend reach to new users Transform Legacy applications cannot easily be integrated into modern workflows Develop Customer, Partner & Supplier Relationships Transform applications to participate in modern e-business workflows with lower risk than replacement strategies Innovate Mission critical processes cannot easily be adapted to changing market conditions Create Entirely New Differentiated Solutions Innovate by componentizing mission-critical applications to enable core processes to be independently modernized and flexibly integrated on demand The first style of modernization, improve, focuses on reducing costs and increasing productivity by improving the user interface.This method is the most accessible for companies because it requires the lowest level of investment.With this method companies can achieve a quick return on investment by creating a better user experience.Improving the user interface improves ease of use and results in lower training costs and an increase in overall customer satisfaction.Higher employee productivity is also a benefit of this method... The second style of modernization, transform, focuses on extending existing applications beyond their siloed original design to make them more horizontally integrated.Investment levels increase from style 1 to style 2 as does business value and process flexibility.With this method companies can turn existing software applications into reusable services.As reusable services, these legacy applications can be accessed by new users or extended to new applications.This improved integration leads to new customer/supplier relations.Integration of applications to develop differentiated front-end capabilities is a lower risk activity than more ambitious replacement strategies. The third style of modernization, innovate, takes the accessibility of style 2 one step further.With this method, components of existing applications are made available for flexible and configurable use in new applications.This reuse of business logic is called componentization and can result in significant cost savings over rewriting the code.With Web services, these components can be used in new e-business applications which can utilize Quality of Service, inherent in enterprise systems. IBMs Enterprise Modernization Solution
Existing Assets Discover Develop Deploy iSeries 5250 user interface Improve User Interface Reengineering zSeries 3270 user interface Test,manageand monitor end-to-end iSeries, zSeries, UNIX And Windows data and applications Identifyandprepare existing assets for reuse Integrate with existing applications Transform IBM has been creating products to support "Enterprise Modernization, which refers to the process of preserving, integrating, and evolving existing applications that predate e-business with new e-business application models. IBMsEnterprise Modernization solution is not any one product new or old. Rather IBMsEnterprise Modernization solution describes how IBMs comprehensive portfolio of AD products can help you to achieve the On Demand goal.You pick the tool that meets your needs. Each dark blue box represents one or more IBM products. There are products to support each style of modernization- Improve, Transform, Innovate (horizontal view) There are products to support each stage of the application development life cycle- Discover, Develop, Deploy. (vertical view) Note that the products for Discover and Deploy support all 3 styles of modernization (tall blue boxes) Lets briefly look at how IBMs portfolio of AD products supports Enterprise Modernization first by looking at tools to support Development, and then by looking at the tools to support Discover and Deploy. Innovate Extend existing applications for integrationas services Manage the team development process Enterprise Program Model
Develop Display Integrate ? Value in circle= style Improve Transform Innovate Position on diagram: Point of interaction with a program 1 2 2 3270/5250 data stream Data Structure 1 2 Screen Maps I will be using this diagram to describe how IBMs tools can support Enterprise Modernization. Each of the numbered circles correspond to a style of modernization. The position of the circle indicates a point in time during execution of a program when a tool can interact with a programs input or output. During the presentation I will associate IBM tools to the numbered circles. Existing Applications(CICS, IMS, iSeries) 3 Three Styles of Modernization
Develop Strategic Business Value Improve Quick ROI: Better User Experience Opportunistic Lets begin by looking at development tools that support the Improve style of modernization. Create a better user experience: Improve on the 3270/5250 user interface by replacing it with a web browser user interface.This is fast and requires no changes to the existing application. Static On Demand Business Process Flexibility Style 1: Improve the end-user experience
Develop Style 1: Improve the end-user experience Web Display Display content of Text UI in Web UI HATS 1 3270/5250 Data Stream Data Structure WebFacing, CICS WebBridge 1 Screen Maps Improve style creates a better user experience by enabling the display of some or all of the content of Text UI in Web UI 2 techniques are possible: Capture the 3270/5250 data stream and extract content; redisplay in Web UI For CICS and iSeries, WebFacing and CICS WebBridge can obtain the text content before it is converted into a data stream. Existing Applications(CICS, IMS, iSeries) Host Access Transformation Server (HATS)
Develop Host Access Transformation Server (HATS) A Web-to-host HTML emulator, with ... rules-based transformation engine, that... converts green screens to graphical user interfaces improves ease-of-use of host applications. Default rules and on-the-fly screen transformation allow 3270 and 5250 applications to be deployed to the Web within hours of loading the software Benefit: Easily extend existing applications to the web Develop The IBM WebFacing Tool Part of WebSphere Development Studio for iSeries Supports 5250 and web interfaces Convert RPG/5250 applications to GUI End-users access applications via browser Three Styles of Modernization
Develop Strategic Business Value Transform Develop Customer, Partner & Supplier Relationships Opportunistic Lets consider the Transform style in which one: Transforms the business process by creating a business flow that combines various legacy applications in a new way.Again no change to the existing application, but requires some business logic in the front end. Static On Demand Business Process Flexibility Develop Creating closer relationships with customers, partners, and suppliers is critical to the survival of a business. A short-term solution is using the Improve style of modernization to make siloed applications more accessible to more. However, to foster even closer relationships, the business process must usually change as well.Therefore, siloed applications need to be transformed into shared applications so that they can be integrated into new business processes. Application adapters are what make this integration possible. (although adaptors, connectors, and other terms have been coined to indicate differences in the programming implementation, I use the term adapter to represent the concept.)Application adapters are programs that provide a callable interface, ideally standards based, so that the outside world can programmatically access an application. They exists for many commercial applications - PeopleSoft, SAP, i2, for example. There are software companies who exist because of the application adapters they sell. IBM provides many generic adapters for customers to use with their own applications.Lets take Lets examine the application adapters that IBM provides that aid in Enterprise Modernization. Style 2: Transform the business process
Develop Style 2: Transform the business process CICS TG IMS Connect MQIAC XML SOAP Integrate Program access to legacy systems Host Pub, HOD Connector 2 2 2 3270/5250 Data Stream Data Structure 2 Transforming the business process usually means creation of a new front-end applications which implement the new business process. The new front-end utilize the logic and content of legacy applications to reduce development time.The technologies listed here provide ways to programmatically access these legacy systems Screen Maps CICS Link3270 Existing Applications(CICS, IMS, iSeries) Ways to Access Existing CICS Applications
SOAP requests over HTTP or MQ messages CICS Transaction Gateway WebSphere on zSeries WebSphere on non-zSeries platform HTTP HTML XML Existing CICSApplications WebSphere zSeries + CICS TG V5 V5 + SNA LU6.2 TCP62 TCP/IP EXCI CICSTS V2 + Local Connector AIX, Solaris, HP-UX, Windows NT/2000 SOAP/XML IIOP Shown here are ways you can access existing CICS applications from a web based client, i.e., ways of re-facing existing CICS applications.You can use J2EE connectors that are provided by the CICS Transaction gateway to accomplish this.The CICS Transaction Gateway is the primary option for connecting Web application servers to CICS applications. The CICS Transaction Gateway works in conjunction with the WebSphere Application Server. You can use IIOP to initiate bean-to-bean calls to EJB running under CICS;these EJBs will then access the existing CICS applications.You can also use SOAP requests over HTTP or MQSeries, taking advantage of the capabilities of the SOAP for CICS feature of CICS Transaction Server for z/OS V2.2. IMS Connect Development Environment WebSphere Studio
Connector for Java Open Transaction Manager Access (OTMA) Connect Runtime Environment Enterprise Application RAR X C F WebSphere Application Server Deploy MFS COBOL DB DB2 Browser IMS Connect, used with WebSphere Studio Enterprise Developer (Enterprise Developer) or WebSphere Studio Application Developer Integration Edition (Integration Edition) and IMS Connector for Java, can significantly ease the development of e-business solutions that access IMS transactions.Java programs developed with these products can be deployed in WebSphere Application Server, allowing you to use Web applications, J2EE applications, or Web services to quickly transform static Web sites into sources of dynamic Web content. IMS Connector for Java provides a resource adapter for deployment in WebSphere Application Server for use in running Java applications.Resource Adapter support is provided thruthe addition to IMS Connect of the IMS Connector for Java J2EE runtime support.The IMS Connector for Java J2EE runtime support provides the runtime environment for Java applications developed using Integration Edition. MQSeries Integrator Agent for CICS Transaction Server
Enable middle-tier applications to access CICS, IMS, and others Adapter flow is surfaced as a "Business Service multiple transactions or applications accessedwith one request from the client e.g., Check Account Balance, Add Sales Order Two components MQSeries Integrator Agent for CICS Adapter Builder Define, model, and build adapters for application integration MQSeries Integrator Agent for CICS Server Run Time Execute adapters for application integration Business transaction is the BTS (Business Transaction Services component of CICS Transaction Server) concept of a transaction - this differs from the classic CICS transaction. Classic CICS transaction: normally short-lived - associated with a CICS task traditionally initiated from a 3270 terminal usually associated with a unit-of work can be linked together pseudo-conversationally to complete a piece of processing BTS - a business transaction is the set of steps required to complete a piece of business e.g., book a Holiday: may be long-lived may be initiated by any CICS input may be made up of a number of CICS transactions However in the current MQIAC deployment, we only drive an instance of the adapter, and hold any "micro flow " state in BTS containers only for Controlling app to compensate by potentially using connecting another Adapter or "micro flow" instance to that state for compensation. Three Styles of Modernization
Develop Strategic Innovate Business Value Create Entirely New Differentiated Solutions Opportunistic The third style of modernization, innovate, takes the accessibility of style 2, Transform, one step further.With this method, components of existing applications are made available for flexible and configurable use in new applications.This reuse of business logic is called componentization and can result in significant cost savings over rewriting the code.With Web services, these components can be used in new e-business applications which can utilize Quality of Service, inherent in enterprise systems. Static On Demand Business Process Flexibility Style 3: Innovate new business components
Develop Style 3: Innovate new business components CICS TG IMS Connect MQIAC XML SOAP Integrate Harvest new components from legacy applications 2 3270/5250 Data Stream Data Structure The concept here is creating new components, especially when harvested (taken) from existing siloed applications. The tools are WebSphere Studio Enterprise Developer for the z/OS environment and WebSphere Development Studio for the iSeries environment. The connectors shown in gray because they still play a part in the solution by providing ways to access these components. however the strategic interface to components should utilize a Service Oriented architecture (web services). Screen Maps WSED, WDS Existing Applications(CICS, IMS, iSeries) 3 Harvest components The WebSphere Studio family
Develop The WebSphere Studio family Enterprise Developer Enterprise development organizations Web services based enterprise modernization Enterprise modeling and RAD Application Developer Integration Edition Advanced J2EE developers Flow composition Visual adapter creation Business rule support Application Developer J2EE developers Relational DB tools Embedded WebSphere Application Server Site Developer Professional Web, Java, and Web services developers Java, XML, Rich media, and Web services This chart is intended to help you explain the WebSphere Studio family of products, showing how each higher version of the product includes all the functions of the lower level, until you reach Enterprise Developer, which provides a consistent, application development environment for both legacy and Web applications. Workbench IBMs commercially supported version of the Eclipse Workbench WebSphere Development Studio for iSeries
For existing and new AS/400 web development Wrapper" RPG applications as web service Modernize 5250 applications via WebFacing Tool Integrate the key tools of e-business, Java, and web development WSAA Overview Discover
WebSphere Studio Asset Analyzer is a tool for maintaining and extending existing assets through impact analysis, connector builder assistance, and graphical application understanding. This tool is designed to help enterprise customers on their journey to e-business by providing knowledge about both their static environment (finding and reusing application code and the components that connects that code).It also helps them to understand their dynamic environment (understanding what code is executing in runtime environments). Let's take a look at the architecture of WebSphere Studio Asset Analyzer. At project startup, or once implemented, as part of a corporate wide effort to manage assets, the key artifacts: JOBS, CICS and IMS transactions, EJBs,Java, COBOL, Program Source and copybooks are loaded into the DB2 Knowledge store in a z/OS environment.This knowledge store is typically synchronized with change management or change control processing. Why DB2, because it performs and can hold large application wide amounts of data, why on z/OS, because it's fast to setup and get information into, so you can get to work. Once the database is loaded, the information is then accessible via a web browser.We can then begin the process of discovering which of our existing assets are candidates for new e-business applications, and determine the impact changes will have on our other systems. Benefits: Use existing skills and application knowledge for evolution to dynamic e-business, and walk through the development process in a significantly faster manner, Improve maintenance and development of applications -Support impact analysis and application understanding of traditional batch and transactional applications -Support impact analysis and application of distributed applications, particularly in the Web, Java and J2EE environments -Support identification and management of service oriented business processes Simplify e-business enablement of applications in three scenarios -Creating connectors for legacy applications without changing the underlying application -Modifying legacy applications to enable reuse in B2B and B2C solutions -Migrating legacy applications to component and service-based architectures Provide these facilities to a wide range of user roles -Including developers, analysts, testers, managers Simplify access to information through Web browser interface Provide an open architecture for integration and extension -Interfaces to source code management tools and processes -Documented DB2 database for custom and ad hoc reporting -Interfaces for custom tools and Connector Information
Discover Tools Application Knowledge Business Knowledge Change Knowledge Data Knowledge e-business Knowledge Discovery/Plan Understand components Define relationships Find Transactions Find JCL Narrow Scope Understand business requirements Define application boundaries Define program flows Define data items Create data flows Generate statement of work Create schedule Find Databases Find Files Find Relationships Generate test cases Define candidate connectors Generate Application Artifacts Structure and Processing Data flow and impact Code Extraction e-business Rating Connector Intelligence WebSphere Studio Asset Analyzer delivers the following kinds of knowledge to all developers in an organization, via the browser based interface. Application knowledge from rapid understanding of application componentry and construction, plus a high-level view or blueprint of an application. . Business knowledge from understanding of business and processing flow through drilling down into applications. Change knowledge from identification of areas of the application that will change based on the requirements, right down to the line of code including where all data items and indirect data items are used. Data knowledge from databases and files that make up the application, plus data flows that provide a logical connection between programs, between processes, and between applications. E-business knowledge from ratings of program modules for their usefulness as components, as well as data definitions that can be imported into WebSphere development tooling.Once a program module has been identified as a good e-business candidate, that code can be extracted using WSAA and a component created. You can explore the information in the database by application, component, or site. This navigation helps you define the scope of the search so that you can drill down to examine the contents at each level. For example, a search by application lets you choose an application to explore from a list of the applications that you have identified in the database. You can then choose a component to explore from a list of that application's components, and so on. You can also search the database for specific words and phrases to find specific data elements. For example, a search on the word "Balance" will give you a list of all the data elements in the database that contain "Balance". You can use WebSphere Studio Asset Analyzer to find specific data elements that make up a business process flow by following the initial data references to balance through the flow and data movement of the application. Providing End-to-End Asset Analysis for traditional, enterprise and e-business support WebSphere Studio Asset Analyzer V2.0 Source Scanning Tools Source Scanning Tools Knowledge Store (DB2) Impact Analysis Exploration Connector Information Netscape / I.E. User Interface Using WSAA for Enterprise Modernization
Discover Using WSAA for Enterprise Modernization Improve: How may screen I/Os Transform: Package COBOL call info for Java programmer Innovate: Harvest code from existing programs WebSphere Studio Application Monitor
Deploy WebSphere Studio Application Monitor Trouble-shooting Performance-monitoring Performance analysis WebSphere for z/OS WebSphere Studio Application Monitor provides information to help resolve problems with applicationsrunning in a WebSphere Application Server environment: It enables developers and Quality Assurance personnel to: Monitor and analyze the behavior of J2EE applications and quickly take corrective actions to resolve problems Delivers a non-intrusive solution that does not require modifications to the applications to generate useful information. Real-time problem determination for Java applications Drill-down capabilities provide views at an enterprise level down to specific thread-level detail Non-intrusive Production-safearchitecture no instrumentation required Application Independence brings total manageability without the need to modify or access application code Performance management Rich set of historical analysis functions Performs Trends Analysis for fine-tuning the applications or the environment, analyzing systems resources and planning for future growth browser Benefit: Resolve performance problems with J2EE applications WebSphere Studio Workload Simulator
Deploy WebSphere Studio Workload Simulator Simulate a large number of web users Web servers Application servers Back-end systems WSWS Benefits: Validate support for production loads Does not pre-req the WAS WebSphere Studio Workload Simulator simulates multiple Internet browser users ("virtual" users), for load-testing Web servers, such as WebSphere Application Server. It offers a graphical, Windows-based user interface through which you create and edit test scripts, control the execution of the test, and analyze test results. It features a controller "capture" function that helps you generate test scripts automatically and quickly. Benefit: Test drive Web applications before you deploy Enterprise S/390 Development Tools
Deploy Enterprise S/390 Development Tools Application Monitor real-time bottleneck analysis Debug Tool source-level diagnostics Fault Analyzer application failure determination and resolution assistance File Manager Manipulates test and production data across multiple file formats Workload Simulator Web application load testing The objective of the S/390 deployment tools is to move applications through the development and implementation cycle more quickly and move investment spent in this area to support new e-business initiatives. The value is that the overall deployment costs are down and applications are delivered more quickly. Application Monitor Provides performance statistics for any job that is monitored, can perform both real-time bottleneck analysis or historical data analysis Debug Tool Displays a source-level view of the point of failure, and provides facilities for diagnosing and correcting the problem, works across multiple languages and platforms Fault Analyzer Helps determine the causes of an application failure, provides assistance on how to solve the problem File Manager Manipulates development, test, and production data across multiple file formats and storage media, includes extensive edit, browse, print, data creation, and copy functions: developers' productivity is increased, eliminates the need for developers to interpret low-level system dumps Workload Simulator Provides the ability to simulate a specified network of terminals and the associated messages, provides insurance that the networks will work under specified transaction volumes Points of Enterprise Modernization Today
Display Integrate CICS TG IMS Connect MQIAC XML, SOAP HATS, HostPub, HOD Connector 1 2 2 3270/5250 Data Stream Data Structure WebFacing, CICS WebBridge 1 2 Screen Maps This is a summary of the tools that are available to modernize your enterprise applications. CICS Link3270 Existing Applications(CICS, IMS, iSeries) 3 WSED,WDS Harvest Components IBMs Enterprise Modernization Solution
Existing Assets Discover Develop Deploy iSeries 5250 user interface HATS WSAM WSWS Improve User Interface Reengineering zSeries 3270 user interface WSAA Test,manageand monitor end-to-end iSeries, zSeries, UNIX And Windows data and applications Identifyandprepare existing assets for reuse WSED Integrate with existing applications Transform AD Product summary WSED Innovate Extend existing applications for integrationas services Manage the team development process Three Styles of Modernization
Strategic Innovate Transform Business Value Create Entirely New Differentiated Solutions Develop Customer, Partner & Supplier Relationships Improve Quick ROI: Better User Experience Opportunistic Static On Demand Business Process Flexibility