Database Reference
In-Depth Information
Centralized realization
Centralization denotes constant reuse through runtime resources lookup and discovery. The
types of lookups and objects are defined in the table in the Runtime lookup section. The al-
teration of the Governance rule by configuration will provide the most profound benefits
when maintained centrally. The following approaches practice the same lookup paradigm
with different degrees of centralization and lookup frequencies.
It is obvious that the number of cross-platform lookups should be limited due to perform-
ance requirements, and the scope of the returned objects must be adjusted to its transaction-
al scope. For this purpose, according to the third assumption, we implemented the Message
Container with the Process Header (SBDH compliant), where the business object and
transaction-related values must be persisted and propagated along the way via all the lay-
ers. So, a certain trade-off must take place to optimize the size of the process transaction-
specific data, the number of lookups, and the transaction MEP.
The Message Container implementation with PH/MH also allows us to have significant in-
dependence from the platform vendors.
Domain Repository
Establishing a centralized Service Repository with global lookup capabilities for the entire
enterprise is not only expensive but also unnecessary. The reasons can vary from dispersed
geographic locations of business units (GU) to dissimilar business models. For instance, for
a telecom company with a dedicated OSS/BSS division, several of their services and arti-
facts will be useful only within this single domain. That is, order management-related ser-
vices are not concerned with the technology domain, responsible for maintaining Software-
defined Networking. At the same time, the number of correlated projects and their common
SLA requirements make a decentralized approach not only feasible, but also dangerous.
Let's take a look at what artifacts and lookup types we can employ in this situation:
Lookup types in use : 1-4
Entities maintained : 1-4
This approach can be a good choice in the following scenarios:
• A GU has a great deal of independence in order to stay more flexible in terms of
business operations
Search WWH ::




Custom Search