Database Reference
In-Depth Information
•
Trading Partner:
TP's Application Endpoint URI cannot be abstract. It is usually
defined at the late stage of the project.
•
Rules:
As we will discuss later, rules can be registered as functional, XPath-
based, and references to the decision tables. In all cases, they cannot be abstract.
•
Services:
Depending on the runtime role, a service can be the ultimate receiver,
which makes it the TP's Endpoint, where a URI cannot be abstract. Another prop-
erty related to the registered Component is an Engine, which must also be con-
crete.
So, the abstract entities' hierarchy can be shaped as follows, where the primary artifacts
are presented in white:
To finalize the practical implementation of this semantic, we will go through all the entit-
ies and identify all the properties essential for the dynamic service compositions. Further,
we will define how these properties can be implemented in a message structure utilized by
Service Broker.
Object
In the serialized form, Entity, Business, or Service-related objects present message busi-
ness payload. The types of Enterprise Business Objects are always quite limited: product,
Search WWH ::
Custom Search