This scenario details the request of reference data from O&M systems to an Enterprise RDL in order to update their internal reference data sets.
|O&M systems||Request reference data set|
|Enterprise RDL||Respond to requests for reference data|
The request data sent from O&M systems may be composed of:
- UUID of reference data set (if known)
- Version of reference data set
- Timestamp from which updates have occurred (for incremental responses)
The response data sent from the Enterprise RDL is, at a minimum, composed of:
- UUID, name, and version of the reference data set
- List of associated taxonomies and types/classes
The data requested by the O&M systems and responded by the Enterprise RDL must conform to MIMOSA CCOM BODs.
MIMOSA CCOM Business Object Documents
The following MIMOSA CCOM BODs should be supported:
The communication between all systems occurs via the ISBM using publish-subscribe services.
O&M systems must implement a client for the ISBM Consumer Request and Channel Management Services. O&M systems may implement the ISBM Notify Listener Service for message notification.
The Enterprise RDL must implement a client for the ISBM Provider Request and Channel Management Services. The Enterprise RDL may implement the ISBM Notify Listener Service for message notification.
Suggested Channel/Topic Configuration
A channel should be created for install requests and should conform to the following format:
As outlined in the document ISBM Guidelines, topics should match the message content. Correspondingly, the following topic format should be used: