-----------------------
Configuration/ Deployment Issues:
	1. mySQL Database on DrLucky 
	2. JBoss 3.0.4 w/ Tomcat 4.1.12 
	3. J2EE SDK 1.3.1 
	4. Java SDK 1.4.1_01 

Known Problems:
	1. user name should be <= 255 characters (not enforced)


-----------------------
Setup:

1. obtain the executables
	a. create a temp directory (TEMPDIR)   
	b. >cd TEMPDIR
	c. download the four zip files found in high_performance/build/release into the TEMPDIR


2. unzip the files in the temp directory 
	a. >unzip pq_ejb.zip          (will result in TEMPDIR/pqdeploy)
	b. >unzip pq_replication.zip  (will result in TEMPDIR/pqreplication)
	c. >unzip pq_ticker.zip       (will result in TEMPDIR/pqticker)
	d. >unzip pq_client.zip       (will result in TEMPDIR/pqclient)


3. make sure that JBOSS_HOME is set
	a. to use your own JBoss installation...
	   export JBOSS_HOME=<your installation path>/jboss-3.0.4_tomcat-4.1.12
	
	b. to use the team's JBoss installation...
	   export JBOSS_HOME=/afs/ece/class/ece841/public_html/team1/jboss-3.0.4_tomcat-4.1.12

   ** please make sure that JBOSS_HOME is either set in your .bashrc file
      or you set it in each terminal that you bring up. **
   
   
-----------------------
Installation:

1. install server(s)
	a. bring up a new terminal (ex: >xterm&)
	b. >cd TEMPDIR/pqticker
	c. >more serverlist.props

	   This will print out a list of hostnames that the server can be installed on.
	   It will look something like this:
               risk = 1
               trouble = 2
               scrabble = 3

	d. ssh to one of the machines listed (ex: >ssh risk)
	e. >cd TEMPDIR/pqdeploy
	f. >chmod +x installserver.sh
	g. >./installserver.sh

	To maintain a running view of the server output logs, 
	>cd /tmp
	>tail -f output.log

	Once the server has been started from the replication manager,
	this will continually update the terminal window with the server log.

(step 1 can be performed for each of the servers listed)


-----------------------
Run:

1. start the JNDI on drlucky
	***you can be logged in as anyone, provided you have set everything up properly***
	a. bring up a new terminal (ex: >xterm&)
	b. >ssh drlucky
	c. >cd $JBOSS_HOME/bin
	d. >./run.sh -c minimal

You should see the following:

looking for JAVA_HOME at /usr/local/j2sdk1.4.0
================================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /afs/ece/class/ece841/public_html/team1/jboss-3.0.4_tomcat-4.1.12

  JAVA: /usr/local/j2sdk1.4.0/bin/java

  JAVA_OPTS: -server -Dprogram.name=run.sh

  CLASSPATH: /afs/ece/class/ece841/public_html/team1/jboss-3.0.4_tomcat-4.1.12/b
in/run.jar:/usr/local/j2sdk1.4.0/lib/tools.jar

================================================================================

NUM_SERVERS = x3x
HOST_NAME = xdrluckyx
SERVER_NUM = xx

...

14:18:28,309 INFO  [Server] JBoss (MX MicroKernel) [3.0.4 Date:200211021607] Sta
rted in 0m:4s:262ms

****when you see the above, the JNDI has started****

2. start the replication manager
	*** This step MUST be done logged in as ksteppe***
	a. bring up a new terminal (ex:  >xterm&)
 	b. >ssh drlucky
	c. >cd TEMPDIR/pqreplication
	d. >chmod +x run-replication.sh
	e. >./run-replication.sh
	
	   Wait a few seconds, some exceptions will display and then the replication manager
	   will start all the servers.

You should end up seeing something like the following:

14:21:29,218 INFO  [ReplicationManager:trouble] built for trouble
14:21:29,264 INFO  [ReplicationManager:scrabble] built for scrabble
14:21:29,265 INFO  [ReplicationManager:risk] built for risk
Options:
1) Halt Replication Managers (includes global)
2) Shutdown everything (including replication managers, but not JNDI)
3) Shutdown all servers, leaving replication managers)
4) Shutdown one server:

There may be additional messages if the servers must be restarted.

3. start the ticker
	***For this step you can log in as anyone***
	a. bring up a new terminal (ex: >xterm&)
 	b. >ssh drlucky
	c. >cd TEMPDIR/pqticker
	d. >chmod +x run-ticker.sh
	e. >./run-ticker.sh

You should see the following:
looking for JAVA_HOME at /usr/local/j2sdk1.4.0
JAVA_HOME is set to /usr/local/j2sdk1.4.0
jbossall-client.jar log4j.jar ticker.jar
jbossall-client.jar
log4j.jar
ticker.jar
CLASSPATH=/afs/ece/usr/jkenlon/powerquotes/build/ticker/ticker.jar:/afs/ece/usr/
jkenlon/powerquotes/build/ticker/log4j.jar:/afs/ece/usr/jkenlon/powerquotes/buil
d/ticker/jbossall-client.jar:
BEANLIST = ejb/powerquotes/TickReceiver_3
BEANLIST = ejb/powerquotes/TickReceiver_2 ejb/powerquotes/TickReceiver_3
BEANLIST = ejb/powerquotes/TickReceiver_1 ejb/powerquotes/TickReceiver_2 ejb/pow
erquotes/TickReceiver_3
/usr/local/j2sdk1.4.0/bin/java -classpath /afs/ece/usr/jkenlon/powerquotes/build
/ticker/ticker.jar:/afs/ece/usr/jkenlon/powerquotes/build/ticker/log4j.jar:/afs/
ece/usr/jkenlon/powerquotes/build/ticker/jbossall-client.jar: powerquotes.datafe
ed.StockTicker 1000 1 stockinfo.props ejb/powerquotes/TickReceiver_1 ejb/powerqu
otes/TickReceiver_2 ejb/powerquotes/TickReceiver_3
14:25:50,029 INFO  [StockTicker] binding to ejb/powerquotes/TickReceiver_1
14:25:50,039 INFO  [StockTicker] binding to ejb/powerquotes/TickReceiver_2
14:25:50,040 INFO  [StockTicker] binding to ejb/powerquotes/TickReceiver_3
14:25:50,077 INFO  [StockTicker] ------------   Sending inital prices   --------
----
14:25:50,156 INFO  [StockTicker] ------------   Done sending inital prices   ---
---------

14:25:50,156 INFO  [StockTicker] ------------   Beginning to generate price upda
tes   ------------

4. start the client(s)
	***For this step you can log in as anyone***
	a. bring up a new terminal (ex: >xterm&)
	b. ssh to any of the ece machines (ex: >ssh candyland)
	c. >cd TEMPDIR/pqclient
	d. If you're running through telnet, make sure to set the DISPLAY value to your current machine
		>declare -x DISPLAY="oyurip:0.0"
	e. >chmod +x run-client-active.sh
	f. >./run-client-active.sh

At the terminal window, you should see the following output:


At this point the GUI or FrontEnd should come up, prompting you for a username.
	Type in a userName, and press enter or click "Submit"
	If you're a an existing user, you'll see the current prices of your selected stocks
	If you're a new user, you'll start with only stock choices, and no current pricing information
	
	To add more stocks to your existing update portfolio, 
		click on the AddStocks tab
		highlight the desired stocks and click on the AddStocks button (bottom left)
	To remove stocks from your existing update portfolio
		click on the RemoveStocks tab
		highlight the desired stocks to delete and click on the RemoveStocks button (bottom left)

To test the failover properties of the active-replication system, go to the Replication Manager terminal window.
		If the options are not displayed, press Enter to see the following:

Options:
1) Halt Replication Managers (includes global)
2) Shutdown everything (including replication managers, but not JNDI)
3) Shutdown all servers, leaving replication managers)
4) Shutdown one server:
		
		Choice 4 will allow you to crash-fault a server of your choice. 

------------------------
Reading logs

1. read server logs
	a. bring up a terminal on the server your interested in
	b. >cd /tmp
	c. log information is in 'pq.log'