IBM Rational Software Development Conference 2007

Transcription

1 It s for IBM System i and System z Jean-Yves B. Rigolet Software Engineer, IBM Rational Software rigolet.j@fr.ibm.com 2007 IBM Corporation Agenda Introduction A brief tour of Jazz Jazz in System i and System z context Leverage the Rational enterprise tools Demo Summary Q&A 1

2 The development focus has shifted from the Individual Remember late 90 s Focus on point tools Who can build the best Java IDE, the best C IDE, the best Web tool, When Eclipse was built Focus a developer s productivity Seamless integration across a set of tools to improve the productivity of one developer to the Team Today, we must focus on the team s productivity Collaboration Geographically distributed Accelerated delivery demands Agility with predictability Innovation and repeatability Increased need for transparency Plus, we want to improve total cost of ownership (TCO) of our solutions And we are introducing Collaborative Development Environments with What is? Innovation A major investment by IBM to create a scalable, extensible team collaboration platform for seamlessly integrating tasks across the software lifecycle Tooling the Eclipse Way A commercial project led by the IBM team that brought you the Eclipse Platform, tooling the agile practices of this proven open collaborative model Innovative Software Engineering Community Jazz.net Jazz project venue for open commercial development of Jazz platform and Jazz-based products and an extension of the world wide Eclipse ecosystem Vision A vision for the value and experience that future Rational products can bring to software and systems delivery teams 2

3 What does do for your enterprise? Enables development teams to collaborate in real time in the context of the work they are doing, especially in globally diverse environments Enables projects to be managed more effectively by providing visibility into accurate project health information drawn directly from actual work Automates traceability and auditability by managing artifacts and their interrelationships across the lifecycle empowering teams to deliver more value Provides customizable process design and enactment through rule-based process guidance, automation and definable checkpoints platform components overview Other Systems! " 3

4 What makes System i and System z special? Both systems have Mutliple application architectures (Batch, TP, WebSphere, Composite, ) Multiple file systems Unique file systems (Record-oriented structure vs. stream) File encoding of EBCDIC (typically becoming mixed) Builds that must be done on-host System i has Ease of system management, yet highly secure Ease of integration and i5/os integrated features to support that (e.g. DB) High automation characteristics (monitoring resource consumption, tuning, etc) Extended 3rd party packaged applications System z has High security requirements tightly controlled access High number of large artifacts supporting large number of applications (COBOL, PL/I, HLASM) Addicted to SCMs for build and deployment with elaborate processes consolidated over the years Huge variances in build mechanisms across enterprises / JCL Strong scalability characteristics / strong reliability characteristics The reputation of not being considered an easy system (this is changing) Application characteristics of System i and System z Existing Systems are vital in many aspects of daily life If these systems were stopped for a day, financial transactions would grind to a halt worldwide Large number of different artifacts manipulated Many different source codes for decades: RPG, COBOL, PL/I, JCL, Rexx, CLIST, Natural, more recently, EGL, J2EE, Web 2.0, Very long lifetime of applications Large number of interrelated artifacts and large artifacts Existing Systems evolved over time Large and complex, built in silos with overlapped info Code predates Structured code concepts, OOA/OOD and Separation of concerns Different data organizations Indexed Sequential, Virtual Sequential, hierarchical data organizations, and others! Many applications subject to strict governance, audit controls Many mission critical applications, 24x7x365 One System z customer has not re-booted since 2000 continuous operation even thru upgrades 4

5 Team characteristics of System i and System z Teams organized around traditional runtimes CICS, IMS, i5/os, Batch, USS, DB2 Stored Procedures Green screen / terminal applications Large number of people (hundreds, thousands) People skills and education are not always very well aligned with existing enterprise technologies & needs Team dimension around Data DBAs and data access groups Many different data organizations Separate team(s) around roles and technologies Rich clients / networked - browser-based Development / Quality Assurance / Build and Deploy / Governance or same group does everything Many different teams, roles & geographies with no integrated way to collaborate and share using a common way Modernization & Architecture groups Chartered with re-structuring application Chartered with providing uniform view across multiple data towers Application programmers do not write the SQL or VSAM access routines but needs to use them correctly Need a clear view of what already exists, who is doing what, where and when Why is important to System i and System z? People / Teams large number of team members, organized under separate lines of management / reporting chains Teams need to talk to one another Artifacts - Huge number of unique artifacts and characteristics; Large artifacts Artifacts need to be usable & reusable Time - Multiple concurrent releases, changing legal requirements that must be satisfied within constrained timeframes Keep track of IT history Jazz gives System i and System z the glue between People Artifacts Time 5

6 Where can help System i and System z? Host the Jazz server on System i and System z Ensure equivalent behavior Support the basic reference Open Source stack Tomcat, Derby, Wildfire Support Value Add stack WAS, DB2, Lotus Sametime Integrate with important System i and System z development tools Across the entire Rational enterprise development stack RAD, RBD entension, WDz, WDSC, RAM, Support System i and System z specific development styles Provide a single way to handle all artifacts and languages across tools COBOL, EGL, RPG, PL/I, HLASM, JCL, CL, in the System i context Support teams building applications to execute on System i independent of where the Jazz Server resides Support platform-specific application artifact types (RPG, COBOL, CL, DDS, ) in one place Support EGL language with target i5/os generation and execution Enable 3rd party existing infrastructure to integrate with Jazz SCM inter-operability (MKS Implementer, Aldon Lifecycle Manager, ) Process engine inter-operability Enhance the collaboration opportunities Integrate process and governance into the fabric of the environment 6

7 in the System z context Support teams building applications to execute on System z independent of where the Jazz Server resides Support platform-specific application artifact types (COBOL, PL/I, HLASM, ) in one place Support EGL language with target z/os generation and execution Enable 3rd party existing infrastructure to integrate with Jazz SCM inter-operability (Endevor, Changeman, SCLM, ) Process engine inter-operability Enhance the collaboration opportunities Integrate process and governance into the fabric of the environment IBM Rational Tools Integration with Many opportunities for the IBM tools to integrate with System i and System z IBM Enterprise tools (Rational Business Developer, WebSphere Developer for System z, WebSphere Studio Asset Analyzer, WebSphere Development Studio Client for System i, ) take full advantage of the Jazz technology Custom advisors for Enterprise languages (EGL, Cobol, PL/I, RPG) Enterprise advisor toolkit SCM interoperation with Jazz ClearCase, ClearQuest, SCLM for z/os Impact Analysis and references Suggestions? 7

8 IBM Rational Software Leveraging IBM Rational Enterprise Tools Rational Business Developer EGL artifact with Jazz update and awareness information Demonstration description Demo context and topology Organization with both distributed developers and traditional developers using a Jazz server on System z and DB2/z v9 Some traditional developers are using WDz and SCLM for z/os Developer Toolkit to develop backend COBOL services Distributed developers are using Jazz enabled Rational Business Developer products to use the COBOL services inside J2EE applications using EGL Both sets of developers are using Jazz enabled Lotus Sametime Will also demonstrate standard and extended Jazz functionalities to support the Enterprise Team interactions Process and Advisors to enforce coding guidelines Use of EGL and Cobol as the languages within a project Produce and share Java or COBOL Jazz Build Engine running build scripts for Java and COBOL build Interoperability with an external SCM Impact analysis using links between Enterprise artifacts 8

9 Demo Summary Consolidate multi-platform development (inc. System i and System z ) Improved IT governance Reduced development & maintenance costs Highly improved software quality Jazz has the potential to positively influence all aspects of your Enterprise developments Provide collaboration & governance to cross platform development teams Manage & share between teams, people and stakeholders all the development artifacts in a common way You can rely on highly available & scalable infrastructure using System i and System z strengths Work effectively with multi-discipline teams and partners in different locations 9

10 Questions Thank You Jean-Yves B. Rigolet Alex A. Akilov 10

11 Backup on System i / System z Ensure equivalent behavior with the Jazz Server hosted on System i and System z Support the basic reference Open Source stack Tomcat, Derby, Wildfire Support Value Add stack WAS, DB2, Lotus Sametime Support native file systems System i : QSYS (Library) file system, IFS System z : PDS, SF, HFS, zfs Support JES / jobs for builds Leverage the scalability and QoS found on System i and System z 11

12 RBD Extension on RAD 8 and Jazz 0.6 screenshots Jazz model extension & impact analysis Subset of the OMG s KDM (Knowledge Discovery Metamodel) Search for references between development artifacts Ex: EGL pgm calling a COBOL pgm 12

13 SCLM & Jazz SCM interoperability Jazz SCM interop based on JSR147 Workspace Versioning and Configuration Management One way (SCLM to Jazz) machinery implemented to date Access to Jazz information from w/in RBD extension Governance on EGL artifacts Who delivered an update? When? Why? Online status 13

14 EGL & COBOL source code advisors Guide & enforce coding policies when delivering to the Team according to the project development phase Can use static analysis results, domain specific naming conventions, Jazz handled System i and System z builds 14