Updating Hosted Customer Instances on the OnPoint Production Server By Peter Westphal

Transcription

1 Updating Hosted Customer Instances on the OnPoint Production Server By Peter Westphal Note: The following instructions use version x of OnPoint Course Manager ( OPCM ) and v1.5.2 of OnPoint Convent Viewer ( OPCV ). If you are updated later versions, please change the file version number to suit. Login to PROD and then Login as Root User All updates must be performed as the root user. To begin, telnet into the server using the command: 1. From a DOS prompt, Telnet into the PROD server: telnet XXX 2. Login to PROD server using standard account: UN: rgadd PW: not******* 3. Change to Root User at the prompt via: su 4. Provide the Root User password: rkoxxx Customer Slice Numbers The remainder of these instructions refer directly to updating a sample customer slice numbered X (e.g. tomcatx). To update other customer slices, change the value X to the appropriate number. (e.g., tomcat2, tomcat3) Commands All of the following command (shell commands) should be issued from the command line. Commands and filenames in Linux/UNIX are case sensitive. Be sure to enter the commands in the same case as presented in this document. Updating OPCM (Course Manager) 1. Change to the customers tomcat directory cd /usr/local/customers/tomcatx 2. Stop the customer s tomcat instance 1

2 3. Remove the customer s temporary work files rm rf./work/standalone/localhost/* 4. Remove the customer s old log files rm rf./logs/* 5. Change the customer s webapps directory cd webapps 6. Copy the opcm release file to the webapps directory cp /home/releases/opcm zip. 7. Unzip the opcm release file unzip opcm zip The unzip program will prompt you with a series of choices, Archive: opcm_ zip replace opcm/.classpath? [y]es, [n]o, [A]ll, [r]ename: _ Select the [A]ll option by entering the uppercase letter A 8. Once the unzip operation has completed, delete the zip file rm opcm zip 9. Change to the./opcm/setup/database directory cd./opcm/setup/database 10. Check the current database version. The database directory contains a series of files named onpoint_update_xxxx.sql. Where the xxxx is a number (i.e. 1016). Each file represents the modifications to the OnPoint database for the specified version. When performing database updates, be sure to perform the updates in sequence. You can see a list of files using the UNIX ls command. ls l To check the current database version number you need to execute the mysql command mysql u root p Use the password rkoxxx. This will log you into mysql as the MySQL root user. You should see the mysql> prompt. Next select the customer s database 2

3 use customerx; Query the database from the current version number select code from opstat where type= DBVERSION ; The mysql program will respond with a version number. For example: code 1014 If the database version number is the same as the latest onpoint_update_xxxx.sql file (largest value for xxxx), then no further updates are required. 11. If database base updates are required then from the mysql prompt issue the following command. You will need to repeat this command for each database version update. The following commands will update the database from version 1014 to source onpoint_update_1015.sql; source onpoint_update_1016.sql; 12. It s a good idea to confirm that the DB changes took by reissuing the version checking command again via: select code from opstat where type= DBVERSION ; The mysql program should respond with a final version number. For example: code Exit mysql quit: 14. Restart the tomcat slice and test the update opcm application /etc/init.d/tomcat1 start Use a browser to access and test the customer s opcm application. Note: There are other required configuration parameters based on the version of opcv (Content Viewer) you re deploying. These steps involve updating the Tomcat server.xml file (in the conf directory) and copying the required jar files to the Tomcat common/lib directory. As of this writing all customer slices have been updated to the currently required server.xml and jar files. Updating OPCV (Content Viewer) 1. Change to the customers tomcat directory 3

4 cd /usr/local/customers/tomcatx 2. Stop the customer s tomcat instance 3. Remove the customer s temporary work files rm rf./work/standalone/localhost/* 4. Remove the customer s old log files rm rf./logs/* 5. Change the customer s webapps directory cd webapps 6. Copy the opcv release file to the webapps directory cp /home/releases/opcv war. 7. Restart Tomcat /etc/init.d/tomcatx start Tomcat will recognize the war file and create a new subdirectory named opcv Stop Tomcat 9. Remove the old opcv directory (if it exists) rm rf opcv 10. You can confirm the proper subdirectory structure is in place by issuing: dir ensuring the correct subdirectories exist and those unneeded have been deleted. 11. Delete the war file rm opcv war 12. Rename the newly created war directory (this is done using the UNIX move command) 4

5 mv opcv opcv 13. Remove the customer s temporary work files rm rf../work/standalone/localhost/* 14. Remove the customer s old log files rm rf../logs/* 15. Restart Tomcat /etc/init.d/tomcatx start Use a browser to access and test the customer s opcv application. 5