• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Unable to work with sharelib in Websphere version 8.5.5 and JAMon

 
gagan patil
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
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
Greenhorn
Posts: 8
  • 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
 
Claude Moore
Ranch Hand
Posts: 785
7
IBM DB2 Java Netbeans IDE
  • 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
 
Mikalai Zaikin
Ranch Hand
Posts: 3332
10
  • 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.

Regards,
MZ
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic