This content has been marked as final. Show 2 replies
When you use startWeblogic.bat to start weblogic server, it runs a script to set all the required environment variable. Also it sets classpath variable. In case when it's running as service i guess, there is problem in setting classpath. Try with mannually passing all entries into system classpath variable. You can open startWeblogic.bat to see those values for classpath.
Edited by: user5547545 on Apr 13, 2012 9:38 PM
This issue is occurring due to oracle jars missing from the classpath when you run as windows service.
When you look at installSvc.cmd, you would realize that it is calling only commEnv.cmd to set the environment variables, due to which CLASSPATH is not set specific to the domain.
set WL_HOME=D:\Middleware\wls1036\wlserver_10.3To enforce the environment variables to be set specific to a domain, I recommend invoking setDomainEnv.cmd
So, in the install script, change the above two lines as shown below:
set WL_HOME=D:\Middleware\wls1036\wlserver_10.3NOTE: setDomainEnv.cmd internally calls commonEnv.cmd, so we need not explicitly call commonEnv.cmd again in our installSvc.cmd script
Doing this will ensure that the installSvc.cmd is setting the environment variables like CLASSPATH exactly as they are set when you use startWebLogic.cmd from your domain.