1 / 20

WebSphere Integration Developer v6.0: Transformations and Data Mapping with Bottom-up Development

This tutorial covers the bottom-up development approach in WebSphere Integration Developer v6.0, including interface mapping, web service integration, and using existing assets. Learn how to generate components, interface mapping, and data mapping using various adapters and technologies.

rgearhart
Download Presentation

WebSphere Integration Developer v6.0: Transformations and Data Mapping with Bottom-up Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WebSphere Integration Developer v6.0Transformations and Data Mapping with Bottom-up Development

  2. Agenda • Bottom-up Development • Interface Mapping

  3. Web Service in UDDI Session EJB Bottom-up Development • In Bottom-up Development we generate components from existing assets • J2EE Assets • Java Objects • Enterprise Java Beans • Web Services • Non- J2EE Assets • EIS (Enterprise Information Systems), Cobol applications, etc… • Can be accessed via Adapters • Adapters • J2C-based Adapters • JMS-based Adapters Java Bean PeopleSoft EIS

  4. Process Services WebSphere Process Server J2C CCI Interface l J2C PeopleSoft Adapter JDBC MQ-Based Adapter DB2 Database J2C Based Adapters - Architecture J2C CCI Interface NativeAPIs

  5. JDBC JMS-Based Adapter J2C PeopleSoft Adapter DB2 Database JMS Based Adapters - Architecture Process Services WebSphere Process Server JMS JMS l NativeAPIs

  6. Drag and drop Java class on Assembly Diagram Component from Java Beans • Creates a Java Component in Navigator • Creates a Java Component in Assembly Diagram

  7. Drag and drop Session EJB on Assembly Diagram Component from Session EJBs • Creates an Import with Session EJB binding in Navigator • Creates a EJB Import in Assembly Diagram

  8. Demo Next Component from Web Services • Import Web Service • Creates Web Services port in Navigator • Creates a EJB Import in Assembly Diagram

  9. Components from EIS: Enterprise Service Discovery Wizard • Discovers operations offered by an EIS • Creates: • Interfaces • For operations offered by an EIS • Business Objects • Define data for interaction with an EIS • EIS Export and Import • Provide SCA integration • Based on the Enterprise Metadata Discovery (EMD) • A joint specification from IBM and BEA (1) ESD Wizard (1)Whitepaper available at: http://www-128.ibm.com/developerworks/library/specification/j-emd/index.html

  10. EMD API PeopleSoft PeopleSoft Adapter EMD API IMPL. Enterprise Metadata Discovery Requests & Retrieves Metadata 3 1 2 5 4 Requests & Receives Metadata Generates: Imports/Exports BOs Interfaces EMD Wizard In WID

  11. 1 • Import Resource Adapter 2 3 4 • Enter connection configuration • Select discovered BOs • Select operations Using Enterprise Service Discovery Wizard

  12. 5 • Enter module/interface and connection information 6 • Examine what was discovered: • Exports and Imports; BOs; Interfaces Using Enterprise Service Discovery Wizard continued…

  13. sq sq Accessing Adapters from Components • Interfaces • In Assembly Editor • Partner links in Components • Exports/Imports • In Assembly Diagram

  14. Agenda • Bottom-up Development • Interface Mapping

  15. Role of Transformations in Bottom-up Development AsBO used by this (bottom-up) existing • In Bottom-up Development we generate components from existing assets – we have no control what the interfaces/object will be • Generated interfaces that may not conform to top-down defined interfaces • Generated Objects are called Application Specific Business Objects (AsBO) • In Top-down Development we control how all interfaces and objects are defined • Top-down generated objects are call Generic Business Objects (GBO) • GBOs are typically used by all interfaces that need to exchange objects of the same type • Example: Account Verification Process GBO used by all top-up implemented Activities

  16. Top-down Defined Interface Generated from WebSphere Business Modeler export or using Interface Editor Developers expected to implement the Interface with a Component Bottom-up Generated Interface Was generated for us when we imported and existing asset The logic is already implemented AsBO GBO Interface Mismatch between Components • We want to use an already implemented logic in an existing asset… • But, the imported interface of the existing asset does not match our top-down define interface!

  17. Top-down Defined Interface Bottom-up Generated Interface Interface Map Component Transforms Mismatched Interfaces AsBO GBO Interface Map Component: Maps Top-down to Bottom-up Interfaces Interface Mapping GBO Mapped to AsBO

  18. Business Object Map Object Map Name • This BO Map maps a GBO to AsBO • Parameters are mapped using different transform types • Other transform types • Move, Join, Extract, Assign, Custom, Custom Callout, Custom Assign,Relationship, Submap GBO AsBO Parameter Mapping

  19. Use of Interface Map in Assembly Diagram “their” Interface “our” Interface “their” Interface “our” Interface GBO Web Service AsBO Interface Map Component Process Component

  20. Thai Traditional Chinese Gracias Russian Spanish Thank You English Merci Obrigado French Brazilian Portuguese Arabic Danke Grazie Italian German Simplified Chinese Japanese

More Related