For instance, Dataworks Enterprise Server component pushes data into the Cache. A plug-in
component then takes that data from the Cache and places it onto the
distribution system. Neither Dataworks Enterprise Server nor the plug-in components are
aware of each other. Most Dataworks Enterprise components perform a simple connectivity
function.
In common with most distribution systems, the Cache supports both Records and
Pages. Pages are modeled using ANSI encoded data with some extensions for
supporting specialised financial data. Pages are encapsulated within Records
for simplicity. Each Record consists of a name, an originator, an arbitrary collection of named
Fields, a status and some additional information known as an Indicator.
The Field has a rich set of attributes reflecting the needs of publishing. Each
field contains:
Fields also provide a standard display method that allows the field to paint
itself. For instance, a field can be displayed by simply asking it to render
itself within a given context. This simplifies the creation of display
applications, especially page displays where there is the requirement to
display Kanji text.
The Plug-Ins
A plug-in component acts as an interface between the real-time Cache and the
distribution system. All services provided by the distribution system are
available to components connected to the Cache. Additionally, the plug-in component can expose sources created in the real-time
Cache to the distribution system.
The Cache also supports multiple plug-ins, allowing the same source of data to
be exposed to more than one distribution system.
A distribution system plug-in makes the market data available to users of
Dataworks Enterprise and allows subscribers of the distribution system access to
information in the Cache.
A publishing application can use the plug-in to place data directly on the
distribution system. Alternatively...
Dataworks Enterprise Client and Server
...it can use the services of Dataworks Enterprise Client and Server. These components
allow the application to pass the information to be published to a central
location where it may be merged with other data and placed on the distribution
system. Using this approach, users can benefit from additional functionality of
Dataworks Enterprise Server.
Dataworks Enterprise Server:
Dataworks Enterprise Client resides on the user's machine and communicates with Dataworks Enterprise
Server using a standard TCP virtual circuit. Both the client and server modules
are transparent to the user. Applications simply indicate which sources are to
be published. Dataworks Enterprise Client detects these and takes responsibility for
exporting the data.
Other Components
When developing a new publishing Excel spreadsheet, COM interfaces are the
natural choice because they are more efficient. However, for existing
spreadsheets, it may be convenient to use Excel as a DDE Server. Dataworks EnterpriseDDE
component allows the user to publish data from these sheets into the real-time
Cache using DDE rather than COM. The Remote Client/Server allows the user to access published data without a
direct connection to the distribution system. The Remote Client resides on the
user's machine and communicates with a Remote Server, which is directly
attached to the distribution system. The entire Cache content on the server is
then made available to the local machine.
Dataworks Enterprise is supplied with a configurable "launch and monitor"
application, called RTLaunch. This is used to launch components such as a
plug-in or a Dataworks Enterprise Server. The launcher monitors components and can
automatically restart them on failure. The launcher is visible through the task
bar and is configured during set-up.
Dataworks Enterprise is installed with a standard set-up program. This supports both silent
installs and SMS. Dataworks Enterprise makes extensive use of shared files and databases for configurations.
These can be installed on network file storage simplifying the management of
installed systems.Dataworks Enterprise Components
The Cache
The core component of Dataworks Enterprise is the Real-Time Cache. This is the central
repository of information in a given host. Higher level applications and other
components interact using the Cache to exchange data.
