|
The provided TMX4J Sample Agent for Solaris consists of a unix daemon, an HTTP Adaptor, an RMI Connector, and a simple bootstrap service.
Before you start
tmx4j/ext/bin/solaris
directory).
The first is the set_tmx4j_home.sh, in which you need to set the TMX4J_HOME
variable (the TMX4J install directory), as well as the JAVA_HOME (the JDK
install directory). The second is the file jmxd.sh, in which you need to set
the EXECUTE_DIR and LOGGING. Without setting these correctly the daemon will
not run.'tmx4j/ext/bin/solaris'
to your system path for
convenience.A note on the Agent Classpath
If you follow these instructions for installing the Sample Agent, your existing system Classpath will be pre-pended with the neccessary TMX4J Classpath. However it must be noted that, once the daemon is running, additional changes to your
CLASSPATH
will not have any effect on the Agent Classpath. To force these changes, you need to stop and restart the daemon.
Startup
tmx4j/ext/bin/solaris
directory and type jmxd.sh
su <username> -c jmxd.sh
bootstrap.properties
file. Running
adaptor.properties
file.ps
-ef | grep jmxd
/etc/syslog.conf
). Your Unix administrator should ensure that the
following message types are handled: user.error and user.notice. The default
is not enabled, which logs daemon-related messages to stdout.jmx.properties
file).Stopping
jmxd
process should be shut down by sending a SIGTERM or SIGINT signal,
for example using the following sequence of commands: ps
-ef | grep jmxd
to get the jmxd process id (pid).
kill
<pid>
to shut down the daemon
|