we have a doubt posted in few sites but didnt get a exact or satisfying answer.You are good at both EBS and weblogic as well as java.we hope we will for sure get an answer from you
In r12.2,we use ad scripts to start the services due to some dependencies(ofcourse not sure exactly what dependencies-if you give some example it would be fine).But why script startWebLogic.sh was included in ad script?Is adscripts using startWebLogic.sh script internally to start the services?
if [ "$silentmode" != "-silent" ]; then
echo "Refer $LOG for details"
fi
fi
elif [ "$control_code" = "startForDeployment" ]; then
if test "$PLATFORM" = "LINUX_X86-64"; then
nohup $LINUX32 /u01/DEVDBAPPS/fs1/FMW_Home/user_projects/domains/EBS_domain_DEVDB/bin/startWebLogic.sh >> $LOG 2>&1 &
else
nohup /u01/DEVDBAPPS/fs1/FMW_Home/user_projects/domains/EBS_domain_DEVDB/bin/startWebLogic.sh >> $LOG 2>&1 &
fi
Those AD scripts are like wrappers, but they control the WLS components using adProvisionEBS.pl.
That weblogic start code, however, doesn't use the adProvisionEBS.pl and it is executed when you execute the relevant AD script with startForDeployment argument.
For example: if you execute adadminsrvctl.sh startForDeployment, then that code you sent will be executed.
But, normally we don't use this startForDeployment argument. (we use start / stop) It is not documented and it is not documented even in the usage of the AD Scripts.
It is an internal argument and that's why it is probably used by the EBS internally.
It may be used by adop during cutover, it may be used during the installation and so on..
It is a parameter to be used to start a pure Weblogic instance. It is a way to tell AD scripts -> start me the weblogic server because I will make some deployments on it.
so it is not something that you should be thinking of..