Architecture 1

User components

This diagram shows how ibrokerKit provides services to i-name users.

(1) The openxri authority resolution server uses the openxri library for reading authorities, subsegments and descriptors (XRDs).
(2) The openxri library accesses the openxri DB.
(3) The ibrokerFront web application uses the iname4Java library for registering and managing both top-level and community i-names.
(4) The iname4Java library uses the openxri library for working with community i-names.
(5) The iname4Java library uses the epptools4Java library for working with top-level i-names.
(6) The epptools4Java library accesses the epptools DB.
(7) The epptools4Java library uses the NeuStar EPP Toolkit library for communicating with the GRS.
(8) The ibrokerFront web application uses the ibrokerStore library for registering and managing users and other core i-broker data.
(9) The ibrokerStore library accesses the ibroker DB.
(10) The ibrokerFront web application uses the iserviceStore library for registering and managing i-services.
(11) The iserviceStore library accesses the iservice DB.
(12) The iserviceFront library uses the openxri library for associating i-services with i-names.
(13) The iserviceFront web application uses the iserviceStore library for reading i-service data.
(14) The oauthFront web application uses the iname4Java library for modifying an i-name's configuration to apply external third party requests.
(15) The oauthFront web application uses the ibrokerStore library for authenticating users when an external third party request is made.