This is the code repository for the Business Ecosystem RSS, one of the components that made up the Business API Ecosystem GE. The Business API Ecosystem is part of FIWARE, and has been developed in collaboration with the TM Forum.
Any feedback is highly welcome, including bugs, typos or things you think should be included but aren't. You can use GitHub Issues to provide feedback.
The Business API Ecosystem is a joint component made up of the FIWARE Business Framework and a set of APIs (and its reference implementations) provided by the TMForum. This component allows the monetization of different kind of assets (both digital and physical) during the whole service life cycle, from offering creation to its charging, accounting and revenue settlement and sharing. The Business API Ecosystem exposes its complete functionality through TMForum standard APIs; concretely, it includes the catalog management, ordering management, inventory management, usage management, billing, customer, and party APIs.
In this context, the Business Ecosystem RSS is in charge of distributing the revenues originated by the usage of a given service among the involved stakeholders. In particular, it focuses on distributing part of the revenue generated by a service between the Business API Ecosystem instance provider and the Service Provider(s) responsible for the service. With the term "service" we refer to both final applications and backend application services (typically exposed through an API). Note that, in the case of composite services, more than one service provider may have to receive a share of the revenues.
The Business Ecosystem RSS is installed as part of the Business API Ecosystem, so the instructions to install it can be found at the Business API Ecosystem Installation Guide. You can install the software in three different ways:
- Using the provided script
- Using a Docker Container
- Manually
For further documentation, you can check the API Reference available at:
To execute the unit tests, just run:
mvn test -fae
You can also find this documentation on ReadTheDocs