Page History

Fineract is spread into roughly 30 projects, building each of which produces an artifact.  This is an overview of the various categories of projects, their generic structure, and how they play a role in the Fineract CN ecosystem.

Table of Contents

Libraries

Libraries are not deployable pieces of code.  They are intended to support the common functionality of the Microservices.  Most library projects produce one build artifact and contain unit tests for its classes.  I've listed a few specific libraries are listed with the integration tests since they are only used in them.

...

Code name: 

Description:

UI

We currently only have one UI project.

fims-web-app

Depends on all the services above (except group) to provide back office functionalityThis is one project which depends on the services.

Integration Tests

Integration tests run multiple services together to check that their interdependencies work as intended.  Integration tests are named for the services they include.

service-starter

Description:Starts services, eureka, and ActiveMQ for the integration tests.

default-setup

Description:For example setup information.  Currently only contains a standard chart of accounts for the accounting service, but should in the future contain roles for identity, and other useful standard data for the rest of the services for a generic initial setup.

test-accounting-portfolio

...

demo-server is a project which uses the same methodology as the integration tests to deploy all the services together except the UI and to provision them in a generic way.  This is a reasonable place to start in playing with deployment, and you will need to understand it's provisioning code well to be successful, but it is unlikely that you will be able to build a production environment based solely on demo-server.