Dear Gabor,
Thanks for contacting us.
FIWARE is based on main blocks called GEs (Generic Enablers) that you can install and use. The word "Generic" means that they are not specific to any sector but general purpose. Nearly all of the reference implementations that we provide are free to use (I can only think of one exception in the Security chapter that we will replace in the future). These GEs are exposed via services (mainly REST interfaces) and anyone can build his own apps that would talk to and use the capabilities of the GEs of his choice. The REST interfaces are described in the Open Specifications (all of them linked from the catalogue ... read on)
The wiki (http://wiki.fi-ware.org/) has lots of information but part of the GEs on the wiki are no longer maintained by FIWARE. The up to date reference is the catalogue (http://catalogue.fi-ware.org/enablers). All the components there are alive and supported. The Catalogue concentrates all the pointers to the materials related to a given GE in the wiki or other places without the need to search everywhere. It also shows you the Terms and Conditions in a dedicated tab. I would go to the catalogue and see if the GEs there are useful for you.
There is a free experimentation environment called FIWARE Lab ( https://lab.fi-ware.org/). This environment allows you to deploy GEs and try them. We are progressively incorporating automated deployment facilities to easily install instances of our software on top of your virtual infrastructure on FIWARE Lab.
Our eLearning web site (FIWARE Academy - http://edu.fi-ware.org/) is also there for you to use. Most of the times you'll get a link to this tool from the catalogue if there is a course for the GE you are browsing on the catalogue.
The way to be "compatible" with us is to speak in the same language, that is to say, implement the REST interfaces to our technology making them compliant with the open specs.
In summary, take a look at the catalogue<http://catalogue.fi-ware.org/enablers>, see what GEs you are going to use and then you will have to install them. You may want to use FIWARE Lab, our free experimentation environment with self deployment facilities. Then, the app you create will have to talk to the GEs of your choice using the APIs that we define.
I hope that this resolves the question and gives the right pointers to start your work
Best regards,
Miguel
El 01/12/2014 10:49, pletlg escribió:
Dear Ms/Mr!
I am working on a reporting product (like Roambi.) that is in the implementation phase. The software design is not yet finalized. FIWARE is very interesing for me and I want to make FiWARE compatible design. How should I start it?
Thank you for the answer!
Gabor Pletl
Sent from my iPad
extRequest
Major
Dear Gabor,
Thanks for contacting us.
FIWARE is based on main blocks called GEs (Generic Enablers) that you can install and use. The word "Generic" means that they are not specific to any sector but general purpose. Nearly all of the reference implementations that we provide are free to use (I can only think of one exception in the Security chapter that we will replace in the future). These GEs are exposed via services (mainly REST interfaces) and anyone can build his own apps that would talk to and use the capabilities of the GEs of his choice. The REST interfaces are described in the Open Specifications (all of them linked from the catalogue ... read on)
The wiki (http://wiki.fi-ware.org/) has lots of information but part of the GEs on the wiki are no longer maintained by FIWARE. The up to date reference is the catalogue (http://catalogue.fi-ware.org/enablers). All the components there are alive and supported. The Catalogue concentrates all the pointers to the materials related to a given GE in the wiki or other places without the need to search everywhere. It also shows you the Terms and Conditions in a dedicated tab. I would go to the catalogue and see if the GEs there are useful for you.
There is a free experimentation environment called FIWARE Lab ( https://lab.fi-ware.org/). This environment allows you to deploy GEs and try them. We are progressively incorporating automated deployment facilities to easily install instances of our software on top of your virtual infrastructure on FIWARE Lab.
Our eLearning web site (FIWARE Academy - http://edu.fi-ware.org/) is also there for you to use. Most of the times you'll get a link to this tool from the catalogue if there is a course for the GE you are browsing on the catalogue.
The way to be "compatible" with us is to speak in the same language, that is to say, implement the REST interfaces to our technology making them compliant with the open specs.
In summary, take a look at the catalogue<http://catalogue.fi-ware.org/enablers>, see what GEs you are going to use and then you will have to install them. You may want to use FIWARE Lab, our free experimentation environment with self deployment facilities. Then, the app you create will have to talk to the GEs of your choice using the APIs that we define.
I hope that this resolves the question and gives the right pointers to start your work
Best regards,
Miguel
El 01/12/2014 10:49, pletlg escribió:
Dear Ms/Mr!
I am working on a reporting product (like Roambi.) that is in the implementation phase. The software design is not yet finalized. FIWARE is very interesing for me and I want to make FiWARE compatible design. How should I start it?
Thank you for the answer!
Gabor Pletl
Sent from my iPad