Database Reference
In-Depth Information
Oracle Registry
One of the main goals of implementing
Service-Oriented Architecture
(
SOA
) is to
reuse the existing applications and achieve business agility. To enable reusability and
loose coupling, the developers and architects should know the taxonomies of avail-
able services within an organization before creating and architecting new applica-
tions. Lack of service visibility and traceability leads to redundant services within an
organization. The ability to discover and use existing services is one of the key suc-
cess criteria of implementing service-oriented architecture.
Oracle Registry
organizes the existing SOA assets into taxonomy of entities and
tModels to assist us in implementing the SOA governance. Ideally, any request of the
resources first goes to the enterprise service bus. The enterprise service bus will do
a
Universal Description, Discovery, and Integration
(
UDDI
) look-up (that is similar
to a
Domain Name Server
(
DNS
) lookup) at the registry. The registry will provide the
following details for the resources:
•
Who is the service provider?
: The details of the party who publishes the
service
•
What is the service?
: The service description
•
Where is the service endpoint?
: The service location, protocol, and port
•
How and Why
: The description for services' specifications and value sets
along with taxonomy, WSDL interfaces, and resources
One can configure Oracle SOA Suite for doing a UDDI look-up at registry for the
resources. We can establish a UDDI connection for resources from the Oracle
JDeveloper during development. It is a leading practice to use the UDDI reference for
resources to design and deploy SOA composite application(s).
The initial step is to register the services with Discovery Registry, as shown in the fol-
lowing diagram. The service bus will do the UDDI look-up with Discovery Registry to
get the services endpoint before accessing the services directly from the service pro-
viders.
