Footer text (edit in View : Header and Footer) The B2B Plugtests event in 2008 – Sophia Antipolis Réunion Architectures techniques TIC PME 2010 Francois.

Footer text (edit in View : Header and Footer)

The B2B Plugtests event in 2008 – Sophia Antipolis

Réunion Architectures techniques

TIC PME 2010

Francois FISCHER

Philippe COUSIN

2

World Class Standards

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


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

COST & TIME SAVING !

6


PlugtestsTM :Your Fully Customizable Service

TechnicalManagement

Customized test bed, test cases set-up with experts, tests slots schedule…

EventManagement

Website, registration on-line, hosting site, legal aspects..

CommunicationManagement

Event promotional kit development, event presentation at key conferences, dissemination by internal/international press…

SponsorshipOpportunities

Sponsor us! Your value…www.etsi.org/plugtests/sponsorus

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:

Messaging

BusinessTransaction

BusinessDocument

ApplicationSemantics

and Services

BusinessProcess

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

Supportteam

16


ApplicationDomain

“Health Care”Team

Testbedteam

StandardsExperts

(ebXML, WS)

ApplicationDomain

“Invoicing”Team

ApplicationDomain “eGov”Team

assist

Softwareproviders

assist

SupportTeam

Application Domain Teams

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


The Korbit test bed

19


KorBIT::Coverage & Vision

SUT Type Current Supports Future Supports

Messaging ebMS 2.0/3.0

RAMP profile W/S

Generic W/S

Document Schema design quality

Content validation

Information mapping

Semantics mapping

Transaction

(Process)

N/A ebBPSS

WS-BPEL

Infrastructure N/A ebReg/Rep

UDDI

20


KorBIT::Test Framework (ATF)

TSE

WS-BPEL

Test Execution Model

ExtractorTCEETSL

Test Case

TestReportTVI TRI

Interface

TestService

TMCMessage out

Message in

Service call

Dynamicinvocation

Non-stationaryComponent

StationaryComponent

Internalinvocation

Document

MEI

21


KorBIT::Test Case Generation

Test Procedure

Test Sequence Verification Script

Abstract Test Case

Test Harness

Standard Specification

Test Assertions Configurations

Executable Test Case

Test Data

User Requirement

User Environments

Transform to

Based on

Implement

Composed of

Abstract Test Suite

Derived from Derived from

Test Requirement

Executable Test Suite

Test Metadata

Referred to

22


KorBIT::Test Orchestration

App. A App. B

(3) Notify

Test Driver

Message validator

Intermediary Testbed

(1) Initiate

(2) Mediate(Notify & Transfer)

(4) Validate

Test case

Initiate Test

Receive Message (A)

Transfer Message

Receive Message (B)

Verify App. A & B


The NIST test bed

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)

STEP

OASIS AppDate

+Time

Date

Employee Person

PersonPerson

0Null

XML MessageXML Message

XML MessageXML Message

APP

25

World Class StandardsXML schema specification for a message

Message guideline

Semantic Constraints

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 Purpose

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);

Test Data Specification

Message Instances and Validation

Conditions

Test Cases

Making Test Specification

26


27


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

28


Tier 1 Supplier to GM

c

Trading Partner A

Apolon IV Toolc

GM

GM Legacy App

Trading Partner C

c

Tier 1 Supplier to GMTier 2 Supplier to Tier 1

Trading Partner B

FTH IV Tool

SyncShipmentSchedule



An Application of the Test Bed: An e-Kanban Transaction Interoperability

InformationMapping

Test

InformationMapping

Test

InformationMapping

Test

29


Examples of Test ResultsMax Kanban Loops Per Message (1..*)

Max Kanbans per loop (1..*)

Kanban number format (string)

GM Legacy 1..1 1..1 String

Apolon 1..1 1..* Integer

Ford Test Harness 1..* 1..* String

Interoperability Profile 1..1 1..1 Integer

SUTs (IV Tools)

Conformance Issues

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

30


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.

31


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.

32


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.

33


Next steps

1. Event planed in Q1 2008

2. ETSI Plugtests web pages to be published during summer.

3. Maintain the relationship and keep support from communities and partners

4. Seek for participants from application and platform vendors

5. Seek urgently for Key account vendors in B2B area.

6. Communicate widely on the Plugtests event.

7. Improve continuously test plan

34


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 ….

35


Partners

Special thanks to partners: Fujistu Siemens Korbit NIST

We expect extending this list in the next weeks!!

36


Questions?

Contacts: Francois FISCHER: [email protected]

+33 4 92944330 Philippe COUSIN: [email protected]

+33 4 92944306

Feel free to contact us Distribute this information to all interested parties.

Footer text (edit in View : Header and Footer) The B2B Plugtests event in 2008 – Sophia Antipolis Réunion Architectures techniques TIC PME 2010 Francois.

Documents

world class standards

plugtests events

etsi members plugtests

b2b plugtests event

organization of test

ebxml slide

event test methodology

test events experts