in our opinion you are very right to take a deep look into the java
based technology frameworks for EAI.

To your questions:

We developed server based oo technology since 1993 and have a very deep
skill in this area of technology.
We come to java frameworks 1998 and found the java technology 100% better
for frameworks than C++ or smalltalk.

The component and java technology is very comfortable to develop server
based, distributed and scaleable frameworks
to the reason of a collabarativ and adaptive EAI tool. The component model
of the java technology (EJB) is real and
the performance is suitable for a large amount of users and processes.

The advantage of such a java based framework is that you could update every
class, process and so on on demand
into a running EAI system. Further more you could combine product interfaces
of different vendors to got a best of breed
for the needed integration scenario and functionality.

The Business 4 Enterprise GmbH has a product suite which is developed 100%
real in java, XML and EJB. All
services and component are server based an we use the servlet technology
only for the connection to the user.
Our product suite is J2EE compliant and could connect other server based
application to deal with there functionality.
We also have implemented a cannel, portal, process and integration layer to
have a good abstraction for large projects.

Compared with JMS and CORBA, java, XML and EJB are today good working
technologies. The performance of EJB
Is good, the IDE`s to develop with EJB are good, the standard is real and
into J2EE oriented into the next future and so on.

JMS and CORBA are technologies for messaging and object distribution. The
functionality of EAI comes from the humane
using and developing of these technologies into an framework. Maybe there
are some frameworks that are using JMS and/or
CORBA, but what does this tell us?!. Only to use a technology is nothing.
The design and the functionality of a framework is
that what a customer needs and wants.

I think what suresh was asking was more specific to
the technology implementations for Java Space and Jini
combine.

I would like to add saying that, there haven't been
Jini based products in the market that are really
stable and popular. This as the parameter would make
your question about EAI substitution a straightforward
one.

I think a combination would perform more like
Web-Services, but the scalability and transaction
support would not be there, which are very critical.
Also the functioning of the Framework would depend on
externally hosted services or remotely running
services.

I think most of us agree that Java as a technology for
EAI is very convenient to use and is becoming a
standard implementation platform.

I would like to get more information on the products
you have Michael. Can I get a feel of the products for
evaluation?

The design of a framework has to reflect the fact that the user of server
based
service of the framework needs transactions and subsystem access. The
digital
processes that are running in our process layer accesses the other
abstraction
layers and there services. We could open a global transaction and could
control
all user interaction, presentation, user behaviour, processes field user and
system
data, subsystem connection and calls with data transforming.

We uses two phase commit (2PC), LDAP and X.509 connection to guard the
information
in a transactional an secure way.

The mainframe is one of the important subsystem that would be connected
through our
framework. Other subsystems could be any server based application with an
proper API
e.g. SAP, Siebel, and so on. The logic of the integration is today include
into the middle
tiers between the user and the subsystems. The business logic of tomorrow
will located
into such a middle tier and could use the infrastructure of that middle tier
as the EAI
infrastructure. The reusability of the components of our framework is very
high and give
a customer the ROI and TCO which he is looking for.

Infrastructure is not a trick and you will find everywhere in IT and real
live. The combination
of business knowledge, it-architecture, design and implementation is the
frame of future
it-business. Design Patterns tells us this since more than 8 years.

The customer know its business and know its business requirement. Both
brings the requirement
for it systems and it infrastructures. To implement such a it
infrastructures is a well knowing
walk through all it technologies and working skills of it.

A framework is not a thing you can put on a CD and deliver to everyone who
ask for.
We can give you papers to understand more what we offer.
If you interested in to look into our classes and design, we have to meet
us.

Our company is a new one, but all unique person have more than 10 years
knowledge of real it and that
in new technologies, architectures, mainframes, databases (relational and
object oriented) and applications.
Since 3 years we have deep experience with EJB?s and since 11 month we
develop our framework (EAI Cooperation Framework).

I agree that the use of JINI for EAI is probably not going to happen.
In addition to lack of market penetration, JINI is Java centric.

I do think however that JXTA may hold promise. JXTA is important for
what it addresses and also for what it doesn't address. For example,
JXTZ is not tied to Java and doesn't mandate specific security or
encryption practices.

I would be interested in hearing about experiences with JXTA in regards
to EIA.

(I would also like our product, iNtegrate!, to be included in list of
new moderately priced approaches to EAI :)

I agree that the use of JINI for EAI is probably not going to happen.
In addition to lack of market penetration, JINI is Java centric.

*** The EAI market with JINI technology would be the upcomming area which i think many EAI Architects should look at.
yes JINI Services are Java centric , but providing SOAP gateway over it would make sense to all clients and would also bring up the market for JINI
there are products like gigaspace.

I do think however that JXTA may hold promise. JXTA is important for
what it addresses and also for what it doesn't address. For example,
JXTZ is not tied to Java and doesn't mandate specific security or
encryption practices.

*** Can u please elaborate , an example would be of more help

I would be interested in hearing about experiences with JXTA in regards
to EIA.

*** TIFOSI is one product which implements JXTA, for EAI, why dont you look into, for further details visit www.fiorano.com

(I would also like our product, iNtegrate!, to be included in list of
new moderately priced approaches to EAI :)

*** I would like to know about your product, can you let me know the website

The component and java technology is very comfortable to develop serverbased, distributed and scaleable frameworksto the reason of a collabarativ and adaptive EAI tool. The component modelof the java technology (EJB) is real andthe performance is suitable for a large amount of users and processes.
The advantage of such a java based framework is that you could update everyclass, process and so on on demandinto a running EAI system. Further more you could combine product interfaces of different vendors to got a best of breedfor the needed integration scenario and functionality.The Business 4 Enterprise GmbH has a product suite which is developed 100%real in java, XML and EJB. Allservices and component are server based an we use the servlet technologyonly for the connection to the user.Our product suite is J2EE compliant and could connect other server basedapplication to deal with there functionality.We also have implemented a cannel, portal, process and integration layer tohave a good abstraction for large projects.

I agree with u,the component model EJB is highly accepted model in most of Industry verticals.But EJB systems are tightly coupled which demands the services ,network should be available 24x7. If u look into any IntegrationServers that are available , the systems are loosely coupled, ensures the message fail-over protection,scalable,and allows to define workflow activites. Alone EJB could not fit into EAI, EJB with workflow, Integration layer would be good for EAI.

Compared with JMS and CORBA, java, XML and EJB are today good workingtechnologies. The performance of EJB Is good, the IDE`s to develop with EJB are good, the standard is real andinto J2EE oriented into the next future and so on.

I dont get ur idea, it seems u r comparing a transport vehicle with the passenger in that vehicle which i think is not valid

JMS and CORBA are technologies for messaging and object distribution. Thefunctionality of EAI comes from the humane using and developing of these technologies into an framework. Maybe thereare some frameworks that are using JMS and/or CORBA, but what does this tell us?!. Only to use a technology is nothing.The design and the functionality of a framework isthat what a customer needs and wants.

a lose coupling is a design pattern and could be achieved with
any programme language (e.g. C++, Java, EJB, and so on). A
programmer has to design a the indirections and abstraction layers
that solve a loose coupling.

So we have skill > 5 years in programming Java and > 3 years for EJB´s.
We come to EJB because with EJB´s you could have a good running
distributed object run time environment. The environment for EJB´s are
application servers (e.g. IBM WebSphere, BEA WebLogic, JBoss, ...).
With WebSphere and WebLogic you could solve a lot of technical
requirements (e.g. fail-over, distribution, backup, ...).

Security is also a point of design and therefore a service into a framework.
SSL is the minimum that has provided from a connection of a customer
To a server based appl.. But what is with the security of process
connections
between more location into an EAI-System-Environment. To support more
location are often a real requirement of a customer of EAI.

24x7 is also an design point. The used technology has to have some important
issues to solve this requirement but the right design is more important than
the
technology. I know systems written in C, C++, Java and EJB that solve this
requirement. Every system achieved 24x7 in a other way and with a other
deepness.

A workflow for digital processes is also not a point of technique and has to
achieved
by the development of systems and also has to bring in into a system by
concepts
and design.

A framework offers you a rich set of ready component that has not to
developed.
Time to market is better, the cost will reduced, the quality is clear and
the risk
could be calculated. That are the 4 most important workflows for projects.
Other
discussions about the usability and details of products could better held if
people meets themselves and know something about the project requirements.

It is a good question. Probably the majority of the people that have
answered does not understand what Jini really is.
Some people think that Jini is an appropriate technology to discover remote
services (have a look to this article
http://www.cbdiforum.com/public/news/index.php3?id =811)
I believe that Jini is really not a solution for EAI. Jini is much more a
technology that will allow your process to discover the most appropriate and
nearest service provider.

I think that Jini could be used in distributed environments to simplify the
administration of such environments. Instead of specifying the routes and
path to the appropriate brokers, the brokers could be discovered at runtime
depending on the needed service and quality level.

The important words here are "COULD BE". Jini, unlike J2EE hasn't reached an
inescapable level. The market will accept or reject Jini technology for
business applications like EAI.