|
The WebFacing Tool creates standard JavaServer Pages, Java beans and
servlets that will run in any application server that supports the
standards for these Java components.
We have sanity tested WebFaced applications on Tomcat and we found no
problems, but we have not completed exhaustive testing. There are a few
Tomcat limitations that I'm aware of:
It can't debug JSPs and servlets because there is no kicker class in
Tomcat. The iSeries AD team created the kicker class for WebSphere
Application Server.
Non-Latin National Language support is problematic. The WebFacing team
suspects that the Tomcat NL support will not handle WebFaced
applications.
When you start to have substantial e-business traffic on your application
server, you will want to upgrade from Tomcat to WAS.
Reasons:
reliability
scalability
security
throughput / performance tuning
==================================
MORE INFORMATION ON THIS TOPIC
==================================
Ask your Web development questions--or help out your peers by answering them--in our live discussion forums.
The Best Web Links: tips, tutorials and more.
Check out this live Q&A with Dave Slater and Jim Mason, How to best get started with WebSphere Development Tools.
|
