Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Ordinateurs - HP Integrity NonStop H-Series (16.73 mb)
Ordinateurs - HP Integrity NonStop H-Series (957.56 kb)
Ordinateurs - HP Integrity NonStop H-Series (881.66 kb)
Ordinateurs - HP Integrity NonStop H-Series (965.62 kb)
Ordinateurs - HP Integrity NonStop H-Series (676.93 kb)
Ordinateurs - HP Integrity NonStop H-Series (393.72 kb)
Ordinateurs - HP Integrity NonStop H-Series (776.57 kb)
Facilité d'utilisation
Introduction
The ZLE Framework
In Figure 1-3, the ZLE framework resembles a wheel, with the various operational
business systems at the outer rim and the real-time hub at the center. The
operational systems include all of the existing legacy systems of a business, running
applications such as reservation systems, order entry, inventory, and all the other
applications required for the operation of the business. The applications are likely the
products of multiple software vendors, and the computers might also be the products of
different hardware vendors. Systems from IBM, Unisys, Sun, and so on, could be
running applications such as SAP, Bann, Siebel, or even custom applications
developed in-house. The applications might have their own databases as well.
The real-time hub, at the center of the ZLE framework, consists of one or more
Integrity NonStop servers. (It is possible to configure a hub using Integrity NonStop
servers interconnected with other systems. This is a distinct advantage for corporations
with an existing infrastructure). Hosted on the Integrity NonStop servers are the two
major components of the ZLE framework: the enterprise application integration
(EAI) environment and the real-time data store.
The real-time data store, or simply data store, is a relational database that serves as a
central repository for business-related data. The data store contains current data from
the business’s operational systems. It provides a single, up-to-the minute, integrated
view of the entire corporation and is able to provide current data to any of the business
applications that need it. It must contain data at a very detailed level. (The data store
does not contain ALL the data from the operational system. When the data store is
designed, decisions must be made as to what subset of the data is required by the
real-time applications and the application integration efforts). For example, various
businesses might have these needs for each customer:
• A telecommunications company might need a detailed record of every call made.
• A bank might need a record of every loan payment, ATM withdrawal or deposit,
credit card purchase, check written, and so on.
• A retailer might need a record of every item purchased, the payment type (cash,
check, or credit card), and so on.
The data store provides a single view of the enterprise and of the customer. For
example, consider the case of a telecommunications company in the business of
selling phone lines through customer service representatives.
A customer calls the service center to request a new line. The service representative
would like to close the deal while the customer is still on the line. To do that, the
representative needs customer information, which resides in the master customer
database. The representative also needs access to a provisioning system, which can
provide a schedule (for line installation) and the new phone number.
On the basis of that information, a billing system needs to provide pricing information
and generate a bill. The challenge is how to give the customer representative access
to these different systems running on different platforms and databases, with each
system largely independent and relying on its own view of the customer. A customer
representative might have access to all these systems and might be able to navigate
through multiple screens and processes to obtain the required information. A real-time
NonStop Systems Introduction for H-Series RVUs — 540083-001
1 -8
...