| |
|
 |
|
| Enterprise Information Management |
|
 |
|
 |
|
|
|
|
|
|
|
 |
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
 |
FAQs |
|
| |
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
Most of Alero is
implemented in Java. As such, a JRE is
required for the installer and the
Alero software. Following are the versions
supported:
For Alero v2006
and v2008: JRE
1.4.2_2 up to 1.5.
For Alero v2008
SP3 and up: JRE 1.4.2_2 up to 1.6.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
The product servers and components
are platform independent and can potentially run in any
Java supported platform. Although the Alero software may
work on any Java supported platform,
Alero Technology only guarantees the platforms tested and
certified by Alero Technology (listed below).
Other platforms and versions may be certified in the future.
For an updated list of platforms, please refer to SUN
Microsystems' web site or ask one of your Alero Technology
representatives. Following are the platforms
certified by us or our partners:
Microsoft Windows: NT, 2000, 2003, 2008
IBM AIX: 5, 6
HP-UX: 11
Sun Solaris: 9,
10
Linux:
Red Hat:
7, 8, 9.
Linux: Red Hat
Enterprise: 4, 5
Linux:
Ubuntu 9
Other Linux platforms are also supported.
Note:
Alero's Unicode foundation is the only
concern when using a different platform.
More than likely, Alero will run fine in any
other Alero non-certified Java supported
platform.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
The product uses an RDMS to keep
definitions, user data, system data, and other information,
and currently supports five of the major RDMS providers,
including:
Microsoft SQL
Server: 2000, 2005, 2008
Oracle Oracle:
8i, 9i, 10g, 11g
Sybase Sybase:
12, 15
IBM DB2: 8.1, 9,
10
IBM Informix: 10,
11
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
Most of Alero's client and administrator
applications are web-based, and are accessed through a Web
server. The product is web stack independent and should work
with any product or combination of products that are compliant
with Servlets specs 1.1. The following products have been
tested or used by Alero Technology or one or more of its
customers:
Microsoft IIS:
5, 6, 7
IBM WebSphere: 4, 5, 6, 7
BEA WebLogic: 7,
8, 9, 10, 11g
Adobe JRun: 3, 4
JBoss
JBoss:
4, 5
Apache Tomcat:
3.2.3, 4, 5, 6
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
The Alero software is
itself a
server and does not require an
application server but can run in the
context of any application server.
The decision of not using an application
server was a conscious decision during the
initial prototyping of the product. The cons
of using an application server outweighed the benefits.
Using an application server was going to add
complexity, overhead, and cost, and would
only help when dealing with records in
databases and not with files. Instead of
using an application server, Alero provides
its own
internal transaction server and the
following built-in features: scalability,
distribution, failover, virtualization,
federation, and
many more.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
Following is a list of
browsers supported by the Alero products.
Microsoft
Internet Explorer:
5, 6, 7, 8, 9
Mozilla Firefox:
1, 2, 3
Note: Other browsers may also work.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
 |
|
E. Technical
Details
Answers |
|
|
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Alero combines an innovative design with a powerful
architecture based on multi-tier, web based, pluggable, service-oriented
architecture (SOA). The entire foundation is based on XML, Unicode, and J2EE.
Based on a multitier architecture,
Alero not only separates the tiers that comprise the
product but also disassociates them from each other
allowing each layer to be changed without affecting
the others. In addition, by using a virtual channel to
communicate between the presentation and logic tiers,
Alero takes this architecture to a new level, allowing
creating next generation application/solutions. In this
way, the presentation layer can access and manage
information from one or multiple repositories as if
working with a single, virtual repository. Whether you
are using Alero's presentation layer or your own, by
simply using Alero's programming interfaces, you
immediately gain this functionality in your own solution.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Alero was designed as an
extensible framework. As such, you can
create and plug-in your own modules as if
they were an integral part of the product. This
extensible framework is comprised of four
types of modules, as follows:
-
Agents implement specific business
logic independently or in cooperation with one or more agents
and/or adapters.
-
Adapters implement specific
interfaces to information sources such as databases, file
systems, applications, other ECM systems, etc. (referred in
this documentation as 'repositories').
-
Security Managers implement user
validation and security algorithms, and may also interact with
external systems such as LDAP, single Sign-on, PKI, etc.
-
Event Managers implement extension
functionality based on transaction events.
Each of these types of modules implement a standard,
well-defined interface (framework), allowing the different types of
modules to work together seamlessly without concern for the specific
details of each implementation.
As a partner or customer of Alero Technology, you
can take full advantage of Alero's architecture, technologies, and
services by using the development tools provided with the product,
including a complete set of programming interfaces (client API's) for
different preferences and a server SDK to create server plug-in modules
such as agents, adapters, security managers and event managers.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Alero is compliant with industry standards.
As such, at the database level, it conforms to JDBC-compliant
relational DBMS and standard SQL; at the server level, the SOA
architecture conforms to JSR170, WfMC, LDAP, XML/JAXP, XPDL,
JavaMail, JCE, PKI/X.509, Unicode; and, at the web level, it
conforms to AJAX, Servlets/JSP, JSF, WebDAV, DASL, WSDL, SOAP,
and .Net.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
The entire architecture is based on
frameworks within frameworks, allowing modules to be created
and added (plugged-in) to the framework by partners as if they were an
integral part of the product, extending the functionality of
the framework (product). For more information, refer to the
answer for question E2 above.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
The product provides
just three applications: one
end-user and two management
applications. With these applications, user-related and
administrator/operator-related tasks can be
performed by end-users and administrators
respectively.
One the one hand, the Alero
Web Client application is a generic
application to facilitate the secure access and management
of information
managed by the product. This is a generic
application that allows users to perform
common user tasks such as accessing and
managing documents and folders, performing
specific tasks in a process, accessing
information in other external systems, etc.
On the other hand, the
entire product can be configured,
administered, and managed using the Alero
Administration application and can be
operated, monitored, and traced using the
Alero Server Manager application. These two
applications are also web-based.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
The Alero Web Client
application is a web based application that
was developed using Java Server Faces (JSF)
and the Java programming interface provided
with the product.
The Alero Administration
and Server Manager applications are also web
based applications that were developed using
Servlets/JSP (specs v1.1) and the Java
programming interface provided with the
product.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Alero Technology is not foreign to
the concept of virtualization. In fact, Alero takes
software virtualization to a new level by implementing
virtualization throughout the entire product, from
information to storage to server to administration.
Following is a brief description.
-
Information virtualization.
Alero virtualizes the management of information by abstracting
logical repository from physical repository, allowing
organizations to manage any type and/or number of repositories
as one single, virtual repository, regardless of their
characteristics such as data managed, location, type, platform,
architecture, language, etc.
-
Storage virtualization. Alero virtualizes storage by abstracting logical storage from physical
storage, allowing end users and applications to read, write, and
delete files without having to know the complexities of storing
and managing those files, including the number, location, and
type of storages; and the number, location, size, format, and
security of the files they are working with.
-
Server virtualization. Alero
virtualizes servers by abstracting logical server from physical
server, allowing multiple Alero servers to be seen as one single,
virtual server, regardless of their characteristics such as
location, type, platform, vendor, etc.
-
Administration virtualization.
Alero virtualizes administration by providing one central point
of configuration and management for the entire system, regardless
of the complexity, including the number of Alero servers,
locations, configurations, platforms, etc.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Designed as a
service-oriented Enterprise Service Bus
(ESB) specifically for the management and
integration of enterprise information, Alero
delivers rapid integration capabilities
through its integration services that let
you concurrently and quickly connect,
integrate, access, manage, and optimize
large-scale information resources.
Integration with other
products is accomplished using adapter
technology (modules). These adapters allow
a loose-coupled integration with third party
applications/solutions, delivering dynamic, bi-directional access to individual or multiple
underlying systems in real time. And, if you
add a comprehensive set of pre-built
services provided with the rest of the
product, which deliver services to the information accessed through
the connectivity layer, Alero allows organizations to immediately shift
the emphasis from data and application integration to information
integration, simplifying the process of integration altogether.
For more information, please refer to the
answer for questions F9 below.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
By
providing a flexible set of security
services, including proprietary and
LDAP-compliant services that validate,
authorize, and control user access rights to
system resources, Alero simplifies the
security implementation of complex
initiatives. And deployment is a snap: Alero's security services can be configured
for a business application in a matter of
hours, making these security capabilities
immediately available.
Alero's approach to security is unique in the market place. Instead of providing built-in security like most products
do, it provides modules of security that can be associated with repositories of information.
This flexible security model lets
organizations meet even the most complex
security requirements by allowing
associating multiple security modules with
any repository managed by the system, by
supporting any number of security standards
(each module can support a different
standard), and by letting partners develop
their own security implementations or
integrate with existing ones without the
need of Alero's intervention (security
modules are plug-in modules in the Alero
framework.)
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
 |
|
F. SDK and
Development
Answers |
|
|
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
Alero's approach to development
is unique in the market place. By providing a
function-rich set of integrated products that
virtualizes the enterprise, Alero allows developers,
Independent Software Vendors (ISV's), and Systems
Integrators (SI's) to shift a large percentage of the
development emphasis from programming to configuration
tasks. And by standardizing the approach to integration,
you can now easily develop your own "Build once, sell
many" integration modules, delivering consistent
and easy-to-use, -maintain and -support integrated composite
solutions in a fraction of the time and costs associated
with traditional development and integration methodologies,
while significantly reducing the risks associated with
customized solutions.
With Alero, simple to complex
development and integration projects can be accomplished
without having to worry about many of the complex
issues'such as communications, scalability, reliability,
integration, fault tolerance, security, administration, operation,
and matters of dependencies like operating systems,
databases, vendors, and data types'that development
projects must deal with. By taking care of these issues,
Alero allows developers to concentrate on the logic of
their solutions and core competencies.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
The Alero Software Development
Toolkit (SDK) provides five programming interfaces
that developers can use to develop and/or integrate
their application solutions with the Alero services,
as follows:
-
Web Services set
-
.NET Managed Code API
set for C#, VB for .NET, etc. development
-
Windows 32-bit API
set for C, C++, VB, ActiveX, ASP development
-
Java API/JB/EJB set
for Java, Servlets/JSP/HTML, etc. development
-
UNIX-C API library
set for C development
In addition to providing application
programming interfaces, the SDK also includes a Java-based
"Server SDK", which allows you to extend the Alero framework
to meet your own market requirements. Developing and
deploying your own customized agents, adapters, security
modules, event modules, filters, etc. in an integrated
solution are just days or weeks versus months or years away.
Alero is completely modular, designed for development
efficiencies without imposing proprietary technology or
techniques.
In addition to the SDK, Alero also provides
extensive user, administration, and operation facilities, that
can be delivered with your solution instead of having to develop
them in your solution, to simplify the initial development,
configuration, maintenance, monitoring, and troubleshooting of
Alero services; and a technical support team that is available
for development, configuration, integration, and implementation
assistance. These applications or facilities were developed
using these programming interfaces or client API's described in
this answer.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Developers can choose one
or more of the programming interfaces or client
API's to develop their solutions based on skills,
requirements, and/or preferences. These programming
interfaces expose all the functions and services of
the product as simple client API's so developers
can provide rich functionality within existing or
new business applications with minimal effort
(short learning curve). To facilitate the development
process, the Alero SDK provides a comprehensive set
of development aids, including: reference manuals,
specifications, technical notes, sample code,
libraries, and interfaces.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Due to the fact that the
server side was built using Java technology, the most
comprehensive toolkit is the Java toolkit,
which contains user, administration and
operation libraries. All our user and
management applications are developed using
this toolkit.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
You can use these
programming interfaces to build new
solutions and add value to existing ones
using Alero, regardless of your skills
and/or preferences in terms of design,
architecture, language, platform, etc. For
more information, please refer to the
answers for questions B5, F3 and F7.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
When developing an
application/solution using Alero, you can
use the Alero framework in two ways:
-
Build any client
side application/program/module that interacts
with the Alero server using the Alero programming
interfaces (client API's). It is straightforward
and simpler (short learning curve).
-
Build any server
side program/module taking advantage of Alero's
extensible server framework. It is more complex
compared to the client API's (longer learning curve).
When developing a server side module, keep in mind
that:
-
Alero is based on an
extensible, pluggable framework. As such, it provides
plug-in interfaces for agents, adapters, security
managers, and event managers.
-
Plug-in modules take
full advantage of existing built-in functionality like
multi-threading, database connection, security,
audit/trail, etc. and follow a well-defined interface.
You do
not have to develop the server side modules
using Alero, if
you do not want to. You can perfectly
develop your business logic and integration
outside of Alero using the client API's to
invoke Alero's services, when needed. However, there are
advantages developing these server side
modules inside Alero, as follows:
-
It will be part of the
product and can take advantage of all the features
and functionality provided with it.
-
Higher performance,
reliability and manageability.
-
All house-keeping will
be done by Alero Technology and the product, including
creating a service or process, installing it, managing
logging, messaging, dealing with operating system and
environmental issues, etc..
-
It can be productized
and delivered as part of the product.
-
You will
invoke your module through your own
API's or the product API's,
depending on the type of module and
its functionality.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
No, you can choose
whatever design, architecture and language
is required and/or desired for your solution
in conjunction with the appropriate
programming interface provided by Alero.
Whether your application is network- or
web-based, requires an application server or
not, is Java or Windows, etc., you can use
one or more of the programming interfaces
provided in the SDK to take advantage of all
the services provided by Alero.
Back
to Top |
|
|
|
|
 |
|
|
 |
|
|
|
|
|
|
|
|
Yes, you can build your
solution to be part of the framework. You
can use Alero's front-end solution or
provide your own, the business logic of your
solution can be developed inside of Alero
using agent technology, the persistent
information required for your solution
(tables in a database) and integration with
other applications/solutions can also be
developed inside of Alero using adapter
technology. By developing your solution this
way, there is no difference between what
Alero Technology provides or what you
provide. Your solution is just an extension
of Alero, dramatically reducing the time,
costs, and risk associated with the
development, deployment, maintenance and
support of custom composite solutions.
Back
to Top |
|
|
|
|
 |
|
|
|
 |
|
|
|
|
|
|
|
|
Again, you can integrate
with third party applications and solutions
by building your own integration modules
outside of Alero or by taking advantage of
Alero's pluggable, extensible architecture.
The most common way to integrate Alero with
other applications/solutions is using the
adapter technology provided with product.
For more information, please refer to the
answers for questions E8 and F6 above.
Back
to Top |
|
|
|
|
 |
|
|
|
|
|
|
|
|
 |
 |
Copyright © 2012 Alero Technology, Inc. All Rights Reserved. |
|
| Phone: 858.720.6688 - Toll Free:877.720.6688 - Fax: 858.720.8585 - info@alerotech.com |
|