• 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 ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

EAR deployment problem Weblogic Migration... additional resources needed on classpath

 
Ranch Hand
Posts: 66
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I am trying to migrate a weblogic application to Websphere 5.1. I have been able to use the Application Server Toolkit to build EJB jars, and an EAR file to deploy on WAS 5.1.
However, the Weblogic application I am trying to migrate has several resources that don't get bundled into the individual EJB jars. These are objects and properties files that need to be seen by the EAR class loader for the whole application.
I tried using the JAR dependency editor, and even importing the file system that contains these jars into my project, and I can see that they are in the EAR.
The application will not start due to missing resources that are in the jars.
My question is where do I put other jars, libraries, or property files in the WAS 5.1 directory structure so that they are visible on the classpath to my application? Should I dump them in the ..\WebSphere\AppServer\config\cells\<myserver name>\applications\<my application name> directory?
Thank you,
Eric McEntee
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When you deploy to WAS, you can set the classpath to include any directory on the machine. After you have installed, you can adjust the classpath (for your application) in the admin console.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic