Development and Deployment Productivity: Middleware Company ...

855 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
855
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Services vs. Application layer. Importance of reusability at application layer. Services at two layers of architecture Logical services: these are the things that represent functionality. Can be part of COTS application or might need to be built. Applications services e.g. logical services models and application structure = architecture style. Basically manipulating pieces of functionality represented by sw components, applications, subsystems, Example: Business workflow – long running, multi-step operations, requiring coordination (may contain both synchronous and asynchronous elements). Business components: Implement the business logic of an application. EG., perform a calculation
  • Context: Position VS, WinFX, Longhorn together. If anyone asks, the locations of the individual graphics within a year don’t have much significance: there’s just not much room on the slide to fit the graphics in  These are some of the key milestones you can expect to see. Visual Studio 2005 will ship in the middle of 2005, and you can expect to see a Longhorn beta at around the same time. WinFX is being developed in tandem with Longhorn and will ship for existing Windows releases at the same time as Longhorn both in beta and in final form. WinFS will be available in beta by the time that Longhorn ships.
  • Key issue: How does integration fill a critical role within the types of challenges customers are facing today Not just about software/applications – very people oriented Access to business functions About the processes that deliver value Top and bottom line results
  • Key issues: What role can Host Integration Server play in an interoperable solution How can reliance on mainframe/mid-range systems be reduced over time
  • Key issues: How might a single business make best use of Microsoft technologies with optimized ROI What are some buy vs. build considerations and the role of custom development Consider: the fit of LOB applications, horizontal tools, and infrastructure Some comparisons to SQL DTS (or ETL): Event based vs. scheduled Batch vs. real-time Records vs. documents/messages .NET Framework is fundamental: Core of technology Natural transition from code to business processes Deep power tool for integration Could do everything! (if you had enough time and skills) Links to SharePoint: Collaborative scenarios Single sign-on Workflow Ad-hoc vs. structured processes
  • Steve Schwartz does “direct” stuff in his talk so I’m going to start with queued and refer to direct by reference to emphasise a key point only.
  • #2 amplified: The why to the second point is: Because both can be done inside a single SQL Server transaction, controlling these two actions using the significantly slower Distributed Transaction Coordinator (DTC) isn’t required. If another kind of resource manager is involved, however, such as another DBMS, DTC will be used to coordinate the transaction. #3 amplified: Communication that can benefit from the conversational approach that SSB provides. All messages sent on a particular conversation are directed to a specific receiver, for example, rather than being read by whatever application happens to next read from that queue. If achieving higher performance requires multiple simultaneous reader applications accessing the same queue, using conversations avoids a number of common errors. Have the MSMQ discussion here: Needs SQL vs. Windows (although it is in SQL Express) Doesn’t support in-memory Sticky conversations with Indigo as well at the message layer and more with a broker)
  • #2 amplified: The why to the second point is: Because both can be done inside a single SQL Server transaction, controlling these two actions using the significantly slower Distributed Transaction Coordinator (DTC) isn’t required. If another kind of resource manager is involved, however, such as another DBMS, DTC will be used to coordinate the transaction. #3 amplified: Communication that can benefit from the conversational approach that SSB provides. All messages sent on a particular conversation are directed to a specific receiver, for example, rather than being read by whatever application happens to next read from that queue. If achieving higher performance requires multiple simultaneous reader applications accessing the same queue, using conversations avoids a number of common errors. Have the MSMQ discussion here: Needs SQL vs. Windows (although it is in SQL Express) Doesn’t support in-memory Sticky conversations with Indigo as well at the message layer and more with a broker)
  • Link to case study: http://www.microsoft.com/resources/casestudies/CaseStudy.asp?CaseStudyID=14962
  • Key issue: How does BizTalk provide a design surface for business processes Simple : Drag & drop Extended : Use of expressions and message construction Sophisticated : inline scripting or embedded .NET assemblies
  • (Click SharePoint to start animation) Key issues: How can InfoPath fit in easily with a deployed business process hosted by BizTalk What types of solutions can expand upon this model Broader workflow via partners like K2.net, Captaris and Ultimus also available InfoPath not the only user experience – SharePoint, ASP .NET, etc. Consider: using Reporting Services on the back-end Consider: BizTalk can generate forms (and form templates) on demand via InfoPath SDK
  • Link to case study: http://www.microsoft.com/resources/casestudies/CaseStudy.asp?CaseStudyID=14962
  • Key issue: Where has BizTalk been used to address high-performance enterprise scenarios Marks & Spencer – no unplanned downtime for 24 months Variables to consider: message size, orchestration complexity, # systems integrated, etc. More BizTalk customers than any other integration product
  • <none>
  • Development and Deployment Productivity: Middleware Company ...

    1. 1. Windows and .NET for iSeries Interoperability Charles Machalani, Solution Architect [email_address] Karen McGregor, .NET Architect Evangelist [email_address] Microsoft Canada
    2. 2. Before we start …. <ul><li>What do you currently interoperate with? </li></ul><ul><li>What scenarios do you implement? </li></ul><ul><li>What Microsoft technology do you have, what scenarios do you see for integrating with iseries? </li></ul>
    3. 3. Microsoft .NET Software to connect information, people, systems and devices Our vision : provide the platform to rapidly build and evolve connected applications Devices Information People Systems
    4. 4. What is the Business value? <ul><li>Faster Time to market </li></ul><ul><li>Lower cost to produce </li></ul><ul><li>Lower cost to deploy </li></ul><ul><li>More flexibility in deployment options (scale up vs. scale out) </li></ul><ul><li>Single standard for internal and external integration </li></ul><ul><li>Shorter cycles to deploy changes </li></ul><ul><li>Short learning curve </li></ul>
    5. 5. User Interface Layers Office XP DOCUMENT I/O ASP.NET Mobile Toolkit THIN DEVICE UI Sharepoint Server USER DOC WORKFLOW Exchange Workflow COLLAB. WORKFLOW ASP.NET WebForms Digital Dashboard WEB BROWSER UI ASP.NET WEB UI .NET Windows Forms SMART CLIENT UI WINDOWS UI OFFLINE CLIENT UI Process and UI Outlook XP Exchange Forms MESSAGING UI XML Web Services UI Components UI Process Components
    6. 6. Services Layer Business Process Automation ADO.NET DataSets BizTalk Messaging Biz Document Exchange Biz Document Transformation Business Workflows, Components, Entities and Service Interfaces XML-Serializable Objects XML Document Management Long-Running Conversations XML Web Services ASP.NET Web Services Persistent Messaging MSMQ Listeners Application Endpoints .NET Remoting & DCOM Distributed Transaction Mgmt Enterprise Services (Windows) Role-Based Security Business Component Hosting .NET frameworks Enterprise Services (Windows) BizTalk Server Business Workflows Business Components Business Entities Service Interfaces
    7. 7. Data Access and Services Agents Data Access Components Web Service .NET Framework BizTalk Adaptors (300+) VS.NET Web Proxy SQL DB2 LDAP WebSphere CICS iSeries Legacy CRM / ERP SQL Server Adapters Exchange 2005 ADO.NET Providers WSE Application Data Other Data Sources Messaging Data Legacy Systems XML Web Services Other Services Data Access Logic Components Service Agents Data Sources Services
    8. 8. .NET Roadmap 2005 2006 2007 Windows Workflow Enterprise Library 2.0 2005 Beta Beta Beta Database Developer
    9. 9. Networking Data Management UNIX Systems Integration XML Web Services Industry Standards Languages Applications Identity Legacy Hosts
    10. 10. Business seeks integration for big wins <ul><li>Collaboration </li></ul><ul><li>Partnerships </li></ul><ul><li>Supply & distribution </li></ul><ul><li>Customer service </li></ul><ul><li>Business Intelligence </li></ul><ul><li>Sales </li></ul>Samsung enables a $3M annual benefit from real-time view of orders, sales, shipping and inventory Virgin Megastore realizes 50% better fraud prevention with integrated systems and process Swedish Hospital delivers better patient care at less cost through an end-to-end experience
    11. 11. Integration Examples <ul><li>Get more value from your iSeries…. </li></ul><ul><ul><li>For EAI/B2B using Visual Studio.NET, IIS and BizTalk Server (inc. Host Adapters) </li></ul></ul><ul><ul><li>For BI using Microsoft SQL Server 2005 Analysis and Reporting Services </li></ul></ul><ul><ul><li>For BPA and Human Workflow using BizTalk Server 2006 and SharePoint Services </li></ul></ul>
    12. 12. <ul><li>Web Services simplified usability, improved access time to ERP data and enabled immediate response and feedback to customers </li></ul><ul><li>iSeries data, routines and business logic are not duplicated but rather reused with the .NET environment </li></ul><ul><li>Worked with Microsoft Certified Partner Ordina to deploy new Web interface using Microsoft® Windows Server System TM and Host Integration Server 2004 to bridge the IBM iSeries ERP application </li></ul><ul><li>IBM iSeries terminal based ERP application was not user-friendly and lacked agility to respond to customer needs </li></ul><ul><li>Deploy Internet application to provide up-to-date product information and enable customers to place and follow up orders online </li></ul>Offered its fifty biggest customers the ability to order online and to consult all information about deliveries and past orders via the Internet . &quot;This project improves our services and lays the foundation for further automation. The data on the iSeries system can be easily and immediately used for other applications from now on.&quot; Eddy Evens, General manager, Raedschelders Raedschelders
    13. 13. Deploy hosts in modern scenarios BizTalk, Windows and/or .NET connectivity TCP/IP and SNA Network Integration TCP/IP and SNA COM, XML, Message Queuing Application Integration APPC, CPI-C, DPL, LUA, BMS, 3270, MQ ADO, OLEDB, ODBC Data Integration DDM (DRDA & RLIO), XA, TDS, CLI, DBLIB IBM zSeries mainframe & iSeries midrange resources Host Integration Adapters Integrated applications, web portals, smart clients BizTalk and .NET
    14. 14. Planning value from an integrated platform Schedules Events Data Processes Deliver on human value Run business units Control the details Retain and review .NET Framework SQL DTS & SSIS BizTalk Server SharePoint Server/Office SQL Relational & Analysis “ Indigo”
    15. 15. Evaluate Service Oriented Architecture (SOA) <ul><li>Means to help build distributed, interoperable systems </li></ul><ul><ul><li>Deliver new capabilities from existing assets </li></ul></ul><ul><ul><li>Consolidate interfaces and protocols </li></ul></ul><ul><ul><li>Model diverse business functions in common way </li></ul></ul><ul><ul><li>Create composite, collaborative applications </li></ul></ul><ul><li>Consists of principles + specifications + technologies </li></ul><ul><ul><li>Service: an end-point capable of dispatching a task </li></ul></ul><ul><li>Analysis: What services do we define? </li></ul><ul><li>Design: How do we conform to best practices? </li></ul><ul><li>Management: How do we monitor and maintain? </li></ul>
    16. 16. Demystifying MS Integration Technologies <ul><li>How do I categorize these capabilities? </li></ul><ul><li>What are the core scenarios per technology? </li></ul><ul><li>Show me </li></ul><ul><li>What if my business scenario requires more than one technology?! </li></ul>
    17. 17. Technologies by Message & Data Microsoft’s Messaging Integration Products Microsoft’s Data Integration Products SQL Integration Services Host Integration Server IBM Mainframe & Midrange connectivity MSMQ Message queuing for Windows Data integration service deeply integrated with SQL WCF Unified Framework for building SOA apps on Windows SQL Service Broker Reliable messaging deeply integrated with SQL BizTalk Server Business process and integration server SQL Replication Data synchronization service deeply integrated with SQL
    18. 18. Microsoft Messaging Technologies Microsoft’s Messaging Integration Products WCF Unified Framework for building SOA apps on Windows SQL Service Broker Reliable messaging deeply integrated with SQL MSMQ Message queuing BizTalk Server Business process and integration server
    19. 19. Message Styles Queued Broker Direct Application Application <ul><li>BizTalk Server </li></ul><ul><li>MSMQ </li></ul><ul><li>WCF </li></ul><ul><li>SSB </li></ul><ul><li>HIS </li></ul><ul><li>RPC, oRPC </li></ul><ul><li>SOAP v1 </li></ul><ul><li>WCF </li></ul><ul><li>HIS </li></ul>Technologies <ul><li>Loosely coupled </li></ul><ul><li>Temporally uncoupled </li></ul><ul><li>Address uncoupled </li></ul><ul><li>Protocol agnostics process </li></ul><ul><li>More loosely coupled </li></ul><ul><li>Temporally uncoupled </li></ul><ul><li>Address coupled </li></ul><ul><li>Simple </li></ul><ul><li>Coding within the app </li></ul><ul><li>Temporal and address coupled </li></ul>Advantages Challenges <ul><li>Even more concepts </li></ul><ul><li>More concepts </li></ul><ul><li>Protocol issues </li></ul><ul><li>N(N-1) interfaces </li></ul><ul><li>Interface coupling </li></ul><ul><li>Protocol and format issues </li></ul>
    20. 20. Queued: Messaging Queuing (MSMQ) <ul><li>Key features </li></ul><ul><ul><li>Queue, APIs (System.Messaging and WCF), MMC </li></ul></ul><ul><ul><li>Either In memory and durable </li></ul></ul><ul><ul><li>Not conversational (no notion of session) </li></ul></ul><ul><li>When to use </li></ul><ul><ul><li>Asynchronous communication is required between two or more Windows applications </li></ul></ul><ul><ul><li>When the sender and receiver might not be running at the same time </li></ul></ul><ul><ul><li>When message-level logging is required </li></ul></ul>
    21. 21. Queued: SQL Server Service Broker <ul><li>Key features </li></ul><ul><ul><li>T-SQL constructs </li></ul></ul><ul><ul><li>Conversational, reliable styles </li></ul></ul><ul><li>When to use </li></ul><ul><ul><li>Connecting stored procedures in SQL Server with another instance in a messaging paradigm </li></ul></ul><ul><ul><li>Applications that must receive a message and perform an update to SQL Server 2005 within the same transaction </li></ul></ul><ul><ul><li>Need sticky conversations </li></ul></ul>
    22. 22. Queued or Direct: WCF <ul><li>Key features </li></ul><ul><ul><li>Simplified, re-factored, more capable distributed component stack </li></ul></ul><ul><ul><li>Support for industry standard web services (WS-Sec,TX, RM…) </li></ul></ul><ul><li>When to use </li></ul><ul><ul><li>Direct web services communication </li></ul></ul><ul><ul><li>Direct Windows communication </li></ul></ul><ul><ul><li>Queued Windows communication through MSMQ (future SSB) </li></ul></ul>
    23. 23. Countrywide increases productivity for tax bill procurement by 25 percent “ Our new solution based on Microsoft .NET is helping us improve efficiency through process automation, support for workflows and work queues, and improved planning and reporting.” Paramjit Chumber, Senior Vice President and Chief Information Officer, Countrywide Tax Services Corporation <ul><li>Wanted to integrate and streamline the process of obtaining tax bills </li></ul><ul><li>AS/400 application had text-based UI and lacked basic workflow features </li></ul><ul><li>All work was being done manually </li></ul><ul><li>Built a new solution using the Microsoft ® .NET Framework and BizTalk ™ Server 2004 </li></ul><ul><li>Can resolve some work automatically </li></ul><ul><li>Supports work queue management </li></ul><ul><li>Improves planning and reporting </li></ul><ul><li>4 of 56 technicians freed to do other jobs </li></ul><ul><li>25 percent productivity increase for remaining users </li></ul><ul><li>25 percent decrease in cycle times </li></ul><ul><li>365 hour reduction in planning time (year-to-date) </li></ul>
    24. 24. Define the flow and behavior of integrations BizTalk orchestration Decision Send Receive Rules Send Custom code
    25. 25. Mix people and automated processes BizTalk Servers Web Services SQL Server Outlook SharePoint InfoPath Apps or embedded flows InfoPath BAM & SQL RS
    26. 26. Broker: BizTalk Server <ul><li>Key features </li></ul><ul><ul><li>Architecture for the intermediary: End-Point “Plug and Play”, tracking, management </li></ul></ul><ul><ul><li>Business process (State Management), activity monitoring, rules </li></ul></ul><ul><li>When to use </li></ul><ul><ul><li>Connecting multiple applications together including applications you didn’t write (e.g MQSeries, SAP, etc) </li></ul></ul><ul><ul><li>Implementing integration processes that run for hours, days, or weeks, and include business rules </li></ul></ul><ul><ul><li>B2B integration requiring industry standards such as EDI, RosettaNet and HIPAA </li></ul></ul><ul><ul><li>Creating business processes that give information workers real-time visibility into an integrated process </li></ul></ul>
    27. 27. <ul><li>Expected savings of U.S.$575,000 over comparable solutions </li></ul><ul><li>Expected $1.8 million increase in overall revenue </li></ul><ul><li>Increased store traffic from improved campaign analysis </li></ul><ul><li>Evaluated business intelligence software from Hyperion, Cognos, and Applix, but chose Microsoft ® Windows Server System TM as most cost-effective and easiest to use </li></ul><ul><li>Worked with Xavor and Analysis Team to build a data-gathering and data-analysis solution </li></ul><ul><li>Wanted to analyze its daily operations data more quickly and in greater depth </li></ul><ul><li>Needed to provide simpler way for key staff to access crucial business metrics </li></ul>Entertainment retailer expects store data analysis to increase sales by $1.8 million “ With Windows Server System and the .NET Framework, we built a comprehensive solution to a pressing business problem. Now, we can influence our results instead of just reviewing them.” Robert Fort, Director of IT, Virgin Entertainment Group, North America
    28. 28. Integration performance delivered <ul><li>EAI Scenarios </li></ul><ul><li>Marks & Spencer – 2500 msgs/sec </li></ul><ul><li>Lotte Magnet – 100 msgs/sec </li></ul><ul><li>London Drug – 52 msgs/sec </li></ul><ul><li>B2B Scenarios </li></ul><ul><li>Akzo Nobel – 5000 msgs/sec </li></ul><ul><li>Osram Sylvania – 800 msgs/sec </li></ul><ul><li>New York Times – 140 msgs/sec </li></ul>>5000 customers rely on BizTalk for high-performance and high business value solutions
    29. 29. Microsoft Data Integration Technologies Microsoft’s Data Integration Products SQL Integration Services Data integration service deeply integrated with SQL SQL Replication Data synchronization service deeply integrated with SQL
    30. 30. SQL Integration Services <ul><li>Key Features </li></ul><ul><ul><li>ETL (Extract, Transform, Load) </li></ul></ul><ul><ul><li>Error Handling & Fuzzy Logic for data cleansing </li></ul></ul><ul><ul><li>DB2 & Oracle data providers included </li></ul></ul><ul><li>When to use </li></ul><ul><ul><li>Combining information from a group of operational databases into a data warehouse </li></ul></ul><ul><ul><li>Transferring data from one DBMS to one or more other DBMSs </li></ul></ul><ul><ul><li>Loading data into SQL Server databases from flat files, spreadsheets, and other diverse data sources </li></ul></ul>
    31. 31. SQL Replication Services <ul><li>Key features </li></ul><ul><ul><li>Incremental changes </li></ul></ul><ul><ul><li>User driven UI </li></ul></ul><ul><ul><li>Support Across SQL Server, CE </li></ul></ul><ul><li>When to use </li></ul><ul><ul><li>Replicating data SQL Server tables (offline, client/server). </li></ul></ul><ul><ul><li>Replication from and to Oracle and IBM databases </li></ul></ul>
    32. 32. iSeries Customers and .NET Self-service web-based application using BizTalk for iSeries integration http://www.microsoft.com/casestudies Plus: Sinclair Broadcast Group, Piedmont Behavioural Healthcare, Lance, Hope Network, Dearborn Wholesale Grocers, Labatt Food Service, Borgata Hotel/Casino, Dell, Affiliated Computer Services, Rock-Tenn … eSkye Alticor, Sandvik, St Louis Zoo BI and data warehousing solutions in SQL 2005 using data from DB2/400 Thomas Miller & Co. XML for claims processing, using data replication for iSeries integration Cbk Visual RPG .NET for Sales Force Automation
    33. 33. I Hate Making Choices <ul><li>Often your scenario will require multiple patterns: </li></ul><ul><ul><li>Aggregate bulk data from multiple stores to SQL. Enough stock? Reorder a part </li></ul></ul><ul><ul><ul><li>SSIS and BTS </li></ul></ul></ul><ul><ul><li>Receive a message through a Web Service and send to a mainframe </li></ul></ul><ul><ul><ul><li>WCF and HIS </li></ul></ul></ul><ul><li>Shared technologies provide strong interop points </li></ul>
    34. 34. The Good News MSMQ WCF SQL Server 2005 Service Broker BizTalk Server 2006 Host Integration Server 2006 SQL Server 2005 Replication SQL Server 2005 Integration Services NET FW 2.0 VS 2005 Designers Platform Interop Support XML SKU Web Services Numerous Numerous ODBC OLEDB OLEDB, ODBC Web Services Windows Windows SQL 2005 Express+ BTS 2006 HIS 2006 SQL 2005 SKU+ SQL 2005 Standard+ Comprehensive capabilities for integration on the Microsoft platform
    35. 35. Microsoft’s Vision <ul><li>Improve the application platform </li></ul><ul><ul><li>Make application development easier </li></ul></ul><ul><ul><li>Make application deployment simpler </li></ul></ul><ul><ul><li>Make application management more cost efficient </li></ul></ul><ul><li>Provide operational excellence </li></ul><ul><li>Make everything universally interoperable </li></ul>

    ×