1. Introduction of Registry Service Integration Architecture ~RSIA~
22-August-2009
NEC Corporation
My mane is Tatsumi Adachi. I’m work for NEC Corporation.
Now I introduce Registry Service Integration Architecture.

2. Environment that surrounds us
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
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.

3. Enterprise System on the Cloud ~Case Study~
SaaS PF(A)
Registry
Service
SaaS PF(SFDC)
Registry
Service
End User Company
Legacy System
Data cooperation Service
Front end Service
(UI)
SaaS PF(C)
This system is composing of three services on Cloud and in-house systems of.
[Each Service explain.]
This system was constructed in a short term and low price.
Registry
Service
End user
Business Intelligence
Service (Analyze)
Web Client

4. Information on service are discovered from Heterogynous Registries.
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.
Catalog information for service（Information of Service provider, etc.）
Information that service user uses
Information on the cooperation between service
UDDI　≒
UDDI etc.
Results of service cooperation
Restriction matter concerning cooperation
Technical restriction matter for cooperation
この図は、クラウド上のサービス連携に必要な情報を簡略化したものです。
This figure is a simplification of information necessary for the service cooperation on Cloud.
Interface information for service call
ebXML/MDR
Information that service developer uses
How to Call (Call I/F, Sequence Pattern)
Data format to which/handed over is returned
PLIB
Value of master who uses it by data to which/handed over is returned
Information for attestation
From SaaS PF
Accounting information
Log information

5. Issue remarks STD# Registry MDR MFI PLIB OTD RDL UDDI ebXML R&R
Metadata
Spec.
Registry　Access I/F　Spec.
remarks
MDR
ISO/IEC 11179 X
N/A
MFI
ISO/IEC 19763
PLIB
ISO13584
API of the Web service base is defined.
ISO29002
OTD
ISO 22745
RDL
ISO 15926
UDDI
OASIS
Access API of the SOAP base is defined.
ebXML R&R
ebRS
(SOAP/REST)
クラウド上のサービス連携の為に、
書くレジストリ
Each registry have a metadeta specification.
But each metadeta specification is different.
幾つかのレジストリは、アクセスインターフェースを定義している。
Interoperability of each metadata standard：MFI
Registry Service Integration area??

6. Registry Service Integration Architecture
Policy and object of standardization (Idea level)
Policy of standardization
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.
Candidate of some standardization objects
Definition of architecture that Registry Service Integration.
The access model‘s definition in registry service.
Define the service profile.

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

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

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