www.it-ebooks.info

Oracle Tuxedo Joining the Exalogic Family
Start/stop tux_msgq_monitor
As we just discussed, tux_msgq_monitor should be started before booting the Oracle
Tuxedo application. The tux_msgq_monitor function is responsible for starting
Msgq_daemon and checking its running status. Before starting tux_msgq_monitor,
ensure that the environment variables TUXCONFIG, LD_LIBRARY_PATH, and TUXDIR
are properly set. If Msgg_daemon terminates abnormally for some reason or other, it
restarts using tux_msgq_monitor. One monitor can only serve one Oracle Tuxedo
application on one logical machine.
Start tux_msgq_monitor
The following command is an example to start tux_msgq_monitor:
Prompt> tux_msgq_monitor -i -d -M -K < key>
The following are the attributes of this command:
• -i – This IPoIB address should be equal to the RDMADAEMONIP parameter in in
the UBBCONFIG file.
• -d – This port number should be the same number as that mentioned in
RDMADAEMONPORT in the UBBCONFIG file.
• -M – The shared memory gets allocated as you start Msgq_daemon. So, it is
very important for you to estimate the size of the shared memory. You can
get the memory size by using tmloadcf -c ubb.
• -K – This is the key number to access the shared memory by Msgq_daemon.
When tux_msgq_monitor is running, you should check and make sure that the tux_
msgq_monitor and Msgq_daemon processes are running. After starting tux_msgq_
monitor successfully, you can boot the Tuxedo application.
You can also use a shell script that helps you start all the processes in the master
node, that is, tux_msgq_monitor and a Tuxedo application. Please make sure
that the environment variables TUXCONFIG, LD_LIBRARY_PATH, and APPDIR are
set properly before you run this command. So, to be very specific, the following
script starts up tux_msgq_monitor, executes tmboot to start the Oracle Tuxedo
application, and starts tlisten if the option -l is specified:
Prompt> tmboot.sh –i daemon_ip –d daemon_port –M shm_size –K shm_key
[-l nlsaddr]
[ 134 ]
www.it-ebooks.info