Changes between Version 2 and Version 3 of drmsUpdateJMD

Timestamp:

06/18/14 12:46:39 (10 years ago)

Author:

joe

Comment:

--

drmsUpdateJMD

@@ -2 +2 @@
 
 1.  wget the jar file from the path given by the NSO.
-2.  Go to your vso path for JMDs. E.g. /opt/vso/JMD_v1.6.4.0.nohmi/jar
+2.  Go to your vso path for JMDs. E.g. 
+{{{ 
+cd /opt/vso/JMD_v1.6.4.0.nohmi/jar 
+}}}
 3.  Copy the new jar file into the path for jar files.  There is no need to remove the old one; the JMD will know what to do and will pick up the correct file.
-4.  Stop the current jmd process, either as the correct user or through sudo:  {{{sudo /opt/JMD/bin/JMD.sh stop}}}
-5.  Make sure there is no other JMD process running.  {{{ps ax |grep java |grep JMD}}}
-5.  Delete the current jetty database and its directory.  You will not lose NetDRMS data doing this action.  The JMD will install a new one one on restart.  It is important to delete the entire directory, not just its contents.  
+4.  Stop the current jmd process, either as the correct user or through sudo:  
+{{{
+sudo /opt/JMD/bin/JMD.sh stop
+}}}
+5.  Make sure there is no other JMD process running.  
+{{{
+ps ax |grep java |grep JMD
+}}}
+5.  Delete the current jetty database and its directory.  You will not lose data, as the JMD will rebuild the database on restart.  It is important to delete the entire directory, not just its contents.  (if you're really paranoid, tarball it before deleting it)
 {{{ 
 ls /opt/vso/derby/derbyDB/  
 sudo rm -rf derbyDB
 }}}
-6.  Restart the JMD and check the logs:  {{{sudo /opt/JMD/bin/JMD.sh start}}}
+6.  Restart the JMD and check the logs:  
+{{{
+sudo /opt/JMD/bin/JMD.sh start
+tail (filename mentioned in start mesage)
+}}}
 7.  Logs should say something like:
 {{{