Document

Introduction of Registry
Service Integration
Architecture
~RSIA~
22-August-2009
NEC Corporation
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.
2
Enterprise System on the Cloud ~Case Study~
Registry
Service
SaaS PF(A)
Registry
Service
End User Company
SaaS PF(SFDC)
Legacy System
Front end Service
(UI)
Data cooperation Service
SaaS PF(C)
Registry
Service
End user
Web Client
Business Intelligence
Service (Analyze)
3
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 etc.
≒
Results of service cooperation
Restriction matter concerning cooperation
Technical restriction matter for cooperation
Interface information for service call
ebXML/MDR
How to Call (Call I/F, Sequence Pattern)
Data format to which/handed over is returned
PLIB
Information
that service
developer
uses
Value of master who uses it by data to which/handed over is returned
Information for attestation
From SaaS PF
Accounting information
4
Log information
Issue
Registry
Access I/F
STD#
Metadata
Spec.
MDR
ISO/IEC 11179
X
N/A
MFI
ISO/IEC 19763
X
N/A
PLIB
ISO13584
X
OTD
ISO 22745
X
API of the Web
service base is
defined.
RDL
ISO 15926
X
UDDI
OASIS
X
Access API of
the SOAP base
is defined.
ebXML
R&R
OASIS
X
ebRS
(SOAP/REST)
Registry
Interoperability of each metadata standard：
MFI
Spec.
remarks
ISO29002
Registry Service Integration area??
5
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.
6
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
Service
Profile
Part of
ebXML Metadata
Part of
PLIB Metadata
The item to which a
service profile is
peculiar.
:
:
Other Metadata
Link or Copy
Metadata
( such asOther
Information
from SaaS PF)
Metadata
( such asOther
Information
from SaaS PF)
( such as Information from SaaS PF)
Scandalized
Registries
Not
Scandalized
Registries
7
Registry Service Integration Model
Registry
(has a another STD.I/F)
RSIA
Interactive
Registry
Service
Integrator
Original
Interactive
Registry
(has a another STD. I/F)
User Site
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.
8
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.
:
:
And so on.
9

Download Report