1. Introduction of Registry Service Integration Architecture ~RSIA~ 22-August-2009 NEC Corporation

2. 2 Environment that surrounds us The information on services obtained from various registries. The discovery and the access method of the registry with information for service are different according to each registry. Diversity in interface on The Cloud. The interface of service is neither only SOA nor Web Service. Environment and problem that surrounds Enterprises system on the Cloud. Enterprise System on the Cloud The Cloud Computing became possible because of the expansion of the SOA technology and the Web service technology. Mounting of a registry system based on various standard specifications works much. Enterprise System was able to combine and make service on the internet. Information for service are discovered from Heterogynous Registries. Information for service is stored in various registries. （ Such as the information by which service is itself, the specification of the data service exchanges, and master data ） Issue

3. 3 Enterprise System on the Cloud ~Case Study~ SaaS PF(SFDC) SaaS PF(C) Legacy System End User Company SaaS PF(A) Data cooperation Service Web Client Business Intelligence Service (Analyze) Front end Service (UI) End user Registry Service Registry Service Registry Service

4. 4 Information on service are discovered from Heterogynous Registries. Interface information for service call How to Call (Call I/F, Sequence Pattern) Data format to which/handed over is returned Value of master who uses it by data to which/handed over is returned Information for attestation Accounting information Log information From SaaS PF UDDI ≒ ebXML/MDR PLIB Information on the cooperation between service Results of service cooperation Restriction matter concerning cooperation Technical restriction matter for cooperation Catalog information for service （ Information of Service provider, etc. ） Information that service user uses Information that service developer uses UDDI etc. The information for service are stored in various registries. It is necessary to refer from various registries to service information. The interface of service on Cloud is not limited to the Web service.

5. 5 Issue Registry STD# Metadata Spec. Registry Access I/F Spec. remarks MDR ISO/IEC 11179X N/A MFI ISO/IEC 19763X N/A PLIB ISO13584X API of the Web service base is defined. ISO29002 OTD ISO 22745X RDL ISO 15926X UDDI OASISX Access API of the SOAP base is defined. ebXML R&R OASISX ebRS (SOAP/REST) Interoperability of each metadata standard ： MFI Registry Service Integration area??

6. 6 Definition of architecture that Registry Service Integration. The access model‘s definition in registry service. Define the service profile. ▌ Policy of standardization ▌ Candidate of some standardization objects Registry Service Integration Architecture Policy and object of standardization (Idea level) It doesn't limit to the Web service on the assumption of the Cloud environment and the registry service with various access methods is examined as a target of integration. It aims esteeming an existing standard, and becoming the foundation of the construction of smooth service integration on Cloud. The reference model of the access specification of Registry Service is Web service.

7. 7 Other Metadata ( such as Information from SaaS PF) Relation between service profile and existing metadata Service Profile Part of UDDI Metadata Part of MDR Metadata Part of ebXML Metadata Part of PLIB Metadata Link or Copy Scandalized Registries : Other Metadata ( such as Information from SaaS PF) Other Metadata ( such as Information from SaaS PF) Not Scandalized Registries The service profile is composed of information that the meta data and the SaaS platform in various registries offer. The item to which a service profile is peculiar.

8. 8 Registry Service Integration Model Registry Service Integrator RSIA Interactive Registry (has a another STD.I/F) Original Interactive Registry (has a another STD. I/F) Original Interactive Registry (has a RSIA I/F) User Site Individual registry service has various I/F as well as service on Cloud. Individual registry service has various I/F as well as service on Cloud. Specification or rules that method of access to different registry unites. Specification or rules that method of access to different registry unites. RSIA Interactive

9. 9 Discovery procedure of registry where user has information wanting it. ▌ Discovery of Services. Registry Service Interactions Requirements of Registry Service Interactions (for examples) Retrieval procedure to discovered registry. ▌ Query of Service ’ s Information. Offer of service profile that user demands. ▌ Obtaining of Service profile. Notification procedure concerning update of information in each registration. ▌ Notification : And so on.