N orthern iS eries U ser G roup Meeting Getting the System i and Microsoft .NET platforms working together Martin Fincham General Manager – EMEA LANSA

LANSA Company Overview Market-leading vendor 20 years in this business 7,000+ customers in 65 countries Multi-million dollar annual R&D budget 300 partners in our global ecosystem IBM and Microsoft are our strategic partners

Market-leading vendor

20 years in this business

7,000+ customers in 65 countries

Multi-million dollar annual R&D budget

300 partners in our global ecosystem

IBM and Microsoft are our strategic partners

LANSA Software Portfolio

Microsoft and LANSA Founders of the Midrange Alliance Program Created in response to customer need Love the System i, frustrated with IBM’s roadmap Sensible Interoperability and Modernisation Harness power and potential of both platforms A Better UI to drive people productivity Transform procedural code to objects for SOA Protect your technology, skills and experience

Founders of the Midrange Alliance Program

Created in response to customer need

Love the System i, frustrated with IBM’s roadmap

Sensible Interoperability and Modernisation

Harness power and potential of both platforms

A Better UI to drive people productivity

Transform procedural code to objects for SOA

Protect your technology, skills and experience

Modernisation Strategies

Microsoft Platform Development Tool Visual Studio Application Server .NET Framework Application Infrastructure Database, Portals, EAI/B2B Core Services Security, Collaboration and Management Smart Client Thin, Rich, Office

Development Tool

Visual Studio

Application Server

.NET Framework

Application Infrastructure

Database, Portals, EAI/B2B

Core Services

Security, Collaboration and Management

Smart Client

Thin, Rich, Office

LANSA Platform Any Relational Database File/Table Central Repository stores Reusable Logic Single Skill Set using High Level Language Deploy application on server of choice Interface independent from application code

What is .NET? Proper name is the .NET Framework Architecture for the real-time enterprise Current version is 3.5 Supports multiple programming languages Primary technologies V2.0 ( ASP.NET, Windows Forms, ADO.NET) Windows Presentation Foundation (XAML) Windows Communication Foundation (WS-*) Windows Workflow Foundation Windows CardSpace

Proper name is the .NET Framework

Architecture for the real-time enterprise

Current version is 3.5

Supports multiple programming languages

Primary technologies

V2.0 ( ASP.NET, Windows Forms, ADO.NET)

Windows Presentation Foundation (XAML)

Windows Communication Foundation (WS-*)

Windows Workflow Foundation

Windows CardSpace

Programming Languages for .NET Visual Basic History as an easy-to-use, applications-oriented tool VB.NET: completely new version of language C# (C-sharp) New language, introduced with .NET Characteristics of C, C++, Java C++ Primary development language for most Windows system programming Can be used in .NET environment

Visual Basic

History as an easy-to-use, applications-oriented tool

VB.NET: completely new version of language

C# (C-sharp)

New language, introduced with .NET

Characteristics of C, C++, Java

C++

Primary development language for most Windows system programming

Can be used in .NET environment

System i and .NET Touch Points

It was Simple with System i One server One operating system One programming language One database One user interface style

One server

One operating system

One programming language

One database

One user interface style

So What Changed? New systems are more complex End-users have new expectations Western labour costs are high Technology directions are fluid Tight coupling is strangling agility Maintenance is crushing innovation

New systems are more complex

End-users have new expectations

Western labour costs are high

Technology directions are fluid

Tight coupling is strangling agility

Maintenance is crushing innovation

We need a Different Approach Technology agnostic Centralised meta data Single skill set and tooling Standards-based interoperability Expose functions as services

Technology agnostic

Centralised meta data

Single skill set and tooling

Standards-based interoperability

Expose functions as services

From System i to SOA 5250 Green Screen Procedural Code Embedded Functions (RPG / COBOL) DB2 Database (integral validation) AS/400, iSeries, System i Components Business Objects Callable Services Any SQL Database (external validation) Windows GUI Rich Web Client Mobile / PDA System i, Microsoft .NET, Linux Data Services Layer Meta Data Repository Application Server Visual Framework Web Services Interface Today Future

Visual Framework Insulates end-users from change Composite applications 5250, DB2, any SQL DB, Web Services Deploy via Windows, Web or .NET New business processes & workflow Eliminate steps, screens, keystrokes Selectively re-write legacy functions and add new functionality

Insulates end-users from change

Composite applications

5250, DB2, any SQL DB, Web Services

Deploy via Windows, Web or .NET

New business processes & workflow

Eliminate steps, screens, keystrokes

Selectively re-write legacy functions and add new functionality

Composite Applications DB2 Query Results Snap-in Refaced 5250 Program Business Object Navigation Flexible System Wide Search Composite Application Sources 5250 Programs Remote Procedure Calls Direct Database Access Visual Components Web Services

5250 Programs

Remote Procedure Calls

Direct Database Access

Visual Components

Web Services

Meta Data Application Server Library of built-in functions That which is common Customer Specific Attributes That which is unique Meta Data Repository Maintain Data Definitions and Rules Separate Business Logic from the UI Component-based Development Portability and Interoperability

Library of built-in functions

That which is common

Customer Specific Attributes

That which is unique

Meta Data Repository

Maintain Data Definitions and Rules

Separate Business Logic from the UI

Component-based Development

Portability and Interoperability

Data Services Layer Benefits Single way to access to all data Reusable data services Fast, simple deployment of solutions Protects data and rules Ensures correctness Packaged Apps Files IBM DB2 XML Data Services Layer Any SQL Database OAM1 OAM2 GW3 Definition Single access layer for all data Abstracts format, location, conventions Data dictionary held in Repository OAMs generated from metadata

Single way to access to all data

Reusable data services

Fast, simple deployment of solutions

Protects data and rules

Ensures correctness

Single access layer for all data

Abstracts format, location, conventions

Data dictionary held in Repository

OAMs generated from metadata

Interoperability Middleware layer Support multiple modes File transfer Remote Procedure Call (RPC) Database access Web Services Visual Data Mapping Process Orchestration Enterprise Service Bus

Middleware layer

Support multiple modes

File transfer

Remote Procedure Call (RPC)

Database access

Web Services

Visual Data Mapping

Process Orchestration

Enterprise Service Bus

Business Process Integration

Summary Combine strengths of System i and .NET Rarely is ‘one-size-fits-all’ the right answer Avoid languages or tools that limit UI, server platform or database choices IBM yesterday, Microsoft today, who’s tomorrow? 5250, Windows, Web, Mobile / PDA, … Use first modernisation project to adopt new software development practices You can start today and vendors can help ;-)

Combine strengths of System i and .NET

Rarely is ‘one-size-fits-all’ the right answer

Avoid languages or tools that limit UI, server platform or database choices

IBM yesterday, Microsoft today, who’s tomorrow?

5250, Windows, Web, Mobile / PDA, …

Use first modernisation project to adopt new software development practices

You can start today and vendors can help ;-)