Architecture 2

Maintenance components

The following services are not directly exposed to i-name users, but are still required for proper i-broker operations.

(1) The openxri.admin web application uses the openxri library for managing authorities, subsegments and descriptors (XRDs).
(2) The openxri library accesses the openxri DB.
(3) The ibrokerTask standalone application uses the iname4Java library for performing maintenance tasks on 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 ibrokerTask standalone application uses the epptools4Java library for polling events from the GRS queue.
(8) The epptools4Java library uses the NeuStar EPP Toolkit library for communicating with the GRS.
(9) The ibrokerTask standalone application uses the ibrokerStore library for performing maintenance tasks on users and other core i-broker data.
(10) The ibrokerStore library accesses the ibroker DB.
(11) The iserviceAdmin web application uses the iserviceStore library for managing i-service data.
(12) The iserviceStore library accesses the iservice DB.