Difference between revisions of "Install xpl hub"
(→Test the hub) |
(→Install the hub) |
||
| Line 16: | Line 16: | ||
and I place the files in <code>/home/control/Documents/Controls</code> on a Linux machine | and I place the files in <code>/home/control/Documents/Controls</code> on a Linux machine | ||
or in <code>/Users/control/Documents/Controls</code> on a Mac. | or in <code>/Users/control/Documents/Controls</code> on a Mac. | ||
| + | |||
| + | Obviously, if you place the scripts in a different location than mine, | ||
| + | you will have to adapt the path everywhere it is given here. | ||
Extract it: | Extract it: | ||
Revision as of 13:02, 16 March 2014
My xPL hub is based on John Bent's xPL ToolKit for Perl.
Install the hub
Download the tarball. It contains:
-
xpl-hub.pl: the hub -
xpl-monitor.pl: a monitor which allows to view the xPL messages -
xpl-send.pl: a utility for sending xPL messages -
xPL: a directory containing Perl functions common to all the scripts
Move it to the location you want the scripts to reside.
This could be /opt/xPL or /usr/opt/xPL.
I personally create a control user who will run these scripts
and I place the files in /home/control/Documents/Controls on a Linux machine
or in /Users/control/Documents/Controls on a Mac.
Obviously, if you place the scripts in a different location than mine, you will have to adapt the path everywhere it is given here.
Extract it:
tar -xvjpf xPL_base.tar.bz2
Test the hub
Lanch the hub:
su control /home/control/Documents/Controls/xpl-hub.pl -v
Monitor xPL messages: open a second terminal window and:
su control /home/control/Documents/Controls/xpl-monitor.pl -v
Send a message: open a third terminal window and:
/home/control/Documents/Controls/xpl-send.pl -vc hbeat.end world=hello
You should see the corresponding world=hello message in the second terminal window.
If it works, stop all the running xPL scripts.
