1 / 6

FIspace Review meeting M12 B2B Component

FIspace Review meeting M12 B2B Component. B2B component. Composed of two complementary modules BCM – Business Collaboration Module EPM – Event Processing Module BCM Enables the orchestration and execution of business collaborations in the FIspace platform

mirabelle-nicolas
Download Presentation

FIspace Review meeting M12 B2B Component

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FIspace Review meeting M12B2B Component

  2. B2B component • Composed of two complementary modules • BCM – Business Collaboration Module • EPM – Event Processing Module • BCM • Enables the orchestration and execution of business collaborations in the FIspace platform • Holistic view of the entire supply chain by all involved stakeholders • Tool: ACSI EU project outcome (design-time and run-time) • EPM • Monitors the actual execution of FIsapce collaborations and alerts in case of exceptions in real-time • Tool: CEP GE (design-time and run-time)

  3. B2B component – Work done M6-M12 (1/2) • Design • First design for all eight use cases in the project in collaboration with the business users has been done both for the BCM and for the EPM. For the BCM, the GSM (Guards, Stages, and Milestones) models have been specified, while for the EPM the event rules have been defined. • Implementation and deployment • Implementation and deployment of the two selected scenarios in each engine BCM and EPM • Integration of the two components with the CSB

  4. B2B component – Work done M6-M12 (2/2) • BCM new features • Development of a Bridge • Connects between incoming/outgoing messages/events from/to the CSB component in the platform and the corresponding Business Entities (BEs) instances for a specific collaboration. • Creates a new BE instance if necessary. • Inclusion of BCM in SDK • EPM new features • Development of a new adapter for the CSB (new consumer and producer) • Inclusion of this new type of adapter both in the authoring and run-time tools • Support for multiple operation systems deployment. The CEP GE now runs on Linux (Ubuntu and CentOS) in addition to Windows • Enrichments to the run-time engine • The ABSENCE pattern has been refactored to also provide information regarding incoming events

  5. B2B component – Work planned M12-M24 • In general, extensions to the engines are driven by use cases requirements • Main goal: improve consumability of the tools • BCM • Basic BE templates • Request-response API (in addition to today’s async. call) • Security • Align with the platform security • Access control integration with IDM • Make use of the Authorization Views (as needed) • EPM • Basic event rules templates • Inclusion of EPM in SDK

  6. B2B component – Challenges • Tools are research assets • Unstable • Extensions imply deep knowledge of the code • Consumability– tools are intended for IT experts in (data-centric) business process management and event processing

More Related