Win a copy of Emmy in the Key of Code this week in the General Computing forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Ron McLeod
  • Carey Brown
Bartenders:
  • Paweł Baczyński
  • Piet Souris
  • Vijitha Kumara

Migration of Application deployed on Websphere Application To TomEE

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,

  I have a requirement where i need to migrate the Application which was already running on WebSphere Application server need to be migrated and deployed onto Tomcat EE. Can you please help what all necessary steps that need to be taken care for this migration.

  In our existing application we are using Struts, Spring and POI. So please suggest steps if anyone done the migration.

  Looking forward for your response.

Thanks and Regards,
Janakiram.
 
Saloon Keeper
Posts: 21229
137
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
TomEE is Tomcat with additions to support parts of the JEE stack that Tomcat does not ordinarily do. That includes JMS, JavaServer Faces and EJB/JPA. Tomcat can do those using third-party libraries, but they have to be bound into the WAR, since they're not in the server.

TomEE, on the other hand does have these features built into the server, which makes it easier to port from full-stack servers like WebSphere, WebLogic and Wildfly. As long as you're working with the same versions, at least.

None of the technologies you mentioned, however, are part of JEE. So it's likely what you have would deploy and run unchanged on TomEE. Except that if you've packaged them in an EAR, you may have to extract the WAR(s), since Tomcat doesn't understand EARs and I'm not sure TomEE does either.

In fact, if you're running WARs and you're truly not using any JEE-specific services, it's quite likely that the WARS will run on straight Tomcat, not just TomEE.
 
Saloon Keeper
Posts: 2747
359
Android Eclipse IDE Angular Framework MySQL Database TypeScript Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I haven't worked with WebSphere before, but I have migrated a number of applications between WebLogic/BEA and WildFly/JBoss, and TomEE.

Other than dealing some implementation-specific details and/or extensions to the standard JEE APIs, I haven't found that much needed to be done with the actual application code.  What was quite different however was the configuration/management/deployment aspects of the different platforms.

Sorry that I can't give a more specific answer, and I doubt anyone will be able to provide all necessary steps to migrate between the platforms.  For me, I would start by setting-up a TomEE development environment, bring-over the application code, and then one-by-one, try to understand and resolve whatever issues arise.
 
Tim Holloway
Saloon Keeper
Posts: 21229
137
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A general note here. JEE is architected so that there are two sources of information required to deploy a web application. One is server-independent, one is server-dependent.

The server-independent deployment descriptor is one that everyone's familiar with. It's the /WEB-INF/web.xml resource in a WAR. 'nuf said.

The server-dependent deployment descriptor is, as its name implies, very different depending on what brand of webapp server you are using. You cannot expect this resource to be the same on WebSphere as it is on Tomcat. Even Wildfly when it was still JBoss with an embedded Tomcat used its own deployment descriptor (I think it was /META-INF/application.xml, but it's been a long time). It's usually not a big issue to create one of these, since most of the webapp (including web.xml) is supposed to be (almost) write-once/run anywhere.

For the most part, the server-dependent deployment descriptor defines server-supplied services, such as security realms, database connection pools, and sometimes environmental variables made available via JNDI to the webapp.
 
Bartender
Posts: 1195
38
IBM DB2 Netbeans IDE Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Ron McLeod wrote:
Sorry that I can't give a more specific answer, and I doubt anyone will be able to provide all necessary steps to migrate between the platforms.  For me, I would start by setting-up a TomEE development environment, bring-over the application code, and then one-by-one, try to understand and resolve whatever issues arise.


What Ron stated is exactly the step I followed when I migrated some web apps from Websphere to Wildfly. Successfully but with some pain. The most complex part was to get rid of proprietary  mappings of resources references in EAR / WAR , because besides web.xml I had to deal with some extension files Websphere requires (for ejb mappings ? Don't remember)At the very end I decided only to create new projects from scratch (no maven used at that time), importing source code,  and fixing all errors.
 
You firghten me terribly. I would like to go home now. Here, take this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!