o idm definition
o idm this container implements the original FIWARE IdM component8 – with few start-up modifications needed to integrate it with other subsystems – and it includes also its own MySQL DBMS; this container make use of docker volumes for ensure data persistence. o mkpl: this container implements the original FIWARE biz-ecosystem9 with few start-up modifications needed to integrate it with other sub-systems; it makes use of bind mounts for ensure configurations persistence, as the original does. 6 ▇▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇/ 7 ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/ 8 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/ging/fiware-idm 9 ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/FIWARE-TMForum/Business-API-Ecosystem o mysql: this container implements the relational DB storage used by the mkpl container and it make use of docker volumes for ensure data persistence. o mongo: this container implements a NoSQL DB storage used by the mkpl container and it make use of docker volumes for ensure data persistence. o kbnode: this container implements a custom search engine developed by ENGINEERING - based on Virtuoso10 and ElasticSearch11 technologies - for semantic search related to the asset entries of the portal; this container make use of docker volumes for ensure data persistence. • Docker subnets o dbnet: this subnet connects portal to its DBMS o officenet: this subnet connects PORTAL to its documents conversion system o kbnet: this subnet connects PORTAL to its KBNODE o hostnet: this subnet connects PORTAL, IDM and MKPL o mkplnet: this subnet connects MKPL to MySQL and mongo o kbnet: this subnet connects KBNODE to the PORTAL • Docker exposed ports o 8080: this is the internal HTTP port that have to be published (mapped to an externally accessible host port) to reach the portal web interface o 8009: this is the AJP connector port that have to be published (mapped to an externally accessible host port) to reach the portal via a Reverse Proxy connection, if necessary o 8000: this is the internal HTTP port that have to be published (mapped to an externally accessible host port) to reach the IDM management web interface o 8000: this is the internal HTTP port that have to be published (mapped to an externally accessible host port) to reach the MKPL management web interface