Win a copy of JDBC Workbook this week in the JDBC and Relational Databases forum
or A Day in Code in the A Day in Code 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 ...
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger

Unable to work with sharelib in Websphere version 8.5.5 and JAMon

Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Problem statement

i want to keep one jar which is common to webapplications deployed on websphere application server version 8.5.5(not in Network deployment mode) so that whenever any object state changed in it it is visible in other web application.
same thing i had achieved in other servers i.e. tomcat and weblogic( i.e. by keeping it in server lib folder) but similar thing when i try to achieve in Websphere 8.5.5 i am unable to do with the help of shared lib concept of websphere.

more details
i am working on creating POC for my orgainization to check feasibility of JAMon application monitoring tool. this discussion is in same context.

your help is appraciated.
gagan patil
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Everyone,
I got workaround for this problem by keeping this common jar in

/usr/IBM/WebSphere/AppServer/lib/ext folder

but it will be helpful if someone help me if same functionality can be achieved by shared lib or not
Posts: 1264
IBM DB2 Netbeans IDE Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Copying jars in was runtime isn't a good practice at all, despite the fact it works. I strongly advice you to try again with shared library instead. I never used shared lib with was 8.5.x, only with was 6.x... in was 6, you need to define a classloader ad associate to it your shared lib, i think the same must be done with 8.5.x
Posts: 3615
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Gagan,

As Claude said - modifying WAS runtime is a bad practice, you should not touch files under WAS lib folder. Also, you may have this not approved in production environment by WAS admins.

I am not sure what problem you have.

We used shared libraries in WAS 7 and WAS 8.5. You should define shared library first in WAS (place JAR to some permanent place, but not under WAS HOME), then during EAR deployment configure application that it uses shared library.

I have a knack for fixing things like this ... um ... sorry ... here is a consilitory tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
    Bookmark Topic Watch Topic
  • New Topic