1.  Execution Model ETSL Test Cases ETSL Processor (includes case interpreter and monitors) KorBIT ebMS Testbed (includes event adapter and eval adaptor) KorBITAdapter Candidate MSH Trigger Event Board 1

2.  Event Board Architecture Events event evproperties property content @evtype, @id, @temp, @timepost @name 2

3.  Event Board Example eac_testcase_t1_2_1 Processor is created for 'eac_testcase_t1_2_1'. 2b1c8248-5f7b-460f-a8e4-b4d856d3c9b2 <TEST:Event xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:TEST="http://www.oasis-open.org/tc/ebxml-iic/testing/messageStore" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" xmlns:mime="http://www.oasis-open.org/tc/ebxml-iic/testing/mime" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.oasis-open.org/tc/ebxml-iic/testing/messageStore"> <mime:Message Content-Type="multipart/related" boundary="----=_Part_3_21153656.1082534064761" start="20040421-045424Z-00003@61.106.51.198" syncType="asynchronous" type="text/xml"> <mime:MessageContainer Content-Type="text/xml" charset="UTF-8" contentId="20040421-045424Z-00003@61.106.51.198" declaration="true"> … 3

4.  Test Case Example <call adapter="org.kiec.gateway.adapter.EbmsTestAdapter" step="step1" type="event"> http://www.oasis-open.org/tc/ebxml-iic/testing/messageStore http://schemas.xmlsoap.org/soap/envelope/ http://www.oasis-open.org/tc/ebxml-iic/testing/mime http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd Events/event[@evtype='Receive Message']/content/TEST:Event/mime:Message http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oasis-open.org/tc/ebxml-iic/testing/mime http://schemas.xmlsoap.org/soap/envelope/ //mime:Message[mime:MessageContainer[1]/SOAP:Envelope /SOAP:Header/eb:MessageHeader[eb:Service='urn:ebxml:iic:test']] … 4

5.  Issues of implementation We created an event board file per a test case.  If a test case is selected and executed, KorBIT generates an event board with unique id and related event information. We used only the element defined in the specification.  We used the element’s key and value when we need other keys and values. The Event Board is a XML file format, So we had a trouble in implementing the Event Manager to process a massive request of posting simultaneously.  We plan to modify the structure of our event board. We believe that we had better use Data base instead of XML file. The element contains the XML schema. Since some XML schema file is of large size, it need not be loaded in the event board. So we would like to exclude the content from event board when the content has no meaning.  The e-TSL specification may contain how to exclude the content element and instead may refer to the external content. 5

6.  Example of the Difference between specification and implementation [4.1 The Event Model] the element is a wrapper for any document associated with the event. Example: An event may be a SOAP message either sent or received. In that case the element contains the SOAP envelope or a subset of it. In case there are attachments (MIME parts) these may remain external to the event envelope representation, and be referred to.  The element in our Testbed contains a whole MIME part. <TEST:Event xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:TEST="http://www.oasis-open.org/tc/ebxml-iic/testing/messageStore" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" xmlns:mime="http://www.oasis-open.org/tc/ebxml-iic/testing/mime" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.oasis-open.org/tc/ebxml-iic/testing/messageStore"> <mime:Message Content-Type="multipart/related" boundary="----=_Part_19_10700675.1206411428765" start="20080325-111708Z-00004@192.168.10.116" syncType="asynchronous" type="text/xml"> <mime:MessageContainer Content-Type="text/xml" charset="UTF-8" contentId="20080325-111708Z-00004@192.168.10.116" declaration="true"> <SOAP:Envelope … <mime:MessageContainer Content-Type="application/octet-stream" contentId="payload_01"> 6