Referencing Classpath's Jars form OSB Projects

Question

Hi all,
We have found a behavior we cannot understand in the OSB. As we have assumed in the [Best Practices|http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/userguide/pojo.html] , if we are going to use a Jar inside an OSB project, we better use a small jar with the static methods and proxy the logic to the libraries placed in the classpath.
Assume a project ProjectA with a library proxyLib.jar which references libA.jar and libB.jar placed in the server's lib folder.
To use libA and libB from the proxyLib we have to first add them into the classpath, thus we assumed it is done editing the "Class Path" field placed in the "Server Start" tab from the WebLogic Server Console, but we wondered why it didn't work because when importing the project, a classnotfound error appeared for the project's library (proxyLib) which references the external libraries.
We solved it editing manually the setDomainEnv.sh file, but we don't understand why it doesn't worked using the console.
Our system is composed by one AdminServer and one Cluster with 2 Managed servers. The classpath modified by the console referenced the absolute path /...../domains/mydomain/lib/libA.jar and the setDomainEnv file edited is also placed in the ..mydomain/bin folder.
Does anyone know the reason?
Thank you in advance and best regards,
rromero

Answer 1

First of all, thanks for your answers.
Anuj Dwivedi wrote:
If you want to add a jar in server classpath then place it in directory $Domian_Home/lib and just restart the servers. Open the readme file inside same directory and you will find -
The jars located in this directory will be picked up and added dynamically to the end of the server classpath at server startup. The jars will be ordered lexically in the classpath. The domain library directory is one mechanism that can be used for adding application libraries to the server classpath.
It is possible to override the $DOMAIN_DIR/lib directory using the -Dweblogic.ext.dirs system property during startup. This property specifies a list of directories to pick up jars from and dynamically append to the end of the server classpath using java.io.File.pathSeparator as the delimiter between path entries.This is the most preffered way to add a jar in server classpath.
Regards,
AnujAs I said, at first instance, the libraries where already in the lib folder and didn't take any effect until I added manually to the setDomainEnv
atheek1 wrote:
Server Start" tab from the WebLogic Server Console,Whatever you configure in server start takes effect only if you use node manager to start that server . If you are not using node manager these settings wont have any impact.
I also beg to differ with Anuj on putting jars in domain/lib, for some reasons i find in certain cases osb doesn't recognize these jars in domain/lib (both for java callouts and when using 3rd party jms providers ), so to be safe its better to put it explicitly in classpath,
This thread discussed one strange problem with putting jars on domain/lib.
http://forums.oracle.com/forums/thread.jspa?messageID=9173629&#9173629
We are using nodemanagers with the managed servers, so that's why I expected the problem to be solved using the "Server Start" tab.
Regards,
rromero