Geek Answers Handbook

What are the differences when deploying to Tomcat vs. Websphere?

If I needed to deploy the application on Tomcat vs. Websphere, what do I need to consider?

Do I have to develop my Java code differently if you are developing in one application server instead of another?

Edit:

I will redirect people from the website to a web application that processes credit cards and electronic signatures (cc and e-sigs are processed through separate services). This is his only job.

+7
source share
3 answers

You cannot use EJB on Tomcat (unless you add OpenEJB). If your WebSphere deployment uses EJBs, you will have to remove them to deploy to Tomcat.

If you use any Java EE functions outside the servlet / JSP engine and the JNDI naming service, you will have to exclude them from your application.

Tomcat accepts WAR packets. If you pack the application in an EAR in WebSphere, you will have to change it to a WAR for Tomcat.

Both use JNDI for data sources. There may be some disagreement in naming conventions, but if you adhere to the standard, they should be portable.

If you use any specific WebSphere code in your application, you will have to remove it to deploy to Tomcat.

If your application is servlets, JSPs, and JDBCs, you can deploy them without problems.

+10
source

You may think that Tomcat is a subset of Websphere, so theoretically everything that works on Tomcat will work on Websphere.

But ... Deployment in Websphere, in my humble opinion, is a terrible pain, and deployment in Tomcat just works. (And if it crashes, just delete the temporary folders)

Not knowing the technologies that you use, all I can say.

+2
source

Depends on what you are trying to deploy?

Tomcat is not a complete EE server - are you trying to deploy an EE application?

If you are just deploying a web application, it is more important to consider which version of the / etc servlet specification. each server implements.

+1
source

More articles:


All Articles