1 / 36

The B2B Plugtests event in 2008 – Sophia Antipolis

The B2B Plugtests event in 2008 – Sophia Antipolis. Réunion Architectures techniques TIC PME 2010. Francois FISCHER Philippe COUSIN. ETSI is…. A non-profit organization, Recognized Standards Development Organization Based in Sophia Antipolis, south of France 688 members from 55 countries

burian
Download Presentation

The B2B Plugtests event in 2008 – Sophia Antipolis

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. The B2B Plugtests event in 2008 – Sophia Antipolis Réunion Architectures techniques TIC PME 2010 Francois FISCHER Philippe COUSIN Footer text (edit in View : Header and Footer)

  2. ETSI is… • A non-profit organization, Recognized Standards Development Organization • Based in Sophia Antipolis, south of France • 688 members from 55 countries • http://www.etsi.org/ • ETSI are: • Manufacturers, network operators, • Service providers, administrations • Research bodies and users

  3. Plugtests is a professional ETSI service • Created in 1999, specialized in the organization oftest events • Cost neutral • Skilled ETSI Staff managing test events • Experts from ETSI and other technical communities • Neutral and open to all organisations • Synergy Conformance & Interoperability in close cooperation with ETSI Committees and PTCC • >60 events in 5 years, 3000 engineers, 900 Companies • 1600 participants surveyed ranked usefulness at 4.3/5 and Service satisfaction 4.35/5

  4. Who attends Plugtests events? • Our events are open to all sorts of companies (big and small) as well as engineers developing a product, • Participants do NOT have to be ETSI members • Plugtests are addressed to any company developing a product such as operators, vendors or equipmentmanufacturers, content providers orapplication providers • Standardization bodies, Fora or interest groups may also attend

  5. COST & TIME SAVING ! During a Plugtests event, engineers can“Come & Test” ! • Also known as bake-off (at IETF), plugfests and interop • Plugtests : • Provides useful feedback to the standardization process • Gives a unique opportunity to meet partners and competitors • Helps to ensure end users’ satisfaction • Improves both quality and features of implementations • Allows for networking with the market key players • Accelerates time to market via quick product debugging

  6. PlugtestsTM :Your Fully Customizable Service

  7. Areas of interest • SERVICES & APPLICATIONS • Mobile Applications, OSA-PARLAY, Triple-Play (over DSL, Powerline..), Human Factors • TELECOM • Wimax, UWB, DSL, RFID, SMS/MMS, NGN, Speech Quality, Powerline, Smart Card, Lawfull Interception,.. • IP • IPv6 and Mobile IPv6, MPLS, SIGTRAN, SIP • HOT TOPICS • Grid Computing, WLAN/WMAN, ITS, Security, RF-ID, ebXML

  8. Summary of the 2004 event • Test methodology: • Interoperability does not guarantee conformance: • Two implementations that interoperate do not necessarily comply with the specifications • Two implementations may pass conformance without being able to interoperate. • Perform conformance testing prior to interoperability testing: • Changing implementation in the middle of interoperability testing (to resolve interoperability issues) may invalidate previous result • Recommend passing first Conformance testing, preferably before the event.

  9. Summary of the 2004 event (cont.) • Conformance test suite: • Conformance test suite to verify implementation compliance to ebMS 2.0. • Driven by the Korbit test center. • OASIS - IIC Test suite – Test framework 1.0 • Checking only critical and non-redundant test cases: 35 from 117. • Interoperability • To check combination of messaging and configuration features between two MSH. • Interoperability testing framework implemented in Korbit test bed. • Test specification from OASIS - IIC

  10. Summary of the 2004 event (cont.) • Test event feedbacks • Raised issues: • Interpretation of the ebMS2 specifications. • Test cases • Test cases interpretation • Korbit test bed • Improvements to reduce interface integration effort • Participants: • Successful event • Ensuring specification compliance and interoperability

  11. The 2008 Plugtests event • Not only focusing on ebXML • Rather a B2B event. • ebXML and Web services platforms • The infrastructure base will support: • ebXML (messaging, process, CPA, registry-rep, Core Components) • application components published as Web services • Keeping it open and flexible : • Independence from Business Document standards (XML, EDI…) • Switching between messaging alternatives (e.g. with a gateway model, such as AS2/ebMS2 Hermes OSS). • Accessing Web services either using an ebMS3 gateway or directly.

  12. Improved Test tools • Korbit proposing: • Enhanced conformance testing: ebMS 3.0, RAMP profile W/S, • Document, Transaction and Infrastructure testing. • NIST testing capabilities: • Application information mapping • With test specification process • Driven by test bed tooling • Both test capabilities above to discover inter-operability issues before inter-operability testing .

  13. End-to-End Interoperability across the eBusiness Stack • Not just at messaging infrastructure level • But: Business Process Business Transaction Application Semantics and Services Business Document Messaging

  14. Solution-oriented PlugTest • From Infrastructure-focused to Solution-focused • PlugTest must allow participants to assess and demonstrate Interoperability from an End-user Perspective: • Adequacy: are the messaging functions supported by this infrastructure/standard, adequate for my specific eBusiness needs? • Maturity: is the software product offering (commercial, OSS) mature enough for my deployments? Do they interoperate well? • Integration: do products offer the integration capabilities my back-end applications need? • Concept validation: what would an end-to-end Solution look like, for my problem?

  15. The PlugTest Participants • eB/eG Application Domain Experts (Public sector, Industry sectors, Health, Retail…) • Product Providers • Commercial • Open Source • eB/eG Test Experts • Testbed engineers • Test suite developers • ebXML/WS experts Support team

  16. Application Domain Teams Application Domain “Health Care” Team Application Domain “eGov” Team Application Domain “Invoicing” Team Support Team Standards Experts (ebXML, WS) assist assist Software providers Testbed team

  17. Interoperability Test Plan • Step 1: Every Application Domain (AD) team defines an Interoperability Objective • Based on a real business use case • Bus docs, transactions, messaging QoS • Step 2: Standards Expert team review, advise • Step 3: software providers advise on architecture of POC • Step 4: implementation of the Use Case • Step 5: testing, and iterate again over previous steps as many times as necessary

  18. The Korbit test bed Footer text (edit in View : Header and Footer)

  19. KorBIT::Coverage & Vision

  20. KorBIT::Test Framework (ATF) Test Execution Model Test Report TVI TRI Test Service Service call TSE WS-BPEL TMC Message out ETSL Test Case MEI Extractor TCE Message in Non-stationary Component Stationary Component Document Interface Dynamicinvocation Internalinvocation

  21. KorBIT::Test Case Generation

  22. KorBIT::Test Orchestration Test case App. A App. B Initiate Test (2) Mediate(Notify & Transfer) Receive Message (A) (3) Notify (1) Initiate Transfer Message (4) Validate Receive Message (B) Test Driver Message validator Verify App. A & B Intermediary Testbed

  23. The NIST test bed Footer text (edit in View : Header and Footer)

  24. Testing Capability: Application Information Mapping Test Bed • Purpose: Verify the mapping between the application’s internal representation and the data exchange specification (i.e., an XML-based business document specifications) APP STEP XML Message OASIS App Date + Time Date XML Message Employee Person Person Person Null 0

  25. XML schema specification for a message Message guideline Semantic Constraints Test Cases Message Instances and Validation Conditions Test Purpose Test Requirement: Check the mapping of the ship-to information when the oa:ShipToParty is omitted at the line level and the oa:ShipToParty is present in the header section Test Data Specification • Occurrences examples: • Header-level ship-to: Occur(1, /aiag:SyncShipmentSchedule[4]); • Line-level ship-to: Occur(0, /aiag:SyncShipmentSchedule[4]/*/*/aiag:ShipmentScheduleLine[1]); • Test data metadata examples: • DUNSID of the ship-to party: UserSpecified(876598675); • Document date and time: DateTimeBefore(PT10M); Making Test Specification

  26. A Testing Application Business Case: Inventory Visibility e-Kanban Process • Project Sponsored by Automotive Industry Action Group (AIAG) • eKanban = “Electronic Kanban” • Cross-partner Business Process • Defined by AIAG • POC Implements eKanban • With Next Gen XML Messaging technology • Variety of Participants • Major OEMs • Suppliers • Multiple IT Vendors

  27. Trading Partner B Tier 1 Supplier to GM Tier 2 Supplier to Tier 1 FTH IV Tool An Application of the Test Bed: An e-Kanban Transaction Interoperability Trading Partner A SyncShipmentSchedule Trading Partner C Tier 1 Supplier to GM GM c Information Mapping Test c Apolon IV Tool GM Legacy App c SyncShipmentSchedule SyncShipmentSchedule Information Mapping Test Information Mapping Test

  28. Examples of Test Results Conformance Issues SUTs (IV Tools) • Examples of other issues found: • Mapping rules between ID & SchemeAgencyID and DUNSID were incorrect • Mapping rules or transformation engine has an issue when mapping multiple kanbans • ATHENA transformation tools are stateless, i.e., they do not maintain any prior information thus it cannot, for example, help fill in sequentially generated information such as document ID

  29. Workshop • A workshop will be held during the same week and at the same place: • To show participants the benefit of Interoperability and conformance testing, • Testing partners (e.g. Korbit, NIST) to present their solutions with use cases, • To show and comment results of the ongoing Plugtests, • ETSI to present its testing methodologies related to standardization • To match the interest of participants on inter-operability issues and the testing solutions.

  30. Benefits for Application Domain Teams • Hands-on understanding and assessment of the technology and standards over a real use case. • Limitations, best practices • Immediate help FROM standards experts and software providers on a personalized solution design. • Very quick feedback TO standards experts, product providers about user requirements. • Acquire leadership to jump-start a general solution design for their domain, and profiling of the eB technology for their app domain. • Discuss and share best practices with teams from other domains.

  31. Benefits for Product Providers • Exposure to requirements from User Communities, acquire advantage over competition. • Verify the value and relevance of their product features with users, over real use cases. • Live feedback to standards committees representatives for future specification improvements. • Verify interoperability and composability of their products.

  32. Next steps • Event planed in Q1 2008 • ETSI Plugtests web pages to be published during summer. • Maintain the relationship and keep support from communities and partners • Seek for participants from application and platform vendors • Seek urgently for Key account vendors in B2B area. • Communicate widely on the Plugtests event. • Improve continuously test plan

  33. Communities to support the Plugtests • To target following communities (not excluding other ones) • Automotiv • BoostAero • DGME (France) • eExport project for cosmetic • GS1 • HL7 • Inventory management project • OASIS • RosettaNet • To be extended ….

  34. Partners • Special thanks to partners: • Fujistu Siemens • Korbit • NIST • We expect extending this list in the next weeks!!

  35. Questions? Contacts: • Francois FISCHER: francois.fischer@etsi.org +33 4 92944330 • Philippe COUSIN: philippe.cousin@etsi.org +33 4 92944306 • Feel free to contact us • Distribute this information to all interested parties.

More Related