/Transaction-Context-Manager

The Transaction-Context-Manager generic building block is an alternative data persistence mechanism for managing the history of context. It is based on Apache NiFi and is a dataflow system based on the concepts of flow-based programming. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic and also offers an intuitive…

Apache License 2.0Apache-2.0

Smart MaaS
SMART MOBILITY SERVICE PLATFORM
Smart MaaS

Contact • Issues • Project Page

Transaction Context Manager

It is a generic building block to process data from a big variety of datasources and processing frameworks on a transaction basis. It offers a new interaction pattern that offers new ways of data processing, brokering and marketing.

The Smart MaaS demo applications are alreay published and available in the file https://github.com/SmartMaaS-Services/Transaction-Context-Manager/blob/main/Transaction-Context-Manager.xml here in the repo. It is a Apache Nifi template that is ready for usage and it contains integrates parts of

  • the Flixbus API for buying tickets for Flixbus and Flixtrain
  • the TripGo API for obtaining individual routing
  • the KillBill API for handling payments and provide clearing and subscription capabilites
  • the EsriGIS datasource for charging stations in Germany

You can simply import the template into Nifi, but for full operation you need the following (you can use parts to start working with some APIs):

  • A Nifi instance
  • A Orion-LD instance
  • Both instances must be available to connect to each other
  • Auth Token for connecting to the Context broker
  • Credentials to connect to the Flixbus API
  • Credentials to connect to the TripGo API
  • A running instance of Killbill with its credentials