| |
Applicability
Any organization with the following needs can benefit from
an eSnap implementation:
- When there is a need to bridge
multiple “data stores” (databases, mail systems,
file systems, etc.),
There must be a common business element in
order to tie in the different data sources (e.g. job no.,
ssn, client name, contract no., etc.).
- When there is a need to add a
new “skin” (web interface) to legacy applications,
eSnap makes it a breeze to web enable your information without
a long and costly rewrite of your current applications.
This would be applicable when the applications are console-based
(text mode) or client/server type of applications. In addition,
eSnap can be implemented for applications that don’t
have an interface; those who simply consist of a data store.
Data warehouses typically fall in this scenario but also
any in-house database gateways.
- When there is a need to reorganize/categorize
the current information without restructuring the existent
software architecture (both client and database),
eSnap allows the creation of “virtual containers”
that would offer a new organization scheme. The virtual
containers would be part of eSnap repository thus eliminating
any need to modify the current software implementation.
- When there is a need to apply
“dynamic security,”
In general, the security model – for databases –
is sort of all-or-none. For example, in the database world,
consider a user has “read or view” privilege
on a particular table: What if what is needed is to allow
the user to view the information that he is responsible
for but not be able to access all other info in the same
table? Out-of-the-box databases do not offer this type of
dynamic security. This feature is built-in in eSnap’s
framework.
- When there is a need to consolidate
information coming from heterogeneous environments (e.g.
Operating Systems – Unix, Windows, OS/400, etc.) and
disparate data store (SQL Server, Oracle, Informix, Sybase,
etc.),
In this case, eSnap acts as a universal thin client to the
enterprise information.
|
|