Submission Daemon Management ---------------------------- This document describes the configuration and deployment of the Phase I and Phase II submission daemons, which are both within the SubmissionDaemon APT subsystem. Phase I ------- The Phase I daemon is run as an end user GUI application due to the need for human interaction in the submission process. The application bundle is built as part of the ant delivery process as the Mac OS X app: Submission Daemon. After running: > ant deliver the Submission Daemon can be found in APT/bin. Deployment is as simple as sending (often via email) the application to Brett Black (blacker@stsci.edu) and Rob Douglas (rdouglas@stsci) for them to install on their machines. Obviously it can sent to whoever else wants a copy, or can be run directly from the build location. Phase II -------- The Phase II submission daemon runs via two crons as test and operational. Currently the crons run on harry.stsci.edu. The test version of the daemon which processes test phase II submissions runs on harry via a cron on the tphase2p account. The operational version runs on harry via a cron on the phase2p account. This machine is behind the firewall so working with the phase II submission daemon first requires you to have access to hrry.stsci.edu which is on the cerberus cluster. Assuming you have access to harry the next requirement is that you have permission to access tphase2p and phase2p via sudo: > sudo su - phase2p > sudo su - tphase2p This gives you access to that account using your own password. You can check on the setup of the crons using: > crontab -l which will list the current cron table for the current user. If you are not familiar with the format of the crontab read the man page for crontab: > man crontab Deployment of the test phase II daemon should be done by ftping the necessary files to the deployment machine. The test code is in: /home/tphase2p/phase-2/code/apt/ Operational deployment should be done by copying the tested code to: /home/phase2p/phase-2/code/apt/ Currently the phase II submission daemon consists of the following jar files: activation.jar APTIDServer.jar ftp.jar jax-qname.jar jaxb-api.jar jaxb-impl.jar jaxb-libs.jar jaxb-xjc.jar jaxb1-impl.jar jconn2.jar jdom.jar mail.jar namespace.jar relaxngDatatype.jar SubmissionDaemon.jar Utilities.jar We should really pare this down if possible. The ant deliver target copies the needed jar files to APT/bin/Submission Daemon.app/Contents/Resources/Java/. All the jars in that directory should be copied to the deployment machine (bundling them up recommended :).