We have a Weblogic (11g 10.3.6.0) Domain created using the Configuration Wizard (WL_HOME/common/bin/config.sh). This domain was configured to use Oracle JRockit JVM. So, all managed servers in this domain uses JRockit. But for some test/P.O.C reasons we want to configure a specific managed server (in this same domain) to run on top of Sun HotSpot. We need do this without change the domain's default JVM (Oracle JRockit).
Is it possible?
I tried many ways but now I'm a bit confused. Reading the DOC  I tried to change the setDomainEnv.sh to set the JAVA_VENDOR ('Sun') and JAVA_HOME (/path/to/sun/jdk). But in this way you change the JVM for whole Domain.
If I change the Server's configuration using AdminConsole (ServerX>Configuration>Server Start page) and them start it using AdminConsole or NodeManager, it (partially) works. I mean, the server starts using Sun Hotspot JVM, but if you look at the command process used to statrt it, you can see something strange.
As you can see above, the server process are still using java.class.path and java.library.path with references to Oracle JRockit JVM.
I've tested in x86_64 and Sun SPARC platform. On x86_64 the server starts with no problem. But on Solaris SPARC the server crashs during startup time.
So, my question is: how can we solve this? Are the Node Manager using setDomainEnv.sh or commEnv.sh vars to set the java.class.path and java.library.path opitons?
You can use a different JVM for specific managed server by editing parameters in server start tab from console. But if you want to change java.class.path and java.library.path with references from Oracle JRockit JVM to JDK hotspot, then you have to create separate commonenv.sh,setdomainenv.sh and startWeblogic.sh file for your managed server.
java.class.path and java.library.path env variables generally generates from commonenv.sh file.
I tried the both approaches you suggested.
In the second one (creating specific scripts: commEnv.sh, setDomainEnv.sh, etc) I can't start my managed server using Node Manager, Right? In this case I have to start it using startManagedServer.sh.