Test if weblogic is running
On reedi or rufus issue this command:
ps -eaf | grep java
You should get a response like this:
reedi.psmfc.org:C1:root: > ps -eaf | grep java root 6233 6221 0 Jan 31 ? 2:50 /usr/local/bea81/jdk141_02/bin/java -server -Xms32m -Xmx200m -XX:MaxPermSize=12 root 6273 6261 0 Jan 31 ? 361:59 /usr/local/bea81/jdk141_02/bin/java -server -Xms256m -Xmx512m -Djava.awt.headle root 1121 6273 0 Feb 08 ? 15:29 /usr/local/bea81/jdk141_02/jre/bin/java -Xms256m -Xmx1024m -cp /global/ds1/pitw root 2087 20643 0 13:44:11 pts/1 0:00 grep java
The processes can be identified by the min and max memory allocated to them.
- -Xms32m -Xmx200m is the weblogic admin console which should only be running on reedi
- -Xms256m -Xmx512m is the general instance of weblogic server that actually serves the PTAGIS site
- -Xms256m -Xmx1024m is the SREE scheduler which should only be on one machine in the cluster
Restart weblogic on the cluster
- Use the admin console to request a graceful shutdown of the server
- start a bash shell on reedi and rufus
- Use this command to start:
cd /usr/local/bea81/user_projects/mydomain2 nohup ./startManagedWebLogic.sh &
- Tail nohup.out until the server enters the running state
- repeat for each server in the cluster
Restart weblogic on the development server
- Use the admin console to request a graceful shutdown
- start a bash shell on pitblade
- Use this command to start:
cd /dsk2/local/bea81/user_projects/mydomain nohup ./startWeblogic.sh &
No comments:
Post a Comment