• 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
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

best way of common application jar (xxx.jar,spring.jar,etc...)using path in websphere 7

 
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear experts,

Which is the best practices of common application jars (xxx.jar,spring.jar,etc...) using path in websphare 7?

Thanks,
SR
 
Ranch Hand
Posts: 446
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bundle all the web related jar files (like struts...) in the WAR and bundle all the other jar (shared between WAR and EJB) in the EAR file. All dependencies/references to these files should be mentioned in the MANIFEST.MF file present in EAR or WAR file.
 
selva raja
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks... My question is different. we have deployed 4 WARS in single application server.Few jars are same, which are used by all WARs.(example: spring.jar,struts.jar,log4j.jar and userdefinedclasses.jar) and put in each individual war file Lib folder.

Those common jars i need to put in websphere server common folder (/opt/IBM/WebSphere/AppServer/profiles/appjars)and set the ClassLoader. (Application Classloader Mode = PARENT_FIRST)

In my question is it correct way or not ?

Thanks,
SR
 
Deepak Pant
Ranch Hand
Posts: 446
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Your question is correct. You can (and one should) always do such optimizations. They help in long run. But sometimes they backfire as well.

One way to achieve this is by creating Shared Library for third party jars (like struts, spring) OR your own custom developed jar files.

But key question to answer before you get into this is:

1. Will all the applications defined on the WebSphere environment always share the same library versions? At some point business users may want upgrades to only one of many apps deployed to the environment.

2. Will applications run independent of each other? So upgrading one app should not cause any downtime to other applications.

All I am trying to suggest is that things which look very logical initially cause huge issues when the application is operational in production environment.
 
So it takes a day for light to pass through this glass? So this was yesterday's tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
    Bookmark Topic Watch Topic
  • New Topic