Installation document for My Messages
From PTAGISWiki
Installation Document
PTAGIS MyMessages Module and Redesigned Notifications
Contents |
New/Changed Functionality
2007-11-14a: nagym
- Implemented the MyMessages functionality
- Redesigned/implemented the report Notifications
Installation instructions:
2007-11-14a:
Set up the corresponding database:
- create table wqb_message (with the right schema, detailed in the design doc)
Deploy the code
- unzip the package in a temporary place
- copy the new and modified files from the zip package
- delete the files no longer in use
Redeploy the ptagis and sree webapps to make the changes to properties visible
Convert the report tasks from the old to the new format (i.e. convert schedule.xml)
As you convert tasks with the web based convertTasks.jsp please ensure that you convert the standard users' tasks first, and then the admin user's tasks last. The reason for this is that 1. the convertTasks logic sets the converted task's ownership to the user whose tasks are processed 2. the admin user has admin access, and all the reports show up under his account As a result, if the admin user is selected for processing before some other standard users are processed, then all those converted tasks will be owned by the admin user. To prevent this, please convert the tasks of the standard users first (e.g. select all users, but de-select admin), and the admin user last.
- backup the schedule.xml and schedule-action.xml from ptagis-1.0\web\sree\WEB-INF\classes
- launch a browser, access the ptagis web site and log in as a user in the "PTAGIS Administrators" group
- navigate to the My Queries area, then change the url to point to http://<machine>/sree/test/convertTasks.jsp
- select all/some users, check convert tasks, check test only, then click execute to test what would be done
- selecting all users but the admin user results in a "Request-URI Too Large" error
- hit the back button
- select all/some users, check convert tasks, uncheck test only, then click execute to test to make the changes
- I selected all the uppercase usernames first (started 9:44, finished 9:50)
- by 10:15 I had completed users through gzydlewski
- but the converter crashed at user dean
- crashed again on user kinzer
- when it crashes, the converter fails to print a final Done. This happens in test or non-test mode, so testing is a good indicator if it will work.
- by 10:33 I had completed users through murdoch
- crashed on user public
- crashed on user streamnet
- completed all users by 11:05 so it took about 1 hour to do them all
- users that still need to be converted: admin, dean, kinzer, public, streamnet
- repeat as needed to process all the users
If problems are encontered the old tasks may be restored by stopping the web server and the scheduler, replacing the scheduler xml files backed up in the first step, then restarting the server
Test instructions:
2007-11-14a:
Test MyMessages
- log in and visit the My MyMesages area
- verify that MyMyMesages brings up the message list
- verify the display/message when no files are present
- add a message through the command line interface
cd /dsk2/ptagis-1.0
bin/run.sh db.MyMessages web/ptagis/WEB-INF/db.properties createMessage <rcpt> <sender> <title> <msg>
bin/run.sh db.MyMessages web/ptagis/WEB-INF/db.properties getMessages <rcpt> <sortBy> <sortDir>
e.g.
bin/run.sh db.MyMessages web/ptagis/WEB-INF/db.properties getMessages nagym
bin/run.sh db.MyMessages web/ptagis/WEB-INF/db.properties createMessage nagym "Sys Admin" "test 01" "this is a test message."
- verify that MyMyMesages show up properly
- verify that the message list can be sorted by clicking on the headers
- exercise the functions and verify that all work properly
- view, delete, multi-item delete
Test report execution notifications
- navigate to the MyQueries area
- select a query (create one if needed) and click Run
- verify that ptagis-1.0/logs/scheduler.log shows a line appended indicating the start of the execution with the sql query
- verify that same log file will display a message about the completion of the report execution
- navigate to the MyMessages area and verify that a message about the report completion has been received
- repeat a similar test with a scheduled report execution
- can also verify through the sree EnterpriseManager that 2 related tasks has been created
- can also verify through the sree EnterpriseManager that the 2 tasks are deleted when the report is deleted
- repeat a similar test with a report template in the My Report Templates area
File List:
(A=added, M=modified, D=deleted) > ptagis-1.0: A src\db\MyMessages.java A src\util\NotificationAction.java M src\util\ReportHelper.java D src\util\SendMyMessage.java A web\ptagis\home\mymessages\action.jsp A web\ptagis\home\mymessages\display.jsp A web\ptagis\home\mymessages\list.jsp A web\ptagis\home\mymessages\status.jsp M web\ptagis\nav.jsp M web\ptagis\WEB-INF\log4j.properties M web\ptagis\WEB-INF\ptagis.properties A web\ptagis\WEB-INF\classes\db\MyMessages.class M web\sree\myreporttemplates.jsp M web\sree\myrpttempaction.jsp M web\sree\runquery.jsp M web\sree\schaction.jsp M web\sree\schedule.jsp M web\sree\scheduleHelper.jspx M web\sree\qb\queryList.jsp A web\sree\test\convertTasks.jsp A web\sree\WEB-INF\log4j.properties M web\sree\WEB-INF\sr.properties M web\sree\WEB-INF\web.xml A web\sree\WEB-INF\classes\util\NotificationAction.class A web\sree\WEB-INF\classes\util\ReportHelper.class A web\sree\WEB-INF\classes\util\ReportHelperException.class
