Can IBM i play with SOA?


Published on

Service Oriented Architecture (SOA) is an architectural style for creating and using business processes, packaged as services, throughout their lifecycle. This short presentation looks at how SOA fits in the world of IBM System i (AS/400, iSeries, IBM i) and how using the LANSA toolset and set you on the right path.

Published in: Technology
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • For a typical System i shop – with a single primary server platform, reams of inhibiting RPG code and a shoestring budget – it can be easy to discount the relevance of new and over-hyped concepts like SOA. But this concept should be closely examined by organisations that run on System i because, contained within a grand vision, there are practical and low-cost steps that can be applied today for: -    Modernising RPG or COBOL applications -    Reducing application development and maintenance costs -    Lowering the cost of integrating different systems -    Accelerating the delivery of new applications This presentation will give practioners the guidance they need to develop a plan for SOA adoption. Special consideration is given to the constraints under which organisations with a substantial commitment in System i technologies must work to protect and extend their legacy investments.
  • Can IBM i play with SOA?

    1. 1. I’m on System i . Can i play with SOA? Keeping your System i relevant in a Service-oriented World Martin Fincham General Manager - Europe, Middle East and Africa LANSA
    2. 2. WARNING ! This is not a presentation about Web Services This is about adoption of a Services-oriented Architecture
    3. 3. SOA: The Consultant’s View
    4. 4. It was Simple with System i <ul><li>One server </li></ul><ul><li>One operating system </li></ul><ul><li>One programming language </li></ul><ul><li>One database </li></ul><ul><li>One user interface style </li></ul>
    5. 5. So What Changed? <ul><li>New systems are more complex </li></ul><ul><li>End-users have new expectations </li></ul><ul><li>Western labour costs are high </li></ul><ul><li>Technology directions are fluid </li></ul><ul><li>Tight coupling is strangling agility </li></ul><ul><li>Maintenance is crushing innovation </li></ul>
    6. 6. We need a Different Approach <ul><li>Technology agnostic </li></ul><ul><li>Centralised meta data </li></ul><ul><li>Single skill set and tooling </li></ul><ul><li>Standards-based interoperability </li></ul><ul><li>Expose functions as services </li></ul>
    7. 7. What is a Service? <ul><li>Programs that perform a specific function </li></ul><ul><li>Designed to be used by multiple apps </li></ul><ul><li>Generic Implementation </li></ul><ul><ul><li>Used by different applications for unrelated purposes </li></ul></ul><ul><ul><li>Examples: “Messaging” “User authentication” </li></ul></ul><ul><li>Business Object Related </li></ul><ul><ul><li>Used by multiple applications but for a similar purpose </li></ul></ul><ul><ul><li>Examples: “get customer information” “create an order” </li></ul></ul>
    8. 8. Composition of a Service <ul><li>Service Implementation </li></ul><ul><ul><li>Encapsulate the business logic (functionality) that makes up the service </li></ul></ul><ul><ul><li>Can be created with any language </li></ul></ul><ul><li>Service Interface </li></ul><ul><ul><li>The “contract” between programs that defines how to access the service </li></ul></ul><ul><ul><ul><li>Defines all necessary data and exchanges </li></ul></ul></ul><ul><ul><ul><li>Could use XML, SOAP, HTTP, Messaging Middleware or shared memory to pass data </li></ul></ul></ul><ul><ul><ul><li>When it uses SOAP to define the data and WSDL to define the interaction, it is called a Web Service </li></ul></ul></ul>
    9. 9. What is an Architecture? <ul><li>A software architecture defines how the components of an application are organised </li></ul><ul><li>A ‘blueprint’ defining how applications will service both current and future needs </li></ul><ul><ul><li>Defining how components will be built and implemented </li></ul></ul><ul><ul><li>Defining how parts of an application relate and inter-communicate </li></ul></ul><ul><li>A plan that manages how an organisation meets their IT objectives </li></ul><ul><li>Examples </li></ul><ul><ul><li>LANSA, Microsoft .NET, J2EE, CORBA, COM, … </li></ul></ul>
    10. 10. 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, Unix Data Services Layer Meta Data Repository Application Server Visual Framework Web Services Interface Today Future
    11. 11. Visual Framework <ul><li>Insulates end-users from change </li></ul><ul><li>Composite applications </li></ul><ul><ul><li>5250, DB2, any SQL DB, Web Services </li></ul></ul><ul><li>Deploy via Windows, Web or .NET </li></ul><ul><li>New business processes & workflow </li></ul><ul><ul><li>Eliminate steps, screens, keystrokes </li></ul></ul><ul><li>Selectively re-write legacy functions and add new functionality </li></ul>
    12. 12. Composite User Interface DB2 Query Results Snap-in Refaced 5250 Program Business Object Navigation Flexible System Wide Search <ul><li>5250 Programs </li></ul><ul><li>Remote Procedure Calls </li></ul><ul><li>Direct Database Access </li></ul><ul><li>Visual Components </li></ul><ul><li>Web Services </li></ul>Composite Application Sources
    13. 13. Meta Data Application Server <ul><li>Library of built-in functions </li></ul><ul><ul><li>That which is common </li></ul></ul><ul><li>Your Intellectual Property </li></ul><ul><ul><li>That which is unique </li></ul></ul><ul><li>Meta Data Repository </li></ul><ul><ul><li>Maintain Data Definitions and Rules </li></ul></ul><ul><ul><li>Separate Business Logic from the UI </li></ul></ul><ul><ul><li>Component-based Development </li></ul></ul><ul><ul><li>Portability and Interoperability </li></ul></ul>
    14. 14. Data Services Layer <ul><li>Single way to access to all data </li></ul><ul><li>Reusable data services </li></ul><ul><li>Fast, simple deployment of solutions </li></ul><ul><li>Protects data and rules </li></ul><ul><li>Ensures correctness </li></ul>Benefits Packaged Apps Files IBM DB2 XML Data Services Layer Any SQL Database GW1 GW2 GW3 <ul><li>Single access layer for all data </li></ul><ul><li>Abstracts format, location, conventions </li></ul><ul><li>Data dictionary held in Repository </li></ul><ul><li>Gateways generated from metadata </li></ul>Definition
    15. 15. Interoperability <ul><li>Middleware layer </li></ul><ul><li>Support multiple modes </li></ul><ul><ul><li>File transfer </li></ul></ul><ul><ul><li>Remote Procedure Call (RPC) </li></ul></ul><ul><ul><li>Database access </li></ul></ul><ul><ul><li>Web Services </li></ul></ul><ul><li>Visual Data Mapping </li></ul><ul><li>Process Orchestration </li></ul><ul><li>Enterprise Service Bus </li></ul>
    16. 16. Point. Click. Connect.
    17. 17. Enterprise Service Bus Middleware that enables software to run in parallel on different platforms, written in different programming languages.
    18. 18. SOA Strategy Options <ul><li>Some will never need SOA </li></ul><ul><ul><li>Just new tools, skills and best practices </li></ul></ul><ul><ul><li>Modernise the front-end, leave the code </li></ul></ul><ul><li>Some just mean interoperability </li></ul><ul><ul><li>Web Services is an open, standard and lightweight implementation of SOA </li></ul></ul><ul><li>Some need to re-architect systems </li></ul><ul><ul><li>Inflexible, poorly structured, lack of skills, mothballed, missing functionality, heterogeneous environment, … </li></ul></ul>
    19. 19. I’m on System i . Can i play with SOA? YES !