APT ID Test Server Management
-----------------------------

1) Getting the Files you need to Test

/clotho/usr/loca/APT/Test is the directory where the
APT test server file are located.  You put the files
in this directory by FTP'ing them from your local work
area.   The files are  

APTIDServer.jar
Utilities.jar
activation.jar
ftp.jar
jconn2.jar
jdom.jar
mail.jar

Mostly you need to just copy the APTIDServer.jar and Utilities.jar
for your updates, because the others don't really get changed by
APT developers. 

If you are want to keep an existing .jar file currently installed in Test,
just rename the file to something like APTIDServer-old.jar before FTP'ing.

2) Stopping the test server

Use the ps command (ps -aef) to get a list of processes and make sure you see
enough of the command to distiguish the test server from the operational server.
Don't want to kill the wrong one.  Example below shows -Dapt.release=Test.  Make
sure you kill the process with this in the command

/clotho/usr/local/APT/jre1.5.0_07/bin/java -Dapt.release=Test -Dapt.database=Te

Simply use kill <process_id>

3) Starting the test server

Use the start_APTIDServer_test start command to start a new test server.  You will
be prompted for the SSTadmin password. Use the ps command to make sure the server
is running.  You don't need to do anything to the .log files.  The server takes care
of managing them.  Either appends or creates new ones if needed.

APT ID Operational Server Management
------------------------------------

1) Getting the files you need to Operational

The operational files are in /clotho/usr/local/APT.
Use the command install_APTIDServer.  This command will
copy the current operational files to the PreviousInstall 
directory and will copy the files from the Test directory
to the operational directory.


2) Stopping the operational server


Use the ps command (ps -aef) to get a list of processes and make sure you see
enough of the command to distiguish the test server from the operational server.
Don't want to kill the wrong one.  You should NOT see -Dapt.release=Test.


/clotho/usr/local/APT/jre1.5.0_07/bin/java  -jar APTIDServer.jar

Simply use kill <process_id>


3) Starting the operational server

Use the start_APTIDServer start command to start a new test server.  You will
be prompted for the SSTadmin password. Use the ps command to make sure the server
is running.  You don't need to do anything to the .log files.  The server takes care
of managing them.  Either appends or creates new ones if needed.


Java Version Management
-----------------------

To update to a new version of Java, you need
to download it yourself.  Create a new directory in 
/clotho/usr/local/APT/<java-version-dir>/ and install
the new version in your new directory.

Update the start_APTIDServer_test and start_APTIDServer scripts
to use the new version of java.  You should update the test script
first and restart the test server for testing.  After testing is
complete, update the operational script and restart the operational server.


Backing out an operational Install
----------------------------------

The PreviousInstallation directory should have the last
operational files in it. You need to get those files back
into /clotho/usr/local/APT/ and follow the operational server
start up procedures.  Running the installAPTServer script does
not make sense in this case since you will be backing out the
the operational install.


Logs
----

There are a number of logs written out to the working directory by the server. Some
self explanatory, others are perhaps not:

start_aptserver[_test].log    stdout from the startup script and server
APT [Test] ID Server.log      incoming ID requests and the ID returned
Address_Server.log            incoming address lookup requests and number returned       
MOSS_Server.log               includes full MOSS output for each request
Status_Server.log             only contains errors right now
Phase<n>[Test]Server.log      submission server logs, named before all the others were added

Note that the logs generally contain dumps for any exceptions thrown.

Directory Structure
-------------------

There are aa few more required files and directories:

Files:

APT [Test] ID Server.ID       contains the next ID to be given out on request
Phase<n>[Test]Server.counter  contains the submission counts by proposal ID

Directory:

mossfiles                     working directory for MOSS, contains all input and output