Server Cut-over Web App Testing
From PTAGISWiki
During the implementation of the server cut-over, we will be excluding public access to http://www.ptagis.org/ptagis/index.jsp. This will be accomplished by shutting down the weblogic appservers on reedi and rufus.
Apache is configured to display a custom error page when it cannot connect to weblogic. This will present an informative page to the public during the maintenance window and prevent any access to our ptagis and sree webapps.
However, we will need a way to test the functionality of our webapps to ensure that the server cut-over was successful.
I have created a new webapp server on rufus called appserver_test and made it a member of the normal weblogic cluster. It thus inherits all the deployments on the cluster, but it is set to listen to a different (unadvertised) port.
When we bring down the other appservers for maintenance, we can use this appserver for testing.
Appserver process IDs
Shutting down the normal appservers should be done through the weblogic admin gui. But if for some reason we need to issue kill signals to the java processes, the appservers can be identified by their memory footprint. Below is a listing of java processes on rufus:
root 557 539 0 15:10:18 pts/17 3:33 /usr/local/bea81/jdk141_02/bin/java -server -Xms250m -Xmx500m -Djava.awt.headle
root 17732 21306 4 Nov 13 ? 647:09 /usr/local/bea81/jdk141_02/jre/bin/java -Xms256m -Xmx1024m -cp /global/ds1/pitw
root 7866 19787 0 15:38:04 pts/17 0:00 grep java
root 21306 21294 0 Nov 07 ? 384:32 /usr/local/bea81/jdk141_02/bin/java -server -Xms256m -Xmx512m -Djava.awt.headle
- appserver_test has the 250/500 memory footprint
- appserver_rufus has the 256/512 memory footprint
- sree scheduler has the 256/1024 memory footprint
Remove after testing is complete
After the testing is complete, the configuration for this appserver instance should be deleted and the custom start-up script (startTestWeblogic.sh) on rufus should be deleted as well.
