1. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Promoting e-Business and Web Services Standards to SMEs in Japan, and Asia www.oasis-open.org 29 October 2007 Kazunori Iwasa, Masahiko Narita, Makiko Shimamura, and Jacques Durand Fujitsu Limited, Fujitsu Computer Systems This article includes a joint effort by Fujitsu, ECOM, DSRI, Fuji Electric Information Service, and NEC Soft, and the following persons were contributing and greatly appreciated: Masahiko Narita, Toshikazu Kasai, Kazunori Iwasa, and Makiko Shimamura from Fujitsu, Hisanao Sugamata from ECOM, Masato Sakamoto from DSRI, Yukinori Saito from Fuji Electric Information Service, and Naomasa Hosoda from NEC Soft.

2. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Table of Contents Background Information  B2B adoption rates in Japan  Goal of Japanese government for B2B-EC adoption  Overview of Japanese Industries Promoting B2B standard to SMEs in Japan  Requirements to promote B2B in SMEs in Japan  Resolution: Client system with Pull messaging  Requirements from Industry Organizations to Pull messaging  Industries have adopted standard specification Promoting Web Services standards by Interoperability testing in Asia  Interoperability testing in eBusiness Asia Committee  Requirements for the Interoperability test  Testing tool for Reliable Messaging was developed  Next Interoperability Testing

3. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Overview: 99% of Japanese Enterprises are SMEs * Capital is more than 300 Million Yen (about $2.5 million). 14,705 1,602,830 Source: 2001 business establishment/Company Statistical Research by Statistics Bureau, Ministry of Internal Affairs and Communications Total:1,617,535

4. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 B2B-EC adoption rates 1) in Large Enterprises : 24% Source: 2001 business establishment/Company Statistical Research by Statistics Bureau, Ministry of Internal Affairs and Communications 2) in SMEs : 8% 127,125 1,475,705 3,499 11,206

5. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 The Goal of the Japanese Government : Making B2B-EC adoption rate more than 60%. (More than 50% in SMEs) Source: 2001 business establishment/Company Statistical Research by Statistics Bureau, Ministry of Internal Affairs and Communications The Key Issue is to increase adoption rate for SMEs.

6. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Overview of Industries and organizations promoting B2B Retail Industry  Japanese standard protocol in retail industry - “Japan Chain Stores Association(JCA) Protocol” is widely used in Retail industry from 1980s. It is a vertical standard in Retail industry in Japan. It is pull messaging that Client asks for messages to receive. Adoption rate between retail stores and wholesale/manufacture for purchase operation is more than 90%.  DSRI (The Distribution Systems Research Institute) has defined Pull Messaging extension for “SOAP-RPC”. They have executed POC in 2004. Manufacturing Industry  JEITA ECALGA project : Parts Procurement System with ebXML (December 2003 ～ ) Standardized a specification that is Open-EDI reference model (ISO14662) compliant It has adopted ebMS 2.0. Many systems are in-service. COXEC (Common XML/EDI Practice Promotion Council)  It aims to promote EDI service with ASP model to SMEs widely.  It has defined “Common XML/EDI Framework” in December 2005. eBusiness Asia Committee (eAC)  eAC has issued certification for 20 products/implementations that has passed interoperability test for ebMS2.0. It is planning to execute the next interoperability test for ebMS3.0 and WS-Reliability/RM.

7. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Activities to promote B2B and Web Services Standards OASIS Standardizing B2B / Web Services specifications Vertical Industry Vertical Standardization Horizontal Market Interoperability Testing AdoptionRequirements Adoption Feedback Activity 1Activity 2 Promoting B2B standard (ebXML) to Vertical organizations Promoting Web Services standard by Interoperability testing

8. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Promoting B2B standard to Vertical: Adopting Industry Requirements into a specification OASIS Standardizing B2B / Web Services specifications Vertical Industry Vertical Standardization Horizontal Market Interoperability Testing AdoptionRequirements Adoption Feedback

9. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Requirements to Promote B2B in SMEs in Japan System should be easy to adopt  It should be light-weight and it should be easy to exchange data on the Internet. Most SMEs are not adopting real time processing. They are not required to process the data in real time. They are not required to connect the Internet 24X7.  A single B2B system should be able to use for all trading partner. Although legacy Web-EDI is affordable, it requires to use the different Web EDI systems for each trading partner. Sometimes it requires to pay multiple system fee for multiple Web-EDI systems. System should be easy to use  It should be easy to exchange message like FAX.  Single interface should allow to exchange with multiple trading partners. Legacy Web EDI systems requires to input data manually in each trading partner. It is expensive in terms of human resources. Messaging data in client system should be reused in other systems  Legacy Web EDI systems don’t allow to reuse data, since all data is stored in server.

10. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Resolutions: Standardizing Pull Messaging for Client/Server System Client/Server system with Pull messaging  It realizes affordable adoption of B2B messaging infrastructure and easy maintenance. Standardizing a Pull messaging standard on ebXML Messaging Services -> Added pull messaging to ebMS2.0 -> ebMS3.0  Standardizing a specification to realize a standard way with a single system to communicate all trading partners.  Existing standard (e.g.,ebMS2.0) is Push messaging. Sender sends an EDI data to the Receiver. Benefit is real time messaging, but it cost a lot for receiver, since it has to stand by for incoming messages. It requires Server operating 24X7, a global IP address, and continuous security maintenance. With Pull messaging, Receiver retrieves an EDI data from Sender.  It is not real time messaging, but the benefit is you don’t have to change the system architecture. It is Legacy EDI friendly. You don’t have to wake your system up 24X7. You can use the client only when you want to receive a message. It doesn’t require global IP address costing you a lot. It is OK even if the Internet connection is dial-up.  Pull messaging meets requirements from SMEs, an it realizes affordable adoption cost and easy maintenance for B2B.

11. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Reference Material Pull Messaging Model  When the server sends a message to the client, it puts the message on the local storage for client to retrieve, rather than sending it directly.  Client sends a query (PullRequest) for a message to receive, when the client is ready to receive the message. This message is sent on HTTP Request typically.  When the server receives a PullRequest from the client, it checks whether there is any message for the client. The server sends back the message on HTTP Response, if there is any. ClientServer

12. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Requirements from Industry Organizations to Pull messaging Requirements from DSRI 、 JEITA 、 COXEC activities ① Supporting a simple authentication for client. ② A mechanism to enable receiver that is not accessible from outside to retrieve a message.  This mechanism is useful when: A Server can not be maintained, The system is not accessible 24X7, There is no global IP address, or The firewall doesn’t allow incoming connection.  It has defined Message Exchange Patterns (MEPs) to define binding to underlying protocol. One of them is Pull messaging. ③ Supporting Prioritized/Categorized Messaging  Message exchange between Client and Server can be categorized. This mechanism enables to prioritize some categorized messages to others. (See the next slide for example.) ④ Supporting Reliable Messaging (e.g., Resending a lost message and recovering after system down) that doesn’t depend on the application These are proposed to ebMS3.0 standardization

13. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Industries have adopted standard specifications ebMS3.0 is approved as OASIS standard in October 2007. JEITA and COXEC have adopted ebMS3.0 and implemented ebMS3.0 to promote in their industry. DSRI have been defining their own pull messaging extension for SOAP-RPC. However, ebMS3.0 may be considered as an alternative, since it is standardized now.

14. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Promoting Web services standards by Interoperability testing OASIS Standardizing B2B / Web Services specifications Vertical Industry Vertical Standardization Horizontal Market Interoperability Testing AdoptionRequirements Adoption Feedback

15. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Interoperability testing in eBusiness Asia Committee(eAC) eAC Interoperability Task Group has executed Interoperability testing for ebMS2.0 since 2003, and 20 organizations from Japan, Korea, China, Chinese Taipei, Hong Kong, and Thailand have obtained certification. It is planning the next interoperability test in 2008 to promote Web Services and B2B Standards further. Candidates are:  ebXML Messaging Services 3.0 / 2.0  WS-Reliability1.1 / WS-RM1.1  WS-Security1.1  And other ebXML and Web Services technologies The first technology to target for interoperability test in ITG is WS-Reliability/RM, since it is critical to B2B.

16. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Requirements for the Interoperability test Interoperability test should cover enough test items and error cases. It should leverage the existing testing process/technologies. E.g., OASIS IIC, ebXML Asia, and others. Tester should be able to verify the testing items itself. E.g., It should allow to validate correctness of test items. Testing and its validation should be easy. E.g., Many testing process should be automated. Testing process should be easy to extend and easy to maintain. E.g., Testing should be independent from protocol binding.

17. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Testing Tool for Reliable Messaging was developed It was developed by Digital Information Equipment Interoperability Platform Project at NEDO/INTAP in Japan The goal of this activity is to ensure interoperability of reliable messaging for Web services. Target specification: OASIS WS-Reliability1.1. And WS-RM1.1. Deliverables from the project:  Profile  Conformance/Interoperability test tools Leveraging existing achievements from ECOM, ebXML Asia and WS-I  E.g., ebXML Message Service Deployment Guide, ebXML Interoperability Test Specification, CPA Templates, WS-I profiles The test tool is offered freely to promote interoperable reliable messaging. If you are interested in testing tool, contact me for detail.

18. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Reference Material Architecture of Testing tool Message Logger Log Data Report Message Log Analyzer Reliable Messaging Engine Trouble Maker Validation Data Application Test Manager Validation Engine Deliverables of this project User Systems Test ProgramApplicationTest Program Error Case Reliable Messaging Engine ApplicationTest Program Trouble Maker

19. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Reference Material Test Categories 1. Message Format Tests Validating a message format exchanged on the network  Conforming to OASIS WS-Reliability1.1 or WS-RM 1.1 specification 2. Binding Tests Validating a binding of messages and underlying protocol 3. Protocol Sequence Tests Guaranteed delivery, Duplicate elimination, and Message ordering Test Patterns Conformance test for reliable messaging engine Interoperability test between two reliable messaging engines Interoperability test between two applications

20. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Reference Material Snapshot of Test Report  The GUI outputs validation result of message format Output with each combination of request and response Display of test item and its test result with each message

21. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Next Interoperability Testing eBusiness Asia Committee has discussed about the next Interoperability testing in the Last F2F meeting in August in Thailand.  WS-Reliability/RM will be ready to test in 1Q2008  ebMS3.0 test will be ready after 2Q2008  There are participants who are interested in ebMS2.0. Testing doesn’t require fee, and the testing tool will also be ready with no charge.

22. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Conclusion Japanese government is going to promote B2B in SMEs. Making a half of SMEs adopt B2B. To Promote B2B standard to Vertical Organizations, we have incorporated their requirements to OASIS standard. E.g., Pull messaging for SMEs to ebMS3.0 To Promote Web Services standards, we are proposing Interoperability testing  Testing Procedure, Testing Tools,and Conformance and Interoperability testing help to promote adoption the standard specifications

23. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Contact Information: Kazunori Iwasa Fujitsu Limited kiwasa@jp.fujitsu.com Contact me for - ebXML MS 3.0 interoperability test, - WS-Reliability/RM interoperability test. Thank you.

24. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007

25. Status of B2B adoption in Japan Electronic trading adoption rate in entire Japanese company is 8.1%  Adoption rate for Large enterprises(which has capital three hundreds million yen or more) is 23.8%  Adoption rate for Small and Medium enterprises(which has capital less than three hundred yen) is 7.9%  It is necessary to have SME which is 99.1% of Japanese enterprises in Japan adopt B2B to increase the rate of B2B adoption. The goal of Japanese government is to make the adoption rate of all enterprises in Japan more than 60%. (50% or more in SMEs) Size of company (Capital) Total number of Japanese enterprises Number of enterprises adopting B2B-EC Number of enterprises ％ Number of enterprise s ％ Large Enterprises (\300million or more) 14,7050.93,49923.8 SMEs (Less than \300million) 1,602,83099.1127,1257.9 Total1,617,535 100. 0 131,0208.1 Source: 2001 business establishment/Company Statistical Research by Statistics Bureau, Ministry of Internal Affairs and Communications

26. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 User B2B System Architecture Typical message exchange is realized with a combination of message and box.  When a message is sent from Client to Server, client specifies the sending box, and send the message with push messaging – “Request Message” and “Acknowledgement Message”.  When the Client receives a message from Server, Client specifies a Box to receive, and it requests a message with Pull Request Message. The the Pull Response Message from the sender contains the message for the receiver. The Receiver can send back Acknowledgement Message as a receipt of the message. Received Message is stored in the specified box. Send Operation Processing a message received in the Sending Box real time. Message Server Client Request Message ＋ Acknowledgement Message Message Distribution Server Sending Box Sending Directory Message Request Message ＋ Acknowledgement Message Message boxId specifies the Sending Box.

27. All Right Reserved, Copyright © Fujitsu Limited and Fujitsu Computer Systems 2006-2007 Example: Categorized message exchange with Message Boxes Each category of messages are specified by Box. Creating a box named “Business Message” and a box named “Signal”. Server put a business message to the Business Message Box, and it puts a signal message - an Error or Acknowledge message – the Signal box. This is realized with Message Partition Flow in ebMS3.0 Business Message box Signal box Server (ASP or Large Enterprises) Internet Client receives Business Messages only Client receives Signal Message (e.g., Acknowledgement message) only Client