Database Reference
In-Depth Information
Managing Service Repository
During the runtime Discoverability analysis phase, we mentioned deployment options on
which we could roll up our taxonomy model. OSR and OER are obvious, where an asset's
definition will be used in OER and tModels in OSR. For OSR-based implementation, we
can see a good match for entities such as message and object. Task/Service can also be eas-
ily implemented in the case of WS-type, with generic WSDL-tModel mapping. So, we can
cover two and a half Runtime Discoverability cases by defining these entities on OSR, and
that's not good enough. Together with OER, we will cover all the Discoverability scenarios
for all entities we identified earlier; however, whatever deployment option we chose, we
will have to follow the taxonomy reference model during the deployment process.
Please see the following figure:
Maintaining entity relationships in SR
Search WWH ::
Custom Search