Dear Sir/Madam,
> >
> > I am in the process of evaluating different EJB components used in
> > e-commerce
> > development, for an important client. In this context I would like
to
> > obtain
> > answers from you for the following set of questions-
> >
> > i) What EJB components are offered by you? What is the
functionality of
> > each component? Any additional comments on each component?
Among others, we have the following session beans:
Membership membership info, attributes, etc
MembershipManager membership management
Merchandise merchandise info, attributes, etc
MerchandiseManager merchandise management
MerchandiseSearch merchandise search capability
OrderDropbox xml-based order submission
OrderManager order management, processing, etc
Payment xml-based payment services, credit card check, etc
Session end-user state storage/mgmt (allows multiple
web servers and servlet engines to service
all users seamlessly)
Shipping xml-based shipping and handling computations
ShoppingCart xml-based shopping cart
SiteProperties global configuration data source
Tax xml-based tax computations
All but Session, ShoppingCart and Membership are stateless, and our
unique architecture allows multiple implementations of each
service/bean
type, so you can, for example, drop in a Cybersource version of the
Payment bean without any client of the service caring that this was
done.
It is also easily extensible, both to subclass and override for
specific
needs and to create new services/beans that operate nicely in our
architecture.
The beans support a multi-catalog approach where it is easy to
implement
one or many store-fronts/catalogs on the same system.
> >
> > ii) Does your offering include user interface components (eg.
servlets
> > and/or
> > JavaServer Pages), and if yes, what are these components?
Yes, a SampleStore and multiple web managers are included that can be
used as is or modified to suit individual needs.
> >
> > iii) Does your offering include a persistence mechanism (eg. bean
managed
> > persistence or container managed persistence using an
Object-Relational
> > mapping tool from a specific vendor), and if yes, what is this
mechanism?
Persistence is achieved by the beans using JDBC to a database.
> >
> > iv) Do the EJB components have any attributes that we should be
aware of
> > to
> > use the components successfully or to integrate them successfully
with
> > custom
> > software (eg. the use of a set of design patterns), and if yes,
what are
> > these
> > attributes?
A strength of ECential is its ability to integrate with and make use
of
other software. It doesn't tie you to any app server or other
restrictions
common in other e-commerce solutions.
> >
> > v) Is your offering tied to a specific J2EE application server, and
if
> > yes,
> > which application server?
No. It works in any EJB 1.1 or EJB 1.0 app server, and also in
Visigenic
CORBA, or java RMI.
> >
> > vi) Can a purchaser purchase individual EJB components only, or is
the
> > purchaser required to purchase the total set of components?
Ecential is sold as a suite of components. An Architect is not
required to use all the default services, yet they are sold together.
> >
> > vii) What do the components cost?
Initial cost of a single enterprise version starts $40,000. Their are
many versions that scale up from there, including multi-store front and
ECential for Retail POS. Pricing is also dependent on the distribution
layout of servers.
> > viii) Any additional information about the components on the
whole.
The most importand aspect to remember in working with ECential is that
it is a development toolset/component model. It was designed to be
highly scalable, customizable based on the business logic of a client,
rather than a project being defined by a proprietary software solution.
We look to the development community to expand upon our core features
and tailor ECential to the specific needs of any niche market or
vertical segment. The ability to compliment ECential with 3rd Party
Apps as well as choosing the development platform open ECential up to a
wide range of users.
Alex Gloeckner
Evergreen Internet
Director, Business Development
480.926.4500 x269
[EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
