Microsoft has won the war for ‘the hearts and minds’ of mid-market customers against the Java camp. Java has failed to gain traction outside of the big enterprise users because it is too heavy (read complex and expensive). Microsoft’s approach is less disruptive and therefore well suited for extending, not just replacing, existing systems. So, how might a classic System i shop take advantage of the .NET Framework and the Windows platform? presentation gives some examples of the potential intersections between a System i server (running core RPG or COBOL programs and a DB2 database) and various Microsoft products and technologies like ASP.NET, SharePoint, Office and CRM.

1. 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

3. LANSA Software Portfolio

5. Modernisation Strategies

7. 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

10. System i and .NET Touch Points

14. 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

20. Business Process Integration