||don't get the wrong idea about what you've found here
What appears below are my personal notes I wish
were part of my long-term memory but don't always seem to fit. I
strive for accuracy and clarity and appreciate feedback. If applying any of this information
anywhere, confirm for youself the correctness of your work as what
you see below might very well be, albeit unintentionally, incorrect
or misleading. These notes are here as an easy reference for
Information worthy of a more formal presentation
will appear elsewhere than this "Scratch" area. - ksb
KSB's DAQ-TEMPLATE deployment notes
Here are my notes about deploying the DAQ-TEMPLATE meta project
into jboss. Note that steps 5-7 are only necessary once per jboss
installation (to initialize the DB with the proper tables
and data) though repeating the steps shouldn't hurt anything.
- Assumed is that you are on a machine where bfd
and jboss are set up.
- Set up a new BFD workspace (not strictly necessary, but done here for simplicity):
ksb@killer[ksb]$ mkdir daq-template
ksb@killer[ksb]$ cd daq-template
ksb@killer[daq-template]$ bfd init /usr/local/icecube/tools
ksb@killer[daq-template]$ source setup.sh
- Check out the DAQ-TEMPLATE
meta-project, build it and set the default deployment directory:
ksb@killer[daq-template]$ bfd co -rV01-00-01 DAQ-TEMPLATE
ksb@killer[daq-template]$ ant lib.all
ksb@killer[daq-template]$ ant -DDEPLOYMENT=/usr/local/icecube/jboss/server/iceboss0/deploy defaultDeployment
- In a separate window, as the jboss user, start jboss:
ksb@killer[ksb]$ su - jboss
jboss@killer[icecube]$ source jboss/setup/setup-iceboss.sh
[jboss runs in the foreground...]
- Now, deploy daq-configuration project into jboss:
You should see that it copied daq-configuration.jar into the jboss deployment dir and jboss deploys it.
ksb@killer[daq-template]$ cd daq-configuration
ksb@killer[daq-configuration]$ ant deploy.jar
- Run the CreateAllBeans program in the
daq-initialization project to populate the DB. Note that this is run in the lib dir of
the workspace where the daq-initialization project was built):
This will produce errors in both the jboss logs and it's own output
about not being able to remove stuff. This is ok as it tries to
remove that which is it creating before creating it. To make sure
it ran correctly, run it again and you should see no
ksb@killer[daq-configuration]$ cd ../lib/
ksb@killer[lib]$ java -Djava.security.manager -cp daq-initialization.jar icecube.daq.initialization.CreateAllBeans
- Now, undeploy the daq-configuration project out of jboss:
You should see that it removed daq-configuration.jar from the jboss deployment dir and jboss undeployed it.
ksb@killer[lib]$ cd ../daq-configuration
ksb@killer[daq-configuration]$ ant undeploy.jar
- Finally, deploy the daq-template sar file into jboss:
You should see that it created and copied daq-template.sar
into the jboss deployment dir and jboss deployed it.
ksb@killer[daq-configuration]$ cd ..
ksb@killer[daq-template]$ ant -DSERVICE=daq-template -DXML=daqcontrol-template/daq-template-deploy.xml deploy.ws.service
You should now be able to hit the jboss console of your machine,
and see all the IceCubeDAQ mbeans.
Keith S. Beattie is
responsible for this document, located at
http://dst.lbl.gov/~ksb/Scratch/daq-template.html, which is subject
to LBNL's Privacy &
Security Notice, Copyright Status and Disclaimers.
Last Modified: Monday, 25-Feb-2013 16:57:57 PST