Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (13)
Similar to Impact 2014 IEC1159 - Trends in Integration & Governance
Similar to Impact 2014 IEC1159 - Trends in Integration & Governance (20)
Recently uploaded
Recently uploaded (20)
Impact 2014 IEC1159 - Trends in Integration & Governance
- 1. © 2014 IBM Corporation IEC1159: IBM Integration & Governance Nicola Hills Development Director, WebSphere Integration & Governance @nickiehills
- 2. Please Note IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
- 3. General Trends & Directions
- 4. 4 Trends & Directions 1) SOA It may not be a high fashion trend, but it is the implementation trend, this is actually what we see clients building today
- 5. 5 Trends & Directions 1) SOA 2) Mobile ● API management → mobile accelerators ● IIB Patterns 1) For IBM Worklight 2) For IBM MessageSight
- 6. 6 Trends & Directions 1) SOA 2) Mobile 3) Cloud Planning for Cloud Plans & Roadmaps Convergence of tasks and approaches Adventures in Cloud Cast Iron & API Management LIVE HVEs – All products IIB Chef scripts Hybrid Cloud IIB Cast Iron Cloud First API Management Cloud Integration with BlueMix
- 7. 7 Trends & Directions 1) SOA 2) Mobile 3) Cloud 4) Shift in user / user expectations Simple/Obvious Open Extendable
- 8. 8 Trends & Directions 1) SOA 2) Mobile 3) Cloud 4) Shift in user / user expectations 5) Analytics Services APIs Flows Flow content
- 9. 9 Trends & Directions 1) SOA 2) Mobile 3) Cloud 4) Shift in user / user expectations 5) Analytics 6) Industry Relevance - HL7 - DICOM - OPC - MQTT - Tlog - POSLog - SO8583SO8583 - NACHANACHA$
- 10. IBM Integration Bus Previously known as: WebSphere Message Broker (WMB) & WebSphere Enterprise Service Bus (WESB)
- 11. The IBM Integration Bus V10 Beta is now open • Try out future features, provide feedback and influence direction • Register at www.ibm.com/software/products/en/integration-bus-advanced Try out a recent open beta driver this week (session IEC-1492) • This is in addition to the V9 lab (IEC-1152) • Weds 3.45pm – 6pm in Murano 3303 – Register for either 3.45pm – 4.45pm or 5pm – 6pm slots Introducing IBM Integration Bus V10 Open Beta 11 Open
- 12. If you look at the Open Beta today what will you see ● Simplification – Greatly improved install (you are only going to have time to grab an instant coffee) – Removal of MQ as a Pre-req ● First class support still for MQ, but no long a must have if you choose not to.
- 13. 13 § New IIB initiative to develop integration components as open source – Part of continuing tradition of IIB supporting open standards – Source freely available on popular Github website under flexible Eclipse Public License – Community contributions (including modifications) actively encouraged! – Fully supported technologies delivered into IIB as appropriate § Varied initial contributions targeting transferrable, embeddable assets – MQTT Client connectors • Easy-to-use inbound and output connectors to MQTT servers • Uses open framework for platform-independent connectors – DFDL Schemas for popular industry formats • E.g. HL7, ISO8583, IBM4690-TLOG, NACHA, PCAP, EDIFACT – Chef cookbooks for simplified IIB provisioning • Customizable scripts allows building of complete IIB environments – Tools for easier conversion between integration products • Initially targeting WESB to IIB - Source for common integration patterns (e.g. event filter) Open Technologies for Integration
- 14. And don't forget the IBM Integration Community www.ibm.com/developerworks/connect/integration ● Articles ● Links ● Updates ● Including WESB migration Learn, Input, Participate ! @IBMintegration
- 15. 15 “Conscious Coupling” of our ESB Technologies Continues as planned No rush to move (WESB EoS Announced: 2018) Work with us to plan your activities Phased Approach Phase I shipped in IIV v9 as planned Phase II under development ➢ Framework on GitHub
- 16. IBM Integration Bus This Week – Selected Sessions Monday • 2.30-3.30 Palazzo H – Integration Featured Session • 2.30-5.00 Murano 3305 – Healthcare Integration Lab • 4.00-5.00 Palazzo H – What's New in IIB • 5.15-6.15 Palazzo H – Introduction to IIB Tuesday • 10.30-11.30 Palazzo H – Cloud Integration Options • 10.30-11.30 San Polo 3502 – Meet The Experts • 1.00-2.00 Palazzo H – WESB Conversion • 1.00-2.00 Marcello 4403 – IIB Retail Integration Pack • 1.00-3.15 Murano 3303 – IIB V9 Lab • 2.15-3.15 Palazzo H – Designing for Performance • 3.45-4.45 Palazzo H – Mobile Integration • 5.00-6.00 Palazzo H – DFDL Introduction • 5.00-6.00 Marcello 4402 – Manufacturing in IIB 16
- 17. IBM Integration Bus This Week – Selected Sessions Wednesday • 10.30-11.30 Palazzo H – .NET Integration • 1.00-2.00 Palazzo H – Effective Application Development • 1.00-2.00 Marcello 4403 – IIB Healthcare Integration Pack • 1.00-2.00 San Polo 3503 – Meet The Experts (Repeat) • 2.15-3.15 Palazzo H – Effective Administration • 3.45-4.45 Palazzo H – Applications, Libraries, APIs • 3.45-6.00 Murano 3303 – IIB Open Beta Lab • 5.00-6.00 Palazzo H – Transformation Options in IIB Thursday • 9.00-10.00 Palazzo H – Predictive Analytics • 10.30-11.30 Palazzo H – BPM Integration • 1.00-2.00 Palazzo H – Modelling Industry Formats • 2.15-3.15 Palazzo H – What's New in IIB (Repeat) 17
- 19. 19 Q4 2013 IIB Retail Pack 1.0 IBM's plans, directions, and intent are subject to change or withdrawal •Q4 2013 •IIB Retail Pack 1.0 Q1 2014 IIB Healthcare Pack 3.0 IIB vNext Q4 2013 IIB 9.0.0.1 WebSphere Commerce Sterling Order Management TLog to POSLog Web User Interface IIB Retail Pack vNext Web User Interface HL7 Error Handling Improvements Home Health Pattern HL7 Transformation Pattern IIB Industry Packs Roadmap
- 20. 20 What’s new in IIB Retail Pack v1.0 § IIB Retail Pack v1.0 released in December 2013 – Follows the success of WMB Healthcare Connectivity Pack § Integration of WebSphere Commerce with Sterling Order Management – Connects Pricing and Promotions modules (WCS) – Connects Inventory and Order modules (SOM) – 6 Applications, 19 integration flows § Integrating Point of Sale with Enterprise – Pattern converts TLog to POSLog – Real-time data feeds from Point of Sale to Enterprise – POSLog as canonical feed – ARTS Operational Data Model integration § Web User Interface – Business views and Operational views – Revenue breakdown across PoS and store location – Operational views to understand retail flow activity
- 21. 21 What’s new in IIB Healthcare Pack v3.0 § IIB Healthcare Pack v3.0 released in March 2014 – 3rd release building on top of existing functions including HL7 connectivity, DICOM, ATNA, MedicalDevice connectivity and Data Analysis Profiles § New Web User Interface – Clinical Application monitoring – Operational views to understand flow activity § HL7 Transformation Pattern – Generates graphical data maps for creation of HL7 messages from scratch – Assigns for individual fields in the MSH § HL7 Error handling enhancments § Home Health Pattern – Generates message flows to support a WAN interface – SOAP/HTTP interface using the IHE industry standard “CommunicatePCDData” WSDL – Security PEP node for SAML Token security (with external STS) – Mapping solution for all 3 forms of acknowledgement
- 22. 22 Manufacturing and IBM Integration Bus Statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. § IIB and Manufacturing – Statement of Direction released on 22nd April 2014 § Plant Connectivity De Facto Standards – Connectors and patterns that support current OPC industry standards for integration of plant and machinery data and events, including a small number of vendor-specific implementations § Plant Connectivity Emerging Standards – Support for emerging OPC Unified Architecture standards to allow broader integration to the enterprise § Enterprise Connectivity – Integrations and connectors, including MQ Telemetry Transport (MQTT), which facilitate the transmission of data from remote locations – Web-based interface to provide operational views of data published from plant and machinery
- 24. WebSphere Service Registry and Repository v8.5 24
- 25. 25 Google-style search Collection filters Email owner Service catalog view Download service definition New in v8.5 New in v8.5 New in v8.5 New in v8.5
- 26. New in v8.5 New in v8.5 Email Consumers New in v8.5 Managing the dashboard
- 27. Service endpoint protection Controlling consumption Endpoint routing
- 28. 28 Control - Workload Management Policy Author and attach workload management policies to control IBM Integration Bus flows at runtime New in v8.5
- 30. Browser Browser Browser Browser Fewer requests from browser to server, with more compression More asynchronous requests WSRR WSRRv8.5 WSRR WSRRv8.5 UI Performance Improvements New in v8.5
- 31. APIs & Services Some superficial differences… APIs SOA Terminology APIs Services Associated Technologies JSON, REST, HTTP Web services, SOAP, XML Applications Mobile apps…- Web, Enterprise apps …yet many similar characteristics Re-usable Abstraction of a repeatable task Composable Encapsulates functionality Well-defined interfaces Governable Shareable
- 32. Two similar worlds converging Service Management API Management Mainly about Services Mainly about APIs Govern services through the lifecycle Expose APIs to the Web, manage them to prevent chaos in usage Began with Web Services Began with REST 100’s of services Smaller number of APIs Typically internal, behind firewall External and Internal Driven by Enterprise Architects Driven by Business, Marketing, Mobile teams, Innovation teams Governs with a Stick Governs with a Carrot Established market presence Newer in market Contracts enforced with ESBs and Gateways Security and Entitlements controlled by Gateway “The overlap between SOA governance technology and API management is significant.” “It is about tracking and monitoring the artifacts in an SOA or an API project, enforcing and ensuring compliance with the policies associated with the artifacts and measuring the outcomes related to their use.” - August 2013, Gartner’s Application Services Governance report Application Services Governance API ManagementSOA Governance
- 33. The Convergence Journey ● Minimum disruption to the current user ● Maximum Speed ● Phase I in WSRR 8.5 & APIm v5 – Ability to see & select WSRR services through APIm Interface ● Phase II – Coming soon – Love to hear your views – Inner Circle Customers ● Thursday 9am Bellini 2104
- 34. 34 “Gartner recently introduced the term application services governance to refer to the union of SOA governance technology functionality and API management, thus preserving the terminology differences between the two, with the view that these aspects will eventually be unified.” - August 2013, Gartner’s Application Services Governance report 34 IBM in the Application Services Governance market Source Gartner – August 2013 IBM in the Application Service Governance market • 2,000 customers • Largest engineering investment in the industry, with over 250 engineers • Over 200 field practitioners • Strong focus on security (no ability to run third-party code, hardware security, etc.), ease of use, and methodology
- 35. WSRR Sessions at Impact 2014 Client use case presentations 2089: Lessons Learned Using a Service Registry for Service Governance • Tuesday: 10:30 – 11:30 – Palazzo F; Steve Romanowski (State Farm), Dennis Miller (IBM) 3358: How PSCU Implemented Its Intelligent Platform Through a SOA COE • Tuesday: 14:15 – 15:15 – Marcello 4402; Prithvi Srinivasan (Prolifics) 1501: API Lifecycle Management: Integrating IBM WSRR & API Management • Wednesday : 10:30 – 11:30 – Marcello 4402; John Falkl (Haddon Hill Group Associates) 2781: How CVS Caremark Implemented a Service Oriented Architecture Center of Excellence • Wednesday : 10:30 – 11:30 – Marcello 4405; Prithvi Srinivasan (Prolifics), Ajay Behuria (CVS CareMark) 2740: Extending IBM WSRR to Legacy IBM WebSphere Application Server • Wednesday: 14:15 – 15:15 – Marcello 4405; Animesh Jain (Prolifics) 2699: SOA at Highmark - One Company's Journey • Wednesday : 17:00 – 18:00 – Lando 4305; Rich Turney (Highmark Inc.), Ed Ober (Highmark Inc.) 3128: Implementing an ESB with IBM Integration Solutions at Danske Bank • Wednesday : 17:00 – 18:00 – Marcello 4404; John Alex Jensen (Danske Bank) 1540: Reusable Policy Templates in IBM WebSphere Service Registry and Repository • Thursday: 10:30 – 11:30 – Palazzo F; Yevgen Khibin (Kaiser Permanente) 2946: SOA Best Practices & Pitfalls • Thursday : 15:45 – 16:45 – Lido 3005; Rich Turney (Highmark Inc.), Ed Ober (Highmark Inc.), Chris Hengst (Highmark Inc.), Bryan Lichtenwalner (Highmark Inc.) 35
- 36. WSRR Sessions at Impact 2014 Product presentations 1250: What’s New in IBM WebSphere Service Registry and Repository • Tuesday : 10:30 – 11:30 – Marcello 4405; Robert Laird (IBM), Nick Butler (IBM) • Wednesday: 15:45 – 16:45 – Marcello 4405; Robert Laird (IBM), Nick Butler (IBM) 1200: IBM WSRR & IBM Integration Bus: Advanced Integration • Tuesday : 17:00 – 18:00 – Palazzo I; Martin Smithson (IBM) 1251: Service Visibility & Management with IBM WebSphere Service Registry and Repository • Wednesday : 13:00 – 14:00 – Marcello 4405; Robert Laird (IBM), Nick Butler (IBM) 3237: Meet the Experts: IBM WebSphere Service Registry and Repository • Thursday: 13:00 – 14:00 – San Polo 3503; Nick Butler (IBM), Martin Smithson (IBM) Roundtable Feedback Sessions 1244: Roundtable: IBM WebSphere Service Registry and Repository • Monday: 17:15 – 18:15 – Zeno 4708; Robert Laird (IBM), Gary Thornton (IBM) • Tuesday: 17:00 – 18:00 – Zeno 4708; Robert Laird (IBM), Gary Thornton (IBM) 36 Hands on labs 1223: Enable Role-based Service Views & Change Notification to Effectively Govern Services • Wednesday: 15:45 – 18:00 - Murano 3305; Martin Smithson (IBM), Dennis Miller (IBM) 1201: IBM WRR & IBM Integration Bus: Advanced Integration Lab • Thursday: 09:00 – 11:30 - Murano 3305; Martin Smithson (IBM), Dennis Miller (IBM)
- 37. API Management Sessions at IMPACT 2014 API Economy 2569: Freedom to innovate through SOA & APIs •Mon 16:00 – 17:00 – Marcello 4405; Thu10:30 – 11:30 – Lando 4203 1339: API Management & Beyond: Introduction, Benefits, Use Cases & Approach, & Reference Architecture •Tue 10:30 – 11:30 – Marcello 4402 1496: API Design Best Practices •Tue 13:00 – 14:00 – Marcello 4402 2509: Business of Internal APIs, by Kin Lane, The API Evangelist •Tue 13:00 – 14:00 – Palazzo G 2739: Differentiating Between Web APIs, SOA, & Integration & Why It Matters to an Architecture •Tue13:00 – 14:00 Palazzo P 1435: Defining a Business Strategy for APIs, by Mehdi Medjaoui (WebShell.io) •Wed 13:00 – 14:00 – Marcello 4402 2803: Skyrocketing Growth Through APIs: Think like a startup & scale like an enterprise Jason Wolenik,(Fabernovel Inc), Elie Chevignard (OAuth.io) •Wed 14:15 – 15: Marcello 4501 B 1504: The API Economy: Identify Opportunities for Monetizing Business Assets •Wed17:00 – 18:00 Lido 3101 B 2356: Banking on APIs Thu10:30 – 11:30 – Marcello 4402 API and Mobile & API and IoT sessions 1398: From Mobile to API: What Are the Security Implications (Part 1) Tue 14:15 – 15:15 – Marcello 4501 B 1487: From Mobile to API: What Are the Security Implications (Part 2) Tue 15:45 – 16:45 – Marcello 4501 B 3236: API First Mobile Strategy Wed 10:30 – 11:30 – Palazzo G 2520: IoT & API - Can’t Spell "Internet of Things" Without A-P-I Thu 14:15 – 15:15 Marcello 4402. Live Demo Session 3512: IBM API Management v3 interactive demo Wed 2:15 - 3:15; 3:45 - 4:45 – Delfino 4103
- 38. API Management Sessions at IMPACT 2014 Client use case sessions 1513: Enterprise API Strategies from Customers & Implementers Panel • Monday 17:15 – 18:15 – Lido 3005; Ren Srinivasan (Citi), Mehdi Medjaoui (WebShell.io),John Falkl (Haddon Hill Group), Jack Hunt (Availity, Inc.), Justin Falciola (Humana), Tim Hundt (GE Capital) 1401: Capitalizing on the API Economy • Tuesday 13:00 – 14:00 – Lando 4201A; Bob Evans (Pitney Bowes), Srikant Varadarajan (Pitney Bowes) 1890: Explore API Economy Through Joint Lab Building the Largest Internet of Vehicles Platform in China • Tuesday 15:45 – 16:45 – Marcello 4401 A; DaoSheng Hu (TransWiseway) 2165: Enabling IBM API Management at WestJet Airlines • Wednesday 10:30 – 11:30 – Lando 4305; Kevin Minshull (WestJet Airlines), Erik Hope (WestJet Airlines) • Product sessions 1434: IBM API Management - Overview & What's New Lecture • Monday 14:30 – 15:30 – Palazzo G; Thursday 9:00 – 10:00 – Palazzo G 1517: Extending Enterprise Integration with IBM API Management • Tuesday 14:15 – 15:15 – Palazzo G 1501: API Lifecycle Management: Integrating WSRR & API Management • Wednesday 10:30 – 11:30 – Marcello 4402 1630: Got CICS? Enter the API Economy with IBM API Management • Thursday 9:00 – 10:00 – Delfino 4003 2913: API Management V3 Technical Overview & Deep Dive • Thursday 10:30 – 11:30 – Marcello 4501 B; Thursday 13:00 – 14:00 – Palazzo G 1080: Extending an Existing IBM WebSphere DataPower Return on Investment with IBM API Management • Thursday 13:00 – 14:00 – Marcello 4501 B 1494: IBM API Management Best Practices: Setup, API Design, & Deployment • Thursday 14:15 – 15:15 – Marcello 4501 B 1325: IBM API Management User Experience Design & Feedback Customer Feedback • Zeno 4701 - Monday 17:15 – 18:15; Tuesday 17:00 – 18:00; Wednesday 13:00 – 14:00
- 39. Questions?
- 40. We Value Your Feedback Don’t forget to submit your Impact session and speaker feedback! Your feedback is very important to us – we use it to continually improve the conference. Use the Conference Mobile App or the online Agenda Builder to quickly submit your survey • Navigate to “Surveys” to see a view of surveys for sessions you’ve attended 40
- 41. Thank You
- 42. Legal Disclaimer • © IBM Corporation 2014. All Rights Reserved. • The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. • References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results. • If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. • If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. • Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both. • If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. • If you reference Java™ in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. • If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. • If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. • If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries. • If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. • If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only. •
Editor's Notes
- <number> This chart shows the current Industry pack roadmap. The most recent release of IIB came at the end of 2013, when IIBv9.0.0.1 came out in December. This followed the release of v9 at the end of Q2 in 2013. Version 9 was the first time that WebSphere Message Broker assumed the new name of IBM Integration Bus, so building on this new naming strategy, when the Retail Pack came to market at the end of 2013, it was christened the IIB Retail Pack. This first release provided two new integration patterns in the IIB Patterns Explorer – one to integrate WebSphere Commerce with Sterling Order Management, and the other to flow transaction data in the Tlog format from Point of Sale devices in store to a POSLog canonical form in the enterprise. WebSphere Commerce has previously offered a “Feature Pack” (FEP5) containing WESB mediation modules which integrate with Sterling Order Management, but with IIB now adopting the WESB use case, the IIB Retail Pack provides IBM’s strategic solution in this space. Our next industry pack release came at the end of Q1 2014. This was the IBM Integration Bus Healthcare Pack, version 3.0. Again, adopting the new IIB naming, this pack has been naturally labelled as version 3, as it follows the previous two WMB Healthcare Connectivity Pack releases. This release was the first to offer a Web User interface for the healthcare pack, monitoring clinical applications. It also incorporates two new patterns – the Home Health Pattern and the HL7 Transformation pattern. The Home Health pattern uses the Continua Alliance defined web service interface and enables IIB to assume the role of WAN Receiver for taking in data readings from home health devices such as weighing scales, and blood pressure devices for example. The HL7 Transformation pattern provides a development accelerator for healthcare transformation and routing scenarios by generating graphical data maps for one or more of the HL7 messages (defined in chapters 3 to 17 of the standard). The icons in the middle and the right of the chart represent our current areas of development and future delivery intentions. The red manufacturing logo in the centre will be covered later in this deck when I’ll talk about a public Statement of Direction which IBM has published regarding an IBM Integration Bus Manufacturing Pack. The other healthcare icon represents our current plan to produce a Fix Pack release for the IIB Healthcare Pack. Towards at least the end of 2014, there are also icons to represent the next releases of IIB core and the IIB Retail Pack. The black icons at the right of the chart symbolise our openess for client conversations regarding further Industry Packs – Insurance, Telecoms, Travel and Transportation, Energy etc.
- The IBM Integration Bus Retail Pack v1.0 was released in December 2013. This is the second IIB Industry Pack which we have brought to market and starts expanding the strategy which was laid down with the WMB Healthcare Connectivity Pack which itself has had two major market releases since it’s inception in May 2011. The Retail Pack provides development accelerators to assist with retail integration both in stores and in the enterprise. The pack provides two patterns and a new Web User Interface. The first pattern provides some pre-built integration flows which are functionally equivalent to the support previously offered by the WebSphere Commerce Feature Pack 5 mediation modules for WESB. With IIB now adopting the WESB use case, this pattern in the IIB Retail Pack forms IBM’s strategic integration solution for exchange of data between WCS and SOM. The second pattern, converts ACE Tlog data into the POSLog XML canonical format. Several variants of the Tlog standard are supported – Binary, XML and MIME. Database scripts and a sample message flow are also included for the creation of a database which conforms to the ARTS Operational Data Model. The sample message flow uses a Graphical Mapping node to insert data originating from a Point of Sale into the ARTS database. The Web User Interface is built upon the existing IIB technology stack (IIB’s REST API, web security model and cutdown Tomcat implementation) but provides a distinct context root “/retail” with a splash page and links which are specific to the pack. The UI offers both a Business view and an Operational view. The Business view tracks the total revenue recorded across an aggregation of POSLog messages from Point of Sale devices in store. This can be used by a store manager through the trading day to track sales with a Point of Sale breakdown, or in the Enterprise to track and compare individual stores at different geographic locations. Built upon IIB Accounting & Statistics and IIB Monitoring publications, the Web UI uses a flow of information into a web socket connection in order to provide a real-time view of performance of the Tlog to POSLog pattern. The operational view groups together a set of flows based on a Pattern Type and Pattern identifier. The throughput of messages through each flow, and the time interval at which the last message was transmitted are displayed. This operational view provides at-a-glance an indication of how the flows which make up a pattern are performing. For example in combination with the WebSphere Commerce to Sterling Order Management pattern, it can be used to track several disparate flows each of which would expect data at wildly varying frequencies (heartbeat pings versus orders flowing etc.)
- The IIB Healthcare pack v3.0 continues our commitment to support core healthcare integration scenarios requiring HL7 data. Often, clinical applications will claim to use data compliant with the HL7 messaging standard but in reality produce and consume messages which do not quite match with the standard. The HL7 Error handling enhancements make it much easier to catch these kinds of situations and therefore make changes to the supplied HL7 DFDL model. The HL7 Transformation Pattern also aids IIB developers in creating message flows which interact with HL7 data structures by automatically generating graphical data maps (or ESQL) which create a logical tree structure for an HL7 message (or HL7 segment) from scratch. HL7 messages often contain thousands of fields, so this really helps speed up the development effort required in this area. The healthcare pack’s new Web User Interface provides a view of connected clinical applications for tracking the sending, receiving and acknowledging of HL7 / MLLP data exchanged between healthcare applications using TCP socket connections. This view is equivalent to the MBX eclipse based view which users may be familiar with from previous releases. The Web User interface also offers some operational views which show the user how the flows which make up particular healthcare pack patterns are performing. The Home Health pattern, symbolised by the pictograms in the green rectangle and the component diagram show that IIB can be used in the role of WAN receiver to take data which is sent as an embedded HL7 Observation Result message within a SOAP body into a message flow. This pattern utilises an industry standard WSDL document published by the Integrating the Healthcare Enterprise group, and then re-used in the Continua Alliance Design Guidelines. These guidelines also suggest using SAML security tokens to ensure that the message is sent from an authorised source. The IIB Security PEP (Policy Enforcement Point) node to check this token with an external Token Service (such as Tivoli Federated Identity Manager for example). The generated flow which the pattern creates also provides graphical data maps for the creation of the correct form of acknowledgement message to be sent back to the requesting Application Hosting Device (typically mobile phone). These acknowlegement messages can take one of three formats – successful acceptance and processing of the observation result, rejection of the observation result, or another form of rejection due to a first acceptance that the observation result was ok but that a downstream problem was encountered.
- http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS214-212&appname=USN On Tuesday 22nd April 2014 IBM made a public Statement of Direction regarding our future intention to deliver a Manufacturing Pack to extend the industry specific capabilities of IBM Integration Bus. The planned capabilities for the Pack will provide ready-to-use connectivity patterns to help save time for integrators seeking to integrate a range of plant and machinery data and events from the production, manufacturing and industrial sectors. It is our intention to focus the efforts of the Pack in three main areas – support for Plant connectivity via existing de facto standards, support for Plant connectivity via new and emerging OPC Unified Architecture standards, and in the area of Enterprise Connectivity with connectors to facilitate the transmission of data from remote locations. Like other Industry packs which IBM has already released, a Web-based interface for the provision of operational views of the data published from plant and machinery is also planned. More on this in a moment, but first let’s consider some of the business drivers in this area … The announcement, reflects the importance of Manufacturing clients to the future reach of the IBM Integration Bus. There are several business imperatives which are driving this excellent market opportunity. Increased expectations from clients are driving the manufacturing world away from just Mass Automation but to “Mass Customisation”. When I order my premium car from my local dealership, I’m expecting regular updates from the production center telling me when the parts have arrived, what stage the assembly is at, and how my delivery date is changing (is the car ahead or behind predicted schedule?). The cultural demands from users now accustomed to interactions on the web and social media mean that it is no longer good enough for a Manufacturer of premium goods to ignore this aspect of their operations. The importance of capturing the “green dollar” (climate and eco-sensitive consumers) cannot be underestimated. The ability for a client to track the raw materials which have been combined to produce their product has real influence on people’s buying decisions. As we emerge from global economic recessions, the growth of the Manufacturing sector as a whole is also driving demand – the impact of the BRIC and MINT economies and their emergent middle classes is driving new opportunities. Existing players cannot afford to be complacent with the globalisation of supply chains, and global competition with lower labour costs. Company internal processes are also driving an integration need in this business space – Increased resoure efficiency can be achieved by scheduling production processes for optimal use of resources and machine time. Production line performance analysis is required, measures of equipment effectiveness and the ability to perform predictive maintenance. Increased competition in the manufacturing sector means that companies also need to become increasingly dynamic – highly responsive to changes in demand using re-configurable production facilities. <AllowedToSayThis?>A closed Early Access Program has also been instantiated, which clients can register for through their IBM Sales and Account representatives. The announcement of the program happened in the second week of April, and we are currently gathering nominations for a kick off call in the second week of May, to be shortly followed by a Beta Code Drop.</AllowedToSayThis?> The slide shows some of the connectivity areas which we are expecting to pursue: Plant Connectivity De Facto standards: OPC Classic support – built on the Windows COM and DCOM communication technologies. OPC Unified Architecture: The future of non-proprietary Open Process Communications – supporting all the data exchanges provided with the OPC Classic Data Access capabilities but built upon SOA principles, including enhanced security. Vendor specific: We are exploring OSIsoft PI Server integration. PI Server is the market leading OPC Server. Founded in 1980 in California, with current revenue levels of approx $270million, OSIsoft now has in excess of 15,000 customer installations spread across more than 110 countries. Enterprise Connectivity: MQTT for remote site connections.