Maintaining the Core – Service Repository - Applied SOA Patterns on the Oracle Platform - page 323

• businessEntity : It's your company, or business unit, that provides a wide
variety of business services, and thus the model should be descriptive enough: the
company's name, description of the line of business, contact details, and available
business services. Previously mentioned business taxonomies, such as NAICS
and UNSPSC, are very well suited for the description of this entity and are widely
used in the identifierBag and categoryBag reference collections (via
tModels of course). In this case, identifierBag answers the question "What
is the company we are describing here?" and categoryBag addresses the ques-
tions "What are the functions of the company?" and "What are the services
provided by the company?"
• businessService : The schema of this entity represents descriptive informa-
tion about a particular family (or domain) of technical services. In addition to the
name, the description, and categoryBag , this has one or several bind-
ingTemplates , representing the technical description of publicly available ser-
vices (as tModels of course).
• bindingTemplate : At the top, it has a human-readable description and the
AccessPoint element holding the host URL. The URL type is provided as an
attribute, such as an HTTP host. Detailed service info is gathered in the
tModelInstanceDetails / tModelInstanceInfo collection.
With so much freedom provided by tModels and the lack of comprehendible taxonomies
in the earlier 2000s, anarchy reigned in the SOA realm, quite severely damaging UDDI
acceptance. With the new arrival of different API servers, we hope that UDDI will im-
prove its reputation. It's still one of the existing strategic technologies shaping the SOA
landscape, and Oracle plays its part quite well here.
To get a closer look at the tool, please proceed with the installation. It's quite similar to
OER. Here, again, you should start with the DB preparation, although only one tablespace
is necessary—the UDDI value-name pairs are quite light and do not require LOBs: