Basically there is a simple IF statement in the "$WL_DOMAIN_HOME$\bin\setDomainEnv.cmd" file:
@REM Set DERBY_FLAG, if derby is available.
if exist %WL_HOME%\common\derby\lib\derby.jar (
So if you want to prevent derby form starting you have a couple of options:
- you can rename "derby.jar" to something else (this is what I have done and it works)
- you can delete the IF statement from start-up script
- maybe you could statically set the DERBY_FLAG to false in the startWeblogic.cmd script
How to set this particular feature in a template I don't know. I hope this at least partially solves your problem.
I guess it is back to tweaking CLASSPATH, system variables and batch files, just like good early days of Java.
I expect thousands questions like that following seemingly "minor" (12.1.2) update of distribution package.
I hope someone can figure out how to disable particular feature in distribution DURING installation process
There's another way: pass the parameter "noderby" when using the script startWeblogic.cmd.
Setting the derby flag to false as suggested in 3 bullet point above seemed to work too. Question is, why would Oracle bundle it this way for production installs?