Shared library in Websphere 7

Question

I deploy my EAR to WAS 6 with 3 modules, all three of these modules have many jar files, which makes my EAR hard to avoid that I want to use the Websphere shared library wizard. Please tell me the link or tell me what changes I should make to my code or resource or any .xml files. I use the link below to configure my Websphere JAR Link to the Websphere shared library 1 Link 2 Link 3

Thanks in advance

Answer 1

This is how the generic libray refers.

Login to the Websphere application server console.

• Go to Environment → Shared Libraries
  • Create your own shared library. Add the classpath to the JAR files.
  • Apply and save this configuration.
  • Now go to Servers → Application Servers → Select Server-> Java and Process Management → ClassLoader.
  • Click on this classloader.
  • Click the link to the shared library
  • Click Add.
  • Add your shared library.
  • Save and restart Websphere servers.

Answer 2

Thanks to everyone for HELP .. Finally I found a solution.

• First delete all .jar files from your EAR, even from different modules.
• Save all .jar files to a specific location.
• Go to the WAS administrator console> Environment> Shared library and give a suitable name and specify the path class of all the necessary jar files. e.g. C: /libs/ojdbc14.jar. Reboot WAS.
• Then deploy the EAR to the WAS, but do not start it.
• Go to the administrator’s console> Application Lists> select your application> Link to the shared library, there you will see all the modules of your EAR. Check the box next to it and click "Reference Library."
• Here you will see the entire previously saved Shared library, add it to all modules.
• Now run your application.

Answer 3

A common problem that I encountered with Shared Libraries was a few instances of banners appearing. So, When installing web applications under WAS, you can set the class loading policy in the parameters of this application (or globally at the server / node level)

If the policy settings (search) are "parent first" / "parent last" and one class loader for each application or for war. The default is parent first / war. If your web application comes with all banks, it will be better for you if the policy is set to "parent last / application". Also, if you edit your web.xml to reflect the changes, be sure to set "use binary configuration", otherwise it will always use what it stored during installation.

You get the class loading parameter under Wepsphere Applications → click on the name of the application where you can see the class loader parameter.