Hey dear WLA most of us come from Development environment to production environments. Hope the scienario thatI am going to discuss here is a common to everyone, who is working on development environment. Sometime or other you might felt I should have a handy script that could takes input as a WebLogic instance port which usually get from the applicaiton URL. The WebLogic port and list all the Process IDs which are associated with it on UNIX(here I got solution for Solaris) environment. Recently I found a Sun blog which is clearly discussed similar issue. I am re-compiling the same with customizing to our WebLogic Listen Port, WebLogic Server runs with a Java generated child Process ID. 'lsof' is the command you can execute and get this solved but most of the times it is a Sun third party downloads, that is not allowed in many Banking, Financial and Insurance Service organizations. And one more reason is small companies doesn't efford for third party tools.
Then, Your choice will be writing a handy script that will do the same task as lsof command helps to find the process id for a given WebLogic Listening port.
Run with argument or without also it will work!! But you need to input the listening port that is must.
Then, Your choice will be writing a handy script that will do the same task as lsof command helps to find the process id for a given WebLogic Listening port.
#!/bin/ksh pids=$(/usr/bin/ps -ef -o pid=) if [ $# -eq 0 ]; then read wlport?"Enter port you would like to know Java Process Id for: " else wlport=$1 fi for f in $pids do /usr/proc/bin/pfiles $f 2>/dev/null | /usr/xpg4/bin/grep -q "port: $wlport$" if [ $? -eq 0 ]; then echo "===============***=============***===============" echo "ListenPort: $wlport is being used by Java PID:\c" ps -ef -o pid -o args | egrep -v "grep|pfiles" | grep $f exit 0 # if you suspect more Weblogic instances with same listen port remove this fi doneNote: Save this script to commonly accessing user location name it as WLPort2Pid.ksh
Run with argument or without also it will work!! But you need to input the listening port that is must.
No comments:
Post a Comment