mirror of https://github.com/sipwise/heartbeat.git
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
5 years ago | |
|---|---|---|
| .. | ||
| Makefile.am | 15 years ago | |
| README | 15 years ago | |
| dummy.c | 15 years ago | |
| ha_mgmt_client.c | 15 years ago | |
| ha_mgmt_client.h | 15 years ago | |
| ha_mgmt_client.i | 15 years ago | |
| ha_mgmt_client_wrap.c | 15 years ago | |
| ha_tsa_common.c | 15 years ago | |
| ha_tsa_common.h | 15 years ago | |
| linuxha-adapter.in | 15 years ago | |
| testrun.sh.in | 15 years ago | |
| tsa_eventd.c | 15 years ago | |
| tsa_hacli.c | 15 years ago | |
README
linux-ha plugin for TSA README
1. REQUIREMENTS
Compiling the TSA plugin requires various software packages.
First of all you need to install the Java SDK software. You also
need the TSA software including the rsct, sam and sam.adapter.
Although in theory the plugin only depends on the sam.adapter,
not installing the sam package will prevent you from installing
the sam.adapter package due to the dependency between the
sam.adater RPM and the sam RPM. Therefor you might have to
install all of them.
The SWIG is also used to generate the interface files at the
compling time.
Running the TSA plugin requires the Java runtime environment
and the sam.adapater package.
2. COMPILING THE PLUGIN
To build the TSA plugin, apply the --enable-tsa-plugin option:
./ConfigureMe bootstrap --enable-tsa-plugin=yes
Options --with-java-home and --with-tsa-dir and optional. The
--with-java-home option specifies the Java sdk directory and the
--with-tsa-dir option specifies the TSA directory. If they are not
presented, the configuration will try to find the Java sdk directory
and set the TSA directory to /opt/IBM/tsamp. By default, the TSA
software is installed to /opt/IBM/tsamp. So usually you don't need
the --with-tsa-dir option but you often need to present the
--with-java-home option.
For example:
./ConfigureMe bootstrap --enable-tsa-plugin=yes \
--with-java-home=/opt/IBMJava2-141
3. CONFIGURATION
First, you need to add the apiauth directives as follows to
the ha.cf to allow the plugin to sign on to heartbeat:
apiauth tsa uid=root gid=root
apiauth tsad uid=root gid=root
Besides, you need to edit the plugin config file:
/etc/opt/IBM/tsamp/sam/cfg/sam.adapter.plugin.properties
and set the value of plugin-impl-class to
org.linuxha.sam.plugin.LinuxHAPlugin. For example:
plugin-impl-class = org.linuxha.sam.plugin.LinuxHAPlugin
This tells the adapater to use the linux-ha plugin.
4. START AND STOP THE PLUGIN
To start the plugin:
/usr/lib/heartbeat/linuxha-adapter start
This will start the tsa_eventd and the adapter in order.
To stop the plugin:
/usr/lib/heartbeat/linuxha-adapter stop
This will stop the adapter and the tsa_eventd in order.
Notice: linuxha-adapter is modified and simplified from
the sam adapter script /usr/bin/samadapter.
If linuxha-adapter does not work. You may want to try
the original one:
cp /usr/bin/samadapter /usr/bin/linuxha-samadapter
then edit /usr/bin/linuxha-samadapter and append
":$plib/linuxhafla.jar" to the end of line 365. This tells
the adapter to load the linux-ha plugin when it starts.
You should start or stop the tsa_eventd manually if
you use the original samadapter.