1 / 31

Covast B2B Suite for IBM WebSphere

Covast B2B Suite for IBM WebSphere. Gijsbert in ‘t Veld CTO Covast Gijsbert.intVeld@covast.com. B2B Trends by Industry Analyst. B2B solutions differentiate themselves by the ESB they are run on Internal A2A and external B2B are converging, giving benefits like:

eyal
Download Presentation

Covast B2B Suite for IBM WebSphere

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. Covast B2B Suite for IBM WebSphere Gijsbert in ‘t Veld CTO Covast Gijsbert.intVeld@covast.com

  2. B2B Trends by Industry Analyst • B2B solutions differentiate themselves by the ESB they are run on • Internal A2A and external B2B are converging, giving benefits like: • One monitoring and management toolset for the full integration experience • BPM for A2A and B2B integration to tie into the same business processes • BAM for A2A and B2B integration for analyzing complete integration flows to make informative business decisions • Single Toolset to master for mapping and EAI development • Integrate EDI standards within the ESB message flow • Pure-play vendors without an ESB will be challenged to deliver a complete A2A and B2B solution • More companies will standardize on IBM because we deliver the full end-to-end solution

  3. Adapters • Workflow • DB and files • Toolkit WebSphere ESB Advantage for B2B IBM Enterprise Integration B2B Trading Partner Traditional B2B Gateways Transports Packaging Protocols Partners Transport Package Routing Partner Management Transformation (optional) Applications Mechanism for connecting, routing, and transforming business data between services

  4. Easy to Support and Manage Your Connections WPG Administrative Console Eclipse WMB Tool Kit EDI Viewer EDI Importer EDI Explorer Document Definition Manager EDI Viewer/Debugger Trading Partners Gateway EDI Parser WMB Mapper Applications OFTP X.400 VANs AS1/2/3 HTTP FTP SMTP MQ EDI Rules Code Tables XRef Tables Functions XML B2B WebSphere Message Broker 6.0

  5. WebSphere Partner Gateway Transport Receiver Business Protocol Document Flow Partner Profile Console GUI Destination Target WebSphere Message Broker WMB Mapper Node EDI Parser Node Message Flow WebSphere Partner Gateway – EDI Extended Supplier Odette FTP Partner EDI Extensions Extended Views Test Production

  6. Trading Partners High Level View: ESB Solution for Automotive B2B Run Time Design Time WebSphere Monitor Eclipse WebSphere Modeler Advanced ESB (WMB 6.0) B2B Gateway WPG Bi- directional EDI Parser Node WMB Mapping Node WMB Input or Output Node Backend Application WMB Toolkit Covast EDI Explorer Application Data Format EDI Messages XML XML WPG / Covast Monitoring Plug-ins • WPG is pure B2B Gateway (Com, Monitoring, Events) • Covast provides OFTP plug-in to WPG and VAN scripts • Covast provides WMB Nodes for EDI Parser, Batch, ACK • Covast EDI Parser Node takes care of XML<> EDI • WMB integrates with WPG through reliable queues • WMB GUI Mapper does transformation e.g. XML <> XML • WMB integrate JMS, MQ, DBs, Apps & Web Services • WPG provides sngle Admin Console view for run time • Solution offers common build, run and operate Covast EDI DB WPG - Covast TPM DB WPG - Covast Audit Trail WMB MRM Generated XML/EDI Schemas WMB = WebSphere Message Broker WPG = WebSphere Partner Gateway

  7. Architecture

  8. What is needed to do “EDI” • Auditing, managing & monitoring • End-to-End acknowledgements • Format and document support • Trading partner management • Syntactic and Semantic validation • Batching facilities • Communication Protocols

  9. Communication protocols • AS1 • AS2 • FTP(/s) • HTTP(/s) • OFTP • X.400 • MQ • Value Added Networks (VAN)

  10. Batching • EDI Interchanges consist of multiple documents or even document types to be sent to one recipient • Cut communication costs • Group logical batches of documents • Batching can be configured on the Trading Partner level in the Trading Partner Management user interface • Batches are created by specialized flows deployed in the Message Broker • Batching can also be influenced from within a mapping, by just mapping a batch reference to the envelope in the target message • For example, combine a number of invoices with a VAT summary report in one outbound interchange

  11. EDI connections setup

  12. EDI validation • All EDI Interchanges and Messages are validated against the specification stored in the EDI Repository – via the Generated XSD. Validation takes place in the EDI Parser Node in a message flow. The following are validated: • Syntax • Code sets • Segment repetition • Hierarchy • Separators • Types • Maximum and Minimum lengths • Mandatory elements and composites • Semantics (inter-segment and element relationships)

  13. Supported standards and formats Download the latest standards from our extensive repository on the website • Supported Automotive standards: • ODETTE • VDA • EDIFACT • Also supported out-of-the-box: • X12 (U.S.) • VICS (U.S. General Merchandise Retail) • WINS (U.S. Warehousing) • UCS (U.S. Grocery Retail) • EANCOM (European Retail) • Tradacoms (U.K.) • Cargo-IMP (Airfreight) • Gencod (France) • Other (User Configurable) • Supports multi-byte encoded EDI messages, including: EDIFACT UNOX and UNOY standard syntaxes

  14. EDI document definition maintenance

  15. Test EDI instances against specification

  16. Generate XSD and deploy to broker

  17. What is in the XSD and how is it used? • The XSD is the XML way of describing the EDI document definition • It also contains detailed parsing instructions used by the EDI Parser Node in the message flows to: • Validate inbound EDI • Translate this EDI into its XML representation • This “translation” is done implicitly at runtime – no need to define a “mapping” for that • The same XSD is used by other nodes in the message flows to access the “XML/EDI” documents

  18. Advantages of using XML/EDI • It is very easy to access information in XML messages from within the other nodes in the message broker • Therefore it is very easy to use this information in making decisions in these business processes • You can actually “read” EDI messages • And… you can use a standard Mapper to create transformations between two documents: • XSLT Node • Graphical Mapper Node • There is of course also one disadvantage: XML messages are bigger, because they are more verbose • You can limit this by generating XSD’s where the element tags are the EDI segment and element tags instead of the long names • This disadvantage does not outweigh the advantages

  19. Create map

  20. Trading Partner Management • Batching options • Validation options • Ability to define deviating EDI level separators • Acknowledgement settings • Control numbering: • Each EDI transaction is treated as a unique business document exchanged with a Trading Partner • This means that the transactions need unique identifiers • Control numbers can be generated per type of message and/or per Trading Partner • They can also be Transactional – meaning that no gaps will occur in the numbers and therefore parties can check if ALL transactions have been received • Inbound duplicates are (optionally) NOT allowed • The Trading Partner Management layer generates all the artifacts needed by WPG to execute the B2B interactions

  21. Trading Partner setup

  22. EDI level acknowledgement handling • Full End-to-End handling of Functional and Technical Acknowledgments • EDIFACT CONTRL (Functional) • X12 997 (Functional) and TA1 (Technical) • Interchange, Group and Document level acknowledgements • Time-out handling • Acknowledgment generation and reconciliation is done by specialized message flows deployed in the Broker • Full reporting via the WPG Console EDI Viewers

  23. Acknowledgement generation and sending

  24. Acknowledgement reconciliation

  25. Auditing • All EDI documents passing through the solution are recorded in the database (metadata and the EDI files themselves) • The system records time stamps for all actions performed on messages • Events get emitted using the Common Events Infrastructure • All details on messages and failures can be viewed in the EDI viewers that are part of the WPG Console • Archive & Delete scheduler – prepare for storage on Tape or CD for legal purposes

  26. EDI reporting

  27. Message details and visualizing errors

  28. A complete outbound message flow

  29. A complete inbound message flow

  30. Example EDI flow: EDIFACT INVOIC->Oracle Finance

  31. Merci Trugarez Gracias French Spanish Breton Korean Arabic Hebrew Tack så mycket Hindi Traditional Swedish Obrigado Chinese go raibh maith agat Brazilian Portuguese Tak Gaelic Grazie Dankon Danish Danke Italian Esperanto Simplified Chinese German Dank u Japanese Thank You Thai Dutch Dekujeme Vam English Tamil Czech

More Related