• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

JNI libraries in WAS

Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am using WAS 3.5.3. We have some JNI shared libraries which need to be loaded when the App.Server instance is started. I can modify the startupServer.sh script to include the directory which contains these libraries, but my client does not allow this. We've explored the option of creating symlinks in the websphere/lib directory, but this is also not allowed. Can someone suggest a viable alternative? We've tried using the command-line arguments to append to the java.library.path property, but haven't been successful so far. Any help will be appreciated. Thanks.
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic