| |
|
 |
|
| Enterprise Information Management |
|
 |
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
| |
|
|
|
 |
|
|
 |
|
Adapter Facts |
|
|
|
|
Interface to the Alero Framework: |
|
Alero proprietary. Current interface
implementation is not compliant with JSR-170. |
|
|
Development SDK: |
|
All adapters have been built using the published
"Alero Server SDK" (Java), which provides
documentation, examples, and a template
or framework that can be used to build new
adapters. |
|
|
Developed For: |
|
Extend the functionality of the product.
Partners and customers can build their own
customized integration modules as part of their
solutions without Alero Technology's
intervention. Create integration modules that
follow the "Build Once, Sell Many" philosophy. |
|
|
Highlights: |
|
The following list describes briefly the
highlights of this adapter technology.
- Bi-directional, intelligent,
plug-and-play technology
- All adapters contain the business logic
required to access and manage information
from the underlying repository gracefully
and securely
- Real time, on demand access to
repositories
- No caching of data
- Each adapter performs the translation of
calls from Alero calls (API's) to repository
language and function calls
- Each adapter can be associated with one
or more security and/or event management
modules
- Adapters respect native security
- Each adapter exposes repository data as
a subset of information that can be access
through a search profile (metadata model)
- Multi-threaded, high performance
adapters
- Can be instantiate multiple times in the
same server, depending of the adapter type.
Some adapters can only be instantiate once.
|
|
|
Purpose: |
|
Integration with external repositories or to
provide services to the framework. Adapters
allow unlocking and exposing data from
repositories to the Alero BUS so services can be
applied to the data. |
|
|
Value Proposition: |
|
Integration methodology/value proposition.
A standardized and productized approach to
integration. Instead of trying to maintain
different versions of each specific integration code for
different customers, you have one code for each
application in the form of an adapter. All
customers integrating to the same application
will use the same adapter. And, by building "Build
Once, Sell Many" integration modules (in
the form of adapters), after the
initial development efforts and costs, every time that you
sell them become mostly profits. |
|
|
Sales: |
|
Adapters are integral part of the Alero
framework. As such, they can be acquired
individually for specific integration or
migration project but require to install the
Alero framework. You cannot just buy an adapter
without the framework. The price of each
adapter varies, depending on the number of users
and type of adapter. |
|
|
Functions: |
|
The functionality provided by every adapter is
divided into two categories, as follows:
- Universal. Universal functions are
functions supported by all the adapters,
including discovery, search, retrieve,
create, delete, properties, foldering,
audit/trail, etc. All these functions are
available through universal API's that allow
programmers to perform these actions without
having to know the specifics of the
repository he/she is working with (location,
type, vendor, etc.), virtualizing the access
and management of information.
- Specific. Specific functions are
functions that are only supported by one or
certain adapters but not all of them. For
instance, all the functions of checking out
and checking in a document in an ECM
product, all the functions to reserve and
process a process instance in a BPM product,
all the functions to process an invoice in
an accounting product, etc. All these
functions are available through specific
API's for each module (adapter).
|
|
|
Adapter Types: |
|
There are three types of categories of adapters:
Generic, Applications, and Standards based.
"Generic" adapters are adapters that can be used
for multiple applications or repositories of the
same type, "Application" adapters are adapters
that can be used for a specific application or
repository ONLY, and "Standards-Based" adapters
are adapters that follow specific standards and
can be used to access information in
repositories that follow those standards. |
|
|
Adapters: |
|
Following is a brief description of the types of
adapters available.
Generic
-
Databases. These types of adapters allow
connecting and managing information stored in
any JDBC Type4-compliant database (tables
and records) in a structured way.
-
File Systems. These types of adapters allow connecting and
managing information stored in file systems that are Java compliant
(folders and files).
- Federated Search. These types of adapters allow aggregating
information stored in multiple repositories for search purposes only.
These types of adapters cannot be used
alone. They require one or more instances of
the other adapters.
Applications
-
IBM FileNet P8 Content Manager*. These types of adapters allow
connecting and managing information stored in
FileNet P8 systems
(documents and folders).
-
OpenText DOCS Open*, also
known as Hummingbird DOCS Open or PCDOCS.
These types of adapters allow connecting and
managing information stored in Hummingbird
DOCS Open systems
(documents and folders).
-
OpenText DM*, also known as
Hummingbird DM. These types of
adapters allow connecting and managing
information stored in Hummingbird DM systems
(documents and folders).
- Microsoft SharePoint.
These types of adapters allow aggregating
information stored in FileNet P8 systems
(documents and folders).
- Tower Software TRIM Context*.
These types of adapters allow connecting and
managing information stored in TRIM Context
systems
(documents and folders).
- Xythos Web Content Server*.
These types of adapters allow connecting and
managing information stored in Web Content
Server systems
(documents and folders).
- Alero ECM**. These types
of adapters allow connecting and managing
information stored in an Alero repository
(documents and folders).
- Alero BPM**. These types
of adapters allow connecting and managing
information stored in an Alero BPM
repository
(processes and process instances).
* These adapters
have been built as prototypes or for specific
migration projects and may or may not be
demonstrable. However, if required for a
business opportunity, they can be turned into
product modules in days.
** The Alero framework
implements its own products using adapter
technology
Standards-Based
-
Dynamic SQL. These types of
adapters performing dynamic SQL (select and
non-select statements) to any JDBC
Type4-compliant database.
-
DASL/WebDAV. These types of adapters allow connecting and
managing information stored in DASL/WebDAV-compliant
applications
(folders and files).
|
|
|
Find out more
product facts... |
|
|
|
|
 |
|
|
|
|
|
|
|
|
Copyright © 2008 Alero Technology, Inc. All Rights Reserved. |
|
| Phone: 858.720.6688 - Toll Free:877.720.6688 - Fax: 858.720.8585 - info@alerotech.com |
|
