> Hi all,
>
> i have currently an dicussion going on about creating
> a 3/Multi Tier Enterprise Application which will
> have one Webbased Client and one Standalone Client.
> The main aim is the Webbased Client.
>
For the most(if not all)modern Enterprise Application is
based on the n-tier, a.k.a., muti-tier archtiecture. Sometimes,
we use the term, 3-tier architecture, but there ia a clear
seperation between the conventional 3-tier and mordern,
a.k.a., enhanced 3 tier, architectures.
>From that architectural sense, if your immediate goal
is bound to the client tier and web tier, a.k.a., presenation
tier( i.e., the other tiers, including business tier, ..., persistence
tier, are not issue nor focus here.), Tomcat will do just
fine for your immediate, specific need.
> The problem is there are some workers which want to
> use .NET and some who want to use J2EE.
> I dont want to start something like a flame war here.
> I just want to find out if we could use the Tomcat
> server and/or other Open Source Projects to
> develop our Application because i dont want
> to go the .NET way.
> The application would be a middle to big size
> CRM system.
>
No need to fight with your colleagues. They are not your enemy.
If possible, all should be able to use whatever they prefer
to use. In that way, you can maintain ONE BIG HAPPY FAMILY
under the SAME UMBRELLAR.
Since XML is a W3C standard and more industries in global
environment adopting the XML based solution, I am sure
you are well awaring of the XML that can be an ideal solution
for you as well.
To wit, if you use the XML document whether you use it as
messaging payload and/or business document, you all can
use the technology each individual of your team prefers while
making everyone's work "interoperable" at the same time.
For example, take a look at the SOAP with Document-style,
not the RPC-style whch is starting to fade out from the
interoperable sense.
> So what we will need is an Application Server which
> can handle EJB's. Even too it should be scalable in a way
> that you can split parts of your application about
> several servers which are working together in a network
> environment.
> As far as i have found out until now Tomcat can't do
> that things. Some people told me that Tomcat only implements
> some J2EE standards.
> I havent found a site on apache.org (Jakarta Side) that
> explains what Tomcat can do and what it cant.
> Anybody has one?
>
Most of Java professioanls should be able to answer this
for you, including JBoss, OpenEJB, ... So that I am skipping
this.
> Can Tomcat work together with other Applications
> that integrate the functions that Tomcat doesnt have
> but are needed for J2EE Applications?
>
Yes. For the Enterprise Application, the component-based
architecture should be one of your technical requirements.
>From that sense, you should consider the "frameworks" which
is a.k.a, architectural patterns. Then Tomcat will be one
of your frameworks and fits well in your component-based
architecture.
> So as far as i can see now. Tomcat is good for some
> mainly Webbased applications which are using Servlets
> but i cant see in which productive environments it is
> used. Could anybody tell me in what kind of projects
> you did use it?
>
For the reliability issue, I will recommend you to develop
a pilot or POC before dive into the production system. In
that way you can test more than one framework during the
early development process. (I am omitting the benefits
why you would do such). Tomcat can be one of those
framworks and you sure can get your own feeling during that
process.
> And now there is another question which doesnt really
> belong to this Mailinglist. But if i am here ... =)
> So if Tomcat cant be used to create Enterprise Applications
> which are mostly using EJB's and should be scalable on the server
> side what other ways are there. I've heard about other
> Open Source J2EE Application Servers and then there are the
> commercial Servers like Websphere and so on.
> I've surley read books about J2EE but none of them didnt
> give much information about the diffrent application servers
> for J2EE. So i know some stuff about programming J2EE applications
> but not much about how to implement them on the server side.
> Any suggestions on that?
>
For scalabilty, it is ideal to maintain the clear seperation, a.k.a,
loosely-coupled, in your architecture. Some commercial App Server
contain too much stuff from that sense. And you will need to have
multiple copies as well as license for that.
Since Tomcat is just for JSP/Servlet, it is one of ideal packages
that fits well in the component-based architecture. (Also, take a
look at the Load Balancing with Apache/HTTPd). To wit, the
mechanisms in this tier can communicate with other mechanisms --
a.k.a., "design patterns", whether they are in the business tier or
some other tier. This communciation can be accomplised in a various
ways. Also, they all can schooled together in a single host even
though they will not do much by keeping them all busy in switching
just the contexts or multiple hosts in the distributed enviroment.
Since n-tier architecture is not a topic you can cover in a single
message, I will let you discover more based on your needs.
>
> Thank you for reading my stuff and if you have any idea about
> my questions any answer would be highly appreciated.
>
You are welcome. And good luck.
> Thanks and Greetings,
> G. Balandres
>
Pae
> --
>
> Even god is a Programmer:
> while heartIsBumping() {
> /* Many
> Cases and If-Else Routines
> which ends with
> exit
> */
>
> doLive()
> }
>
>From the technical point of view in developing the Enterprise
Application, god also can be an architect, OO modeler, etc.
This means that god is wearing the mutilpe hats if you can
consider the other viewpoints. :-)
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
