1. 1 What's New in IBM Integration Designer 7.5 for IBM Business Process Manager and WebSphere ESB Allen Chan, STSM Lead Architect, IBM Integration Designer

2. 2 IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal 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.

3. 3 Agenda  What is IBM Integration Designer?  Support for IBM Business Process Manager and WebSphere ESB – Out of the Box experience – Process Center – Business and IT Collaboration – Pattern-based integration – Mediation enhancements – Enhanced transformation – Integrated Test Client

4. What is IBM Integration Designer?

5. 5 9/19/2016 What is IBM Integration Designer? IBM Integration Designer Rational Application Developer (subset) Eclipse 5 New name for WebSphere Integration Developer Build on top of a subset of Rational Application Developer The development tool for IBM BPM, WebSphere ESB and now WebSphere DataPower.

6. © 2010 IBM Corporation IBM WebSphere BPM 6 Out-of-box Process Portal Configurable Business Space Optional Microsoft Add-ons BPMNRulesMonitoringBPELESB Process Server Process Designer Governance of Entire BPM Life Cycle Shared Assets Versioned Assets Server Registry Design DeployImprove Measure Business & IT Authors IT Developers Authors & Admins Process End-Users Process Owners Integration Designer Process Center BPM Repository Backward compatibility, easy migration from WLE & WPS IBM BPM widgets work with IBM WebSphere Portal IBM Business Process Manager V7.5 7.5NEW7.5NEW

7. 7 WebSphere ESB, IBM Integration Designer and IBM Process Server Advanced Edition IBM Process Server Advanced Edition IBM Integration Designer WebSphere ESB WebSphere Application Server Rational Application Developer (subset) Eclipse IBM Integration Designer is the new name for WebSphere Integration Developer

8. 8 Programming model  An architecture where components implement business logic, exports describe the interface to the service consumers, and imports describes the interface to the service providers. Module Component1 Export Component1 Import Interface : How to call this component, modeled as WSDL/XSD. Exports: SCA Web Services JMS MQ HTTP EJB (session) Adapters Exports: SCA Web Services JMS MQ HTTP EJB (session) Adapters Imports: SCA Web Services JMS MQ HTTP EJB (session) Adapters Imports: SCA Web Services JMS MQ HTTP EJB (session) Adapters Components: Java Mediation Flow Process Human Task State Machine Business Rule Interface Map Selector Components: Java Mediation Flow Process Human Task State Machine Business Rule Interface Map Selector Process Server only

9. Component Interfaces  Interface Editor Edit interface definition backed by WSDL Port Type Simplified user interface ● Operations One-Way or Request Response Arguments are Business Objects or simple types Faults

10. Business Objects Business Object Editor Edit data structure definitions backed by XSD Simplified user interface Nesting Arrays Inheritance Restrictions

11. 11 Non-XML Data  Data coming into or going out of a module, can be non-XML – Conversion to/from XML is achieved via a “Data Binding” on the Export or Import – Can build your own custom Data Binding class – Many pre-supplied Data Bindings:

12. 12 Connectivity Support  Defined as Export and Import nodes in application modules.  Supported Connectivity Bindings: o Native SCA (module to module) o HTTP Access (REST, XML/HTTP) o Web Services (SOAP/HTTP, SOAP/JMS) o Messaging (JMS, MQ, JMS MQ, generic JMS 3 rd party adapters) o JEE Applications (Session EJB) o Java Connectivity Architecture (JCA) adapters  Supplied Adapters: o IBM WebSphere Adapter for Email o IBM WebSphere Adapter for FTP o IBM WebSphere Adapter for Flat Files o IBM WebSphere Adapter for JDBC o IBM WebSphere Adapter for System i o IBM WebSphere Adapter for ECM o IBM WebSphere Adapter for Lotus Domino o IBM CICS ECI Resource Adapter o IBM IMS Connector for Java o IBM WebSphere Adapter for Oracle® E-Business Suite o IBM WebSphere Adapter for PeopleSoft o IBM WebSphere Adapter for SAP® Software o IBM WebSphere Adapter for Siebel® Business Applications o IBM WebSphere Adapter for JD Edwards EnterpriseOne® Built-in 7.5Updated7.5Updated

13. BPEL Component ● Choreographed execution ● Long running (stateful) ● Short running ● Based on BPEL 1.1 and a draft version of the WS-BPEL 2.0 Compensation standard ●.

14. Business State Machine Component ● Business process choreography using a state machine definition ● Simpler to define when: ● Business process is heavily event-driven ● Reaction to these events is dependent on the process state ● Process may revert to prior states Transition Event Action (Logic) Guard (Check) State Entry (Logic) Exit (Logic) Composite State Time-out

15. 15 Mediation Flow Component Pre-defined Mediation Primitive functions: Transformation Validation Enrichment Protocol conversion Routing Service Gateway Fan-In, Fan-Out Registry Lookup Events and Trace … access to context and protocol information

16. 16 Service Message Object  Within a mediation flow component, the component’s interface parameters (in request flow) or response data (in response flow) are wrapped in a Service Message Object (SMO)  In addition to the “payload” or business object data, the SMO contains contextual information: – Protocol information such as SOAP headers or JMS properties – Information populated by primitives within the mediation flow SMO

17. Human Task Component ● Points of human interaction with the application ● Roles and Permission Settings ● Client Settings ● Web, Portal interface ● Escalations Settings ● Notification – e-Mail – Human Task – Event ● Priority Aging Permission Settings Client Interface Escalation Settings

18. Business Rules Component  Two definition styles If-Then rules Decision Table rules (balanced binary tree format)  Rule Templates Determine which aspects of the rule can be modified at runtime  Modifiable at runtime Business Rules Manager Changes can be exported back to tools If-Then Rules Decision Table Rules Parameterized Rule Template

19. Version 7.5 Highlights: Out of the Box Experience

20. 20 Enhanced Welcome  Getting started – embedded Welcome Constrain the projects and artifacts to those that can be deployed to a given environment. Easy access to information for new and returning users 7.5Enhanced7.5Enhanced

21. 21 Process Center Perspective List of Process Applications or Toolkits Open Process Applications directly in Integration Designer to implement Services. Direct access to Process Center for collaboration with Process Designer. 7.5NEW7.5NEW ** Process Center integration is only available for IBM BPM

22. Version 7.5 Highlights: Business and IT Collaboration

23. Integrates with IBM Process Center  Support collaboration with process designers in the creation of integration and services modules of a process application  Allow service modules to be associated with Process Applications for version control and collaboration.  Support playback of Services modules on Process Center.  Generate end-to-end monitor model for Process Applications and Services modules. 7.5New7.5New

24. © 2010 IBM Corporation IBM WebSphere BPM 24 BPMN Process Design with Integration Design approach – Business Author  Use Process Designer iterative approach, playbacks, change management  Implement all the human interaction flows in Process Designer  Identify integrations and defer their implementation to a later stage –Create service request for Advanced Integration Service (AIS) –Use simple javascript emulation to get going! Design Approach – IT Developer  Bring the Process Application or Toolkit into a Integration Designer workspace  Implement Advanced Integration Service (AIS) defined by Business Author  Use a full power of Integration Designer visual development to implement complex integration logic: –BPEL long running processes –BPEL microflows –Mediation Flows –Data Maps –Technology and Application IBM Adapters –Test Cases –End to End Monitoring  Primarily applicable in situations where: –Process creation is driven by Business Author, but integration is also a requirement –Integration requirements are not completely formulated or formally documented 7.5NEW7.5NEW

25. © 2010 IBM Corporation IBM WebSphere BPM 25 Business Led Development of Processes and Services Process Center BPM Repository Process Designer Integration Designer 1 – Process is iteratively modeled in Process Designer 2 – Advanced integrations are identified and modeled 3 – Integration designer imports process apps 4 – Advanced integrations are implemented, tested locally 5 – Modules with advanced integrations delivered 6 – Advanced integration are consumed by process 1 1 2 2 3 3 4 4 6 6 5 5 Business Author Integration Developer7.5NEW7.5NEW

26. Business Author: Request a Service Business Authors request a Service to be implemented by creating an Advanced Integration Service (AIS) activity. 7.5NEW7.5NEW

27. IT Developer: Implement a Service (Part 1) IT Developer opens the same Process Applications or Toolkit from the Process Center. 7.5NEW7.5NEW

28. IT Developer: Implement a Service (Part 2) IT Developer selects an existing Service Request and implements the service. 7.5NEW7.5NEW

29. IT Developer: Publish the Service implementation When the service implementation is completed, developer can publish the implementation back to the Process Center to be used by the business process. 1. Publish to Process Center in Integration Designer 2. Used in the business process in Process Designer. 7.5NEW7.5NEW

30. Version 7.5 Highlights: Pattern Based Integration

31. 31 Scenario Patterns and Micro-Patterns  IBM Integration Designer support two forms for pattern-based integration: – Scenario Patterns These are patterns that create an entire application An example of a scenario pattern is a Service Gateway – Micro-Patterns These are snippets of mediation logic that codify a way to implement a certain integration pattern These micro-patterns are meant to be used in combination to create an application An example of a micro-pattern is a Message Filter primitive

32. 32 IBM's categories of Integration/ESB Patterns Service Enablement Gateway OR Message-based Integration File Processing Event-driven Integration Service Virtualization

33. 33 IBM's categories of Integration/ESB Patterns Service Enablement Gateway OR Message-based Integration File Processing Event-driven Integration Service Virtualization Expose aspects of application functionality through a service oriented interface Provide a level of indirection which hides the true identity and location of services Connect and integrate applications using a messaging infrastructure Provide boundary functions which are independent of format or interface Integrate applications which exchange data using files. Distribute and correlate information and events across the enterprise

34. 34 Built-in Patterns – Pattern Explorer  Provides patterns for: – Service gateway – Simple service proxy – Service virtualization  User: 1) Explores available patterns 2) Selects a pattern 3) Specifies pattern parameters 4) Generates the pattern New in Feature Pack 1

35. 35 Service Gateway  A Service Gateway provides a single network addressable endpoint for accessing and providing a control point for a multiple service providers  This differs from the typical service mediation/proxy pattern were each service provider is fronted by a different network addressable endpoint Service Consumer A Service Provider A Service Consumer B Service Provider B Service Consumer C Service Provider C Service Gateway Service Consumer A Service Consumer B Service Consumer C Service Provider A Service Provider B Service Provider C Typical Service Mediation Service Gateway Mediation

36. 36 Simple Proxy Pattern  A simple proxy provides basic service virtualization by allowing user to expose a backend service using any one of the supported binding types (e.g. web services, JMS, etc)

37. 37 Service Translator  Allows a service to be made available with a different interface  Allows certain operations on the interface to be hidden  Interface can be made available with a completely different structure which is more appropriate for specific users of that interface

38. 38 Service Selector  Allows multiple implementations of the same service interface to be grouped behind a single endpoint address  Supports multiple transport protocols

39. 39 9/19/2016 Integration Patterns – Create Your Own “expert” developer “everyday” developer New instance New data types and data mapsIntegration Pattern Pattern Capture Create ESB Mediation/BPEL Flow Capture Pattern with the help of IBM Services in IBM Integration Designer Publish pattern to Pattern Library Explore Pattern Library Instantiate pattern with local artifacts Deploy pattern instance to IBM BPM or WESB IBM Services 7.5NEW7.5NEW

40. Version 7.5 Highlights: Mediation Enhancements

41. 41 Mediation Flow Editor enhancements (V7) 41 Improved flow navigation using breadcrumbs Request and Response tab are moved to the top to improve discoverability Examine the message structure within the flow editor and create XPath expression Quick way to map between mediation primitives with different terminal types

42. 42 Built-in mediation primitives 7.5Enhanced7.5Enhanced

43. 43 Message enrichment by service invocation  Simplified development of scenario where service invocation is used to enrich message content  Previously required three mediation primitives: 1) XSLT to save message body to context 2) Service invoke 3) XSLT to merge results with original message body  Explicit message enrichment mode added to Service Invoke mediation primitive  XPaths specified to define location of request parameter for service invocation and location to place response 7.5NEW7.5NEW

44. 44 Textual mediation flow format  Mediation flow definition serialized in to new simple XML format  New format documented in InfoCenter  Supports multiple new scenarios: – Textual compare/merge of mediation flows in team based development environment – Notepad editing of mediation flow definitions – Programmatic generation of mediation flows e.g. instantiation of patterns from templates 7.5NEW7.5NEW

45. 45 Operation level catch-all error handling  It is a common requirement to have common error processing for all unhandled exceptions  Previously required all fail terminals to be manually wired to a common subflow – Time consuming, error prone and obscures main flow path  With 7.5, we introduce the concept of an operation level catch-all error flow  Error flow might for example: – Log the error and then fail the mediation flow – Return a modeled fault – Return a response message 7.5NEW7.5NEW

46. Version 7.5 Highlights: Enhanced Tranformation

47. 47 Data transformation enhancements  Support built-in functions in both XPath 1.0 and XPath 2.0.  Support for both XSLT1 and XSLT2.  Enhanced Auto Map support.  Various Improvements includes: – Support smart data type conversion (e.g. string->int, date->dateTime). – Direct casting from derived/weak to concrete types. – Complex conditional lookup using user-defined lookup function. – Support “if / elseif / else” conditions, Join Transform, Supplemental Inputs, Nillable and Empty element assignment policy. – Data Mapping overlay for copying complex objects and overriding individual fields. – Variable Support. – Provide map catalog to show list of maps in a project. 7.5Enhanced7.5Enhanced

48. 48 IBM Confidential9/19/201648 TB XPath 2.0 functions/operators (partial list) String functions string normalize (string?) string upper-case (string?) string lower-case (string?) string encode-for-uri (string?) string iri-to-uri (string?) string escape-html-uri (string?) boolean contains (string?, string?, string?) boolean starts-with (string?, string?, string?) boolean ends-with (string?, string?, string?) string substring-before (string?, string?, string?) string substring-after (string?, string?, string?)... Regular expression matching functions boolean matches (string?, string?, string?) string replace (string?, string?, string?) string* tokenize (string?, string, string?) Date/time operators yearMonthDuration-less-than yearMonthDuration-greater-than dayTimeDuration-less-than dayTimeDuration-greater-than duration-equal dateTime-equal dateTime-less-than dateTime-greater-than date-equal date-less-than date-greater-than time-equal time-less-than time-greater-than adjust-dateTime-to-timezone adjust-date-to-timezone adjust-time-to-timezone... 7.5NEW7.5NEW XSLT 2.0 and XPath 2.0

49. 49 IBM Confidential9/19/201649 TB 7.5NEW7.5NEW XSLT 2.0 and XPath 2.0

50. 50 IBM Confidential9/19/201650 TB 7.5NEW7.5NEW Support for Join Transform type and variables in the XML Mapper

51. 51 IBM Confidential9/19/201651 TB 7.5NEW7.5NEW Support for Join Transform type and variables in the XML Mapper

52. 52 IBM Confidential9/19/201652 TB  Allows user to automatically map sources to targets using name matching.  Name matching options could be: match by exact name, match by similar name (%), and match using a synonyms file.  Extremely important when mapping from one version of a XML Schema structure to an enhanced version 7.5Enhanced7.5Enhanced Auto Mapping Improvements

53. Version 7.5 Highlights: Integration Test Client

54. 54 Integration Test Client  Basically a client for dynamically invoking exports, components and imports  The goal is to test your components to ensure they behave as expected  But can also... – Monitor – Evalute – Attach 54 Events Shows execution trace Events Shows execution trace Values Editor For entering and displaying data Values Editor For entering and displaying data

55. 55 Updated test case support  New test cases can be captured directly from test execution trace greatly speeding up the creation of test cases  Test Cases that include inline emulators and event verification steps can now be created from test traces. 7.5Enhanced7.5Enhanced

56. 56 Generic Service Client for MQ and JMS testing New Generic Service Client that support the ability to send test messages to Web Services, JMS and MQ endpoints. 7.5NEW7.5NEW

57. 57 Process Center Integration  Versioned modules contained in Process Applications and Toolkits an be tested using the Integration Test Client  Component Test Cases can be authored against modules contained in Process Applications or Toolkits and can be stored in the Process Center  Tests can be run against modules in Process Applications that are deployed to “production” environments. This includes environments that are ND. 7.5NEW7.5NEW

58. 58 Summary  What is IBM Integration Designer?  Support for IBM Business Process Manager and WebSphere ESB – Out of the Box experience – Process Center – Business and IT Collaboration – Pattern-based integration – Mediation enhancements – Enhanced transformation – Integrated Test Client

59. 59 We love your Feedback!  Don’t forget to submit your Impact session and speaker feedback! Your feedback is very important to us, we use it to improve our conference for you next year.  Go to impactsmartsite.com from your mobile device  From the Impact 2011 Online Conference Guide; – Select Agenda – Navigate to the session you want to give feedback on – Select the session or speaker feedback links – Submit your feedback

60. 60 © IBM Corporation 2011. All Rights Reserved. IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml. Copyright and Trademarks