Administering DataTurbine
This assumes that DataTurbine has been deployed as described in the FAQ.
- The DataTurbine server program is contained in the executable Java Archive (jar),
${RBNB_HOME}/bin/rbnb.jar.
Invocations of this program take the form:
java -jar ${RBNB_HOME}/bin/rbnb.jar
(in Windows terminal, it's java -jar %RBNB_HOME%\bin\rbnb.jar)
with command-line arguments:
-a {server address - [host][:port]}
-A {security file URL}
-D {mask},{level}
-F
-H {archive home directory}
-l [{log period (millis)}][,{log cache frames}][,[{log cache frames}][,[{log archive frames}][,[{log archive mode}]]]]
-L
-m [{metrics period (millis)}][,[{metrics cache frames}][,[{metrics archive frames}][,[{metrics archive mode}]]]]
-M {maximum activity threads}
-n {server name}
-O {options file URL}
-p {parent server address}
-P [{userid}][,{password}]
-s {shortcut name},{remote address},[{cost}]
-S {maximum open filesets}
SOFTWARE ADMINISTRATION
- Select filesystem locations where the DataTurbine server is to maintain its disk archive and log. These locations will be referred to as RBNB_ARCHIVE and RBNB_LOG, respectively, from this point on. The preparation of convenience scripts to control the server is highly recommended. Some examples are at the end of this article.
- DataTurbgine ships with an administration utility, ${RBNB_HOME}/bin/admin.jar. When connected to a DataTurbine server, it displays a list of all entities available from that server. This is handy as a very basic verification of the presence of sources and channels. It also provides actions via a right-click menu popup. Some particularly useful features are:
- Terminate - removes a source from the servers cache and commits its data to the disk archive (if there is one).
- Load Archive - loads the disk archive from an inactive source into the cache. This requires prior knowledge of the archive's name.
EXAMPLES
- Linux (make a file called rbnb; this is a proper /etc/init.d script)
#!/bin/bash
#
# Init script for the RBNB server
#
# chkconfig: 345 98 98
# description: Start the RBNB server
#
# Megabytes to use for the JVM running RBNB
RBNB_MEM='512'
RBNB_ARCHIVE='/var/rbnb_archive'
RBNB_LOG ='/var/log/rbnb.log'
RBNB_PIDFILE='/var/run/rbnb.pid'
start() {
mkdir -p ${RBNB_ARCHIVE}
java -Xmx${RBNB_MEM}M -jar ${RBNB_HOME}/bin/rbnb.jar -n dataturbine -L -H ${RBNB_ARCHIVE} > /var/log/rbnb.log 2>&1 &
echo $! > ${RBNB_PIDFILE}
}
stop() {
kill `cat ${RBNB_PIDFILE}`
rm -f ${RBNB_PIDFILE}
}
case "$1" in
'start')
echo "Starting the RBNB server"
start
;;
'stop')
echo "Stopping the RBNB server"
stop
;;
'restart')
echo "Restarting the RBNB server"
stop
start
;;
*)
echo "Usage: ${0} {start|stop|restart} "
;;
esac
- Windows (make a file called rbnb.bat)
set RBNB_ARCHIVE=C:\\rbnb_archive
set RBNB_LOG=rbnb.log
mkdir %RBNB_ARCHIVE%
java -jar %RBNB_HOME%\\bin\\rbnb.jar -L -H %RBNB_ARCHIVE% -n "dataturbine" >> %RBNB_LOG% 2>&1
An Enerprise Service Bus
An Enerprise Service Bus (ESB) free scripts provides an modular and standards-based integration environment that spans well beyond the reach of cheap web hosting tradition hub-and-spoke architecture and provides a clean separation of application logic and integration services and enables agile SOA-based service development, deployment, and dedicated servers testing. GlassFish Enterprise Service Bus (ESB) is a lightweight and agile ESB platform with in-built functionality for clustering, load balancing and high availability for mission critical enterprise free web hosting1. GlassFish is open source with an option for commercial support from Sun.