[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-656153-105":59,"doc-detail-656153-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","access-point-ws-plugin-interface-control-document-version-38-status-final","Access Point - WS plugin - Interface Control Document - Version 3.8 - Status Final","","European Commission Digital Europe Programme interface control document for the Access Point WS plugin, detailing functional and behavioural specifications across multiple components. It defines purpose, scope, intended audience, and references, then covers use case overviews and detailed scenarios for submitting, retrieving, checking status, and listing pending messages. The document specifies WS plugin configuration, WSDL model for Domibus 5.x.y, payload referencing, security (authentication and authorization), plugin notifications, multitenancy, push-to-backend rules, backward compatibility, and annexes with message standards and error codes.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/access-point-ws-plugin-interface-control-document-version-38-status-final/656153/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/access-point-ws-plugin-interface-control-document-version-38-status-final/656153.png","ImageObject",300,407,{"name":92,"@type":93},"Mia  ","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-25",true,{"@type":102,"interactionType":103,"userInteractionCount":14},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What is the purpose and scope of the Access Point WS plugin Interface Control Document?","Question",{"text":112,"@type":113},"It provides the interface control for the Access Point WS plugin, describing its purpose, scope, and intended audience, supported by listed references.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"Which use cases are specified for message handling?",{"text":117,"@type":113},"The document defines detailed use cases for submitting messages, retrieving messages, getting message status, and listing pending messages.",{"name":119,"@type":110,"acceptedAnswer":120},"How does the document address security for the plugin interface?",{"text":121,"@type":113},"It includes a dedicated security section covering authentication and authorization requirements.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},656153,1793030767,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":14,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":139,"language":140,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":141,"faqs":142,"seo_title":143,"seo_description":67,"update_tm":144,"read_time":145},687207024478,"https://ap-avatar.wpscdn.com/davatar_a8503ba1806abce46bf441b54a3ca4cd","EUROPEAN COMMISSION  \nDIGIT  \nDigital Europe Programme  \nAccess Point  \nInterface Control Document  \nWS plugin  \nVersion [3 .8]  \nStatus [Final]  \n© European Union, 2024  \nReuse of this document is authorised provided the source is acknowledged. The Commission's reuse policy is implemented by Commission Decision 2011/833/EU of 12 December 2011 on thereuse of Commission documents.  \nDate: 19/03/2024  \nTable of Contents  \n1. INTRODUCTION ................................................................................................................. 5  \n1.1. Purpose of the Interface Control Document.............................................................................5  \n1.2. Scope of the document .............................................................................................................5  \n1.3. Audience ....................................................................................................................................5  \n1.4. References .................................................................................................................................6  \n2. INTERFACE FUNCTIONAL SPECIFICATION ............................................................................ 7  \n2.1. Purpose of the Access Point component ..................................................................................7  \n2.2. Use case overview .....................................................................................................................8  \n2.2.1. Actors......................................................................................................................................8  \n2.2.2. Use cases diagram ..................................................................................................................8  \n2.3. Detailed uses cases....................................................................................................................9  \n2.3.1. UC01 – Submit Message .......................................................................................................11  \n2.3.2. UC02-Retrieve Message ..................................................................................................... 18  \n2.3.3. UC03-Get the status of the Message..................................................................................26  \n2.3.4. UC04 – List Pending Messages .............................................................................................28  \n3. INTERFACE BEHAVIOURAL SPECIFICATION........................................................................ 30  \n3.1. WS plugin configuration ..........................................................................................................30  \n3.2. WSDL model for Domibus 5.x.y ...............................................................................................32  \n3.2.1. The WSDL schema ................................................................................................................32  \n3.2.2. The data model applicable to SubmitMessage from C1 to C2 (domibus-submission.xsd) ..33  \n3.3. Referencing Payloads ..............................................................................................................46  \n4. SECURITY......................................................................................................................... 48  \n4.1. Authentication.........................................................................................................................48  \n4.2. Authorization...........................................................................................................................48  \n5. PLUGIN NOTIFICATIONS ................................................................................................... 50  \n6. MULTITENANCY............................................................................................................... 51  \n7. PUSH TO BACKEND ...................................","cbCaiiG7VblSial5","https://ap.wps.com/l/cbCaiiG7VblSial5","pdf",1554599,74,"English","# 1. Introduction\n## 1.1. Purpose of the Interface Control Document\n## 1.2. Scope of the document\n## 1.3. Audience\n## 1.4. References\n# 2. Interface Functional Specification\n## 2.1. Purpose of the Access Point component\n## 2.2. Use case overview\n## 2.3. Detailed uses cases\n# 3. Interface Behavioural Specification\n## 3.1. WS plugin configuration\n## 3.2. WSDL model for Domibus 5.x.y\n## 3.3. Referencing Payloads\n# 4. Security\n## 4.1. Authentication\n## 4.2. Authorization\n# 5. Plugin Notifications\n# 6. Multitenancy\n# 7. Push to Backend\n## 7.1. Introduction\n## 7.2. Notifications to plugin\n## 7.3. Rules configuration\n## 7.4. Notifications to backend\n# 8. Backward Compatibility\n## 8.1. Domibus 5.x: new Web Service\n## 8.2. Migration guide from the old WS Plugin interface to the new WS Plugin interface\n# 9. Annexes\n## 9.1. WS plugin interface message standards\n## 9.2. Backend interface message standard","[{\"question\":\"What is the purpose and scope of the Access Point WS plugin Interface Control Document?\",\"answer\":\"It provides the interface control for the Access Point WS plugin, describing its purpose, scope, and intended audience, supported by listed references.\"},{\"question\":\"Which use cases are specified for message handling?\",\"answer\":\"The document defines detailed use cases for submitting messages, retrieving messages, getting message status, and listing pending messages.\"},{\"question\":\"How does the document address security for the plugin interface?\",\"answer\":\"It includes a dedicated security section covering authentication and authorization requirements.\"}]","Access Point - WS plugin - Interface Control Document - Version 3.8 - Status Final | PDF",1792966738,186]