Slide 1
Cooperating Registries
- Enables multiple ebXML Registries to work together to address user needs
- Based on a loosely-coupled federation model:
- Allows local autonomy to each registry operator
- Enables smaller registries to appear like a big registry
- Allow registries to work together to meet more demanding user needs
Cooperating Registries:
Key Features
- Registry Federations
- Enable federated queries
- Do not enable federated lifecycle management
- Inter-registry object references
- Object relocation
- From one registry to another
- From one user to another
- Object replication
Registry Federation
Federation Information Model
Federation: Key Concepts
- Enable clients to query multiple registries as if they were a single registry
- Referred to as a federated queries
- Any registry can create a Federation
- Any registry may join pending approval by Federation creator
- All registry peers are equal (P2P model)
- A registry may belong to multiple Federations
Federation: Key Concepts
- Federation metdata stored a registry called Federation home
- Uses existing LifeCycleManager interface for create/remove/join/leave
- Federations members do not have to replicate data (but can)
- Only the Federation metadata must be replicated
Federated Queries
- AdhocQueryRequest new attributes
- Boolean federated: true implies federated query
- Boolean federated: false implies local query
- ID federation: specifies target federation id (option)
- Processed by all Federation members
- Parrallel-distributed query
- Unified result returned by registry that received the federated query
Inter-registry Object References
- Local and remote ObjectRefs
- Home registry is where an object resides
- ObjectRef = id + home
- No home specified for local ObjectRef
Object Relocation
Object Relocation
- Used to relocate an object from a user in one registry to a user in another registry
- sourceRegistry, sourceUser
- destinationRegistry, destinationUser
- Event notification used by destination registry to notify destinationUser
- Introduces a new Object Relocation protocol to LifeCycleManager
Object Relocation Protocol
Object Replication
Object Replication
- Enable fault tolerance and performance
- Hot objects should be replicated for performance
- Loosely coupled replication, NOT transactional replication
- A local replica may be created in a registry for an object in a remote registry
- Replica of replicas are allowed
- Uses existing API for client API for replication
- Replicas are read-only (no life cycle mgt.)
Iterative Query Support
- Divide-and-conquer solution to handling queries that match a large result set
- Requires minor schema enhancements
- Schema changes are backward compatible with V2
- Non-transactional model - may result in duplicate results or missing results
- Unlikely due to sparse updates
Iterative Query Example
- 1007 objects, fetch 100 in each iteration