STIMULATING INNOVATION IN THE FOOD SUPPLY-CHAIN THROUGH SMART USE OF ICT: ASSISTING SMES PARTICIPATE IN DIGITAL SUPPLY C

1. STIMULATING INNOVATION IN THE FOOD SUPPLY-CHAIN THROUGH SMART USE OF ICT: ASSISTING SMES PARTICIPATE IN DIGITAL SUPPLY CHAINS IN THE SINGLE MARKET • eFoodChain B2B Connector • Development of solutions based on the eFoodChain Interoperability Framework • Hackathon like session César Toscano, ctoscano@inesctec.pt • Smart AgriMatics Conference, Paris, 2014-06-18/19

2. Agenda • Introduction to the eFoodChain B2B Connector • eFoodChain Messaging Service • Software implementation • Achieved functions • Integration with ERP-like systems • Interaction between Connectors • Web Service API • Practical session: • Install the B2B Connector on your personal computer • Configure the B2B Connector • Send and receive a message (shared folder) • Send and receive a message (web service)

3. The eFoodChain Messaging Service • Service provided to any actor in the supply chain (farmer, producer organization, technical partner, etc.) allowing him to send a business document in electronic form to another actor in the supply chain with whom he has a business relationship Two types of data interchange: • Direct interchange • Intermediated interchange API (Application Program Interface) and communication protocols: • AS2 / HTTP - for exchanging EDIFACT documents • SOAP / HTTPS - for exchanging XML-based documents Documents are encapsulated by the UN / CEFACT Standard Business Document Header (SBDH)

4. Software implementation • Low cost, ‘plug & play’ software element, able to be deployed and configured in the SME’s ICT infrastructure within the maximum time frame of one day • Software implementation of the eFoodChain Messaging Service, under the Open Source license CDDL • 32 bit / 64 bit releases for Windows and Linux operating systems, available at: • http://www.efoodchain.euor • http://co-operate.inescporto.pt/efoodchain_b2b_connector/ • Provides a web-based user interface

5. Achieved functions Secure Transmission Storage Visualisation B2B Connector Attachments Notification Archiving External Programs Files upload/download

6. Integration with ERP-like systems SME eFoodChain Connector Internet HTTPS ERP Message Message • API through: • Shared folder • Web Service SME - Small or medium sized company ERP - Enterprise Resource Planning system

7. Interaction between Connectors • Direct interaction

8. Interaction between B2B Connectors • Interaction through a mediator A test bed B2B mediator with a B2B Connector is available at co-operate.inescporto.pt

9. Web Service API • Connection scenario A

10. Web Service API • Connection scenario B

11. Practical session: Install the B2B Connector • On Windows-like operating system: • Expand the distribution file “efoodchain-connector-win32-1_4_0.zip” on you personal computer • Run the script “efoodchain-setup/SETUP.bat” • Define a StationID for your connector. Available StationIDs: “urn:efoodchain:eu:smartagrimatics:001” “urn:efoodchain:eu:smartagrimatics:002” … “urn:efoodchain:eu:smartagrimatics:015” • Run the script “efoodchain-tomcat-7.0.42/install-service.bat” • Run the script “efoodchain-tomcat-7.0.42/start-service.bat” • On Linux-like operating system: • Expand the distribution file “efoodchain-connector-linux32-1_4_0.tar” on you personal computer • Run the script “efoodchain-setup/SETUP.sh” • Define a StationID for your connector. Available StationIDs: “urn:efoodchain:eu:smartagrimatics:001” “urn:efoodchain:eu:smartagrimatics:002” … “urn:efoodchain:eu:smartagrimatics:015” • Run the script “efoodchain-tomcat-7.0.42/install-daemon.sh” • Run the script “efoodchain-tomcat-7.0.42/start-daemon.sh”

12. Practical session: Configure the B2B Connector • Activate you Internet browser on link: http://localhost:8080/efoodchain • Authenticate yourself: User: admin Password: admin • Choose “CONNECTIONS / Outbound Connections”, select the single outbound connection you find there (testbed B2B mediator) and edit it Define password as “01020304” • Choose “CONNECTIONS / Check Connections”, select the outbound connection and press “Check Connection” button “Check Retrieval of Messages” button • Access to remote host and service should be OK. • Choose “CONNECTIONS / Routings”, there is a single routing entry: all types of messages are sent to urn:efoodchain:pt:inescporto:porto:001

13. Practical session: Configure the B2B Connector • Choose “WORKFLOW / Configuration” and press “Add Notification” button Select outbound in the Process field Define en in the language field Select admin field and transfer it to Users to notify field Save “Add Notification” button Select inbound in the Process field Define en in the language field Select admin field and transfer it to Users to notify field Save

14. Practical session: Send and receive a message (shared folder) • Get sample of XML file on your software distribution: “efoodchain-xml-samples/agro-observation-report-sample.xml” • Copy file to folder “efoodchain-data/messages-to-send-to-internet” File is sent to the testbed B2B mediator • In the browser, choose “DASHBOARD” An outbound transaction will appear stating that the message was accepted by the testbed B2B Mediator After some time, an inbound transaction will appear stating that you have received a new message (the testbed B2B Mediator is sending back to you all messages that you send)

15. Practical session: Send and receive a message (web service) • Web Service WSDL available on your Connector: http://localhost:8080/efoodchain/services/EFoodChainB2BConnectorErpAdapterApi?wsdl • Call web service operation: dispatchMessage(“ErpAdapter”, “ErpAdapter.13579”, “...message…”) Message is delivered to your Connector (to be subsequently sent) • Call web service operation: List<String> messages = getMessages(“ErpAdapter”, “ErpAdapter.13579”, 0, “*”) Received messages are taken from the Connector

16. The eFoodChain B2B Connector • Thank you for your participation.