1 / 21

Contents

Contents. ebXML Registry Features Registry Federation Federation Architecture Federation Metadata Federated Query ebRIM Future Directions. Publish, Discover, Manage/ Govern Web Services. Cataloging, Validation of Content, Ver-sion Control. Federated SQL & XML Queries.

yin
Download Presentation

Contents

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Contents • ebXML Registry Features • RegistryFederation • Federation Architecture • Federation Metadata • Federated Query • ebRIM • Future Directions

  2. Publish, Discover, Manage/ Govern Web Services Cataloging, Validation of Content, Ver-sion Control Federated SQL & XML Queries Web Services Registry Content Management Federated Architecture ebXML Registry Secure Architecture Standard Metadata DSig, Role-Based Access Control, Audit Trail Events Classification, Associations,Taxonomies Content-Based Event Notification ebXML Registry Features • A Service Oriented Architecture registry as well as a repository • Classification of any type of information • Managing relationships between information • Taxonomy hosting, browsing and validation • File/folder organization of information

  3. Registry Server-1 Organization-A Registry Server-2 Organization-B Registry Server-1 Organization-A Registry Client-1 Registry Client-1 Registry Server-2 Organization-B Registry Client-2 Registry Client-2 RegistryFederation • A registry federation is a group of registries that have voluntarily agreed to form a loosely coupled union. • Registry federations appear as a single logical registry to registry clients.

  4. Federation Registry B Registry A Replication TRP Web Server Relocation Event Notification Security Controller SOAP Binder Security Manager Federated Query System Registry Service Registry Service Controller Object Manager Object Query Manager Query Manager Lifecycle Manager EJB Application Server RIM Objects and Security Objects Persistence Manager Federation Metadata RegRep RegRep Content Management Service Security Model Authorization Authentication Access Control Federation Architecture • Federation: functions to make federation scope and manage life cycle of data object in a federation • Replication: functions to manage local cache or replica consistently for enhancing performance of federated query • Relocation: functions for relocating ownership of registry objects • Federated Query: functions required to issue queries targeted to a federation • Security Model: functions for guaranteeing safe access and use data securely in a federation: authorization, authentication and access control • Federation Metadata: data structure for managing a federation consistently. It is composed of Federation, Association, Registry • Event Notification: functions for notifying change of data objects subscribed in a federation

  5. Federation Metadata • Composed of Federation, Registry, and Association • Should be locally cached and synchronized by polling or event notification RO:federation V3.0 V3.0 RO:registry SYSTEM-PROPERTIES:registry

  6. Creating Federation Instance Federation Meta Data • A Federation Home can be a Federation Home (FH) by making a Federation Instance Fed. Home F :Federation Instance Rh R : Registry Instance A : Association of HasFederation Member A F Steel RR Trade RR Rs Rt

  7. Joining Federation Federation Meta Data • Each registry suggests Association of HasFederationMember and its Registry Instance to FH to be a Federation Member. Fed. Home F :Federation Instance Rh R : Registry Instance A : Association of HasFederation Member A F R :Registry Instance replica A’ A’ Rk Rt Trade RR Steel RR A A Rt Rk

  8. Approve joining Federation Federation Meta Data • FH approves joining of candidate registries by sending its Federation Meta Data Fed. Home F :Federation Instance Rh R : Registry Instance A : Association of HasFederation Member A F R :Registry Instance replica A’ A’ F : Federation Instance replica Rs Rt Trade RR Steel RR F Rh A’ F Rh A’ A’ A A’ A Rs Rt Rt Rs

  9. Leaving Federation Federation Meta Data • In the case of changes in Fed. Meta data, FH should notify it to all of its members to synchronize the replicas of Fed. Meta data. F :Federation Instance Fed. Home R : Registry Instance Rh : Association of HasFederation Member A A R :Registry Instance replica F change F : Federation Instance replica A’ Rs Steel RR Trade RR F Rh A’ F’ A Rs Rt

  10. Federation Meta Data FH (Federation Home) Management • Problem • Any registry can become a FH. One registry may compete against other registry in the same industry or in a country for a FH, so confusion will happen in the middle of each registry trying to become a FH. • Solution • FH certification authority in each country must manages a certified FHs. • Any registry which wants to bean FH should refer an FH list.

  11. Federated Query  Problem: non-interoperable registries • It is difficult to have Federation if registries have various version of ebRIM and ebRS • different version of Registry: failure in query • required translation process of ebRIM, ebRSor Backward Compatibility of ebRIM Registry Server-Remote A1 V2.1 Registry Server-Remote A2 V2.5 Registry Server-Home V3.0 Registry Client Registry Server-Remote B1 V3.0 others (ex)UDDI

  12. Federated Query Consideration • Determine: local query to local data + replica or remote query • Check whether target registries are alive • Federated query to registries implemented in various version Replica and Event Notification Mgmt Result of Remote Query Remote Query General user Local Query + Remote Query Result of Local Query Federation Mgmt General user

  13. Federated Query Problem: Performance of Federated Query • Search time increases rapidly as the number of Federation member increases,because of limitation of Synchronous method => Replication of all registry data => Asynchronous Federation Agent Registry Server-Remote Async Federation Agent Registry Server-Home Registry Client Registry Server-Remote Registry Server-Remote

  14. Federated Query Problem:Federated query about local replica If a client submits a federated query to a federation that has many registries with the same local replica, then a client may receive same results redundantly because of same local replica of each registry CO1 2 2 Replication 2 2 2 Reg/Rep R R 2 R R R R Replica Replica Replica RegRep1 RegRep2 RegRep3 Replica CO2 CO1 Original Data O CO1 O2 O1 O3 CO3 CO2 Copy of Original Data CO3 CO 3. Response 3. Response 3. Response CO1 R Retrieve CO1 O1 Federation 1. Fed Query to O1 3. Result O1 , CO1 , CO1 Registry Client

  15. Federated Query Solution: Federated query about local replica • The registry that receives a query must distinguish a federated query from a local query. • federated query : the registry must retrieve only its own local data without local replica. • local query : the registry can retrieve both local data and local replica. CO1 Replication 2 2 Reg/Rep R R 2 R Replica Replica Replica RegRep1 RegRep2 RegRep3 Replica CO2 CO1 Original Data O CO1 O2 O1 O3 CO3 CO2 Copy of Original Data CO3 CO 3. Response 3. Response 3. Response R Retrieve O1 Federation 1. Fed Query to O1 4. Result O1 Registry Client

  16. Federated Query Problem: Latency in Query Response When a FH submits a federated query to a downed registry, a FH may wait for a result of a downed registry until time-out. This problem leads to a low performance. 3. Low performance FH A FH is waiting for the response of downed registry 1. Fed query 2. Response 2. No Response 2. Response 2. Response Reg Rep Reg Rep Reg Rep Reg Rep down alive alive alive Federation

  17. Federated Query Solution: Ping-Pong Protocol • A FH submit a ping request message to all members of federation to receive a pong response message from them. • A FH excludes the non-response registry in member list temporarily. 1. Retrieve 3. Update FH FH Federation Extended Metadata Federation Extended Metadata 1. Ping Request Message 2. Pong Response Message 2. Fed query No Fed query 2. No Response 3. Response 2. Pong Response Message 2. Pong Response Message 3. Response 3. Response Reg Rep Reg Rep Reg Rep Reg Rep Reg Rep Reg Rep Reg Rep Reg Rep down down alive alive alive alive alive alive Federation Federation

  18. ebRIM (Registry Information Model) Slot • Definition: • Object for extending RegistryObject in ebRIM data model. • Problem: Data Loss • According to implementation mechanism (especially RDB-based), it could give an abnormal result in federated query and relocation process. Registry 1 Registry 2 RO1 RO1 c1 c1 c5 c3 c2 c2 c3 c4 Object View RegistryObject RegistryObject relocation Slot Slot Data View

  19. ebRIM (Registry Information Model) Classification • Definition: • Object for RegistryObject taxonomy. • Problem: mapping Classification Node • In the case that there is a difference between the name of classification node, how to match the nodes whose content is semantically same? Registry 1 Registry 2 A A B C C B′ Matching B=B’ FHR Select Obj from all registries where ClassificationNode = B

  20. Focusing SOA architecture Interoperability testing Conformance specification Semantic content management More profiles More protocol bindings (SMTP, RM, ebMS, etc.) Future Directions

More Related