Start weblogic remotely

Question

I setup Wl451 in solaris 2.6 , and want to remote start it and let it
run in background, but when I start WL from a terminal using
"startWebLogic.sh", if I close the terminal, the WL server will
shutdown, how can I reslove the problem. I have to start WL from a
terminal by
"startWebLogic.sh".
Thanks

Answer 1

frank wrote:
>
I run the "# nohup ./startWebLogic.sh &" in weblogic account and root ,
the error message followed:
Sending output to nohup.out
nohup: ./startWebLogic.sh: Permission denied
Wei Guan wrote:
use "nohup startWeblogic.sh &"
Cheers - Wei
frank <[email protected]> wrote in message news:[email protected]...
I setup Wl451 in solaris 2.6 , and want to remote start it and let it
run in background, but when I start WL from a terminal using
"startWebLogic.sh", if I close the terminal, the WL server will
shutdown, how can I reslove the problem. I have to start WL from a
terminal by
"startWebLogic.sh".
Thanks
Frank,
Here's the script I use. It's a more standardized init.d script.
Things to note are that I changed my startWeblogic.sh script to be
able to be run from anywhere (that's important since they make a beef in
the docs about the location of the weblogic.properties file.
Note on the init.d script: if you have more than one thing that will
identify itself as 'java' via the 'grep' in kill_proc() you'll need to
change the string to grep on.
/etc/init.d/webglogic
#!/bin/sh
# Start weblogic application
PROJECT_HOME=/path/to/where/I/installed/weblogic
# Kill all processes matching a certain name
kill_proc () {
ps -ef | grep "$1" | grep `/usr/xpg4/bin/id -un` | grep -v grep | while read PROC; do \
PID=`echo ${PROC} | awk '{ print $2 }'`
[ ${PID} -gt 0 ] && kill ${PID}
done
case "$1" in
start)
cd ${PROJECT_HOME}/weblogic
startWebLogic.sh >/dev/null 2>/dev/null &
echo "weblogic application started.";
stop)
kill_proc "java"
echo "weblogic application stopped.";
echo "Usage: $0 { start | stop }"
exit 1
esac
exit 0
${PROJECT_HOME}/weblogic/startWeblogic.sh
(only for jdk1.2 and non-AIX 'cause I removed some junk I didn't need)
#!/bin/sh
JAVA=/usr/local/java/jdk12/bin/java
WL_HOME=/export/home/steveh/weblogic
MYSERVER=$WL_HOME/myserver
CLIENT_CLASSES=$MYSERVER/clientclasses
SERVER_CLASSES=$MYSERVER/serverclasses
SERVLET_CLASSES=$MYSERVER/servletclasses
MY_CLASSES=/any/project/classpath/stuff/here
# Make sure we're in the right place
if [ ! -f $WL_HOME/license/WebLogicLicense.xml -o ! -f $WL_HOME/weblogic.policy ]; then
echo "startWeblogic.sh: must be run from the WebLogic installation directory." 1>&2
exit 1
fi
# Grab some file descriptors.
maxfiles=`ulimit -H -n`
if [ ! $? -a "$maxfiles" != 1024 ]; then
if [ "$maxfiles" = "unlimited" ]; then
maxfiles=1025
fi
if [ "$maxfiles" -lt 1024 ]; then
ulimit -n $maxfiles
else
ulimit -n 1024
fi
fi
# Check whether we're running Java 2
#$JAVA -X > /dev/null 2>&1
#if [ $? -a -n "$JDK_HOME" ]; then
# # Java 1
# JAVACLASSPATH=$JDK_HOME/lib/classes.zip:./classes/boot:./eval/cloudscape/lib/cloudscape.jar
#else
# # Java 2, or Java 1 and java knows where classes.zip is
# JAVACLASSPATH=$WL_HOME/classes/boot:$WL_HOME/eval/cloudscape/lib/cloudscape.jar:$WL_HOME/lib/poolor
b.jar
JAVACLASSPATH=$WL_HOME/classes/boot
#fi
## sp3 changes
WEBLOGICCLASSPATH=$WL_HOME/lib/weblogic451sp3.jar:$WL_HOME/license:$WL_HOME/classes:$WL_HOME/lib/weblo
gicaux.jar:$WL_HOME/myserver/serverclasses:$MY_CLASSES
$JAVA -ms64m -mx64m -classpath $JAVACLASSPATH -Dweblogic.system.home=$WL_HOME -Dweblogic.class.path=$W
EBLOGICCLASSPATH -Djava.security.manager -Djava.security.policy==$WL_HOME/weblogic.policy -Djava.compi
ler weblogic.Server
The first thing to get running is the startWeblogic.sh script so that it can be run from anywhere.
After that, the init.d script is trivial.
One more thing I did was to set:
weblogic.system.enableConsole=false
so we aren't just dumping all that junk to /dev/null. Of course this means if you
are using something like System.out or System.err for debugging output you'll
need to use the T3Services log functions to output that stuff.
If you were to redirect to a log file rather than /dev/null you'd not only
have to deal with the problem of rotating the log files over a long period of time
but also (if you didn't turn the console off) you'd have duplicate message to both places
(can we say slow?).
Enjoy!
Steve